On-demand SIB1 communication method

Abstract

The present application provides a communication method for requesting a system information block 1 (SIB1) message on demand, applied to a first-type terminal, and comprising: receiving configuration information of a first cell from a first network device, wherein the configuration information of the first cell includes a random access MSG1 resource for N types of terminals, the MSG1 resource is used for sending a message requesting first system information of the first cell, the first system information is an SIB1, and N is an integer greater than or equal to 1. A second network device manages the first cell, and the first network device and the second network device are different. Thus, a terminal device can acquire an SIB1 message of the first cell on demand by using a random access resource matching a terminal type.

Description

A communication method of on-demand SIB1

[0001] The present application claims priority to the Chinese patent application No. 202410639291.2, filed on May 21, 2024, and entitled "A communication method of on-demand SIB1", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] The present application relates to the field of wireless communication, and more particularly, to a communication method of on-demand SIB1. BACKGROUND

[0003] With the increase of the deployment range of base stations and the increase of user data, the power consumption problem of the base station is more and more prominent. The base station can reduce the energy consumption of the base station by not sending some signals or reducing the sending frequency of sending some signals. When the terminal device needs some messages, the terminal device can send a wake-up signal to the base station to wake up the base station to send the corresponding messages, so as to realize that the terminal device acquires relevant information based on the messages to realize access to the base station.

[0004] In the prior art, the system information block 1 (SIB1) of the cell is a signal that the base station is always broadcasting. The SIB1 is used to provide necessary system information for the cell, including cell access information, cell selection information, etc. In order to ensure that the terminal device can acquire the cell access information and the cell selection information, the SIB1 needs to be periodically broadcasted. The base station periodically broadcasts the SIB1, which results in large energy consumption of the base station. Therefore, how the base station sends the SIB1 to reduce the energy consumption of the base station is a problem to be solved. SUMMARY

[0005] The present application provides a communication method, a communication device and a system, which are beneficial to reduce the network energy consumption caused by the periodic broadcast of SIB1.

[0006] In a first aspect, the present application provides a communication method, which can be applied to a network device, for example, can be executed by the network device, or can also be executed by a component (such as a processor, a chip, a chip system, etc.) configured in the network device, and can also be realized by a logic module or software capable of realizing all or part of the functions of the network device. The present application does not make any limitation in this regard.

[0007] The method comprises: a first network device adapted to receive configuration information of a first cell from a second network device, the configuration information of the first cell comprising MSG1 resources for random access of N terminal types, the MSG1 resources being used to send a message requesting first system information of the first cell, the first system information being system information block 1 (SIB1), N being an integer greater than or equal to 1, the second network device managing the first cell, the first network device being different from the second network device, and the first network device broadcasting the configuration information of the first cell.

[0008] In the method, a network energy saving (NES) cell can configure different random access resources for different types of terminals, and subsequently, by receiving MSG1 messages sent through different random access resources, different terminal types requesting SIB1 messages can be distinguished, and different scheduling resources can be allocated to different terminal types, so that different types of terminals can obtain the requested SIB1 messages of the NES cell as needed.

[0009] In combination with the first aspect, the MSG1 resources for random access at least include one of the following: time domain resources, frequency domain resources, preamble information, uplink carrier information corresponding to the MSG1 resources, and the number of repetitions of the MSG1.

[0010] As long as any of the above resources is different, it is different MSG1 resource for random access of different terminal types, for example, different types of terminals have different time domain resources.

[0011] In combination with the first aspect, the configuration information of the first cell further includes one or more of the following: a physical cell identity (PCI) of the first cell, absolute frequency point information (absoluteFrequencySSB) of a synchronization signal block (SSB) of the first cell, PDCCH configuration information corresponding to N terminal types, or cell barring information of the N terminal types. The absolute frequency point information of the SSB includes cell-defining SSB (CD-SSB) frequency point information or non-cell-defining SSB (NCD-SSB) frequency point information. The PDCCH configuration information corresponding to the N terminal types is used for receiving MSG2 of random access or for receiving the first system information. The physical cell identity (PCI) of the first cell and the absolute frequency point information (absoluteFrequencySSB) of the SSB of the first cell can help the terminal distinguish different NES cells.

[0012] In a second aspect, a method for a terminal to request a SIB1 message is provided. The method includes, for a first type of terminal, receiving configuration information of a first cell from a first network device, the configuration information of the first cell including MSG1 resources of random access for N terminal types, the MSG1 resources being used for sending a message for requesting first system information of the first cell, the first system information being a system information block 1 (SIB1), N being an integer greater than or equal to 1, the first cell being managed by a second network device, the first network device being different from the second network device.

[0013] According to the MSG1 resources of random access for the first type of terminal, a MSG1 message of random access is sent to the first cell of the second network device, the MSG1 message being used for requesting the first system information of the first cell.

[0014] The method can ensure that the terminal uses random access resources matching its own type, thereby requesting the SIB1 message of the NES cell on demand.

[0015] In combination with the second aspect, the MSG1 resources of random access include at least one of the following: time domain resources, frequency domain resources, preamble information, uplink carrier information corresponding to the MSG1 resources, and a number of repetitions of the MSG1.

[0016] As long as any of the above resources are different, it is different MSG1 resource of different random access of different terminal type, such as different type terminal has different time domain resource.

[0017] In combination with the second aspect, the configuration information of the first cell further includes one or more of the following information: a physical cell identity (PCI) of the first cell, absolute frequency SSB information (absoluteFrequencySSB) of the first cell, PDCCH configuration information corresponding to N terminal types, and cell barring information of the N terminal types. The absolute frequency SSB information includes CD-SSB frequency point information or NCD-SSB frequency point information defined by the cell. The PDCCH configuration information corresponding to the N terminal types is used for receiving MSG2 of random access or for receiving the first system information. The physical cell identity (PCI) of the first cell and the absolute frequency SSB information (absoluteFrequencySSB) of the first cell can help the terminal to distinguish different NES cells.

[0018] In combination with the second aspect, there is another possible implementation method. The first type terminal receives the second system information of the second network device, and the second system information indicates that the state of the first cell is in the barred state. In a case where the configuration information of the first cell includes random access resources of the first type terminal, it is determined that the first cell is in the notbarred state for the first type terminal. Or, in a case where the configuration information of the first cell does not include random access resources of the first type terminal, it is determined that the first cell is in the barred state for the first type terminal.

[0019] In this method, the barred state indicates that the terminal excludes the first cell from the candidate cell of cell selection / reselection within 300s; and the notbarred state indicates that the terminal takes the first cell as the candidate cell of cell selection / reselection.

[0020] In this method, the terminal can reasonably understand the cell barring state of the first cell for the first type terminal through the configuration information of the first cell and the cell barring information broadcast by the first cell.

