System information transmission method and apparatus

Abstract

A system information transmission method and apparatus. The method comprises: receiving system information in a first cell, wherein the system information comprises first adjacent carrier frequency information corresponding to a second cell, the first adjacent carrier frequency information indicates a first ARFCN and first information, the first information indicates a network type of the second cell corresponding to the first adjacent carrier frequency information, and the carrier frequency of the second cell is different from the carrier frequency of the first cell; and when the network type indicated by the first information is not supported, not receiving an SSB of the second cell on the basis of the first ARFCN. A network type of a second cell is indicated by means of first information in first adjacent carrier frequency information, so that a terminal device can determine the network type of the second cell on the basis of the first information, and can thus determine whether to receive SSBs of the second cell on the basis of the first adjacent carrier frequency information, thereby standardizing the behavior of the terminal device and improving the system compatibility.

Description

System information transmission method and device

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of the People's Republic of China on February 8, 2024, with application number 202410178290.2 and invention name "A System Information Transmission Method and Device", the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application relates to the field of communication technology, and in particular to a system information transmission method and device. Background Art

[0004] The 3rd Generation Partnership Project (3GPP) is discussing the introduction of narrowband new radio (NB-NR) in the new radio (NR) system. The main application scenarios of NB-NR are some private network scenarios, such as railway mobile radio networks, or public protection and disaster relief (PPDR) scenarios. In NB-NR, terminal equipment can operate in a narrowband dedicated spectrum network with a bandwidth of less than 5MHz, which is referred to as a private network below. Due to the limited frequency domain resources of the private network, there is no available synchronization grid on some frequency bands of the private network, so the synchronization grid in the private network scenario is redefined. Among them, the synchronization grid can be understood as the candidate frequency position for the network to send the synchronization signal broadcast channel block (synchronous signal / physical broadcast channel block, SS / PBCH block, SSB), and it is aligned with the center subcarrier of the SSB.

[0005] There are two ways for the terminal device to detect the SSB transmission position. One is to detect the SSB by searching the synchronization grid, and the other is to receive the SSB through the adjacent frequency carrier frequency information in the system information block (SIB) 4 sent by the neighboring cell.

[0006] As mobile communication systems evolve, the information in SIB4 will also change. For example, in private network scenarios, SIB4 may carry information about adjacent carrier frequencies corresponding to the private network cell. This newly added information may not be recognized by terminal devices that do not support private networks. Therefore, as mobile communication systems evolve, how to minimize the impact of system information changes on terminal devices and improve system compatibility is an urgent issue to be addressed. Summary of the Invention

[0007] The present application provides a system information transmission method and apparatus to reduce the impact of changes in system information on terminal devices and improve system compatibility.

[0008] In the first aspect, the present application provides a system information transmission method, the execution subject of the method is a terminal device or a module or chip on the terminal device side, and the terminal device is used as the execution subject for description. The method includes: receiving system information in a first cell; the system information includes first adjacent frequency carrier frequency information corresponding to a second cell, the first adjacent frequency carrier frequency information indicates a first absolute radio frequency channel number ARFCN and first information, the first information indicates the network type of the second cell corresponding to the first adjacent frequency carrier frequency information; the carrier frequency of the second cell is different from the carrier frequency of the first cell; the network type indicated by the first information is not supported, and the synchronization signal broadcast channel block SSB of the second cell is not received according to the first ARFCN; or, the network type indicated by the first information is supported, and the synchronization signal broadcast channel block SSB of the second cell is received according to the first ARFCN.

[0009] In the above scheme, the network type of the second cell is indicated by the first information in the first adjacent carrier frequency information, so that the terminal device can determine the network type of the second cell based on the first information, thereby enabling the terminal device to determine whether to receive the SSB of the second cell based on the first adjacent carrier frequency information, standardizing the behavior of the terminal device and improving system compatibility.

[0010] In one implementation, the first information is the subcarrier spacing indicated by the first adjacent carrier frequency information; if the first subcarrier spacing indicated by the first adjacent carrier frequency information is not equal to the second subcarrier spacing, the network type indicated by the first information is a private network, and the second subcarrier spacing matches the first frequency band number associated with the first ARFCN.

[0011] In the above scheme, by reusing the existing subcarrier spacing field as the first information, the terminal device can distinguish the adjacent frequency carrier frequency information of different types of networks through the subcarrier spacing field without changing the existing system information, thereby improving system compatibility.

[0012] In one implementation, the first information is the subcarrier spacing indicated by the first adjacent carrier frequency information; if the first subcarrier spacing indicated by the first adjacent carrier frequency information is equal to the second subcarrier spacing, then the network type indicated by the first information is a broadband network, and the second subcarrier spacing matches the first frequency band number associated with the first ARFCN.

[0013] In one implementation, the second subcarrier spacing is 15 kHz.

[0014] In one implementation, the first subcarrier spacing is 30 kHz.

[0015] In one implementation, the first frequency band number associated with the first ARFCN is any one of the following frequency band numbers: n26; n28; n85; n100; n106.

[0016] On the second aspect, the present application provides a system information transmission method, the execution subject of the method is a network device or a module or chip on the network device side, and the network device is used as the execution subject for description. The method includes: determining system information; the system information includes first adjacent frequency carrier frequency information corresponding to the second cell, the first adjacent frequency carrier frequency information indicates a first absolute radio frequency channel number ARFCN and first information, the first information indicates the network type of the second cell corresponding to the first adjacent frequency carrier frequency information; sending the system information in the first cell; the carrier frequency of the second cell is different from the carrier frequency of the first cell.

[0017] In one implementation, the first information is the subcarrier spacing indicated by the first adjacent carrier frequency information; if the first subcarrier spacing indicated by the first adjacent carrier frequency information is not equal to the second subcarrier spacing, the network type indicated by the first information is a private network, and the second subcarrier spacing matches the first frequency band number associated with the first ARFCN.

[0018] In one implementation, the first information is the subcarrier spacing indicated by the first adjacent carrier frequency information; if the first subcarrier spacing indicated by the first adjacent carrier frequency information is equal to the second subcarrier spacing, then the network type indicated by the first information is a broadband network, and the second subcarrier spacing matches the first frequency band number associated with the first ARFCN.

[0019] On the third aspect, the present application provides a system information transmission method, the execution subject of the method is a network device or a module or chip on the network device side, and the network device is used as the execution subject for description. The method includes: determining system information; the system information includes adjacent frequency carrier list information and private network adjacent frequency carrier list information, the adjacent frequency carrier list information is used to indicate the carrier frequency information of the broadband network cell, and the private network adjacent frequency carrier list information is used to indicate the carrier frequency information of the private network cell; the value of the adjacent frequency carrier list information is an invalid value; and the system information is sent in the first cell.

[0020] In the above scheme, by setting the value of the adjacent frequency carrier list information to an invalid value, the terminal equipment that supports the broadband network cannot determine the valid frequency carrier information based on the adjacent frequency carrier list information, ensuring that the adjacent frequency carrier list information carried in the system information will not affect the terminal equipment, thereby improving system compatibility.

[0021] In one implementation, the value of the adjacent frequency carrier list information is an invalid value, including: the value of the adjacent frequency carrier list information is the same as the value of the private network adjacent frequency carrier list information.

[0022] In one implementation, the value of the adjacent frequency carrier list information being an invalid value includes: the value of the adjacent frequency carrier list information being a preset value.

[0023] In one implementation, the preset value is independent of the carrier frequency information of the broadband network cell. For example, the preset value is 0.

[0024] In a fourth aspect, the present application provides a system information transmission method, the execution subject of the method is a terminal device or a module or chip on the terminal device side, and the terminal device is used as an example for description. The method includes: receiving system information in a first cell; the system information includes adjacent frequency carrier list information and private network adjacent frequency carrier list information, the adjacent frequency carrier list information is used to indicate the carrier frequency information of the broadband network cell, and the private network adjacent frequency carrier list information is used to indicate the carrier frequency information of the private network cell; the value of the adjacent frequency carrier list information is an invalid value; not receiving the synchronization signal broadcast channel block SSB according to the adjacent frequency carrier list information; or, receiving the SSB according to the private network adjacent frequency carrier list information.

[0025] In one implementation, the value of the adjacent frequency carrier list information is an invalid value, including: the value of the adjacent frequency carrier list information is the same as the value of the private network adjacent frequency carrier list information.

[0026] In one implementation, the value of the adjacent frequency carrier list information is an invalid value, including: the value of the adjacent frequency carrier list information is a preset value.

[0027] In one implementation, the preset value is independent of the carrier frequency information of the broadband network cell.

[0028] In a fifth aspect, the present application provides a system information transmission method, the execution subject of which is a terminal device or a module or chip on the terminal device side. Here, the terminal device is used as the execution subject for example for description. The method includes: receiving system information in a first cell; the system information includes first adjacent carrier frequency information corresponding to a second cell, and the first adjacent carrier frequency information indicates a first frequency band number; the carrier frequency of the second cell is different from the carrier frequency of the first cell; the first frequency band number is different from any one of the following frequency band numbers: n1, n2, n3, n5, n7, n8, n12, n20, n25, n28, n34, n38, n39, n40, n41, n50, n51, n66, n70, n71, n74, n75, n76, n77, n78, n79, n80, n81, n82, n83, n84, n86, n257, n258, n260, n261; and not receiving a synchronization signal broadcast channel block SSB of the second cell.

[0029] In the above scheme, for the private network cell, the first frequency band number indicated by the first adjacent carrier frequency information is the frequency band number mapped by the second frequency band number. The terminal device that does not support the private network cannot identify the association between the first frequency band number and the first ARFCN, and thus does not receive the SSB of the second cell according to the first adjacent carrier frequency information, which standardizes the behavior of the terminal device and improves system compatibility.

[0030] In one implementation, the second cell is a private network cell.

[0031] In one implementation, there is a mapping relationship between the first frequency band number and the second frequency band number; the second frequency band number is a frequency band number corresponding to the new radio interface NR working frequency band.

[0032] In one implementation, the first adjacent carrier frequency information further indicates a first absolute radio frequency channel number ARFCN; the first ARFCN is associated with a second frequency band number.

[0033] In one implementation, the mapping relationship satisfies: the first frequency band number is equal to the second frequency band number plus X, where X is a number greater than 0.

[0034] In one implementation, the method is applicable to a first terminal device side;

[0035] The transmission bandwidth of the control resource set CORESET#0 supported by the first terminal device is greater than the bandwidth of the private network.

[0036] In one implementation, the bandwidth of the private network is the transmission bandwidth of CORESET#0 of the private network.

[0037] In one implementation, the bandwidth of the private network is 12PRB, 15PRB, or 20PRB.

[0038] In a sixth aspect, the present application provides a system information transmission method, the execution subject of which is a terminal device or a module or chip on the terminal device side. Here, the terminal device is used as the execution subject for example for description. The method includes: receiving system information in a first cell; the system information includes first adjacent carrier frequency information corresponding to a second cell, the first adjacent carrier frequency information indicating a first frequency band number and a first absolute radio frequency channel number (ARFCN); the carrier frequency of the second cell is different from the carrier frequency of the first cell; the first frequency band number is different from any one of the following frequency band numbers: n1, n2, n3, n5, n7, n8, n12, n20, n25, n28, n34, n38, n39, n40, n41, n50, n51, n66, n70, n71, n74, n75, n76, n77, n78, n79, n80, n81, n82, n83, n84, n86, n257, n258, n260, n261; and receiving a synchronization signal broadcast channel block (SSB) of the second cell according to the first adjacent carrier frequency information.

[0039] In one implementation, the second cell is a private network cell.

[0040] In one implementation, there is a mapping relationship between the first frequency band number and the second frequency band number; the second frequency band number is any one of the following frequency band numbers: n26; n28; n85; n100; n106.

[0041] In one implementation, the first adjacent carrier frequency information further indicates a first ARFCN; the first ARFCN is associated with the second frequency band number.