[0021] In a case where the cell barring state of the first cell for the first type terminal is in the notbarred state, the first type terminal selects the random access MSG1 resource matched with the first type terminal according to the configuration information of the first cell, and sends MSG1 of random access to the second network device.

[0022] In combination with the second aspect, the first type of terminal receives the MSG2 message of the random access or the first system information according to the configuration information of the first cell.

[0023] In combination with the second aspect, the first type of terminal is a RedCap UE, or an eRedCap UE, or a normal terminal.

[0024] In the third aspect, the present application provides a processor for executing the method provided by any one of the implementation manners of the first aspect and the second aspect. In the process of executing the method, the process of transmitting the information and the process of obtaining / receiving the information in the above method can be understood as the process of outputting the information by the processor and the process of receiving the input information by the processor. When the information is output, the processor outputs the information to an interface, and transmits the information through the interface. After the information is output by the processor, the information can also need to be processed further, and then reaches the interface. Similarly, when the processor receives the input information, the interface obtains / receives the information and inputs the information to the processor. Furthermore, after the interface receives the information, the information can need to be processed further, and then is input to the processor.

[0025] For the operations of transmitting, sending and obtaining / receiving involved, if no special description is made, or if it does not contradict the actual role or inherent logic in the related description, it can be understood as the operations of outputting and receiving, inputting, and also can be understood as the operations of transmitting, sending and receiving by the radio frequency circuit and the antenna, and the present application does not limit this.

[0026] In the implementation process, the processor can be a processor specially used for executing the method, or can be a processor for executing the computer program or instructions in the memory, such as a general processor. The memory can be a non-transitory memory, such as a read only memory (ROM), which can be integrated on the same chip as the processor, or can be arranged on different chips respectively, and the present application does not limit the type of memory and the arrangement mode of the memory and the processor.

[0027] In the fourth aspect, a computer readable storage medium is provided, which stores program codes for execution by a device, and the program codes include codes for executing the method provided by any one of the implementation manners of the first aspect and the second aspect.

[0028] In the fifth aspect, a computer program product containing instructions is provided, which, when the computer program product is run on a computer, causes the computer to execute the method provided by any one of the implementation manners of the first aspect and the second aspect.

[0029] In a seventh aspect, a chip is provided, and the chip includes a processor and a communication interface. The processor reads instructions stored on a memory through the communication interface, and executes the method provided in any of the implementation manners of the first aspect to the second aspect.

[0030] Optionally, as an implementation manner, the chip can further include a memory, and the memory stores a computer program or instructions. The processor is configured to execute the computer program or instructions stored on the memory, and when the computer program or instructions are executed, the processor is configured to execute the method provided in any of the implementation manners of the first aspect to the second aspect. BRIEF DESCRIPTION OF DRAWINGS

[0031] FIG. 1 is a schematic diagram of a system architecture provided by an embodiment of the present application;

[0032] FIG. 2 is a schematic diagram of a 5G network architecture provided by an embodiment of the present application;

[0033] FIG. 3 is a schematic diagram of an open RAN architecture provided by an embodiment of the present application;

[0034] FIG. 4 is a schematic flowchart of a method for requesting system information provided by an embodiment of the present application;

[0035] FIG. 5 is a schematic flowchart of another method for requesting system information provided by an embodiment of the present application;

[0036] FIG. 6 is a schematic diagram of first cell configuration information provided by an embodiment of the present application;

[0037] FIG. 7 is a schematic flowchart of another method for requesting system information provided by an embodiment of the present application;

[0038] FIG. 8 is a schematic block diagram of a communication apparatus provided by an embodiment of the present application.

[0039] FIG. 9 is a schematic diagram of another communication apparatus provided by an embodiment of the present application.

[0040] FIG. 10 is a schematic diagram of a chip system provided by an embodiment of the present application. DETAILED DESCRIPTION

[0041] The technical solutions in the present application will be described below with reference to the accompanying drawings.

[0042] First, in the present application, “for indicating” can include for directly indicating and for indirectly indicating. When describing that certain indication information is for indicating A, it can include that the indication information directly indicates A or indirectly indicates A, and does not mean that A must be carried in the indication information.

[0043] The information indicated by the indication information is referred to as to-be-indicated information. In a specific implementation process, there are many ways to indicate the to-be-indicated information, for example, but not limited to, the to-be-indicated information can be directly indicated, such as the to-be-indicated information itself or an index of the to-be-indicated information. The to-be-indicated information can also be indirectly indicated by indicating other information, where the other information and the to-be-indicated information have an association relationship. The to-be-indicated information can also be only indicated in part, and other parts of the to-be-indicated information are known or agreed in advance. For example, the indication of specific information can also be implemented by means of the arrangement order of various information agreed in advance (for example, specified by a protocol), thereby reducing the indication overhead to a certain extent. Meanwhile, a common part of various information can be identified and uniformly indicated, so as to reduce the indication overhead caused by separately indicating the same information.

[0044] Secondly, in the present application, "at least one" refers to one or more, and "multiple" refers to two or more. In addition, in the embodiments of the present application, "first", "second", and various numerical numbers (for example, "#1", "#2", and the like) are only used for differentiation for the convenience of description, and do not limit the scope of the embodiments of the present application. The size of the serial number of each process below does not mean the order of execution, and the execution order of each process should be determined according to its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present application. It should be understood that the objects thus described can be interchanged under appropriate circumstances, so as to be able to describe schemes other than the embodiments of the present application. In addition, in the embodiments of the present application, "S210" and the like are only used for identification for the convenience of description, and do not limit the order of execution steps.

[0045] Thirdly, in the embodiments of the present application, the words "exemplary" or "for example" are used to mean serving as an example, instance, or illustration. Any embodiment or design presented as "exemplary" or "for example" in the present application should not be interpreted as being more preferred or advantageous than other embodiments or design solutions. Rather, the use of "exemplary" or "for example" is intended to present relevant concepts in a specific manner.

[0046] Fourthly, in the embodiments of the present application, "storage" can refer to storage in one or more memories. The one or more memories can be separately arranged, or integrated in an encoder or decoder, a processor, or a communication device. The one or more memories can be partially separately arranged and partially integrated in a decoder, a processor, or a communication device. The type of the memory can be any form of storage medium, and the present application does not limit this.

[0047] Fifthly, in the embodiments of the present application, the term "protocol" can refer to a standard protocol in the field of communication, for example, can include the NR protocol and the related protocol applied in the future communication system, and the present application does not limit this.

[0048] Sixthly, in the embodiments of the present application, the terms "of", "corresponding", "relevant", "corresponding" and "associated" can be used interchangeably at times, and it should be pointed out that the meanings expressed are consistent when the distinction is not emphasized.

[0049] Seventhly, in the embodiments of the present application, the terms "in the case of", "when", "if" can be used interchangeably at times, and it should be pointed out that the meanings expressed are consistent when the distinction is not emphasized.