[0042] In one implementation, the mapping relationship satisfies: the first frequency band number is equal to the second frequency band number plus X, where X is a number greater than 0.

[0043] In one implementation, the method is applicable to the second terminal device side; the transmission bandwidth size of the control resource set CORESET#0 supported by the second terminal device is 12PRB or 15PRB or 20PRB.

[0044] In the seventh aspect, the present application provides a system information transmission method, the execution subject of the method is a network device or a module or chip on the network device side, and the network device is used as an example for description here. The method includes: determining system information; the system information includes first adjacent carrier frequency information corresponding to a second cell, the first adjacent carrier frequency information indicating a first frequency band number and a first absolute radio frequency channel number (ARFCN); a mapping relationship exists between the first frequency band number and the second frequency band number; the first frequency band number is different from any one of the following frequency band numbers, and the first frequency band number is any one of the following frequency band numbers: n1, n2, n3, n5, n7, n8, n12, n20, n25, n28, n34, n38, n39, n40, n41, n50, n51, n66, n70, n71, n74, n75, n76, n77, n78, n79, n80, n81, n82, n83, n84, n86, n257, n258, n260, n261; sending the system information in the first cell, the carrier frequency of the second cell is different from the carrier frequency of the first cell.

[0045] In one implementation, the second cell is a private network cell.

[0046] In one implementation, there is a mapping relationship between the first frequency band number and the second frequency band number; the second frequency band number is any one of the following frequency band numbers: n26; n28; n85; n100; n106.

[0047] In one implementation, the first adjacent carrier frequency information further indicates a first absolute radio frequency channel number ARFCN; the first ARFCN is associated with a second frequency band number.

[0048] In one implementation, the mapping relationship satisfies: the first frequency band number is equal to the second frequency band number plus X, where X is a number greater than 0.

[0049] In one implementation, the method is applicable to the second terminal device side; the transmission bandwidth size of the control resource set CORESET#0 supported by the second terminal device is 12PRB or 15PRB or 20PRB.

[0050] In an eighth aspect, the present application further provides a communication device capable of implementing any of the methods provided in any of the first to seventh aspects. The communication device can be implemented in hardware or by hardware executing corresponding software implementations. The hardware or software includes one or more units or modules corresponding to the above-mentioned functions.

[0051] In one possible implementation, the communication device includes a processor configured to support the communication device in executing the corresponding functions of the network device or terminal device in the above-described method. The communication device may also include a memory, which may be coupled to the processor and stores program instructions and data necessary for the communication device. Optionally, the communication device also includes an interface circuit for supporting communication between the communication device and a device such as a terminal device.

[0052] In one possible implementation, the communication device includes corresponding functional modules for implementing the steps in the above method. The functions can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0053] In one possible implementation, the structure of the communication device includes a processing unit and a communication unit, which can perform the corresponding functions in the above method examples. For details, please refer to the description of the method provided in any one of the first to seventh aspects, which will not be repeated here.

[0054] In a ninth aspect, a communication device is provided, comprising a processor and an interface circuit, wherein the interface circuit is configured to receive signals from a communication device other than the communication device and transmit the signals to the processor, or to transmit the signals from the processor to the communication device other than the communication device, wherein the processor implements the functional modules of the method in any possible implementation of any of the first to seventh aspects through logic circuits or by executing computer programs or instructions. Optionally, the communication device further comprises a memory configured to store the computer program or instructions.

[0055] In the tenth aspect, a computer-readable storage medium is provided, which stores a computer program or instruction. When the computer program or instruction is executed by a processor, the method in any possible implementation of any aspect from the first to the seventh aspect is implemented.

[0056] In the eleventh aspect, a computer program product storing instructions is provided, which, when read and executed by a computer, implements the method in any possible implementation of any one of the first to seventh aspects.

[0057] In a twelfth aspect, a circuit is provided for executing the method in any possible implementation of any one of the first to seventh aspects, wherein the circuit may include a chip circuit. Optionally, the circuit may also be coupled to a memory.

[0058] In a thirteenth aspect, a chip is provided, comprising a processor. When the processor executes a computer program or instruction, the processor is configured to implement the method of any possible implementation of any of the first to seventh aspects. Optionally, the chip may further include a memory. The chip may be composed of a single chip or may include a chip and other discrete components.

[0059] In the fourteenth aspect, a communication device is provided, comprising a processor, which implements the method in any possible implementation of any one of the first to seventh aspects through a logic circuit or executing a computer program or instruction.

[0060] In a fifteenth aspect, a communication device is provided, comprising a unit or module for executing the method in any possible implementation of any one of the first to seventh aspects.

[0061] In the sixteenth aspect, an embodiment of the present application further provides a communication system. The communication system includes: a terminal device for implementing the method in the aforementioned first aspect and any possible implementation of the first aspect; a network device for implementing the method in the aforementioned second aspect and any possible implementation of the second aspect. Alternatively, the communication system includes: a network device for implementing the method in the aforementioned third aspect and any possible implementation of the third aspect; a terminal device for implementing the method in the aforementioned fourth aspect and any possible implementation of the fourth aspect. Alternatively, the communication system includes: a terminal device for implementing the method in the aforementioned fifth aspect and any possible implementation of the fifth aspect; a terminal device for implementing the method in the aforementioned sixth aspect and any possible implementation of the sixth aspect; a network device for implementing the method in the aforementioned seventh aspect and any possible implementation of the seventh aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0062] FIG1 is a schematic diagram of a network device architecture applicable to an embodiment of the present application;

[0063] FIG2 is a schematic diagram of a network device architecture provided by an embodiment of the present application;

[0064] FIG3 is a schematic diagram of a spectrum provided in an embodiment of the present application;

[0065] FIG4 is a schematic diagram of an SSB provided in an embodiment of the present application;

[0066] FIG5 is a schematic diagram of a flow chart of a system information transmission method provided in an embodiment of the present application;

[0067] FIG6 is a schematic diagram of a cell provided in an embodiment of the present application;

[0068] FIG7 is a schematic diagram of a flow chart of a system information transmission method provided in an embodiment of the present application;

[0069] FIG8 is a schematic diagram of a flow chart of a system information transmission method provided in an embodiment of the present application;

[0070] FIG9 is a schematic diagram of a flow chart of a system information transmission method provided in an embodiment of the present application;

[0071] FIG10 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application;

[0072] FIG11 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application;

[0073] FIG12 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0074] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application. Obviously, the embodiments described are only a part of the embodiments of the present application, not all of the embodiments. The terms "first", "second" and corresponding terminology labels in the present application are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the terms used in this way can be interchangeable under appropriate circumstances. This is merely a way of distinguishing objects with the same properties when describing the embodiments of the present application. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, so that a process, method, system, product or device that includes a series of units is not necessarily limited to those units, but may include other units that are not clearly listed or inherent to these processes, methods, products or devices. The methods and devices provided in the embodiments of the present application are based on the same or similar technical concepts. Since the principles of solving problems by the methods and devices are similar, the implementation of the devices and methods can refer to each other, and the repetitions will not be repeated.

[0075] The method provided in the embodiment of the present application can be applied to various mobile communication systems, for example, the Internet of Things (IoT), narrowband Internet of Things (NB-IoT), a fourth generation (4G) communication system (such as long term evolution (LTE)), a fifth generation (5G) communication system (such as 5G new radio (NR)), a hybrid architecture of LTE and NR, 6G or new communication systems emerging in future communication developments, etc. The communication system may also include a machine to machine (M2M) network, a machine type communication (MTC) or other networks.

[0076] The mobile communication system architecture diagram shown in Figure 1 is a communication system architecture diagram used in embodiments of the present application. As shown in Figure 1 , the communication system includes a radio access network 100 and a core network 200. Optionally, the communication system may also include the Internet 300. The radio access network 100 may include at least one radio access network device (such as 110a and 110b in Figure 1 ) and at least one terminal device (such as 120a-120j in Figure 1 ). The terminal device is wirelessly connected to the radio access network device, and the radio access network device is wirelessly or wiredly connected to the core network. The core network device and the radio access network device may be independent, distinct physical devices, or the core network device's functions and the radio access network device's logical functions may be integrated into the same physical device, or a single physical device may integrate some of the core network device's functions and some of the radio access network device's functions. Terminal devices and radio access network devices may be interconnected via wired or wireless connections. Figure 1 is merely a schematic diagram. The communication system may also include other network devices, such as wireless relay devices and wireless backhaul devices, which are not shown in Figure 1 .

[0077] In the embodiments of the present application, the network device may be a device in a wireless network, and the network device may also be referred to as a network apparatus, a radio access network device, or an access network device. For example, the network device may be a radio access network (RAN) node that connects a terminal device to a wireless network, and may also be referred to as an access network device. Network equipment includes but is not limited to: base stations, evolved NodeBs (eNodeBs), transmission reception points (TRPs), next generation NodeBs (gNBs) in fifth generation (5G) mobile communication systems, access network equipment in open radio access networks (O-RANs), next generation base stations in sixth generation (6G) mobile communication systems, base stations in future mobile communication systems, or access nodes in wireless fidelity (WiFi) systems, etc.; or it may be a module or unit that completes part of the functions of a base station, for example, a centralized unit (CU), a distributed unit (DU), a centralized unit control plane (CU-CP) module, or a centralized unit user plane (CU-UP) module. The access network equipment may be a macro base station, a micro base station, an indoor station, a relay node, a donor node, etc. The specific technology and specific device form adopted by the network equipment are not limited in this application.

[0078] As shown in Figure 2, in some implementations, network equipment may include a centralized unit (CU) and a distributed unit (DU). RAN equipment, including CU and DU nodes, splits the protocol layers of the gNB in ​​the NR system. Some protocol layer functions are centrally controlled by the CU, while some or all of the remaining protocol layer functions are distributed in the DU, which is centrally controlled by the CU. Furthermore, the CU can be divided into a control plane (CU-CP) and a user plane (CU-UP). The CU-CP is responsible for control plane functions, primarily including radio resource control (RRC) and the control plane's corresponding packet data convergence protocol (PDCP) (i.e., PDCP-C). PDCP-C is primarily responsible for encryption, decryption, integrity protection, and data transmission of control plane data. The CU-UP is responsible for user plane functions, primarily including the service data adaptation protocol (SDAP) and the user plane's corresponding PDCP (i.e., PDCP-U). SDAP is primarily responsible for processing core network data and mapping flows to bearers. The PDCP-U is primarily responsible for data plane encryption and decryption, integrity protection, header compression, sequence number maintenance, and data transmission. The CU-CP and CU-UP are connected via the E1 interface. The CU-CP represents the gNB's connection to the core network via the NG interface and to the DU via the F1 interface control plane (i.e., F1-C). The CU-UP connects to the DU via the F1 interface user plane (i.e., F1-U). Alternatively, the PDCP-C may also reside in the CU-UP.

[0079] It is understood that in different systems, CU (including CU-CP or CU-UP) or DU may have different names, but those skilled in the art can understand their meanings. For example, in an open radio access network (O-RAN) system, CU may also be called an open CU (O-CU), DU may also be called an open DU (O-DU), CU-CP may also be called O-CU-CP, and CU-UP may also be called O-CU-UP. For convenience of description, this application uses CU, CU-CP, CU-UP and DU as examples. The network device may also include an active antenna unit (AAU). The CU implements some functions of the gNB, and the DU implements some functions of the gNB. For example, the CU is responsible for processing non-real-time protocols and services and implementing the functions of the RRC layer. The DU is responsible for processing physical layer protocols and real-time services and implementing the functions of the radio link control (RLC) layer, the media access control (MAC) layer, and the physical (PHY) layer. In some deployments, the CU can be further divided into a Centralized Unit Control Plane (CU-CP) node and a Centralized Unit User Plane (CU-UP) node, where the CU-CP is responsible for control plane functions and the CU-UP is responsible for user plane functions.