[0050] Eighthly, the term "and / or" in the present application is only a description of the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B can represent: A exists alone, A and B exist together, and B exists alone. In addition, the character " / " in the present application generally represents that the front and rear associated objects are in an "or" relationship.

[0051] In order to facilitate the description, the system architecture of the embodiments of the present application is described in detail below.

[0052] The technical solutions of the embodiments of the present application can be applied to various communication systems, for example: a global system of mobile communication (GSM) system, a code division multiple access (CDMA) system, a wideband code division multiple access (WCDMA) system, a general packet radio service (GPRS), a long term evolution (LTE) system, an LTE frequency division duplex (FDD) system, an LTE time division duplex (TDD), a universal mobile telecommunication system (UMTS), a worldwide interoperability for microwave access (WiMAX) communication system, a 5th generation (5G) mobile communication system or a new radio (NR), and a future evolved communication system, etc., and the present application is not limited thereto. The 5G mobile communication system can be a non-standalone (NSA) or standalone (SA).

[0053] The technical solutions provided in the application can also be applied to machine type communication (MTC), long term evolution-machine (LTE-M), device-to-device (D2D) network, machine to machine (M2M) network, internet of things (IoT) network or other network. The IoT network may, for example, include a vehicle network. In the vehicle network system, the communication modes are collectively referred to as vehicle to X (V2X, X can represent any thing), for example, the V2X can include vehicle to vehicle (V2V) communication, vehicle to infrastructure (V2I) communication, vehicle to pedestrian (V2P) communication or vehicle to network (V2N) communication, and the like.

[0054] In the embodiments of the present application, the terminal device can also be referred to as a user equipment (UE), a mobile station (MS), a mobile terminal (MT), etc., and refers to a device that provides voice and / or data connectivity to a user. For example, the terminal device can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a mobile internet device (MID), a wearable device, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in remote medical treatment, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, a drone, a drone controller, etc. The embodiments of the present application do not limit the application scenarios. The terminal device also includes a device capable of sidelink (sidelink) communication, such as a vehicle terminal, or a handheld terminal capable of V2X (vehicle-to-everything) communication, etc. For the convenience of description, the terminal device will be described below by taking a terminal or a UE as an example.

[0055] It should be noted that the terminal device can be a device or apparatus with a chip, or a device or apparatus integrated with a circuit, or a chip, module or control unit in the above-mentioned devices or apparatus, and the specific embodiments of the present application are not limited. For example, the chip can be a chip responsible for communication function in the terminal device, such as a Modem chip, also known as a baseband chip, or a system on chip (SoC) chip or system in package (SIP) chip containing a modem core.

[0056] In a communication system, terminals have different capabilities according to different implementation complexities, and are classified into different terminal types. For example, one type of terminal is a reduced capability UE (RedCap UE), another type of terminal is an enhanced reduced capability UE (eRedCap UE), and another type of terminal is a normal terminal, such as an enhanced mobile broadband (eMBB) terminal.

[0057] The different types of terminal devices have different device features and device capabilities, including one or more of the following:

[0058] Bandwidth, number of supported or configured resources, number of transmit antenna ports and / or receive antenna ports, number of radio frequency channels, number of hybrid automatic repeat request (HARQ) processes, supported peak rate, application scenario, latency requirement, processing capability, protocol version, duplex mode, service, and the like. The different features are described in detail below.

[0059] Bandwidth, or channel bandwidth, or maximum channel bandwidth supported or configured by a terminal device, the bandwidths of different types of terminal devices are different, for example: the bandwidth of a RedCap or eRedCap terminal can be 20MHz or 10MHz or 5MHz, and the bandwidth of a legacy terminal can be 100MHz. It can be understood that, with the development of communication technology, the bandwidth of a RedCap or eRedCap terminal can also evolve into a wider or narrower bandwidth, such as 3MHz, 25MHz, or 50MHz.

[0060] Number of supported or configured resources, which can be the number of RBs, REs, subcarriers, RB groups, REG bundles, control channel elements, subframes, radio frames, time slots, mini-slots, and / or symbols, for example: a normal terminal device supports 48 RBs, and a RedCap terminal device supports 96 RBs.

[0061] Number of transmit antenna ports and / or number of receive antenna ports, for example: the number of transmit antenna ports of a RedCap terminal device can be 1, and the number of receive antenna ports can be 2; the number of transmit antenna ports of a normal terminal device can be 2, and the number of receive antenna ports can be 4.

[0062] Number of radio frequency channels, for example: the number of radio frequency channels of a RedCap terminal device can be 1, and the number of radio frequency channels of a normal terminal device can be 2.

[0063] The number of hybrid automatic repeat request (HARQ) processes, for example, the number of HARQ processes of the RedCap terminal device can be 8, and the number of HARQ processes of the normal terminal device can be 16.

[0064] The supported peak rate, for example, the maximum peak rate supported by the RedCap terminal device can be 100 Mbps, and the peak rate supported by the normal terminal device can be 200 Mbps.

[0065] Application scenarios, for example, the RedCap terminal device is applied to industrial wireless sensing, video monitoring, wearable devices, etc., and the normal terminal device is applied to mobile communication, video surfing, etc.

[0066] The latency requirement, for example, the latency requirement of the RedCap terminal device can be 500 milliseconds, and the latency requirement of the normal terminal device can be 100 milliseconds.

[0067] Processing capability, and the processing timing of different types of terminal devices for channels or data under different subcarrier space (SCS) conditions, processing speed is different, for example, the RedCap terminal device does not support complex operations, the complex operations can include artificial intelligence (AI), VR rendering, and the normal terminal device supports complex operations.

[0068] Duplex mode, including half duplex and full duplex, for example, the RedCap terminal device works in half duplex mode, and the normal terminal device works in full duplex mode.

[0069] Business, including but not limited to Internet of Things applications, such as video monitoring, mobile broadband MBB, etc., for example, the RedCap terminal device supports video monitoring, and the normal terminal device supports mobile broadband MBB. The embodiments of the present application are not limited thereto.

[0070] The access network device or network device refers to a radio access network (RAN) node (or device) that accesses a terminal to a wireless network, which can also be referred to as a base station, such as an NR gNB, an LTE eNB, and various types of base stations. For ease of description, the embodiments of the present application uniformly refer to the "access network device" as "network device" or "base station". Among them, the NR gNB can adopt a centralized unit (CU) and distributed unit (DU) separation architecture, such as the base station #1 shown in FIG. 1, the CU and the DU are connected through the F1 interface for message transmission; or can adopt a CU and DU integrated architecture, such as the base station #2 shown in FIG. 1, the embodiments of the present application do not limit it. In the separation deployment scenario of the access network device including the CU and the DU, the CU supports radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), and other protocols; the DU mainly supports the radio link control layer (RLC), the media access control layer (MAC), and the physical layer protocol. In the dual connectivity (DC) scenario, the terminal device can be connected to two base stations at the same time, one of which is used as a control anchor point to provide control plane connection and user plane connection for the terminal, referred to as the master base station, and the other only provides user plane connection for the terminal, referred to as the secondary base station.

[0071] The core network device refers to a device in a core network (CN) that provides service support for a terminal. Currently, some examples of the core network device are: an access and mobility management function (AMF) entity, a session management function (SMF) entity, a user plane function (UPF) entity, and the like, which are not listed one by one here. Among them, the AMF entity can be responsible for access management and mobility management of the terminal; the SMF entity can be responsible for session management, such as session establishment of a user; and the UPF entity can be a functional entity of a user plane, mainly responsible for connecting an external network. It should be noted that the entity in the present application can also be referred to as a network element or a functional entity, for example, the AMF entity can also be referred to as an AMF network element or an AMF functional entity, and for another example, the SMF entity can also be referred to as an SMF network element or an SMF functional entity, and the like.

[0072] The network device provides services for a cell, and a terminal device communicates with the cell through transmission resources (for example, frequency domain resources, or spectrum resources) allocated by the network device. The cell can belong to a macro base station (for example, a macro eNB or a macro gNB, etc.), or a base station corresponding to a small cell. The small cell here can include a metro cell, a micro cell, a pico cell, a femto cell, etc., which have the characteristics of small coverage and low transmit power, and are suitable for providing high-speed data transmission services.

[0073] In the present application, the device for implementing the function of the access network device can be an access network device, or a device capable of supporting the access network device to implement the function, such as a chip system, a hardware circuit, a software module, or a hardware circuit plus a software module. The device can be installed in the access network device or can be used with the access network device. In the technical solutions provided in the present application, the device for implementing the function of the access network device is an access network device, and the access network device is taken as an example of a base station to describe the technical solutions provided in the present application. In the embodiments of the present application, one network device can include one or more cells, and each cell includes one or more transmission reception points (TRPs) or transmission points (TPs).

[0074] With the continuous development of wireless communication systems, wireless communication greatly enriches people's communication and life. Faster network, better network experience, more people and things connection, let people enjoy the beauty of smart life. At the same time, the energy consumption brought by wireless communication cannot be ignored, so realizing green network connection is an important problem to be solved.

[0075] In a wireless communication system, system information can include remaining minimum system information (RMSI) and other SIBs. Among them, the RMSI can include a master information block (MIB) and a SIB1; the other SIBs can include a system information block type n (SIBn), where n is a positive integer greater than or equal to 2 (for example, the value of n can be 2-18).

[0076] Among them, the MIB can include radio frame number information, which can be used for receiving the configuration of the SIB1;

[0077] The SIB1 can include the access configuration (such as random access resource configuration) of the cell and the scheduling information of the other SIBs (including SIB2 to SIB18);

[0078] The SIB2 can include cell reselection information, which is mainly related to the serving cell;

[0079] The SIB3 can include the serving frequency and the intra-frequency neighbor cell information related to cell reselection, wherein the intra-frequency neighbor cell information can include frequency-common cell reselection parameters and cell-specific reselection parameters;

[0080] The SIB4 can include other NR frequencies and inter-frequency neighbor cell information related to cell reselection, which can also be used for NR idle / inactive measurement, wherein the inter-frequency neighbor cell information can include frequency-common cell reselection parameters and cell-specific reselection parameters;

[0081] The SIB5 can include evolved universal terrestrial radio access (E-UTRA) frequencies and E-UTRA neighbor cell information related to cell reselection, wherein the E-UTRA neighbor cell information can include frequency-common cell reselection parameters and cell-specific reselection parameters;

[0082] SIB6 can include earthquake and tsunami warning system (ETWS) primary notification;

[0083] SIB7 can include ETWS secondary notification;

[0084] SIB8 can include commercial mobile alert system (CMAS) warning notification;

[0085] SIB9 can include global positioning system (GPS) time and coordinated universal time (UTC) related information;

[0086] SIB10 can include a human-readable network name (HRNN) of a non-public network (NPN) listed in SIB1;

[0087] SIB11 can include information related to idle / inactive measurements;

[0088] SIB15 can include disaster roaming related information;

[0089] SIB16 can include slice-based cell reselection information;

[0090] SIB17 can include tracking reference signal (TRS) configuration related information of a terminal in an RRC_idle / RRC_inactive state;

[0091] SIB18 can include information related to a group ID for network selection (GIN) associated with an SNPN listed in SIB1.

[0092] At present, there are two broadcast modes that SIBn can support: one is periodic broadcast, and the other is on demand broadcast based on different terminal demand conditions. However, for SIB1, the network equipment always broadcasts periodically regardless of whether there is terminal demand in the cell, which will bring higher network energy consumption.

[0093] Therefore, the present application provides a method for requesting system information. The terminal can send a request message to the network device to request SIB1 according to its own needs. For example, the terminal can send the request message when the version of the locally stored SIB1 is not the latest version. For another example, the terminal can send the request message when the locally stored SIB1 is invalid. In this way, the network device can send SIB1 according to the needs of the terminal, thereby reducing the network energy consumption caused by the periodic broadcast of SIB1 by the network device.

[0094] The method provided by the present application will be described in detail below with reference to the drawings. It should be understood that the technical solutions of the present application can be applied to the network architecture shown in FIG. 2 or FIG. 3. It can be understood that the network architectures shown in FIG. 2 to FIG. 3 can be applied to the communication system shown in FIG. 1.

[0095] It should be noted that the steps performed by the network device in the following multiple drawings can be performed by the gNB or ng-eNB in the network architecture shown in FIG. 2, or can be performed by the gNB-CU and gNB-DU in the network architecture shown in FIG. 3, without limitation. In the embodiments shown in the following multiple drawings, the interaction process between the terminal and the network device is taken as an example to describe each flow, but this should not constitute any limitation on the execution subject of the present application. For example, the terminal can also be replaced by a component configured in the terminal, such as a chip, a chip system or other modules that can be used to realize part or all of the functions of the terminal; the network device can also be replaced by a component configured in the network device, such as a chip, a chip system or other modules that can be used to realize part or all of the functions of the network device.

[0096] The system information request method provided by the present application will be described in detail below with reference to FIG. 4.

[0097] FIG. 4 shows a method 400 for requesting system information according to an embodiment of the present application. The method 400 includes steps 410 to 420. Each step in the method 400 will be described in detail below.

[0098] In step 410, the terminal sends a request message to the network device, and the request message is used to request the first system information. Correspondingly, the network device receives the request message from the terminal.

[0099] The first system information is the first system information of the first cell, and the first system message is the system information block 1 (SIB1). The system information block 1 (SIB1) contains the information required by the terminal for initial access in the first cell, as well as the scheduling information of other system information blocks except SIB1.

[0100] In step 420, the network device sends the first system information to the terminal in response to the request message. Accordingly, the terminal receives the first system information from the network device.