[0080] The terminal device involved in the embodiments of the present application may be a wireless terminal device capable of receiving scheduling and instruction information from a network device. The terminal device may be referred to as a terminal device, and may also be referred to as user equipment (UE), terminal, mobile station (MS), mobile terminal (MT), etc. The terminal device may be a device that includes wireless communication capabilities (providing voice / data connectivity to the user). For example, a handheld device with wireless connection capabilities, or an in-vehicle device, in-vehicle module, etc. Currently, some examples of terminal devices include: mobile phones, tablet computers, laptop computers, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in the Internet of Vehicles, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, or wireless terminals in smart homes, device-to-device (D2D) communication terminal devices, vehicle-to-everything (V2X) communication terminal devices, smart vehicles, telematics boxes (T-boxes), machine-to-machine / machine-type communications (M2M / MTC) terminal devices, Internet of Things (IoT) The IoT (Internet of Things) terminal devices, etc. For example, the terminal device can be an onboard device, complete vehicle equipment, an onboard module, a vehicle, an onboard unit (OBU), a roadside unit (RSU), a T-box, a chip, or a system on chip (SOC), etc. The above chip or SOC can be installed in the vehicle, OBU, RSU, or T-box. Wireless terminals in industrial control can be cameras, robots, etc. Wireless terminals in smart homes can be TVs, air conditioners, vacuum cleaners, speakers, set-top boxes, etc.The terminal device can also be a V2X device, such as a smart car (or intelligent car), a digital car, an unmanned car (or driverless car or pilotless car or automobile), a self-driving car or autonomous car, a pure electric vehicle (or Battery EV), a hybrid electric vehicle (HEV), a range extended EV (REEV), a plug-in hybrid electric vehicle (PHEV), a new energy vehicle (new energy vehicle), and a roadside unit (RSU). The terminal device can also be a device in device-to-device (D2D) communication, such as an electricity meter, a water meter, etc. In addition, in an embodiment of the present application, the terminal device can also be a terminal device in an IoT system. IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection.

[0081] 1. Private network refers to a narrowband dedicated network, which can also be called a narrowband private network.

[0082] Narrowband new radio (NB-NR) systems are primarily used in private network scenarios, such as railway mobile communication networks. Railway mobile communication networks can provide secure, reliable, and efficient connections within railway scenarios, improving the passenger experience.

[0083] Private networks are typically deployed on dedicated frequency bands. For example, a railway mobile communications network can be deployed on the (extended) railway-global system for mobile communications ((E)R-GSM) 900 MHz frequency division duplexing (FDD) band. For example, Figure 3 shows the spectrum (or bandwidth) allocation for the (E)R-GSM 900 MHz FDD band.

[0084] The uplink or downlink spectrum occupied by R-GSM may be 4 MHz. Specifically, the uplink spectrum may range from 876 MHz to 880 MHz, and the downlink spectrum may range from 921 MHz to 925 MHz. (E) The uplink or downlink spectrum occupied by R-GSM may be 3 MHz. Specifically, the uplink spectrum may range from 873 MHz to 876 MHz, and the downlink spectrum may range from 918 MHz to 921 MHz.

[0085] When the above-mentioned (E)R-GSM 900MHz FDD band evolves to the NR system, the (E)R-GSM 900MHz FDD band needs to support both NR-railway (Railway, R) and GSM-R. Therefore, after the spectrum of this band is refarmed, NR-R and GSM-R can share 5.6MHz uplink or downlink spectrum. Specifically, NR-R can occupy the lower frequency 3.6MHz uplink or downlink spectrum, and GSM-R can occupy the higher frequency 2MHz uplink or downlink spectrum. The uplink spectrum can range from 874.4MHz to 880MHz, and the downlink spectrum can range from 919.4MHz to 925MHz. It can be seen that the spectrum available for NR-R is less than 5MHz. Usually, a narrowband dedicated network with a bandwidth of less than 5MHz (hereinafter referred to as "narrowband dedicated network") can be configured for a dedicated frequency band. The conditions met by the private network or narrowband private network mentioned in the embodiments of the present application include but are not limited to at least one of the following: the channel bandwidth is equal to 3MHz or 5MHz, the maximum transmission bandwidth is less than 5MHz or belongs to the NB-NR system, and the subcarrier spacing only supports 15kHz.

[0086] In this application, the difference between a terminal device that only supports a private network and a terminal device that only supports a broadband network (such as a terminal device in NR Rel-15 or Rel-16) includes at least one of the following:

[0087] 1. Different channel bandwidth capabilities. For example, a terminal device supporting a broadband network can support data transmission with network equipment using a maximum of 100MHz frequency resources on a single carrier, while a terminal device supporting a private network can support data transmission using a maximum of 5MHz or 3MHz frequency resources on a single carrier.

[0088] 2. Different transmission bandwidth capabilities. For example, when the subcarrier spacing is 15 kHz, the minimum maximum transmission bandwidth for a terminal device supporting a broadband network is 25 PRBs in a 5 MHz channel bandwidth. Terminal devices supporting private networks support 3 MHz and 5 MHz channel bandwidths, which correspond to transmission bandwidths less than 25 RBs, such as 12, 15, 18, or 20 PRBs.

[0089] In addition, in the (E)R-GSM 900MHz FDD band, public GSM, universal mobile telecommunications system (UMTS), or long term evolution (LTE) occupy 35MHz of uplink or downlink spectrum. The uplink spectrum can range from 880MHz to 915MHz, and the downlink spectrum can range from 925MHz to 960MHz.

[0090] 2. Synchronization signal and physical broadcast channel block (synchronization signal and PBCH block, SSB).

[0091] In the NR system, when a terminal device accesses the network, it can synchronize the time and frequency with the network device through the SSB and obtain broadcast information. Specifically, the synchronization signal (SS) can include the primary synchronization signal (PSS) and the secondary synchronization signal (SSS). The terminal device can complete the time and frequency synchronization with the network device through the PSS and SSS. The physical broadcast channel (PBCH) mainly carries broadcast information, including the master information block (MIB) from the upper layer and timing-related information from the physical layer.

[0092] For example, Figure 4 is a schematic diagram of the structure of the time-frequency resources occupied by SSB in the NR system. In conjunction with Figure 4, an SSB can occupy 4 consecutive orthogonal frequency division multiplexing (OFDM) symbols (hereinafter referred to as "symbols") numbered 0 to 3 in the time domain, and can occupy 20 resource blocks (RBs) in the frequency domain. Among them, 1 RB can contain 12 subcarriers, so 20 RBs can contain 240 subcarriers.

[0093] Specifically, in the time domain, PSS can occupy the symbol numbered 0; in the frequency domain, PSS can occupy subcarriers numbered 56 to 182. In the time domain, SSS can occupy the symbol numbered 2; in the frequency domain, SSS can occupy subcarriers numbered 56 to 182. SSB can occupy subcarriers numbered 0 to 55 on the symbol numbered 0, and subcarriers numbered 183 to 239, and set them to 0. SSB can also occupy subcarriers numbered 48 to 55 on the symbol numbered 2, and subcarriers numbered 183 to 191. The PBCH in Figure 2 includes the PBCH and the demodulation-reference signal (DM-RS) of the PBCH. The PBCH in Figure 4 can occupy the entire symbols numbered 1 and 3. In other words, the PBCH can occupy all subcarriers on the symbols numbered 1 and 3. In addition, the PBCH in FIG4 may also occupy subcarriers numbered 0 to 47 and subcarriers numbered 192 to 239 on the symbol numbered 2.

[0094] In the embodiment of the present application, the RB may also be replaced by a physical resource block (PRB), which is uniformly described here and will not be repeated below.

[0095] 3. Synchronous grid.

[0096] The synchronization grid in the NR system is used to indicate the frequency domain location where SSB may appear in the spectrum. The synchronization grid can be understood as the candidate frequency location for the network device to send SSB, and the position of the synchronization grid can be aligned with the center subcarrier of the SSB. In the frequency band below 3GHz, the position of the synchronization grid can be calculated using the formula N*1200kHz+M*50kHz. Among them, the value of N is any value from 1 to 2499, and the value of M is 1, 3 or 5. The terminal device can detect SSB according to the pre-defined synchronization grid.

[0097] For private networks, due to limited frequency domain resources, there is no available synchronization grid for SSB on some frequency bands, so the synchronization grid in the private network scenario is redefined. For example, the synchronization grid under a 3MHz channel bandwidth can be the frequency point determined according to the formula N*600kHz+M*50kHz+300kHz in Table 1, where N is any value from 1 to 1665 and M is 1, 3 or 5; or, the synchronization grid under a 3MHz channel bandwidth can also be the frequency point of 920.73MHz in Table 2; the synchronization grid under a 5MHz channel bandwidth can be the frequency point of 921.45MHz in Table 2. The frequency point of SSB is identified by the global synchronization channel number (GSCN), and a GSCN is associated with an absolute radio frequency channel number (ARFCN).

[0098] Table 1

[0099] Table 2

[0100] Fourth, SIB4, SIB4 contains relevant information for inter-frequency cell reselection, which can also be used for measurements in idle or inactive states. The cell reselection frequency information contained in SIB4 is public, and can also be said to be a cell-level reselection parameter. SIB4 includes an adjacent carrier frequency list (interFreqCarrierFreqList), which can be used to configure adjacent carrier information. Up to 8 groups of adjacent carrier frequency information (interFreqCarrierFreqInfo) can be configured. Each group of adjacent carrier frequency information contains a downlink carrier frequency (dl-CarrierFreq) field and a frequency band list (frequencyBandList) field; the downlink carrier frequency (dl-CarrierFreq) field can indicate the ARFCN, and the frequency band list (frequencyBandList) field can indicate the frequency band number; wherein, the ARFCN indicated by the downlink carrier frequency field is related to the absolute frequency point corresponding to the synchronization grid. Adjacent carrier frequency information can also include other fields, such as the SSB subcarrier spacing (ssbSubcarrierSpacing) field, etc., which are not listed one by one here.

[0101] There are two ways for terminal equipment to determine the SSB frequency position, one is to determine the SSB frequency position through the synchronization grid, and the other is to determine the SSB frequency position through the adjacent frequency carrier frequency information in SIB4. For terminal equipment that does not support private networks, if the adjacent frequency carrier frequency information in SIB4 indicates the frequency information of the SSB of the private network cell, then the terminal equipment may not be able to recognize the adjacent frequency carrier frequency information, and the behavior of the terminal equipment will be unpredictable. For example, the terminal equipment may misinterpret the adjacent frequency carrier frequency information, or it may believe that the information in SIB4 is erroneous. To this end, the present application provides a method, when SIB4 includes adjacent frequency carrier frequency information related to the private network cell, it can reduce the impact on terminal equipment that does not support the private network and improve system compatibility.

[0102] It can be understood that the present application does not specifically limit the specific structure of the execution subject of the method provided in the embodiment of the present application. It can be applied to modules in terminal devices or network devices. As long as it can communicate according to the method provided in the embodiment of the present application by running a program that records the code of the method provided in the embodiment of the present application, it can be used. The interaction between the terminal device and the network device is used as an example for explanation below.

[0103] FIG5 is a flow chart of a method for transmitting system information according to an embodiment of the present application, wherein the method includes:

[0104] Step 501: The network device determines system information.

[0105] In one implementation, the system information includes first adjacent carrier frequency information corresponding to the second cell, the first adjacent carrier frequency information indicating a first ARFCN and first information, the first information indicating a network type of the second cell corresponding to the first adjacent carrier frequency information. The first ARFCN is related to the GSCN of the SSB of the second cell, and the first ARFCN can be used to indicate the center frequency of the SSB of the second cell.

[0106] The first adjacent carrier frequency information may further indicate a first frequency band number, which may be associated with a first ARFCN. One frequency band number may be associated with multiple ARFCNs, and the association between the frequency band number and the ARFCN is predefined or preset.