[0101] It should be understood that the network device sending the first system information to the terminal does not mean that the network device only sends the first system information to the terminal sending the request message. For example, the network device can broadcast the first system information or unicast the first system information, which is not limited in the present application.

[0102] Based on the above scheme, the network device can send the first system information on demand in response to the request of the terminal, thereby reducing the network energy consumption caused by the periodic sending of the first system information by the network device. Since the first system information of the first cell can be sent in response to the request of the terminal, that is, sent on demand, in other words, the first system information is on-demand system information. Therefore, the network energy consumption of the first cell is reduced, and the first cell can be referred to as a network energy saving (NES) cell. The NES cell is a cell in which the first system information (such as SIB1) needs to be sent based on a request. In contrast, the second cell can periodically send the first system information (such as SIB1), which can be referred to as a non-network energy saving cell (i.e., a non-NES cell). The non-NES cell is a cell in which the first system information (such as SIB1) does not need to be sent based on a request.

[0103] FIG. 5 is a system information request method 500 provided by an embodiment of the present application. The system information request method 500 takes the interaction of a terminal, a second network device managing a first cell, and a first network device managing a second cell as an example to describe the implementation process of the method. It should be understood that the first cell is different from the second cell, and the first network device is different from the second network device. The method 500 shown in FIG. 5 is based on the method 400 provided in FIG. 4, and shows a more complete processing logic of the system information request method.

[0104] In S501, the first network device receives the configuration information of the first cell sent by the second network device. Correspondingly, the second network device sends the configuration information of the first cell to the first network device. The second network device manages the first cell. The first cell is a cell supporting network energy saving (NES). The first network device is different from the second network device.

[0105] The configuration information of the first cell can be carried in an Xn interface message, and the existing Xn message can be reused. For example, the XN SETUP REQUEST, the XN SETUP RESPONSE, the NG-RAN NODE CONFIGURATION UPDATE, or other Xn interface messages, or other newly defined messages. The configuration information of the first cell can be exchanged when the interface between the first network device and the second network device is established, or can be updated when the network energy saving state of the second network device changes, or when the configuration information changes. The second network device can determine to turn on or turn off the network energy saving of the first cell based on its own energy saving demand, and update the network energy saving state and the configuration information of the first cell to the first network device.

[0106] As shown in FIG. 6, the configuration information of the first cell includes MSG1 resources for random access of N terminal types, and N is an integer greater than or equal to 1. That is, the configuration information of the first cell can include MSG1 resources for random access of the first type of terminal, and up to MSG1 resources for random access of the Nth type of terminal. The MSG1 resources for random access of the N terminal types can be used for the terminal to request the first system message of the first cell, and the first system message is the system information block 1 (SIB1). For example, the N terminal types can be normal terminals, RedCap terminals, eRedCap terminals, or other terminal types. The system information block 1 (SIB1) contains information required for UE initial access, as well as scheduling information of other system information blocks other than SIB1. The configuration information of the first cell configures different MSG1 resources for random access of different terminal types.

[0107] The MSG1 resource of the random access includes at least one of the following: a time domain resource, a frequency domain resource, a preamble (Preamble) information, an uplink carrier information corresponding to the MSG1 resource, and a repetition number of the MSG1. The time domain resource can be a PRACH configuration index configured by a higher layer, by which the terminal can calculate the timing of sending the Preamble. The time domain resource can also be other time domain related configuration information. The terminal can determine the time domain resource of the terminal sending the MSG1 by using the corresponding table in the 3GPP protocol TS38211. The frequency domain resource can be information such as msg1-FDM and msg1-FrequencyStart configured by a higher layer, or other frequency domain related configuration information. The uplink carrier information corresponding to the MSG1 resource indicates that the MSG1 can be sent by a normal uplink (NUL) or a supplementary uplink (SUL). The repetition number of the MSG1 can indicate the number of times the terminal repeats sending the Preamble. The configuration information of the first cell can configure different MSG1 resources of the random access for different terminal types, that is, at least one of the MSG1 resources used by different terminals is different. For example, the time domain resources can be different, or the frequency domain resources can be different.

[0108] Optionally, the configuration information of the first cell can include a physical cell identity (PCI) of the first cell. The configuration information of the first cell can also include SSB absolute frequency information (absoluteFrequencySSB) of the first cell, which can be cell-defined synchronization signal block (CD-SSB) frequency information or non-cell-defined synchronization signal block (NCD-SSB) frequency information. After receiving the configuration information of the different cells, the terminal can distinguish different cells by the physical cell identity and the SSB absolute frequency information.

[0109] Optionally, the configuration information of the first cell can include PDCCH configuration information corresponding to N terminal types. The terminal uses the PDCCH configuration information matched with the terminal type to receive the random access MSG2 message or scheduling information for receiving the SIB1 message requested by the terminal. The scheduling information can be carried in the DCI. For example, different terminal types can be configured with different receiving bandwidths by different PDCCH configuration information, for example, a RedCap terminal receives with a 5M bandwidth, and a normal terminal receives with a 20M bandwidth.

[0110] Optionally, the configuration information of the first cell can further include cell barring information corresponding to N terminal types. For example, the cell barring information can be an indication of whether a low-complexity terminal is barred from access (cellBarredRedCap-r17), or an indication of whether a more low-complexity terminal is barred from access (cellBarredRedCap-r18), or an indication of whether network energy saving is barred from access (cellBarredNES). Further, the indication can be made according to the protocol version and the number of receive antennas of the low-complexity terminal, and the specific indication information is cellBarredRedCap1Rx-r17, cellBarredRedCap2Rx-r17, cellBarred-eRedCap1Rx-r18, and cellBarred-eRedCap2Rx-r18. The cell barring information corresponding to N terminal types can also be other barring information besides the above-mentioned barring information, which is not limited in the present application. The values of the above-mentioned indication information can be barred (barred) or not barred (notBarred).

[0111] S502, the first network device broadcasts the configuration information of the first cell. For example, the configuration information can be broadcast through the system message of the cell managed by the first network device. Correspondingly, different types of terminals receive the configuration information of the first cell through the broadcast message of the first network device.

[0112] S503, after the terminal receives the configuration information of the first cell, the terminal can identify the random access MSG1 resource of the terminal type to which the terminal belongs through the information. The terminal sends a MSG1 message to the first cell using the random access MSG1 resource matched with the terminal type, and the MSG1 message is used to request the first system message of the first cell. The first system message can be a SIB1 message.

[0113] S504, after the first cell of the second network device receives the MSG1 message of the terminal, the first cell can distinguish the terminal type requesting the first system message through the random access resource used by the MSG1.

[0114] For example, if the first type of terminal is a RedCap terminal, the RedCap terminal receives the configuration information of the first cell from the first network device, and if the configuration information of the first cell contains MSG1 random access resources that can be used by the RedCap terminal, when the RedCap terminal needs to request the first message SIB1 of the first cell, the MSG1 message is sent using the random access resources of the first cell for the RedCap terminal type. After the first cell receives the MSG1 message, it can identify that the terminal type is a RedCap terminal through the random access resources allocated by itself. The above method can also be applied to other types of terminals, for example, the first type of terminal can also be a normal MBB terminal, which is not limited in the present application.

[0115] S505, the first cell of the second network device uses the PDCCH configuration matched with the terminal type to send the terminal the scheduling information of the MSG2 message or the SIB1 message requested by the terminal, and further, the scheduling information can be a DCI message. Correspondingly, the terminal can use the PDCCH configuration information corresponding to the terminal type in the configuration information of the first cell to receive the scheduling information of the MSG2 or SIB1. For example, if the first type of terminal is a RedCap terminal, the RedCap terminal can use the PDCCH configuration information corresponding to the RedCap terminal in the configuration information of the first cell to receive the scheduling information of the MSG2 or SIB1. Similarly, the above method can also be applied to other types of terminals, for example, the first type of terminal can also be a normal MBB terminal, which is not limited in the present application.

[0116] S506, the first cell of the second network device uses the above scheduling information to send the terminal the MSG2 or SIB1 message.

[0117] Based on the above scheme, in the case of N different types of terminals in the network, the network device can send the configuration information of the NES cell corresponding to different types of terminals to the terminal, so as to ensure that the terminal uses the network resource matched with its own type, and ensures that the terminal can obtain the first system message of the NES cell as needed.

[0118] FIG. 7 is a system information request method 700 provided by another embodiment of the present application. The system information request method 700 takes the interaction between the terminal, the second network device managing the first cell, and the first network device managing the second cell as an example to describe the implementation process of the method. It should be understood that the first cell is different from the second cell, and the first network device is different from the second network device. The method 800 shown in FIG. 5 is based on the method 400 provided in FIG. 4, and shows a more complete processing logic of the system information request method.

[0119] The method 700 of requesting system information is described by taking the interaction among a terminal, a network device #1 managing a first cell, and a network device #2 managing a second cell as an example. It should be understood that the first cell is different from the second cell, and the network device #1 is different from the network device #2. The method 700 shown in FIG. 7 is a more complete processing logic of the method of requesting system information based on the method 400 provided in FIG. 4 and the method 500 provided in FIG. 5. Hereinafter, the steps different from the method 500 are mainly described, and the same steps as those in the method 500 can be referred to the related description in the method 500, and will not be described herein.

[0120] S701, the first network device receives the configuration information of the first cell sent by the second network device. Correspondingly, the second network device sends the configuration information of the first cell to the first network device. The configuration information of the first cell includes MSG1 resources of random access of N types of terminals, and N is an integer greater than or equal to 1. That is, the configuration information of the first cell can include MSG1 resources of random access of a first type of terminal, MSG1 resources of random access of a second type of terminal, and MSG1 resources of random access of an Nth type of terminal.

[0121] S702, the first network device broadcasts the configuration information of the first cell.

[0122] The configuration information of the first cell has been described in detail in the method 500, and the steps S701 and S702 are the same as the steps S501 and S502 in the method 500, and will not be described herein.

[0123] S703, the second network device broadcasts the second system information of the first cell. Correspondingly, the terminal receives the second system information of the first cell. The second system information includes cell barring state information of the first cell, and the second system information can be Master Information Block (MIB) information. The MIB information includes the cell barring state information of the first cell and basic physical layer configuration information required for receiving other more system information, such as configuration information of CORRSET#0.

[0124] S704, the terminal can reasonably understand the cell barring status information of the first cell according to the cell barring status information in the second system information broadcast by the first cell and the configuration information of the first cell received from the first network device. The terminal receives the cell barring status as "barred" in the second system information, but there is first configuration information matching the terminal type in the configuration information of the first cell, i.e. there is random access MSG1 resource matching the terminal type, so the terminal can consider that the cell status information of the first cell for the terminal type is "not barred". The terminal receives the cell barring status as "barred" in the second system information, but there is no first configuration information matching the terminal type in the configuration information of the first cell, i.e. there is no random access MSG1 resource matching the terminal type, so the terminal can consider that the cell status information of the first cell for the terminal type is "barred" status. The above "barred" status means that the terminal needs to exclude the first cell from the candidate cell of cell selection / reselection within 300s. The above "not barred" status means that the terminal can initiate random access in the first cell or can be a candidate cell for cell selection or reselection.

[0125] For example, the first terminal type is a RedCap terminal, the terminal receives the cell barring status information as "barred" in the MIB message broadcast by the first cell. The terminal receives the configuration information of the first cell from the first network device, which contains MSG1 random access resource that can be used by RedCap, so the terminal can consider that the cell status information of the first cell for the RedCap terminal is "not barred", i.e. the RedCap terminal can initiate random access in the first cell or can be a candidate cell for cell selection or reselection. The terminal receives the configuration information of the first cell from the first network device, which does not contain MSG1 random access resource that can be used by RedCap, so the terminal considers that the cell status information of the first cell for the RedCap terminal is "barred", i.e. the RedCap terminal needs to exclude the first cell from the candidate cell of cell selection / reselection within 300s.

[0126] S705, if the first cell status for the terminal type is "not barred", the terminal sends MSG1 message to the first cell of the second network device to request the first system information SIB1 according to the configuration information of the first cell received from the first network device.

[0127] S706, after receiving the MSG1 message of the terminal, the first cell of the second network device can distinguish the terminal type of requesting the first system message through the random access resource used by the MSG1.

[0128] S707, the first cell of the second network device sends the MSG2 message or the scheduling information of the SIB1 message requested by the terminal to the terminal, and uses the PDCCH configuration matched with the terminal type.

[0129] S708, the first cell of the second network device sends the MSG2 or the SIB1 message to the terminal through the scheduling information.

[0130] In the above scheme, steps S705-S708 are the same as S503-S506 in method 500, and the detailed steps have been described in method 500, which will not be repeated in method 700.

[0131] The above scheme can ensure the flexibility of different types of terminals and reasonably understand the cell barring state of the NES cell. Without the need to transfer the NES cell to different network devices for different types of cell barring state information, and without the need to broadcast to the terminal through other network devices, the signaling overhead between network devices and broadcast information messages can be saved.

[0132] It should also be understood that in some embodiments described above, the devices in the existing network architecture are mainly exemplarily described, and it should be understood that the specific form of the device is not limited in the embodiments of the present application. For example, devices that can achieve the same function in the future are also applicable to the embodiments of the present application.

[0133] It can be understood that the methods and operations implemented by the network device in each of the above method embodiments can also be implemented by components (such as chips or circuits) applicable to the device.

[0134] It can also be understood that some optional features in each embodiment of the present application can not depend on other features in some scenarios, or can be combined with other features in some scenarios, and are not limited.