[0107] The system information may further include other information, for example, the system information includes second adjacent carrier frequency information corresponding to the third cell, the second adjacent carrier frequency information indicating a second ARFCN and second information, the second information indicating a network type of the third cell corresponding to the second adjacent carrier frequency information. The second ARFCN is related to the GSCN of the SSB of the third cell.

[0108] In this application, network types may include private networks and broadband networks. In one implementation, the bandwidth of the private network may satisfy at least one of the following:

[0109] Channel bandwidth is equal to 3MHz or 5MHz;

[0110] The maximum transmission bandwidth is less than 5MHz;

[0111] The PBCH transmission bandwidth of the private network is 12 or 20 PRBs;

[0112] When the channel bandwidth is 3MHz, the PBCH transmission bandwidth of the private network is 12 PRBs;

[0113] When the terminal device performs a cell search on a 3 MHz channel bandwidth, the UE does not expect to receive subcarriers numbered 0 to 47 and 192 to 239 on the four OFDM symbols of the SSB;

[0114] The transmission bandwidth of the private network's Control Resource Set (CORESET) #0 is 12, 15, 18, or 20 PRBs.

[0115] When the channel bandwidth is 3 MHz, the transmission bandwidth of CORESET#0 in the private network is 12 or 15 PRBs;

[0116] When the channel bandwidth is 5 MHz, the transmission bandwidth of CORESET#0 in the private network is 20 PRBs.

[0117] In addition, the private network supports only 15kHz subcarrier spacing. This means that both the SSB subcarrier spacing and the channel subcarrier spacing of the private network only support 15kHz.

[0118] In one implementation, the broadband network is a network with a maximum transmission bandwidth of not less than 5 MHz, for example, the broadband network is at least one of a network defined by NR release (Rel) 15, a network defined by NR Rel-16, or a network defined by NR Rel-17.

[0119] In one implementation, the system information may be SIB 4. The system information may also be other SIBs, which is not limited in this application.

[0120] Taking the system information SIB4 as an example, the first adjacent carrier frequency information can be an adjacent carrier frequency information (interFreqCarrierFreqInfo) in the adjacent carrier frequency list (interFreqCarrierFreqList) of SIB4. The first adjacent carrier frequency information can include a downlink carrier frequency (dl-CarrierFreq) field, and the downlink carrier frequency field can be used to indicate the first ARFCN.

[0121] In this application, in one implementation, the network type of the second cell may be directly indicated by the first information, for example, a new field in the system information may be added to carry the first information. In another implementation, the network type of the second cell may also be indirectly indicated by the first information, for example, an existing field in the system information may be reused to carry the first information.

[0122] For example, the first adjacent carrier frequency information can also indicate the subcarrier spacing, and the subcarrier spacing indicated by the first adjacent carrier frequency information can be used as the first information, and the subcarrier spacing is the subcarrier spacing of the SSB of the second cell. The subcarrier spacing can correspond to the frequency band number, and the correspondence can be predefined or preset. For example, in the NR system, the subcarrier spacing corresponding to the frequency band number n26 is 15kHz, that is, the subcarrier spacing of the frequency band corresponding to the frequency band number n26 is 15kHz. For cells in a private network, only one subcarrier spacing is supported, that is, the second subcarrier spacing. For this reason, in this application, the private network or broadband network can be indicated in the following manner: the subcarrier spacing indicated by the adjacent carrier frequency information corresponding to the private network cell is not equal to the second subcarrier spacing, that is, the subcarrier spacing indicated by the adjacent carrier frequency information corresponding to the private network cell does not match the frequency band number indicated by the adjacent carrier frequency information; the subcarrier spacing indicated by the adjacent carrier frequency information corresponding to the broadband network cell matches the frequency band number indicated by the adjacent carrier frequency information.

[0123] Specifically, the first ARFCN indicated by the first adjacent carrier frequency information is associated with the first frequency band number, or the first adjacent carrier frequency information indicates the first frequency band number. If the first subcarrier spacing indicated by the first adjacent carrier frequency information is not equal to the second subcarrier spacing, the network type indicated by the first information is a private network, that is, the network type of the second cell is a private network; if the first subcarrier spacing indicated by the first adjacent carrier frequency information is equal to the second subcarrier spacing, the network type indicated by the first information is a broadband network, that is, the network type of the second cell is a broadband network. The second subcarrier spacing matches the first frequency band number associated with the first ARFCN, that is, the second subcarrier spacing is the subcarrier spacing corresponding to the first frequency band number. For a broadband network, the first subcarrier spacing can be greater than 15kHz, for example, 30kHz, 60kHz, 120kHz, etc.

[0124] For a terminal device supporting a private network, the terminal device may ignore the first subcarrier spacing indicated by the first adjacent carrier frequency information. If the terminal device determines that it supports the first frequency band number indicated by the first adjacent carrier frequency information, that is, it can operate in the frequency band corresponding to the first frequency band number, the terminal device may receive the SSB of the second cell according to the first ARFCN indicated by the first adjacent carrier frequency information. For a private network, the supported first frequency band number may be any of the following frequency band numbers:

[0125] n26; n28; n85; n100; n106.

[0126] For terminal devices that support broadband networks, the terminal device can determine the first subcarrier spacing, the first frequency band number and the first ARFCN based on the first adjacent carrier frequency information. If the terminal device determines that the subcarrier spacing corresponding to the first frequency band number is not equal to the first subcarrier spacing, it can be determined that the network type of the second cell is a private network. At this time, the terminal device does not receive the SSB of the second cell based on the first ARFCN.

[0127] For example, the second subcarrier spacing supported by the private network is 15kHz, and the first subcarrier spacing is 30kHz. Assuming that the network type of the second cell is a broadband network, and the first frequency band number of the second cell is n26, then the first frequency band number indicated by the first adjacent frequency carrier frequency information corresponding to the second cell is n26, and the first subcarrier spacing indicated by the first adjacent frequency carrier frequency information is 30kHz. For terminal equipment that supports broadband networks, since it is determined that the first subcarrier spacing indicated by the first adjacent frequency carrier frequency information is 30kHz, which does not match the first frequency band number n26 indicated by the first adjacent frequency carrier frequency information, it can be determined that the network type of the second cell is a private network. For terminal equipment that supports private networks, since it is determined that it supports working in the frequency band corresponding to n26, the SSB of the second cell can be received according to the first ARFCN.

[0128] Taking the system information SIB4 as an example, when the first information is the subcarrier spacing indicated by the first adjacent carrier frequency information, the first information can be located in the SSB subcarrier spacing (ssbSubcarrierSpacing) field of the first adjacent carrier frequency information.

[0129] Step 502: The network device sends system information in the first cell.

[0130] The carrier frequency of the second cell is different from that of the first cell, or the second cell is a neighboring cell of the first cell. The carrier frequency of the third cell is different from that of the first cell, or the third cell is a neighboring cell of the first cell.

[0131] Correspondingly, the terminal device receives the first configuration information from the network device.

[0132] As shown in Figure 6, taking the first cell including the first terminal device (UE1 in the figure) and the second terminal device (UE2 in the figure) as an example, assuming that the first terminal device does not support the network type indicated by the first information, and the second terminal device supports the network type indicated by the first information, then the first terminal device and the second terminal device respectively execute the following processes.

[0133] The fact that the first terminal device does not support a private network may mean that the transmission bandwidth of CORESET#0 supported by the first terminal device is greater than the bandwidth of the private network. The fact that the second terminal device supports a private network may mean that the transmission bandwidth of CORESET#0 supported by the first terminal device is less than or equal to the bandwidth of the private network. The bandwidth of the private network is the transmission bandwidth of CORESET#0 of the private network. Alternatively, the synchronization grid supported by the first terminal device may be different from the synchronization grid supported by the private network.

[0134] Step 503: The first terminal device does not receive the SSB of the second cell according to the first ARFCN.

[0135] The first terminal device determines, based on the first information in the first adjacent carrier frequency information, that it does not support the network type indicated by the first information or does not support the network type of the second cell, and may ignore the first adjacent carrier frequency information.

[0136] Taking the case where the network type indicated by the first information is a private network and the first terminal device does not support the private network as an example, for example, the first ARFCN indicated by the first adjacent carrier frequency information is associated with the first frequency band number (e.g., n26), or the first adjacent carrier frequency information indicates the first frequency band number, and the first frequency band number matches the second subcarrier spacing (e.g., 15kHz). If the first adjacent carrier frequency information indicates the first subcarrier spacing (e.g., 30kHz), that is, the first subcarrier spacing is not equal to the second subcarrier spacing, the first terminal device determines that the first subcarrier spacing (e.g., 30kHz) does not match the first frequency band number (e.g., n26), then it is determined that the network type indicated by the first information is a private network. The first terminal device can ignore the first adjacent carrier frequency information and does not receive the SSB of the second cell based on the first ARFCN.

[0137] Step 504: The second terminal device receives the SSB of the second cell according to the first ARFCN.

[0138] The second terminal device determines, based on the first information in the first adjacent carrier frequency information, that the network type indicated by the first information is supported or the network type of the second cell is supported, and can receive the SSB of the second cell based on the first ARFCN.

[0139] Taking the network type indicated by the first information as a private network and the second terminal device supporting the private network as an example, for example, the first ARFCN indicated by the first adjacent carrier frequency information is associated with the first frequency band number (for example, n26), or the first adjacent carrier frequency information indicates the first frequency band number, and the first frequency band number matches the second subcarrier spacing (for example, 15kHz). Regardless of the value of the subcarrier spacing indicated by the first adjacent carrier frequency information, the second terminal device will consider that the subcarrier spacing indicated by the first adjacent carrier frequency information is equal to 15kHz. If the second terminal device supports the first frequency band number (for example, n26), the second terminal device can receive the SSB of the second cell according to the first ARFCN.

[0140] Taking the network type indicated by the first information as a broadband network and the second terminal device supporting a broadband network as an example, for example, the first ARFCN indicated by the first adjacent carrier frequency information is associated with the first frequency band number (e.g., n24), or the first adjacent carrier frequency information indicates the first frequency band number, and the first frequency band number matches the second subcarrier spacing (e.g., 30kHz). If the first adjacent carrier frequency information indicates the first subcarrier spacing (e.g., 30kHz), that is, the first subcarrier spacing is equal to the second subcarrier spacing, the second terminal device determines that the first subcarrier spacing (e.g., 30kHz) matches the first frequency band number (e.g., n24), then it is determined that the network type indicated by the first information is a broadband network. The second terminal device can receive the SSB of the second cell based on the first ARFCN.

[0141] In the present application, the specific process of the second terminal device receiving the SSB of the second cell according to the first ARFCN is not limited. For example, the second terminal device receives the SSB with the first ARFCN as the SSB center frequency, which will not be repeated here.

[0142] In this application, if a terminal device supports two network types, namely, a private network and a broadband network, then the terminal device can receive the SSB of the second cell according to the first ARFCN, and can also receive the SSB of the third cell according to the second ARFCN. This application does not limit how to receive the SSB.

[0143] Through the method provided in the present application, by carrying the first information in the first adjacent carrier frequency information and indicating the network type of the second cell through the first information, the terminal device can determine the network type of the second cell based on the first information, thereby enabling the terminal device receiving the system information to determine whether to receive the SSB of the second cell based on the first adjacent carrier frequency information, standardizing the behavior of the terminal device and improving system compatibility.

[0144] It has been described above that the system information includes an adjacent frequency carrier frequency list (interFreqCarrierFreqList), and the adjacent frequency carrier frequency list may include at least one adjacent frequency carrier frequency information. However, each adjacent frequency carrier frequency information may correspond to a private network cell, or may correspond to a broadband network cell. In order to improve system compatibility, a new private network adjacent frequency carrier frequency list may be added to the system information, and the private network adjacent frequency carrier frequency list includes at least one private network adjacent frequency carrier frequency information. Then, each private network adjacent frequency carrier frequency information in the private network adjacent frequency carrier frequency list only corresponds to a private network cell, and each adjacent frequency carrier frequency information in the adjacent frequency carrier frequency list only corresponds to a broadband network cell. In this way, for terminal devices that support different network types, it is only necessary to read the information in the system information that is the same as the network type it supports, thereby avoiding misinterpretation of the adjacent frequency carrier information in the system information.

[0145] FIG7 is a flow chart of a method for transmitting system information according to an embodiment of the present application, wherein the method includes:

[0146] Step 701: The network device determines system information.

[0147] The system information includes adjacent frequency carrier list information and private network adjacent frequency carrier list information. The adjacent frequency carrier list information is used to indicate the carrier frequency information of the broadband network cell, and the private network adjacent frequency carrier list information is used to indicate the carrier frequency information of the private network cell. The specific contents of the private network and broadband network can be referred to the previous description and will not be repeated here.

[0148] In this application, the name of the private network adjacent frequency carrier frequency list is only an example, and there may be other names. This application does not limit its name. As long as there is information with the same or similar function as the private network adjacent frequency carrier frequency list, it can be regarded as a private network adjacent frequency carrier frequency list.

[0149] In one implementation, the adjacent carrier list information includes at least one adjacent carrier frequency information, where the adjacent carrier frequency information is used to indicate carrier frequency information corresponding to a broadband network cell. For example, the carrier frequency information may include at least one of an ARFCN, a frequency band number, and a subcarrier spacing. The ARFCN may indicate the SSB center frequency of the broadband network cell, the frequency band number is associated with the ARFCN, and the subcarrier spacing indicates the subcarrier spacing of the SSB of the broadband network cell.

[0150] In one implementation, the private network adjacent frequency carrier list information includes at least one piece of private network adjacent frequency carrier frequency information. One piece of private network adjacent frequency carrier frequency information is used to indicate the carrier frequency information corresponding to the private network cell. For example, the carrier frequency information may include at least one of an ARFCN, a frequency band number, and a subcarrier spacing. The ARFCN may indicate the SSB center frequency of the private network cell, the frequency band number is associated with the ARFCN, and the subcarrier spacing indicates the subcarrier spacing of the SSB of the private network cell.

[0151] For example, taking the system information as SIB4, the adjacent carrier list information can be the adjacent carrier frequency list (interFreqCarrierFreqList) of SIB4; the private network adjacent carrier list information can be a newly added field in SIB4, which is dedicated to indicating the carrier frequency information of the broadband network cell.

[0152] In one implementation, the private network adjacent frequency carrier list information is optional information, that is, the system information may not include the private network adjacent frequency carrier list information. For example, the neighboring area of ​​the first cell does not include the private network cell, or the network device does not obtain the carrier frequency information of the private network cell, then the system information may not include the private network adjacent frequency carrier list information, and only include the adjacent frequency carrier list information.

[0153] In one implementation, the value of the adjacent frequency carrier list information may be an invalid value, which can be understood as: the terminal device cannot determine the carrier frequency information of the broadband network cell based on the adjacent frequency carrier list information. For example, the neighboring area of ​​the first cell does not include a broadband network, or the network device does not obtain the carrier frequency information of the broadband network, then the value of the adjacent frequency carrier list information in the system information is an invalid value. The invalid value means that the terminal device determines that its meaning is invalid based on the value. The invalid value can be a default value, or all bits are filled with 0, or all bits are filled with 1. This application does not limit its specific value.

[0154] This application does not limit how to implement the invalid value of the adjacent frequency carrier list information. For example, in implementation method 1, the value of the adjacent frequency carrier list information is the same as the value of the private network adjacent frequency carrier list information. Specifically, the carrier frequency information indicated by the adjacent frequency carrier list information is the same as the carrier frequency information indicated by the private network adjacent frequency carrier list information.

[0155] In this implementation, for a terminal device that does not support a private network, such as a first terminal device, the first terminal device cannot determine valid carrier frequency information, such as a valid ARFCN, based on the adjacent frequency carrier list information, and thus ignores the adjacent frequency carrier list information and does not receive SSB based on the adjacent frequency carrier list information. For a terminal device that supports a private network, the carrier frequency information can be determined based on the private network adjacent frequency carrier list information, and the SSB can be received based on the carrier frequency information.

[0156] Implementation method two, the value of the adjacent frequency carrier list information is a preset value, which cannot indicate the carrier frequency information. It can be understood that the preset value is irrelevant to the carrier frequency information of the broadband network cell. For example, the value of the adjacent frequency carrier list information is 0, that is, the value of all bits included in the adjacent frequency carrier list information is 0; or the value of the adjacent frequency carrier list information is 1, that is, the value of all bits included in the adjacent frequency carrier list information is 1. There may be other situations for the preset value, which are not listed one by one here. Exemplarily, the value of the frequency band list (frequencyBandList) field in the adjacent frequency carrier list information can be nX, where the value of X can be an integer greater than 100.

[0157] In this implementation, for terminal devices that do not support private networks, such as the first terminal device, the first terminal device cannot determine the valid carrier frequency information, such as the valid ARFCN, based on the preset value corresponding to the adjacent frequency carrier list information, and thus ignores the adjacent frequency carrier list information and does not receive SSB based on the adjacent frequency carrier list information.

[0158] Step 702: The network device sends system information in the first cell.

[0159] This application does not limit how the network device sends system information and will not be elaborated here.

[0160] Taking the first cell including the first terminal device and the second terminal device as an example, assuming that the first terminal device does not support the private network and the second terminal device supports the private network, the first terminal device and the second terminal device respectively execute the following processes.

[0161] The fact that the first terminal device does not support a private network may mean that the transmission bandwidth of CORESET#0 supported by the first terminal device is greater than the bandwidth of the private network. The fact that the second terminal device supports a private network may mean that the transmission bandwidth of CORESET#0 supported by the first terminal device is less than or equal to the bandwidth of the private network. The bandwidth of the private network is the transmission bandwidth of CORESET#0 of the private network. Alternatively, the fact that the first terminal device does not support a private network may mean that the synchronization grid supported by the first terminal device is different from the synchronization grid supported by the private network.

[0162] Step 703: The first terminal device does not receive SSB according to the adjacent frequency carrier list information.

[0163] The first terminal device cannot determine the valid carrier frequency information based on the adjacent frequency carrier list information and can ignore the adjacent frequency carrier list information.

[0164] For example, the value of the adjacent frequency carrier list information is the same as the value of the private network adjacent frequency carrier list information. The first terminal device does not support the carrier frequency information determined according to the adjacent frequency carrier list information, such as the ARFCN determined according to the adjacent frequency carrier list information, and then ignores the adjacent frequency carrier list information.

[0165] For example, the first terminal device determines that the value in the adjacent frequency carrier list information is a preset value, and valid carrier frequency information cannot be determined based on the preset value, and the adjacent frequency carrier list information is ignored. For another example, the first terminal device determines that the value of each bit in the adjacent frequency carrier list information is 0, and the adjacent frequency carrier list information is ignored.

[0166] Since the first terminal device does not support the private network, the first terminal device will not interpret the private network adjacent frequency carrier list information in the system information, that is, ignore the private network adjacent frequency carrier list information.

[0167] Step 704: The second terminal device receives SSB according to the private network adjacent frequency carrier list information.

[0168] For example, the second terminal device determines the carrier frequency information of a private network cell based on the private network adjacent frequency carrier list information, and receives the SSB of the private network cell based on the carrier frequency information.

[0169] In this application, if a terminal device supports two network types, namely, a private network and a broadband network, then the terminal device can receive SSB according to the private network adjacent frequency carrier list information and ignore the adjacent frequency carrier list information.

[0170] Through the above method, by setting the value of the adjacent frequency carrier list information to an invalid value, the terminal device that supports the broadband network cannot determine the valid frequency carrier information based on the adjacent frequency carrier list information, ensuring that the system information must carry the adjacent frequency carrier list information while not affecting the terminal device, thereby improving system compatibility.

[0171] This application also provides a method that can regulate the behavior of terminal devices without adding additional information to the system information, thereby avoiding terminal devices that do not support private networks from misinterpreting the adjacent frequency carrier frequency information of private network cells.

[0172] FIG8 is a flow chart of a method for transmitting system information according to an embodiment of the present application, wherein the method includes:

[0173] Step 801: The network device determines system information.

[0174] In one implementation, the system information includes first adjacent carrier frequency information corresponding to the second cell, where the first adjacent carrier frequency information indicates at least one of the following: a first frequency band number; and a first ARFCN. If the second cell is a private network cell, the first frequency band number is different from any frequency band number corresponding to the NR operating frequency band; the first frequency band number is mapped to the second frequency band number; and the second frequency band number is a frequency band number corresponding to the NR operating frequency band.

[0175] Optionally, the system information also includes second adjacent carrier frequency information corresponding to the third cell, where the second adjacent carrier frequency information indicates at least one of the following: a third frequency band number; and a second ARFCN. If the third cell is a broadband network cell, the third frequency band number is associated with the second ARFCN; the third frequency band number is a frequency band number corresponding to the NR operating frequency band.

[0176] For example, the first frequency band number is different from any of the following frequency band numbers: n1, n2, n3, n5, n7, n8, n12, n20, n25, n28, n34, n38, n39, n40, n41, n50, n51, n66, n70, n71, n74, n75, n76, n77, n78, n79, n80, n81, n82, n83, n84, n86, n257, n258, n260, n261.

[0177] The second frequency band number and the third frequency band number are any one of the following frequency band numbers: n1, n2, n3, n5, n7, n8, n12, n20, n25, n28, n34, n38, n39, n40, n41, n50, n51, n66, n70, n71, n74, n75, n76, n77, n78, n79, n80, n81, n82, n83, n84, n86, n257, n258, n260, n261.

[0178] In this application, the first frequency band number may be associated with a first ARFCN. A frequency band number may be associated with multiple ARFCNs, and the association between the frequency band number and the ARFCN is predefined or preset. The first ARFCN is associated with the GSCN of the SSB of the second cell and may be used to indicate the center frequency of the SSB of the second cell.

[0179] This application does not limit how to implement the mapping relationship between the first frequency band number and the second frequency band number. In one implementation method, two frequency band numbers are defined for a frequency band. For example, for the first frequency band, two different frequency band numbers correspond to each other: the first frequency band number and the second frequency band number. The first frequency band number is carried in the information corresponding to the private network, and the second frequency band number is carried in the information corresponding to the broadband network. When the center frequency of the SSB of the private network cell belongs to the first frequency band, the first frequency band number can be indicated in the adjacent frequency carrier frequency information corresponding to the private network cell; when the center frequency of the SSB of the broadband network cell belongs to the first frequency band, the second frequency band number can be indicated in the adjacent frequency carrier frequency information corresponding to the broadband network cell.

[0180] For example, the mapping relationship between the first frequency band number and the second frequency band number may be as shown in Table 3.

[0181] Table 3

[0182] For example, the second cell is a private network cell, the third cell is a broadband network cell, the first ARFCN corresponding to the center frequency of the SSB of the second cell belongs to frequency band 2, and the second ARFCN corresponding to the center frequency of the SSB of the third cell also belongs to frequency band 2. Then the frequency band number indicated by the first adjacent carrier frequency information in the system information is n328, and the frequency band number indicated by the second adjacent carrier frequency information in the system information is n28.

[0183] In another implementation, the mapping relationship between the first frequency band number and the second frequency band number is preconfigured or preset. In this implementation, a virtual frequency band number can be introduced in the private network. The first frequency band number can be considered as the virtual frequency band number of the second frequency band number, and the virtual frequency band number is carried in the adjacent frequency carrier frequency information corresponding to the private network.

[0184] For example, the mapping relationship between the first frequency band number and the second frequency band number satisfies:

[0185] The first frequency band number is equal to the second frequency band number plus X, where X is a number greater than 0. The value of X is not limited, for example, X=100.

[0186] For example, the mapping relationship between the first frequency band number and the second frequency band number may be as shown in Table 4.

[0187] Table 4

[0188] For example, the second cell is a private network cell, the third cell is a broadband network cell, the first ARFCN corresponding to the center frequency of the SSB of the second cell belongs to frequency band 2, and the second ARFCN corresponding to the center frequency of the SSB of the third cell also belongs to frequency band 2. Then the frequency band number indicated by the first adjacent carrier frequency information in the system information is n28+X, and the frequency band number indicated by the second adjacent carrier frequency information in the system information is n28.

[0189] In one implementation, the system information may be SIB 4. The system information may also be other SIBs, which is not limited in this application.

[0190] Taking the system information SIB4 as an example, the first adjacent carrier frequency information can be an adjacent carrier frequency information (interFreqCarrierFreqInfo) in the adjacent carrier frequency list (interFreqCarrierFreqList) of SIB4. The first adjacent carrier frequency information can include a downlink carrier frequency (dl-CarrierFreq) field and a frequency band list (frequencyBandList) field. The downlink carrier frequency field can be used to indicate the first ARFCN, and the frequency band list (frequencyBandList) field can indicate the first frequency band number.

[0191] Step 802: The network device sends system information in the first cell.

[0192] Among them, the carrier frequency of the second cell is different from the carrier frequency of the first cell, or the second cell is a neighboring cell of the first cell; the carrier frequency of the third cell is different from the carrier frequency of the first cell, or the third cell is a neighboring cell of the first cell.

[0193] Taking the first cell including the first terminal device and the second terminal device as an example, assuming that the first terminal device does not support the private network and the second terminal device supports the private network, the first terminal device and the second terminal device respectively execute the following processes.

[0194] The fact that the first terminal device does not support a private network may mean that the transmission bandwidth of CORESET#0 supported by the first terminal device is greater than the bandwidth of the private network. The fact that the second terminal device supports a private network may mean that the transmission bandwidth of CORESET#0 supported by the first terminal device is less than or equal to the bandwidth of the private network. The bandwidth of the private network is the transmission bandwidth of CORESET#0 of the private network. Alternatively, the synchronization grid supported by the first terminal device may be different from the synchronization grid supported by the private network.

[0195] Step 803: The first terminal device does not receive the SSB of the second cell.

[0196] The first terminal device determines the first frequency band number and the first ARFCN based on the first adjacent frequency carrier frequency information. The first terminal device determines that the first ARFCN is not supported, and / or the first terminal device determines that the first ARFCN is not associated with the first frequency band number. Then, the first adjacent frequency carrier frequency information is determined to be invalid information, and the first adjacent frequency carrier frequency information is ignored, thereby not receiving the SSB of the second cell based on the first adjacent frequency carrier frequency information.

[0197] Among them, the first frequency band number is the frequency band number mapped to the second frequency band number, and the first ARFCN has no association with the first frequency band number, but the first ARFCN has an association with the second frequency band number. However, since the first terminal device does not support the private network, the first terminal device determines that the first ARFCN has no association with the first frequency band number, and cannot determine the second frequency band number based on the first frequency band number. The first terminal device can determine that the first adjacent frequency carrier frequency information is invalid information and ignore the first adjacent frequency carrier frequency information.

[0198] Alternatively, since the first terminal device does not support the private network, the first ARFCN is the ARFCN defined in the private network, the first terminal device cannot identify the first ARFCN, and the first terminal device can determine that the first adjacent carrier frequency information is invalid information and ignore the first adjacent carrier frequency information.

[0199] For the second adjacent carrier frequency information of the third cell, the first terminal device can determine that the second ARFCN is associated with the third frequency band number, so that the SSB of the third cell can be received according to the second ARFCN.

[0200] Step 804: The second terminal device receives the SSB of the second cell according to the first adjacent carrier frequency information.

[0201] The second terminal device determines the first frequency band number and the first ARFCN based on the first adjacent carrier frequency information. The second terminal device can determine the second frequency band number based on the first frequency band number. For example, in conjunction with the previous Table 3, the frequency band number indicated by the first adjacent carrier frequency information is n328, then the second terminal device can determine the second frequency band number to be n28. For another example, in conjunction with the previous Table 4, the frequency band number indicated by the first adjacent carrier frequency information is n28+X, then the second terminal device can determine the second frequency band number to be n28.

[0202] For the second adjacent carrier frequency information of the third cell, since the second terminal device does not support the broadband network, the second adjacent carrier frequency information can be ignored. Even if the second terminal device can receive the second ARFCN and the third frequency band number based on the second adjacent carrier frequency information, if the second terminal device does not support the broadband network, it does not support working in the second ARFCN, and thus the second adjacent carrier frequency information can be ignored, and the SSB of the third cell is not received according to the second ARFCN.

[0203] In this application, if a terminal device supports two network types, namely, a private network and a broadband network, then the terminal device can receive the SSB of the second cell according to the first ARFCN, and can also receive the SSB of the third cell according to the second ARFCN. This application does not limit how to receive the SSB.

[0204] Through the method provided in the present application, for private network cells, the first frequency band number indicated by the first adjacent carrier frequency information is the frequency band number mapped by the second frequency band number. Terminal devices that do not support private networks cannot identify the association between the first frequency band number and the first ARFCN, and thus do not receive the SSB of the second cell based on the first adjacent carrier frequency information, thereby standardizing the behavior of the terminal devices and improving system compatibility.

[0205] This application also provides a method, which can be specifically described below.

[0206] FIG9 is a flow chart of a method for transmitting system information according to an embodiment of the present application, wherein the method includes:

[0207] Step 901: The network device determines the MIB.

[0208] The MIB includes first configuration information, and the first configuration information indicates the time and frequency resources of CORESET#0.

[0209] Specifically, the first configuration information indicates index information, where the index information indicates a time-frequency resource of CORESET#0.

[0210] For example, the first configuration information is PDCCH configuration SIB1 (Pdcch-ConfigSIB1) information in the MIB, and the PDCCH configuration SIB1 (Pdcch-ConfigSIB1) information can indicate the time-frequency resources of CORESET# 0. Specifically, the upper 4 bits of the PDCCH configuration SIB1 (Pdcch-ConfigSIB1) information can indicate an index information.

[0211] Step 902: The network device sends the MIB.

[0212] Accordingly, the terminal device receives the MIB.

[0213] Step 903: The terminal device determines the time and frequency resources of CORESET#0 according to the first configuration information in the MIB.

[0214] The terminal device can receive SIB1 based on the time and frequency resources of CORESET#0.

[0215] For example, for a terminal device supporting a private network, a time-frequency resource of CORESET#0 corresponding to the index information can be determined in Table 5 according to the index information.

[0216] For a terminal device supporting a broadband network, a time-frequency resource of CORESET#0 corresponding to the index information can be determined according to the index information in Table 6. The "terminal device supporting a broadband network" here may refer to a terminal device that only supports a broadband network and does not support a private network.

[0217] Among them, the first column in Table 5 is the index information (Index). Table 5 shows the set of resource blocks and time slot symbols of the CORESET of the Type 0 PDCCH (Type0-PDCCH) search space set for the frequency band with a minimum channel bandwidth of 3 MHz and a channel bandwidth of 3 or 5 MHz when the {SS / PBCH block, PDCCH} subcarrier spacing (SCS) is {15, 15} kHz. Tables 5 and 6 can be preset or preconfigured or protocol predefined. The first column in Table 6 is the index information (Index). Table 6 shows the set of resource blocks and time slot symbols of the CORESET set for the Type 0 PDCCH search space when the {SS / PBCH block, PDCCH} SCS is {15, 15} kHz, for the frequency band with a minimum channel bandwidth of 5 MHz or 10 MHz or a minimum channel bandwidth of 3 MHz and a channel bandwidth greater than 3 MHz.

[0218] For example, in Table 5, the number of symbols of CORESET#0 corresponding to index information Index0 is 3, and the number of RBs is 12; the number of symbols of CORESET#0 corresponding to index information Index1 is 2, and the number of RBs is 12. Other cases are not described in detail. By combining the number of symbols and the offset value, the overlap of the CORESET#0 time-frequency resource patterns in Table 5 and Table 6 corresponding to the same index information is minimized, thereby preventing a terminal device supporting a broadband network from mistakenly receiving CORESET#0 sent by a private network through Table 6 and the first configuration information sent by the private network device.

[0219] Through the above method, for terminal devices supporting different types of networks, different modes are used to determine the time and frequency resources of CORESET#0, thereby avoiding erroneous reception of CORESET#0 in unsupported networks and improving network compatibility.

[0220] Table 5: Set of resource blocks and slot symbols of CORESET for Type0-PDCCH search space set when{SS / PBCH block,PDCCH}SCS is{15,15}kHz for frequency bands with minimum channel bandwidth 3MHz and channel bandwidth 3MHz or 5MHz.

[0221] Table 6: Set of resource blocks and slot symbols of CORESET for Type0-PDCCH search space set when{SS / PBCH block,PDCCH}SCS is{15,15}kHz for frequency bands with minimum channel bandwidth 5MHz or 10MHz or with minimum channel bandwidth 3MHz and channel bandwidth larger than 3MHz

[0222] It is understood that in order to implement the functions in the above embodiments, the terminal device or network device includes hardware structures and / or software modules corresponding to the execution of each function. It should be readily apparent to those skilled in the art that, in combination with the units and method steps of each example described in the embodiments disclosed in this application, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in hardware or in a manner driven by computer software depends on the specific application scenario and design constraints of the technical solution.

[0223] The following is a schematic diagram of the structure of possible communication devices provided in the embodiments of the present application. These communication devices can be used to implement the functions of the terminal device or network device in the above method embodiments, and thus can also achieve the beneficial effects possessed by the above method embodiments.

[0224] As shown in Figure 10, the communication device 1000 includes a processing unit 1010 and a communication unit 1020. The communication device 1000 is used to implement the functions of the terminal device or network device in each of the above-mentioned method embodiments.

[0225] In one implementation, the communication device 1000 is used for the following functions:

[0226] A communication unit, configured to receive system information in a first cell; the system information including first adjacent carrier frequency information corresponding to a second cell, the first adjacent carrier frequency information indicating a first absolute radio frequency channel number (ARFCN) and first information, the first information indicating a network type of the second cell corresponding to the first adjacent carrier frequency information; the carrier frequency of the second cell being different from the carrier frequency of the first cell;

[0227] A processing unit is configured to not support the network type indicated by the first information and not receive the synchronization signal broadcast channel block SSB of the second cell according to the first ARFCN; or to support the network type indicated by the first information and receive the synchronization signal broadcast channel block SSB of the second cell according to the first ARFCN.

[0228] In one implementation, the communication device 1000 is used for the following functions:

[0229] a processing unit, configured to determine system information; the system information including first adjacent carrier frequency information corresponding to the second cell, the first adjacent carrier frequency information indicating a first absolute radio frequency channel number ARFCN and first information, the first information indicating a network type of the second cell corresponding to the first adjacent carrier frequency information;

[0230] A communication unit is used to send the system information in a first cell; the carrier frequency of the second cell is different from the carrier frequency of the first cell.

[0231] In one implementation, the communication device 1000 is used for the following functions:

[0232] A processing unit, configured to determine system information; the system information includes adjacent frequency carrier list information and private network adjacent frequency carrier list information, the adjacent frequency carrier list information is used to indicate the carrier frequency information of the broadband network cell, and the private network adjacent frequency carrier list information is used to indicate the carrier frequency information of the private network cell; the value of the adjacent frequency carrier list information is an invalid value;

[0233] A communication unit is configured to send the system information in the first cell.

[0234] In one implementation, the communication device 1000 is used for the following functions:

[0235] A communication unit, configured to receive system information in a first cell; the system information including adjacent frequency carrier list information and private network adjacent frequency carrier list information, the adjacent frequency carrier list information being used to indicate carrier frequency information of a broadband network cell, and the private network adjacent frequency carrier list information being used to indicate carrier frequency information of a private network cell; a value of the adjacent frequency carrier list information being an invalid value;

[0236] A processing unit is configured to receive the synchronization signal broadcast channel block SSB not according to the adjacent frequency carrier list information; or to receive the SSB according to the private network adjacent frequency carrier list information.

[0237] In one implementation, the communication device 1000 is used for the following functions:

[0238] A communication unit, configured to receive system information in a first cell; the system information includes first adjacent carrier frequency information corresponding to a second cell, the first adjacent carrier frequency information indicating a first frequency band number; the carrier frequency of the second cell is different from the carrier frequency of the first cell; the first frequency band number is different from any one of the following frequency band numbers: n1, n2, n3, n5, n7, n8, n12, n20, n25, n28, n34, n38, n39, n40, n41, n50, n51, n66, n70, n71, n74, n75, n76, n77, n78, n79, n80, n81, n82, n83, n84, n86, n257, n258, n260, n261;

[0239] A processing unit is used to not receive the synchronization signal broadcast channel block SSB of the second cell.

[0240] In one implementation, the communication device 1000 is used for the following functions:

[0241] A communication unit, configured to receive system information in a first cell; the system information includes first adjacent carrier frequency information corresponding to a second cell, the first adjacent carrier frequency information indicating a first frequency band number and a first absolute radio frequency channel number (ARFCN); the carrier frequency of the second cell is different from the carrier frequency of the first cell; the first frequency band number is different from any one of the following frequency band numbers: n1, n2, n3, n5, n7, n8, n12, n20, n25, n28, n34, n38, n39, n40, n41, n50, n51, n66, n70, n71, n74, n75, n76, n77, n78, n79, n80, n81, n82, n83, n84, n86, n257, n258, n260, n261;

[0242] A processing unit is used to receive the synchronization signal broadcast channel block SSB of the second cell according to the first adjacent carrier frequency information.

[0243] In one implementation, the communication device 1000 is used for the following functions:

[0244] a processing unit, configured to determine system information; the system information includes first adjacent carrier frequency information corresponding to a second cell, the first adjacent carrier frequency information indicating a first frequency band number and a first absolute radio frequency channel number ARFCN; the first frequency band number and the second frequency band number have a mapping relationship; the first frequency band number is different from any one of the following frequency band numbers, and the first frequency band number is any one of the following frequency band numbers: n1, n2, n3, n5, n7, n8, n12, n20, n25, n28, n34, n38, n39, n40, n41, n50, n51, n66, n70, n71, n74, n75, n76, n77, n78, n79, n80, n81, n82, n83, n84, n86, n257, n258, n260, n261;

[0245] A communication unit is used to send the system information in a first cell, and the carrier frequency of the second cell is different from the carrier frequency of the first cell.

[0246] A more detailed description of the processing unit 1010 and the communication unit 1020 can be directly obtained by referring to the relevant descriptions in the above-mentioned method embodiments, and will not be repeated here.

[0247] It should be understood that the division of units in the above device is merely a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or physically separated. Moreover, the units in the device can all be implemented in the form of software called through processing elements; or all be implemented in the form of hardware; or some units can be implemented in the form of software called through processing elements, and some units can be implemented in the form of hardware. For example, each unit can be a separately established processing element, or it can be integrated into a certain chip of the device. In addition, it can also be stored in the form of a program in a memory, called by a certain processing element of the device and execute the function of the unit. In addition, all or part of these units can be integrated together, or they can be implemented independently. The processing element here can also be a processor, which can be an integrated circuit with signal processing capabilities. In the implementation process, each operation of the above method or each unit above can be implemented by the integrated logic circuit of the hardware in the processor element or by software called through the processing element.

[0248] In one example, the unit in any of the above devices may be one or more integrated circuits configured to implement the above method, such as one or more application specific integrated circuits (ASICs), one or more digital singnal processors (DSPs), one or more field programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms. For another example, when the unit in the device can be implemented in the form of a processing element scheduler, the processing element can be a processor, such as a general-purpose central processing unit (CPU), or other processor that can call a program. For another example, these units can be integrated together and implemented in the form of a system-on-a-chip (SOC).

[0249] The above-mentioned receiving unit is an interface circuit of the device, which is used to receive signals from other devices. For example, when the device is implemented as a chip, the receiving unit is the interface circuit of the chip used to receive signals from other chips or devices. The above-mentioned sending unit is an interface circuit of the device, which is used to send signals to other devices. For example, when the device is implemented as a chip, the sending unit is the interface circuit of the chip used to send signals to other chips or devices.

[0250] As another possible product form, the terminal device or network device of the embodiment of the present application can be implemented by a general bus architecture. For ease of explanation, refer to Figure 11, which is a structural diagram of a communication device 1100 provided in an embodiment of the present application, and the communication device 1100 includes a processor 1101 and a transceiver 1102. The communication device 1100 can be a terminal device, or a chip or chip system therein; or, the communication device 1100 can be a network device, or a chip or module therein. Figure 11 only shows the main components of the communication device 1100. In addition to the processor 1101 and the transceiver 1102, the communication device 1100 can further include a memory 1103, and an input and output device (not shown in the figure).

[0251] Optionally, the processor 1101 is primarily used to process communication protocols and communication data, as well as control the entire communication device, execute software programs, and process software program data. The memory 1103 is primarily used to store software programs and data. The transceiver 1102 may include a radio frequency circuit and an antenna. The radio frequency circuit is primarily used to convert baseband signals into radio frequency signals and process radio frequency signals. The antenna is primarily used to transmit and receive radio frequency signals in the form of electromagnetic waves. Input and output devices, such as a touch screen, display, and keyboard, are primarily used to receive user input and output data to the user.

[0252] Optionally, the processor 1101 , the transceiver 1102 , and the memory 1103 may be connected via a communication bus.

[0253] When the communication device is powered on, the processor 1101 can read the software program in the memory 1103, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be sent wirelessly, the processor 1101 performs baseband processing on the data to be sent and outputs the baseband signal to the radio frequency circuit. The radio frequency circuit performs radio frequency processing on the baseband signal and then transmits the radio frequency signal to the outside in the form of electromagnetic waves through the antenna. When data is sent to the communication device, the radio frequency circuit receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor 1101. The processor 1101 converts the baseband signal into data and processes the data.

[0254] In another implementation, the RF circuit and antenna can be set independently of the processor performing baseband processing. For example, in a distributed scenario, the RF circuit and antenna can be arranged remotely from the communication device.

[0255] In some embodiments, in terms of hardware implementation, those skilled in the art may conceive that the above-mentioned communication device 1000 may take the form of the communication device 1100 shown in FIG. 11 .

[0256] As an example, the functions / implementation process of the processing unit 1010 in FIG10 may be implemented by the processor 1101 in the communication device 1100 shown in FIG11 calling computer-executable instructions stored in the memory 1103. The functions / implementation process of the communication unit 1020 in FIG10 may be implemented by the transceiver 1102 in the communication device 1100 shown in FIG11.

[0257] As another possible product form, the terminal device or network device in the present application may adopt the structure shown in Figure 12, or include the components shown in Figure 12. Figure 12 is a schematic diagram of the structure of a communication device 1200 provided in the present application.

[0258] As shown in FIG12 , the communication device 1200 includes at least one processor 1201. Optionally, the communication device further includes a communication interface 1202.

[0259] When the program instructions are executed in the at least one processor 1201, the communication device 1200 can implement the method provided in any of the aforementioned embodiments and any possible designs therein. Alternatively, the processor 1201 implements the method provided in any of the aforementioned embodiments and any possible designs therein through logic circuits or by executing code instructions.

[0260] The communication interface 1202 can be used to receive program instructions and transmit them to the processor. Alternatively, the communication interface 1202 can be used for the communication device 1200 to communicate with other communication devices, such as exchanging control signaling and / or service data. Exemplarily, the communication interface 1202 can be used to receive signals from devices other than the communication device 1200 and transmit them to the processor 1201, or to send signals from the processor 1201 to other communication devices other than the communication device 1200.

[0261] Optionally, the communication interface 1202 may be a code and / or data read and write interface circuit, or the communication interface 1202 may be a signal transmission interface circuit between a communication processor and a transceiver, or a pin of a chip.

[0262] Optionally, the communication device 1200 may further include at least one memory 1203, which may be used to store required program instructions and / or data. It should be noted that the memory 1203 may exist independently of the processor 1201 or may be integrated with the processor 1201. The memory 1203 may be located within or outside the communication device 1200, without limitation.

[0263] Optionally, the communication device 1200 may further include a power supply circuit 1204, which may be used to supply power to the processor 1201. The power supply circuit 1204 may be located in the same chip as the processor 1201, or in another chip other than the chip where the processor 1201 is located.

[0264] Optionally, the communication device 1200 may further include a bus, and various parts of the communication device 1200 may be interconnected via the bus.

[0265] In some embodiments, in terms of hardware implementation, those skilled in the art may conceive that the communication device 1000 shown in FIG. 10 may take the form of the communication device 1200 shown in FIG. 12 .

[0266] As an example, the functions / implementation process of the processing unit 1010 in FIG10 may be implemented by the processor 1201 in the communication device 1200 shown in FIG12 calling computer-executable instructions stored in the memory 1203. The functions / implementation process of the communication unit 1020 in FIG10 may be implemented by the communication interface 1202 in the communication device 1200 shown in FIG12.

[0267] It should be noted that the structure shown in FIG12 does not constitute a specific limitation on the terminal device or network device. For example, in other embodiments of the present application, the terminal device or network device may include more or fewer components than shown in the figure, or combine or split some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0268] When the communication device is a chip used in a terminal, the terminal chip implements the functions of the terminal in the above method embodiments. The terminal chip receives information from other modules in the terminal (such as a radio frequency module or antenna), and the information is sent by the base station to the terminal; or the terminal chip sends information to other modules in the terminal (such as a radio frequency module or antenna), and the information is sent by the terminal to the base station.

[0269] When the above-mentioned communication device is a module applied to a base station, the base station module implements the functions of the base station in the above-mentioned method embodiment. The base station module receives information from other modules in the base station (such as a radio frequency module or an antenna), and the information is sent by the terminal to the base station; or the base station module sends information to other modules in the base station (such as a radio frequency module or an antenna), and the information is sent by the base station to the terminal. The base station module here can be the baseband chip of the base station, or it can be a DU or other module. The DU here can be a DU under the open radio access network (O-RAN) architecture.

[0270] It is understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.

[0271] The method steps in the embodiments of the present application can be implemented by hardware or by a processor executing software instructions. The software instructions can be composed of corresponding software modules, and the software modules can be stored in a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an erasable programmable read-only memory, an electrically erasable programmable read-only memory, a register, a hard disk, a mobile hard disk, a CD-ROM or any other form of storage medium well known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and the storage medium can be located in an ASIC. In addition, the ASIC can be located in a base station or a terminal. Of course, the processor and the storage medium can also exist in a base station or a terminal as discrete components.

[0272] In the above embodiments, all or part of the embodiments may be implemented using software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are performed in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device, or other programmable device. The computer program or instructions may be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions may be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; an optical medium, such as a digital video disk; or a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or nonvolatile storage medium, or may include both volatile and nonvolatile types of storage media.

[0273] In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0274] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, optical storage, etc.) that contain computer-usable program code.

[0275] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the present application. It should be understood that each flow and / or box in the flow chart and / or block diagram, as well as the combination of the flow chart and / or box in the flow chart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one or more flow charts and / or one or more boxes in the block diagram.