[0135] Those skilled in the art should realize that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be realized in the form of hardware or a combination of hardware and computer software. Whether a certain function is realized in hardware or computer software driven hardware depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to realize the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0136] The communication apparatus provided by the embodiments of the present application will be described in detail below in combination with FIG. 8 to FIG. 10. It should be understood that the description of the apparatus embodiments corresponds to the description of the method embodiments, and therefore, the content not described in detail can be referred to the method embodiments described above, and for brevity, some content will not be described again.

[0137] The embodiments of the present application can divide the function modules of the sending end device or the receiving end device according to the method examples described above, for example, each function module can be divided according to each function, or two or more functions can be integrated in one processing module. The integrated module can be realized in the form of hardware or in the form of a software function module. It should be noted that the division of the modules in the embodiments of the present application is illustrative, and is only a logical function division, and another division mode can be used in actual implementation. The following will be described taking the example of dividing each function module according to each function.

[0138] FIG. 8 is a schematic block diagram of the communication apparatus 8 provided by the embodiments of the present application. The apparatus 8 includes a transceiver module 11 and a processing module 12. The transceiver module 11 can realize corresponding communication functions, and the processing module 12 is used for data processing, that is, the transceiver module 11 is used to perform operations related to receiving and sending, and the processing module 12 is used to perform operations other than receiving and sending. The transceiver module 11 can also be referred to as a communication interface or a communication unit.

[0139] Optionally, the apparatus 8 can further include a storage module 13, which can be used to store instructions and / or data, and the processing module 12 can read the instructions and / or data in the storage module to enable the apparatus to implement the actions of the device in each of the foregoing method embodiments.

[0140] In one design, the apparatus 8 can correspond to the first network device in the method embodiments described above. The transceiver module 11 can be used to perform the transceiver-related operations of the first network device described above, and the processing module 12 can be used to perform the processing-related operations of the first network device described above.

[0141] In one possible implementation, the transceiver module 11 is configured to receive configuration information of a first cell from a second network device, the configuration information of the first cell including MSG1 resources for random access of N terminal types, the MSG1 resources being used to send a message requesting first system information of the first cell, the first system information being a system information block 1 (SIB1), and N being an integer greater than or equal to 1. The transceiver module 11 can also be configured to broadcast the configuration information of the first cell.

[0142] In another possible implementation, the apparatus 8 can correspond to the first type of terminal in the above method embodiments. The transceiving module 11 can be configured to perform the above transceiving related operations of the first type of terminal, and the processing module 12 can be configured to perform the above processing related operations of the first type of terminal.

[0143] In one possible implementation, the transceiving module 11 receives the configuration information of the first cell from the first network device, the configuration information of the first cell including MSG1 resources for random access of N types of terminals, the MSG1 resources being used for sending a message for requesting first system information of the first cell. The processing module 12 can select the random access MSG1 resources matching the terminal type according to the terminal type corresponding to the apparatus 8. Then the transceiving module 11 can send a MSG1 message using the above random access MSG1 resources matching the terminal type, the MSG1 message being used for requesting the first system information of the first cell, the first system information being the SIB1 message.

[0144] The transceiving module 11 can also receive the DCI using the PDCCH configuration information matching the first type of terminal, and receive the MSG2 or the SIB1 message of the first cell using the scheduling information in the DCI.

[0145] It should also be understood that the apparatus 8 herein is embodied in the form of functional modules. The term "module" herein can refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (shared, dedicated or group) and memory that execute one or more software or firmware programs, a combinational logic circuit, and / or other suitable components that provide the described functionality. In one optional example, those skilled in the art can understand that the apparatus 10 can be embodied as the first network device in the above embodiments, and can be configured to perform the above processes and / or steps corresponding to the first network device in the above method embodiments; or the apparatus 10 can be embodied as the second network device in the above embodiments, and can be configured to perform the above processes and / or steps corresponding to the second network device in the above method embodiments; or the apparatus 10 can be embodied as the first type of terminal in the above embodiments, and can be configured to perform the above processes and / or steps corresponding to the first type of terminal in the above method embodiments, and thus details are not repeated here.

[0146] The apparatus 8 of each of the above solutions has the function of implementing the corresponding steps performed by the device (e.g., the first network device) in the above method. The function 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; for example, the transceiver module can be replaced by a transceiver (e.g., the sending unit in the transceiver module can be replaced by a transmitter, and the receiving unit in the transceiver module can be replaced by a receiver), and other units, such as the processing module, can be replaced by a processor, which respectively performs the transceiving operations and related processing operations in each method embodiment.

[0147] In addition, the transceiver module 11 described above can also be a transceiver circuit (e.g., which can include a receiving circuit and a sending circuit), and the processing module can be a processing circuit.

[0148] FIG. 9 is a schematic diagram of another communication apparatus 20 provided by an embodiment of the present application. The apparatus 20 includes a processor 21 configured to execute computer programs or instructions stored in a memory 22, or read data / signaling stored in the memory 22, to perform the methods in the above method embodiments. Optionally, the processor 21 is one or more.

[0149] Optionally, as shown in FIG. 9, the apparatus 20 further includes the memory 22 configured to store computer programs or instructions and / or data. The memory 22 can be integrated with the processor 21, or can be separately arranged. Optionally, the memory 22 is one or more.

[0150] Optionally, as shown in FIG. 9, the apparatus 20 further includes a transceiver 23 configured to receive and / or send signals. For example, the processor 21 is configured to control the transceiver 23 to receive and / or send signals.

[0151] As one solution, the apparatus 20 is configured to implement the operations performed by the first network device or the second network device or the first type terminal in the above method embodiments.

[0152] It should be appreciated that a processor as mentioned in this application can be any known or future developed processor, and more particularly, a central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or the like. The general purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, microcontroller, or state machine, etc.

[0153] It should also be appreciated that a memory as described herein can be volatile memory or nonvolatile memory, or a combination of both. The nonvolatile memory can be, for example, read only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically EPROM (EEPROM), or flash memory. The volatile memory can be, for example, random access memory (RAM), which can be externally accessible. By way of example and not limitation, RAM can include the following types: static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct rambus RAM (DR RAM).

[0154] It should be noted that when the processor is a general processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic, discrete hardware component, the memory (storage module) can be integrated in the processor.

[0155] It should also be noted that the memory described herein is intended to include, but not be limited to, the following types of memory: these and any other suitable type of memory.

[0156] FIG. 10 is a schematic diagram of a chip system 30 according to an embodiment of the present application. The chip system 30 (or also referred to as a processing system) includes a logic circuit 31 and an input / output interface 32.

[0157] The logic circuit 31 can be a processing circuit in the chip system 30. The logic circuit 31 can be coupled to a storage unit, and invoke instructions in the storage unit, so that the chip system 30 can implement the methods and functions of the embodiments of the present application. The input / output interface 32 can be an input / output circuit in the chip system 30, and output information processed by the chip system 30, or input data or signaling information to be processed by the chip system 30.

[0158] As an option, the chip system 30 is configured to implement the operations performed by the first network device or the second network device or the first type of terminal in the above method embodiments.

[0159] For example, the logic circuit 31 is configured to implement the processing-related operations performed by the first network device or the second network device or the first type of terminal in the above method embodiments; and the input / output interface 32 is configured to implement the related operations performed by the first network device or the second network device or the first type of terminal in the above method embodiments.

[0160] The embodiments of the present application further provide a computer readable storage medium, which stores computer instructions for implementing the method performed by the device in the above method embodiments.

[0161] For example, the computer program is executed by a computer, so that the computer can implement the method performed by the first network device or the second network device or the first type of terminal in the above method embodiments.

[0162] The embodiments of the present application further provide a computer program product, which includes instructions, and the instructions are executed by a computer to implement the method performed by the first network device or the second network device or the first type of terminal in the above method embodiments.

[0163] The embodiments of the present application further provide a communication system, which includes the first network device and the second network device, and optionally, the communication system can further include the first type of terminal.

[0164] The explanations and beneficial effects of the related contents in any of the above provided apparatuses can refer to the corresponding method embodiments provided above, and will not be repeated here.

[0165] Those skilled in the art can clearly understand that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be realized by electronic hardware or a combination of computer software and electronic hardware. Whether the functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0166] Those skilled in the art can clearly understand that, for the convenience and brevity of the description, the specific working processes of the above-described system, device and unit can refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

[0167] In several embodiments provided in the present application, it should be understood that the disclosed system, device and method can be implemented in other ways. For example, the above-described device embodiments are only schematic, for example, the division of the units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interface, device or unit, and can be electrical, mechanical or other forms.

[0168] The units described as separate components can or can not be physically separated, and the components shown as units can or can not be physical units, that is, they can be located in one place, or can be distributed on a plurality of network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment.

[0169] In addition, each functional unit in each embodiment of the present application can be integrated into a processing unit, or each unit can exist physically independently, or two or more units can be integrated into one unit.

[0170] If the functions are implemented in the form of software function units and sold or used as independent products, they can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application essentially or the parts that contribute to the prior art or parts of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various media that can store program codes.

[0171] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A communication method characterized by comprising: The method comprises: a first network device receives configuration information of a first cell from a second network device, the configuration information of the first cell comprising MSG1 resources for random access of N terminal types, the MSG1 resources being used to send a message requesting first system information of the first cell, the first system information comprising system information block 1 (SIB1), N being an integer greater than or equal to 1, the second network device managing the first cell, the first network device and the second network device being different; the first network device broadcasts the configuration information of the first cell.

2. The method according to claim 1, wherein the configuration information of the first cell further comprises one or more of the following: a physical cell identity (PCI) of the first cell; absolute frequency SSB information of the first cell, the absolute frequency SSB information comprising cell-defined synchronization signal block (CD-SSB) frequency information or non-cell-defined synchronization signal block (NCD-SSB) frequency information; PDCCH configuration information corresponding to the N terminal types, the PDCCH configuration information being used to receive MSG2 of random access or to receive the first system information; or cell barring information of the N terminal types.

3. The method according to claim 2, wherein the MSG1 resources for random access at least comprise one of the following: time domain resources, frequency domain resources, preamble information, uplink carrier information corresponding to the MSG1 resources, or a number of repetitions of the MSG1.

4. The method according to claim 3, wherein the MSG1 resources for random access of different types of terminals are different.

5. The method according to any one of claims 1 to 4, wherein the configuration information of the first cell is carried in an Xn interface message.

6. A communication method characterized by comprising: The method is applied to a first type of terminal, and the method comprises: receiving configuration information of a first cell from a first network device, the configuration information of the first cell comprising MSG1 resources for random access of N terminal types, the MSG1 resources being used to send a message requesting first system information of the first cell, the first system information being system information block 1 (SIB1), N being an integer greater than or equal to 1, the second network device managing the first cell, the first network device and the second network device being different; sending a MSG1 message of random access to the second network device according to MSG1 resources for random access of the first type of terminal, the MSG1 message being used to request the first system information of the first cell.

7. The method according to claim 6, wherein the configuration information of the first cell further comprises one or more of the following: a physical cell identity (PCI) of the first cell; absolute frequency information of a synchronization signal block (SSB) of the first cell, the absolute frequency information of the SSB comprising cell-defined SSB (CD-SSB) frequency information or non-cell-defined SSB (NCD-SSB) frequency information; PDCCH configuration information corresponding to the N terminal types, the PDCCH configuration information being used for receiving MSG2 of random access or being used for receiving the first system information; or cell barring information of the N terminal types.

8. The method of claim 7, wherein the MSG1 resource of the random access at least comprises one of: time domain resource, frequency domain resource, preamble information, uplink carrier information corresponding to the MSG1 resource, or repetition number of the MSG1.

9. The method of any one of claims 5 to 8, wherein, further comprising: receiving second system information of the second network device, the second system information indicating that the state of the first cell is a barred state; in a case where the configuration information of the first cell comprises random access resource of the first type of terminal, determining that the first cell is in a notbarred state for the first type of terminal; or in a case where the configuration information of the first cell does not comprise random access resource of the first type of terminal, determining that the first cell is in a barred state for the first type of terminal.

10. The method of claim 9, wherein, further comprising: in a case where the cell barring state of the first cell for the first type of terminal is a notbarred state, sending MSG1 of random access to the second network device according to the configuration information of the first cell.

11. The method of claim 10, wherein, further comprising: receiving MSG2 of random access or the first system information according to the configuration information of the first cell.

12. The method of claim 9, wherein the barred state indicates that the terminal excludes the first cell from candidate cells of cell selection / reselection within 300s; the notbarred state indicates that the terminal takes the first cell as a candidate cell of cell selection / reselection.

13. The method of any one of claims 6 to 12, wherein the first type of terminal is a RedCap UE, or an eRedCap UE, or a normal terminal.

14. A communication apparatus, comprising one or more functional units configured to implement the method of any one of claims 1 to 5, or to implement the method of any one of claims 6 to 13.

15. A communication apparatus, comprising a processor configured to execute program code to cause the communication apparatus to implement the method of any one of claims 1 to 5, or to implement the method of any one of claims 6 to 13.

16. A computer-readable storage medium having stored thereon a computer program. ​ ​ The computer program, which when executed by a processor, causes the method of any one of claims 1 to 5, or for implementing the method of any one of claims 6 to 13, to be performed.

17. A computer program product, characterized in that, The computer program, which when executed by a processor, causes the method of any one of claims 1 to 5, or for implementing the method of any one of claims 6 to 13, to be performed.

Images