[0276] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0277] Obviously, those skilled in the art may make various changes and modifications to the present application without departing from the scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include these modifications and variations.

Claims

1. A system information transmission method, characterized in that: include: receiving system information in a first cell; The system information includes first adjacent frequency carrier frequency information corresponding to the second cell, the first adjacent frequency carrier frequency information indicating a first absolute radio frequency channel number (ARFCN) and first information, the first information indicating a network type of the second cell corresponding to the first adjacent frequency carrier frequency information; the carrier frequency of the second cell is different from the carrier frequency of the first cell; The network type indicated by the first information is not supported, and the synchronization signal broadcast channel block SSB of the second cell is not received according to the first ARFCN; Alternatively, the network type indicated by the first information is supported, and the synchronization signal broadcast channel block SSB of the second cell is received according to the first ARFCN.

2. The method according to claim 1, characterized in that The first information is the subcarrier spacing indicated by the first adjacent carrier frequency information; if the first subcarrier spacing indicated by the first adjacent carrier frequency information is not equal to the second subcarrier spacing, the network type indicated by the first information is a private network, and the second subcarrier spacing matches the first frequency band number associated with the first ARFCN.

3. The method according to claim 1, characterized in that The first information is the subcarrier spacing indicated by the first adjacent carrier frequency information; if the first subcarrier spacing indicated by the first adjacent carrier frequency information is equal to the second subcarrier spacing, then the network type indicated by the first information is a broadband network, and the second subcarrier spacing matches the first frequency band number associated with the first ARFCN.

4. The method according to claim 2, characterized in that The second subcarrier spacing is 15 kHz.

5. The method according to claim 2 or 4, characterized in that The first subcarrier spacing is 30 kHz.

6. The method according to any one of claims 2, 4 and 5, characterized in that: The first frequency band number associated with the first ARFCN is any one of the following frequency band numbers: n26; n28; n85; n100; n106.

7. A system information transmission method, characterized in that: include: Determine system information; The system information includes first adjacent carrier frequency information corresponding to the second cell, the first adjacent carrier frequency information indicating a first absolute radio frequency channel number (ARFCN) and first information, the first information indicating a network type of the second cell corresponding to the first adjacent carrier frequency information; The system information is sent in a first cell; a carrier frequency of the second cell is different from a carrier frequency of the first cell.

8. The method according to claim 7, characterized in that The first information is the subcarrier spacing indicated by the first adjacent carrier frequency information; if the first subcarrier spacing indicated by the first adjacent carrier frequency information is not equal to the second subcarrier spacing, the network type indicated by the first information is a private network, and the second subcarrier spacing matches the first frequency band number associated with the first ARFCN.

9. The method according to claim 7, characterized in that The first information is the subcarrier spacing indicated by the first adjacent carrier frequency information; if the first subcarrier spacing indicated by the first adjacent carrier frequency information is equal to the second subcarrier spacing, then the network type indicated by the first information is a broadband network, and the second subcarrier spacing matches the first frequency band number associated with the first ARFCN.

10. A system information transmission method, characterized in that: include: Determine system information; the system information includes adjacent frequency carrier list information and private network adjacent frequency carrier list information, the adjacent frequency carrier list information is used to indicate the carrier frequency information of the broadband network cell, and the private network adjacent frequency carrier list information is used to indicate the carrier frequency information of the private network cell; the value of the adjacent frequency carrier list information is an invalid value; The system information is sent in the first cell.

11. The method according to claim 10, characterized in that The value of the adjacent frequency carrier list information is an invalid value, including: The value of the adjacent frequency carrier list information is the same as the value of the private network adjacent frequency carrier list information.

12. The method according to claim 10, characterized in that The value of the adjacent frequency carrier list information is an invalid value, including: The value of the adjacent frequency carrier list information is a preset value.

13. The method according to claim 12, characterized in that The preset value has nothing to do with the carrier frequency information of the broadband network cell.

14. A system information transmission method, characterized in that: include: receiving system information in a first cell; The system information includes adjacent frequency carrier list information and private network adjacent frequency carrier list information, the adjacent frequency carrier list information is used to indicate the carrier frequency information of the broadband network cell, and the private network adjacent frequency carrier list information is used to indicate the carrier frequency information of the private network cell; the value of the adjacent frequency carrier list information is an invalid value; Not receiving a synchronization signal broadcast channel block SSB according to the adjacent frequency carrier list information; Alternatively, the SSB is received according to the private network adjacent frequency carrier list information.

15. The method according to claim 14, characterized in that The value of the adjacent frequency carrier list information is an invalid value, including: The value of the adjacent frequency carrier list information is the same as the value of the private network adjacent frequency carrier list information.

16. The method according to claim 14, characterized in that The value of the adjacent frequency carrier list information is an invalid value, including: The value of the adjacent frequency carrier list information is a preset value.

17. The method according to claim 16, characterized in that The preset value has nothing to do with the carrier frequency information of the broadband network cell.

18. A system information transmission method, characterized in that: include: receiving system information in a first cell; The system information includes first adjacent carrier frequency information corresponding to the second cell, where the first adjacent carrier frequency information indicates a first frequency band number; the carrier frequency of the second cell is different from the carrier frequency of the first cell; the first frequency band number is different from any one of the following frequency band numbers: n1, n2, n3, n5, n7, n8, n12, n20, n25, n28, n34, n38, n39, n40, n41, n50, n51, n66, n70, n71, n74, n75, n76, n77, n78, n79, n80, n81, n82, n83, n84, n86, n257, n258, n260, and n261; The synchronization signal broadcast channel block SSB of the second cell is not received.

19. A system information transmission method, characterized in that: include: receiving system information in a first cell; The system information includes first adjacent carrier frequency information corresponding to the second cell, where the first adjacent carrier frequency information indicates a first frequency band number and a first absolute radio frequency channel number (ARFCN); the carrier frequency of the second cell is different from the carrier frequency of the first cell; the first frequency band number is different from any one of the following frequency band numbers: n1, n2, n3, n5, n7, n8, n12, n20, n25, n28, n34, n38, n39, n40, n41, n50, n51, n66, n70, n71, n74, n75, n76, n77, n78, n79, n80, n81, n82, n83, n84, n86, n257, n258, n260, n261; Receive the synchronization signal broadcast channel block SSB of the second cell according to the first adjacent carrier frequency information.

20. A system information transmission method, characterized in that: include: Determine system information; The system information includes first adjacent carrier frequency information corresponding to the second cell, where the first adjacent carrier frequency information indicates a first frequency band number and a first absolute radio frequency channel number ARFCN; there is a mapping relationship between the first frequency band number and the second frequency band number; the first frequency band number is different from any one of the following frequency band numbers, and the first frequency band number is any one of the following frequency band numbers: n1, n2, n3, n5, n7, n8, n12, n20, n25, n28, n34, n38, n39, n40, n41, n50, n51, n66, n70, n71, n74, n75, n76, n77, n78, n79, n80, n81, n82, n83, n84, n86, n257, n258, n260, n261; The system information is sent in a first cell, and a carrier frequency of the second cell is different from a carrier frequency of the first cell.

21. A communication device, characterized in that: include: a communication unit, configured to receive system information in a first cell; The system information includes first adjacent frequency carrier frequency information corresponding to the second cell, the first adjacent frequency carrier frequency information indicating a first absolute radio frequency channel number (ARFCN) and first information, the first information indicating a network type of the second cell corresponding to the first adjacent frequency carrier frequency information; the carrier frequency of the second cell is different from the carrier frequency of the first cell; A processing unit is configured to not support the network type indicated by the first information and not receive the synchronization signal broadcast channel block SSB of the second cell according to the first ARFCN; or to support the network type indicated by the first information and receive the synchronization signal broadcast channel block SSB of the second cell according to the first ARFCN.

22. A communication device, characterized in that: include: a processing unit for determining system information; The system information includes first adjacent carrier frequency information corresponding to the second cell, the first adjacent carrier frequency information indicating a first absolute radio frequency channel number (ARFCN) and first information, the first information indicating a network type of the second cell corresponding to the first adjacent carrier frequency information; A communication unit is used to send the system information in a first cell; the carrier frequency of the second cell is different from the carrier frequency of the first cell.

23. A communication device, characterized in that: include: A processing unit, configured to determine system information; the system information includes adjacent frequency carrier list information and private network adjacent frequency carrier list information, the adjacent frequency carrier list information is used to indicate the carrier frequency information of the broadband network cell, and the private network adjacent frequency carrier list information is used to indicate the carrier frequency information of the private network cell; the value of the adjacent frequency carrier list information is an invalid value; A communication unit is configured to send the system information in the first cell.

24. A communication device, characterized in that: include: a communication unit, configured to receive system information in a first cell; The system information includes adjacent frequency carrier list information and private network adjacent frequency carrier list information, the adjacent frequency carrier list information is used to indicate the carrier frequency information of the broadband network cell, and the private network adjacent frequency carrier list information is used to indicate the carrier frequency information of the private network cell; the value of the adjacent frequency carrier list information is an invalid value; A processing unit is configured to receive the synchronization signal broadcast channel block SSB not according to the adjacent frequency carrier list information; or to receive the SSB according to the private network adjacent frequency carrier list information.

25. A communication device, characterized in that: include: a communication unit, configured to receive system information in a first cell; The system information includes first adjacent carrier frequency information corresponding to the second cell, where the first adjacent carrier frequency information indicates a first frequency band number; the carrier frequency of the second cell is different from the carrier frequency of the first cell; the first frequency band number is different from any one of the following frequency band numbers: n1, n2, n3, n5, n7, n8, n12, n20, n25, n28, n34, n38, n39, n40, n41, n50, n51, n66, n70, n71, n74, n75, n76, n77, n78, n79, n80, n81, n82, n83, n84, n86, n257, n258, n260, and n261; A processing unit is used to not receive the synchronization signal broadcast channel block SSB of the second cell.

26. A communication device, characterized in that: include: a communication unit, configured to receive system information in a first cell; The system information includes first adjacent carrier frequency information corresponding to the second cell, where the first adjacent carrier frequency information indicates a first frequency band number and a first absolute radio frequency channel number (ARFCN); the carrier frequency of the second cell is different from the carrier frequency of the first cell; the first frequency band number is different from any one of the following frequency band numbers: n1, n2, n3, n5, n7, n8, n12, n20, n25, n28, n34, n38, n39, n40, n41, n50, n51, n66, n70, n71, n74, n75, n76, n77, n78, n79, n80, n81, n82, n83, n84, n86, n257, n258, n260, n261; A processing unit is used to receive the synchronization signal broadcast channel block SSB of the second cell according to the first adjacent carrier frequency information.

27. A communication device, characterized in that: include: a processing unit for determining system information; The system information includes first adjacent carrier frequency information corresponding to the second cell, where the first adjacent carrier frequency information indicates a first frequency band number and a first absolute radio frequency channel number ARFCN; there is a mapping relationship between the first frequency band number and the second frequency band number; the first frequency band number is different from any one of the following frequency band numbers, and the first frequency band number is any one of the following frequency band numbers: n1, n2, n3, n5, n7, n8, n12, n20, n25, n28, n34, n38, n39, n40, n41, n50, n51, n66, n70, n71, n74, n75, n76, n77, n78, n79, n80, n81, n82, n83, n84, n86, n257, n258, n260, n261; A communication unit is used to send the system information in a first cell, and the carrier frequency of the second cell is different from the carrier frequency of the first cell.

28. A communication device, characterized in that: including processor and memory; The processor is configured to execute the computer program or instructions stored in the memory, so that the communication device implements the method according to any one of claims 1 to 20.

29. A chip, characterized in that: The chip comprises a processor coupled to a memory and configured to execute a computer program or instruction stored in the memory, so that the chip implements the method according to any one of claims 1 to 20.

30. A computer program product, characterized in that When a computer reads and executes the computer program product, the method according to any one of claims 1 to 20 is performed.

Images