Communication method and device and readable storage medium

Abstract

The invention relates to the technical field of communication, in particular to a communication method and device and a readable storage medium, and the method comprises the steps: receiving one or more segments of a first SIB; the first SIB is effective in an RRC idle state or an inactive state; receiving a second SIB after the first communication device transitions from the RRC connected state to the RRC idle state or the inactive state; the second SIB comprises first indication information and second indication information, the first indication information is used for indicating a first cell in which the first communication device resides in an RRC idle state or an inactive state, and the second indication information is used for indicating whether the first SIB is changed; and when the first cell and a second cell in which the first communication device resides in the RRC connected state are the same cell and the first SIB is not changed, maintaining one or more segments of the first SIB. According to the embodiment of the invention, the multi-segment SIB can be received more quickly, the duration of receiving the broadcast by the UE is reduced, and the power consumption of the UE is reduced.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method, apparatus and readable storage medium. Background Technology

[0002] System information primarily characterizes relevant parameters of a radio cell. It includes the Master Information Block (MIB) and the System Information Block (SIB). SIBs come in several types; Type 1 SIBs are abbreviated as SIB1, Type 2 SIBs as SIB2, and so on. SIBs other than SIB1 are also called Other System Information (OSI). User equipment (UE) needs to receive all system messages to properly utilize the radio resources provided by the radio cell. System information blocks can be broadcast from radio access network equipment (such as base stations) to UEs within the cell over the air interface.

[0003] Currently, in existing Long Term Evolution (LTE) or New Radio (NR) communication systems, there is a type of system information block that can be broadcast in multiple segments, known as a multi-segment system information block (SIB). Examples include SIB28 in LTE and SIB12, SIB17, SIB17bis, and SIB23 in NR. The UE needs to receive all segments of a multi-segment SIB to parse the information cells within it and apply their carried parameters. The more segments a multi-segment SIB has, the longer it takes for the UE to receive all segments, resulting in the UE being unable to apply the parameters carried by the information cells in the multi-segment system information block in a timely manner. Furthermore, the longer the UE receives the broadcast, the higher the power consumption. Therefore, the industry is exploring solutions to provide a way to receive multi-segment system information blocks more quickly. Summary of the Invention

[0004] This application provides a communication method, apparatus, and readable storage medium that can collect multi-segment system information blocks more quickly, reduce the time for the UE to receive broadcasts, reduce the UE's power consumption, and thus improve the user experience.

[0005] The present application is described below from different aspects. It should be understood that the different implementation methods and beneficial effects described below can be referenced from each other.

[0006] In a first aspect, this application provides a communication method, characterized in that it is applied to a first communication device, the method comprising:

[0007] Receive one or more segments of the first system information block (SIB); the first SIB is valid in the Radio Resource Control (RRC) idle state or the RRC inactive state;

[0008] After the first communication device transitions from the RRC connected state to the RRC idle state or the RRC inactive state, it receives the second SIB; the second SIB includes first indication information and second indication information, the first indication information is used to indicate the first cell in which the first communication device camps in the RRC idle state or the RRC inactive state, and the second indication information is used to indicate whether the first SIB has changed.

[0009] When the first cell and the second cell where the first communication device is camped in the RRC connection state are the same cell, and the first SIB has not changed, the one or more segments of the first SIB are maintained.

[0010] In this embodiment, after the UE receives one or more segments of the first system information block (SIB) valid in the RRC idle state or RRC inactive state, when the UE transitions from the RRC connected state to the RRC idle state or RRC inactive state, it can first determine whether the camping cell in the RRC idle state or RRC inactive state is the same cell as the serving cell in the RRC connected state, and determine whether the first SIB has changed. When the camping cell and the serving cell are the same cell and the first SIB has not changed, the UE maintains the received first SIB segments without discarding (clearing) the received first SIB segments and then re-receiving all segments from the beginning. This allows for faster collection of the first SIB segments, enabling faster application of the first SIB parameters, reducing the UE's broadcast reception time, and lowering UE power consumption.

[0011] In one possible implementation, receiving one or more segments of the first SIB includes: receiving the one or more segments of the first SIB in the RRC idle state or RRC inactive state; the method further includes: entering the RRC connected state and camping on the second cell.

[0012] In this embodiment of the application, the UE may receive segments of the multi-segment SIB only in the RRC idle state or the RRC inactive state. When exiting the RRC connected state, if it is determined that the camping cell and the serving cell are the same cell and the multi-segment SIB has not changed, the UE may maintain the segments of the multi-segment SIB previously received.

[0013] In one possible implementation, receiving one or more segments of the first SIB includes: entering an RRC connected state and camping on the second cell; and receiving the one or more segments of the first SIB in the RRC connected state.

[0014] In this embodiment of the application, the UE can receive segments of the multi-segment SIB only in the RRC connected state. When exiting the RRC connected state, if it is determined that the camping cell and the serving cell are the same cell and the multi-segment SIB has not changed, the UE can maintain the segments of the multi-segment SIB previously received.

[0015] In one possible implementation, the segment receiving the first SIB includes:

[0016] Receive a portion of the plurality of segments of the first SIB in the RRC idle state or RRC inactive state;

[0017] Enter the RRC connection state and camp on the second cell;

[0018] In the RRC connection state, another portion of the plurality of segments of the first SIB is received.

[0019] In this embodiment of the application, the UE can receive a portion of the multi-segment SIB in the RRC idle state or the RRC inactive state, and another portion of the multi-segment SIB in the RRC connected state. Subsequently, when the UE exits the RRC connected state, if it determines that the camping cell and the serving cell are the same cell and the multi-segment SIB has not changed, the UE can maintain the segments of the multi-segment SIB previously received.

[0020] In one possible implementation, the method further includes:

[0021] When the first cell and the second cell are different cells, and / or when the first SIB changes, the one or more segments of the first SIB are cleared.

[0022] In this embodiment of the application, if the UE determines that the camping cell and the serving cell are different cells when exiting the RRC connection state, or if the multi-segment SIB changes, the UE can clear (discard) the segments of the previously received multi-segment SIB.

[0023] Secondly, this application provides a first communication device, the device comprising:

[0024] The receiving unit is configured to receive one or more segments of a first system information block (SIB); the first SIB is valid in the Radio Resource Control (RRC) idle state or the RRC inactive state.

[0025] The receiving unit is further configured to receive a second SIB after the first communication device transitions from the RRC connected state to the RRC idle state or the RRC inactive state; the second SIB includes first indication information and second indication information, the first indication information is used to indicate the first cell in which the first communication device camps in the RRC idle state or the RRC inactive state, and the second indication information is used to indicate whether the first SIB has changed;

[0026] The processing unit is configured to maintain the one or more segments of the first SIB when the first cell and the second cell in which the first communication device receives service under the RRC connection state are the same cell and the first SIB has not changed.

[0027] In one possible implementation, the receiving unit is specifically configured to receive one or more segments of the first SIB in the RRC idle state or RRC inactive state; the first communication device enters the RRC connected state and camps on the second cell.

[0028] In one possible implementation, the first communication device enters the RRC connection state and camps in the second cell; the receiving unit is specifically configured to receive one or more segments of the first SIB in the RRC connection state.

[0029] In one possible implementation, the receiving unit is specifically configured to: receive a portion of the plurality of segments of the first SIB in the RRC idle state or the RRC inactive state;

[0030] The first communication device enters the RRC connection state and camps in the second cell;

[0031] The receiving unit is further configured to: receive another portion of the plurality of segments of the first SIB in the RRC connection state.

[0032] In one possible implementation, the processing unit is further configured to clear one or more segments of the first SIB when the first cell and the second cell are different cells, and / or when the first SIB changes.

[0033] Thirdly, this application provides a communication device that may include a processor, a transceiver, and a memory. The memory stores a computer program, and the transceiver sends and receives various messages. The computer program includes program instructions that, when executed by the processor, cause the communication device to perform the method described in any of the possible implementations of the first aspect. The transceiver may be a radio frequency module in the communication device, or a combination of a radio frequency module and an antenna, or an input / output interface of a chip or circuit.

[0034] Fourthly, this application provides a computer-readable storage medium storing program instructions that, when run on a computer, cause the computer to perform the method described in any of the possible implementations of the first aspect above.

[0035] Fifthly, this application provides a program product containing program instructions that, when run, cause the method described in any of the possible implementations of the first aspect to be executed.

[0036] Sixthly, this application provides a communication device, which can be implemented as a chip, a device, or a component within a device, etc. The device includes a processor. The processor is used to read and execute a program stored in a memory to perform the communication method provided by any of the possible implementations of the first aspect described above. Optionally, the communication device further includes a memory connected to the processor via a circuit. Further optionally, the communication device includes a communication interface to which the processor is connected. The communication interface is used to receive data packets and / or information to be processed. The processor obtains the data packets and / or information from the communication interface, processes the data packets and / or information, and outputs the processing result through the communication interface. The communication interface can be an input / output interface.

[0037] In a seventh aspect, this application provides a chip system including a processor for supporting a device in implementing the functions involved in any of the possible implementations of the first aspect, such as generating or processing information involved in the communication method described above. In one possible design, the chip system further includes a memory for storing necessary program instructions and data for the device. This chip system may be composed of chips or may include chips and other discrete devices.

[0038] Alternatively, the processor and memory can be physically independent units, or the memory can be integrated with the processor.

[0039] It should be noted that the technical effects achieved in the above aspects can be referred to each other or to the beneficial effects in the method embodiments shown below, which will not be repeated here. Attached Figure Description

[0040] To more clearly illustrate the technical solutions in the embodiments of this application or the background art, the accompanying drawings used in the embodiments of this application or the background art will be described below.

[0041] Figure 1a This is a schematic diagram of the architecture of the communication system provided in the embodiments of this application;

[0042] Figure 1b This is a schematic diagram of a Sidelink UE-to-Network Relay scenario provided in an embodiment of this application;

[0043] Figure 1c This is a schematic diagram of a Sidelink UE-to-UE Relay scenario provided in an embodiment of this application;

[0044] Figure 2 This is a flowchart illustrating a communication method provided in an embodiment of this application;

[0045] Figure 3 This is a schematic diagram of the processing flow of a communication method provided in an embodiment of this application;

[0046] Figure 4 This is a schematic diagram of the processing flow of another communication method provided in an embodiment of this application;

[0047] Figure 5 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0048] Figure 6 This is a schematic diagram of another communication device provided in an embodiment of this application;

[0049] Figure 7 This is a schematic diagram of the structure of another communication device provided in the embodiments of this application. Detailed Implementation

[0050] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0051] In the description of this application, the terms "first," "second," etc., are used only to distinguish different objects and do not limit the quantity or order of execution, nor do they imply that they must be different. For example, "first instruction information" and "second instruction information," etc., are merely used to distinguish different instruction information and do not limit their order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or devices.

[0052] In the description of this application, unless otherwise stated, " / " means "or". For example, A / B can mean A or B. "And / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone. Furthermore, "at least one item", "one or more of the following", or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can represent: a, b, c; a and b; a and c; b and c; or a and b and c. Here, a, b, and c can be single or multiple.

[0053] In the description of this application, the words "exemplary," "exemplarily," or "for example" are used to indicate examples, illustrations, or illustrative purposes. Any embodiment or design described as "exemplary," "for example," or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Rather, the use of the words "exemplary," "for example," or "for example" is intended to present the relevant concepts in a specific manner.

[0054] It is understood that in the description of this application, "when," "if," and "if" all refer to the device making a corresponding action under certain objective circumstances, and are not time-limited, nor do they require the device to make a judgment action when it is implemented, nor do they mean that there are other limitations.

[0055] In this application, "simultaneously" can be understood as at the same point in time, within a period of time, or within the same cycle; the specific meaning can be determined by considering the context.

[0056] In this application, the use of singular designations for elements is intended to represent "one or more" rather than "one and only one," unless otherwise specified.

[0057] It is understood that in the various embodiments of this application, "A and B correspond" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information.

[0058] It is understood that in the embodiments of this application, "for indicating" and "indication" can include direct and indirect indication, as well as explicit and implicit indication. When describing "a certain indication information is used to indicate A" or "indication information of A", it can include the indication information directly indicating A or indirectly indicating A, but does not necessarily mean that the indication information carries A. The information indicated by a certain information is called the information to be indicated. In the specific implementation process, there are many ways to indicate the information to be indicated, such as, but not limited to, directly indicating the information to be indicated, such as the information to be indicated itself or its index. It can also indirectly indicate the information to be indicated by indicating other information, where there is an association between the other information and the information to be indicated. It can also indicate only a part of the information to be indicated, while the other parts of the information to be indicated are known or agreed upon in advance. For example, the indication of specific information can also be achieved by using the arrangement order of various information in advance (e.g., according to an agreement), thereby reducing the indication overhead to a certain extent. At the same time, the common parts of various information can be identified and indicated uniformly to reduce the indication overhead caused by individually indicating the same information. In addition, the specific indication method can also be various existing indication methods, such as, but not limited to, the above-mentioned indication methods and their various combinations. Specific details of various indication methods can be found in existing technologies and will not be repeated here. As described above, for example, when multiple pieces of information of the same type need to be indicated, the indication methods for different pieces of information may differ. In specific implementation, the required indication method can be selected according to specific needs. This application does not limit the selection of the indication method. Therefore, the indication methods involved in this application should be understood to cover various methods that enable the party to be indicated to know the information to be indicated. The information to be indicated can be sent as a whole or divided into multiple sub-information and sent separately. Moreover, the sending period and / or sending time of these sub-information can be the same or different. This application does not limit the specific sending method.

[0059] For ease of understanding, the technical solution provided in this application will be described below with reference to more accompanying drawings.

[0060] The technical solutions of this application can be applied to various communication systems, such as: Universal Mobile Telecommunications System (UMTS), also known as third-generation (3G) systems; Long Term Evolution (LTE) systems, also known as fourth-generation (4G) systems; Worldwide Interoperability for Microwave Access (WiMAX) communication systems; fifth-generation (5G) systems, such as new radio (NR) technologies; networks integrating multiple systems; Internet of Things (IoT) systems; vehicle-to-everything (V2X) systems; and future communication systems, such as sixth-generation (6G) systems and even seventh-generation (7G) systems. The technical solutions of this application can also be applied to open RAN (O-RAN or ORAN), cloud radio access networks (CRAN), or communication networks including two or more of the above. The technical solutions of this application can also be applied to sidelink communication systems, or to other communication systems operating in unlicensed spectrum. It is understood that the "communication system operating in unlicensed spectrum" mentioned in this application means that the communication system operates in unlicensed spectrum under some circumstances, and of course, the communication system can also operate in licensed spectrum under other circumstances.

[0061] It should be understood that the network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of communication network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0062] See Figure 1a , Figure 1a This is a schematic diagram of the architecture of the communication system provided in an embodiment of this application. Figure 1a As shown, the communication system includes a wireless access network 100. The wireless access network 100 may include at least one wireless access network device (such as...). Figure 1a 110a and 110b in the above), may also include at least one terminal device (such as Figure 1a(120a-120j in the original text). Terminal devices can connect to wireless access network devices wirelessly, and terminal devices and wireless access network devices can be interconnected via wired or wireless means. Understandably, Figure 1a This is just an illustration; the communication system may also include other network devices, such as core network equipment, wireless relay equipment, and wireless backhaul equipment. Figure 1a It is not shown in the middle.

[0063] Wireless access network equipment, often simply referred to as network equipment, is the access device that enables terminals to wirelessly access a communication system. Wireless access network equipment can be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next-generation NodeB (gNB) in 5G mobile communication systems, a next-generation base station in 6G mobile communication systems, a base station in a future mobile communication system, or an access node in a WiFi system; it can also be a module or unit that performs some of the functions of a base station, for example, it can be a central unit (CU) or a distributed unit (DU). The CU here performs the functions of the radio resource control protocol and packet data convergence protocol (PDCP) of the base station, and can also perform the functions of the service data adaptation protocol (SDAP). The DU performs the functions of the radio link control layer and medium access control (MAC) layer of the base station, and can also perform some or all of the physical layer functions. For specific descriptions of the above protocol layers, please refer to the relevant technical specifications of the 3rd Generation Partnership Project (3GPP). The radio access network equipment can be a macro base station (such as...) Figure 1a 110a in the text), can also be a micro base station or an indoor station (such as... Figure 1a 110b) in the text can also be a relay node or a donor node, etc. The embodiments of this application do not limit the specific technology or device form used in the wireless access network equipment. For ease of description, the following description uses a base station as an example of a wireless access network device.

[0064] A terminal device is a device with wireless transceiver capabilities, capable of sending signals to or receiving signals from a base station. Terminal devices can also be referred to as terminals, user equipment (UE), mobile stations, mobile terminals, etc. They can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), the Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, intelligent transportation, and smart cities. Terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, airplanes, ships, robots, robotic arms, smart home devices, and mobile broadband modems, etc. The embodiments of this application do not limit the specific technologies or device forms used in the terminals.

[0065] Optionally, the base station and terminal can be fixed or mobile. The base station and terminal can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of the base station and terminal.

[0066] Alternatively, the roles of the base station and the terminal can be relative, for example, Figure 1a The helicopter or drone 120i can be configured as a mobile base station. For terminals 120j accessing the wireless access network 100 via 120i, terminal 120i is a base station; however, for base station 110a, 120i is a terminal, meaning that 110a and 120i communicate via a wireless air interface protocol. Of course, 110a and 120i can also communicate via a base station-to-base station interface protocol; in this case, 120i is also a base station relative to 110a. Therefore, both base stations and terminals can be collectively referred to as communication devices. Figure 1a The 110a and 110b in the text can be referred to as communication devices with base station functions. Figure 1a The 120a-120j in the text can be referred to as communication devices with terminal functions.

[0067] Optionally, communication can be conducted between base stations and terminals, between base stations, and between terminals through licensed spectrum, through unlicensed spectrum, or simultaneously through both licensed and unlicensed spectrum; communication can be conducted through spectrum below 6 GHz, through spectrum above 6 GHz, or simultaneously using both spectrum below 6 GHz and spectrum above 6 GHz.

[0068] It is understood that the interface between terminals is a PC5 interface, and the interface between a terminal and a base station is a Uu interface. Terminals can use unlicensed spectrum to communicate with other terminals via sidelink. Communication between terminals can be unicast, multicast, or broadcast. In sidelink communication, a terminal can be configured with one or more antennas for sending and receiving messages / information / data, etc. It is understood that the terminal may also include multiple components related to message / information / data transmission and reception (e.g., processor, modulator, multiplexer, demodulator, or demultiplexer, etc.).

[0069] In this application embodiment, the device for implementing the terminal's functions can be a terminal itself; it can also be a device capable of supporting the terminal in implementing those functions, such as a chip system, a communication module, or a modem, etc., which can be installed in the terminal. In this application embodiment, the chip system can be composed of chips, or it can include chips and other discrete devices. In the technical solutions provided in this application embodiment, the device for implementing the terminal's functions is a terminal, and the terminal is a UE (User Equipment) as an example, to describe the technical solutions provided in this application embodiment. The embodiments of this application do not limit the specific technology or specific device form adopted by the terminal device.

[0070] In some scenarios, the UE can also be used as a base station. For example, the UE can act as a scheduling entity, providing sidelink signaling between UEs in vehicle-to-everything (V2X), device-to-device (D2D), or peer-to-peer (P2P) networks.

[0071] In some scenarios, the UE can also be used as a relay node. For example, the UE can act as a relay device or an integrated access and backhaul (IAB) node to provide wireless backhaul services to terminal devices.

[0072] Optionally, a typical application scenario for sidelink communication is vehicle-to-everything (V2X). The method provided in this application can be applied not only to V2X scenarios (as mentioned above) Figure 1aIn scenarios involving communication between 120a and 120b, it can also be applied to sidelink UE-to-Network Relay and sidelink UE-to-UE Relay scenarios. See also Figure 1b , Figure 1b This is a schematic diagram of a Sidelink UE-to-NetworkRelay scenario provided in an embodiment of this application. For example... Figure 1b As shown, the Sidelink UE-to-Network Relay scenario includes a Remote UE and a Relay UE, as well as a base station; the method provided in this application can be applied to communication between the Remote UE and the Relay UE. See also Figure 1c , Figure 1c This is a schematic diagram of a Sidelink UE-to-UE Relay scenario provided in an embodiment of this application. For example... Figure 1c As shown, the Sidelink UE-to-UE Relay scenario includes a Source UE, a Relay UE, and a target UE; the method provided in this application can be applied to communication between the Source UE and the Relay UE and / or communication between the Relay UE and the target UE.

[0073] In the embodiments of this application, the term "wireless communication" can also be abbreviated as "communication", and the term "communication" can also be described as "data transmission", "information transmission" or "transmission".

[0074] To better understand the technical solutions of the embodiments of this application, several terms or nouns related to this application are briefly introduced below so that those skilled in the art can understand them.

[0075] I. Community Search and System Information Acquisition

[0076] The terminal performs a cell search (also known as a network search). After finding the target cell, it obtains system information to confirm whether it can stay in the cell.

[0077] System information is a message sent by the base station that contains information required for terminal initialization as well as information related to some other functions / features.

[0078] System information is divided into minimum system information (Minimum SI) and other system information (Other SI). Minimum system information includes the master information block (MIB) and system information block 1 (SIB1), also known as remaining minimum system information (RMSI). The MIB is periodically broadcast on the broadcast channel (BCH). SIB1 is periodically broadcast on the downlink shared channel (DL-SCH) or sent to RRC-connected terminals via dedicated signaling.

[0079] Other system information consists of other SIBs, such as SIB2 to SIB9. Other SIBs are periodically broadcast on the DL-SCH, or sent on demand (i.e., the network only sends a certain SIB to the UE when a terminal in the RRC idle state (RRC_IDLE) or RRC inactive state (RRC_INACTIVE) requests it; otherwise, it does not send the SIB), or sent to terminals in the RRC connected state via dedicated signaling.

[0080] The basic process for a terminal in the RRC idle state and RRC inactive state to obtain system information is as follows: the terminal first obtains the MIB, then obtains SIB1 based on the scheduling information in the MIB, and then obtains other SIBs based on the scheduling information in SIB1.

[0081] II. RRC State Transitions

[0082] RRC states include RRC idle state (RRC_IDLE), RRC inactive state (RRC_INACTIVE), and RRC connected state (RRC_CONNECTED).

[0083] Different RRC states can be transitioned through different procedures. For example, the connection establishment procedure can typically transition from RRC_IDLE to RRC_CONNECTED; the connection recovery procedure can transition from RRC_INACTIVE to RRC_CONNECTED; and when the terminal is in the RRC_CONNECTED state, it can maintain the RRC_CONNECTED state through the handover and connection reconstruction procedures, or it can transition from RRC_CONNECTED to RRC_INACTIVE or RRC_IDLE through the RRC release procedure.

[0084] (1) Procedure for a terminal to transition from idle state to connected state:

[0085] After the terminal completes cell search and system message acquisition and camps on a cell, it can enter the connected state after the initial access process is completed.

[0086] After entering the RRC_CONNECTED state, optionally, if the network side needs to query the terminal's capabilities, the network side can initiate a terminal capability query process.

[0087] Taking the transition from idle to connected state by a terminal in an NR system as an example, the transition process includes the following steps:

[0088] 1. The terminal requests to establish a new connection in the RRC_IDLE state: It sends an RRC Setup Request to the access network device. At this time, the signaling connection state (non-stratum) between the terminal and the access and mobility management function (AMF) network element is in the connection management-idle (CM-IDLE) state.

[0089] 2. Access network device completes RRC establishment process: The access network device sends an RRC establishment (RRCSetup) message to the terminal, the terminal enters the RRC_CONNECTED state (NAS layer is in CM-IDLE state), and sends an RRC establishment complete (RRCSetupComplete) message to the access network device.

[0090] 3. The access network device sends the first NAS message, namely the Initial UE Message, which is included in the RRC establishment completion message and is transmitted from the access network to the AMF of the core network.

[0091] At this point, the NAS layer is in the connection management-connected state (CM-CONNECTED).

[0092] 4. Other NAS messages exchanged between the terminal and AMF: AMF sends downlink NAS transfer to access network equipment; access network equipment sends downlink information transfer to terminal; terminal sends uplink information transfer to access network equipment; and access network equipment sends uplink NAS transfer to AMF.

[0093] 5. The AMF sends the user context to the access network device: The AMF prepares the terminal context data (including packet data unit (PDU) session context, key, terminal radio capabilities and terminal encryption capabilities, etc.) and sends an initial context setup request to the access network device.

[0094] 6. Access network device activates AS security: The access network device sends a security mode command (SecurityModeCommand) to the terminal; the terminal sends a security mode complete message (SecurityModeComplete) to the access network device.

[0095] 7. The access network device establishes signal radio bearer (SRB)2 and data radio bearer (DRB): the access network device sends an RRC reconfiguration message to the terminal; the terminal sends an RRC reconfiguration complete message to the access network device.

[0096] 8. gNB indicates that the AMF establishment process has been completed: The access network device sends an Initial Context Setup Response to the AMF.

[0097] (2) The process of a terminal transitioning from an inactive state to a connected state:

[0098] The terminal's RRC layer is in the RRC_INACTIVE state, while the NAS layer is in the CM-CONNECTED state. Due to service requirements, the terminal attempts to restore the connection and migrates from the RRC_INACTIVE state to the RRC_CONNECTED state.

[0099] Taking the connection recovery triggered by the terminal in the NR system as an example, the conversion process may include the following steps:

[0100] 1. The terminal sends an RRC recovery request (RRCResumeRequest) to the access network device currently providing services.

[0101] 2. The currently serving access network device obtains the terminal context from the most recently serving access network device (Last Serving gNB): The currently serving access network device sends a request to obtain the terminal context (RETRIEVE UE CONTEXT REQUEST) to the most recently serving access network device, and the most recently serving access network device sends a response to obtain the terminal context (RETRIEVE UE CONTEXT RESPONSE) to the currently serving access network device.

[0102] 3. The access network device currently providing services sends an RRC recovery (RRCResume) message to the terminal.

[0103] The terminal enters the RRC_CONNECTED state, and the NAS layer is in the CM-CONNECTED state.

[0104] 4. The terminal sends an RRC recovery complete message to the access network device.

[0105] 5. The currently providing service access network device sends an XN-U address indication (Xn-UADDRESS INDICATION) message to the nearest providing service access network device. (Optional step)

[0106] 6. The access network device currently providing services sends a path switch request (PATH SWITCH REQUEST) to the AMF.

[0107] 7. The AMF sends a PATH SWITCHREQUEST RESPONSE response to the currently serving access network device.

[0108] 8. The currently providing access network equipment sends a UE CONTEXT RELEASE message to the nearest providing access network equipment.

[0109] (3) Handover process of terminal in connected state:

[0110] The terminal's RRC layer is in the RRC_CONNECTED state. Due to user mobility and other needs, the handover process is triggered while maintaining the RRC_CONNECTED state, attempting to reconnect in the same cell or a new cell.

[0111] Taking the handover of an NR terminal in connected state as an example, the process includes the following steps:

[0112] 1. The source access network device sends a handover request to the target access network device.

[0113] The target access network device performs admission control.

[0114] 2. The target access network device sends a handover request response (HANDOVER REQUESTACKNOWLEDGE) to the source access network device.

[0115] 3. The source access network device sends an RRC reconfiguration message to the terminal.

[0116] The terminal switched to the new cell.

[0117] 4. The terminal sends an RRC reconfiguration complete message to the target access network device.

[0118] (4) The terminal initiates a connection reconstruction process while in the connected state:

[0119] The terminal's RRC layer is in the RRC_CONNECTED state. The handover failed, the reconfiguration failed, or a connection reconstruction was triggered after a related anomaly was detected, attempting to restore the connection in the connected state.

[0120] The reconstruction process begins with cell selection. Once selected, a reconstruction request is sent to attempt to restore the connection. The target cell for reselection may be a new access network (the currently providing access network equipment is different from the most recently providing access network equipment) or the current access network (the currently providing access network equipment is the same as the most recently providing access network equipment).

[0121] After the reconstruction process is successful, the network reallocates relevant resources to the UE through a reconfiguration process, and the UE continues to complete relevant services in the connected state.

[0122] Taking the reconnection rebuilding of an NR terminal in the connected state as an example, the process includes the following steps:

[0123] 1. The terminal's RRC layer is in RRC connected state, and the NAS layer is in CM-CONNECTED state. The terminal sends an RRC Reestablishment Request to the currently providing access network equipment.

[0124] 2. The currently providing access network device obtains the terminal context from the most recently providing access network device: The currently providing access network device sends a request to obtain the terminal context (RETRIEVE UE CONTEXT REQUEST) to the most recently providing access network device, and the most recently providing access network device sends a response to obtain the terminal context (RETRIEVE UE CONTEXT RESPONSE) to the currently providing access network device.

[0125] 3. The access network device currently providing services sends an RRC Reestablishment message to the terminal, and the terminal sends an RRC Reestablishment Complete message to the access network device currently providing services.

[0126] 4. The access network device currently providing the service also sends an RRC reconfiguration message to the terminal, and the terminal sends an RRC reconfiguration completion message to the access network device currently providing the service. (Optional step)

[0127] 5. The currently providing service access network device sends an XN-U address indication message from the nearest providing service access network device. (Optional step)

[0128] 6. The most recently providing service access network device sends an SN STATUS TRANSFER message to the currently providing service access network device. (Optional step)

[0129] 7. The access network device currently providing services sends a path switch request (PATH SWITCH REQUEST) to the AMF.

[0130] 8. The AMF sends a PATH SWITCHREQUEST RESPONSE response to the access network device currently providing services.

[0131] 9. The currently providing access network device sends a terminal context release message from the nearest providing access network device.

[0132] (5) Terminal transition from connected state to idle / inactive state:

[0133] When the terminal's RRC layer is in the RRC_CONNECTED state, if there is no data transmission for a period of time, or if the UE and the base station experience RRC reconfiguration failure, handover failure, radio link failure, or integrity protection failure, the RRC Release procedure is initiated to change the UE from the RRC connected state to the RRC idle state or the RRC inactive state.

[0134] Taking NR terminal exiting the connected state as an example, when the UE is in the RRC connected state and receives an RRC Release message that does not contain suspendConfig, it releases the RRC and the UE transitions from the RRC connected state to the RRC idle state. When the UE is in the RRC connected state and receives an RRC Release message that contains suspendConfig, it suspends the RRC and the UE transitions from the RRC connected state to the RRC inactive state. Furthermore, when the UE is in the RRC inactive state and receives an RRC Release message that does not contain suspendConfig, it releases the RRC and the UE transitions from the RRC inactive state to the RRC idle state.

[0135] First, this application analyzes and proposes the specific technical problem it aims to solve. Currently, in LTE or NR communication systems, there is a type of system information block (which can be called a multi-segment system information block) that can be broadcast in multiple segments. Examples include SIB28 in LTE and SIB12, SIB17, SIB17bis, and SIB23 in NR. The UE needs to receive all segments of a multi-segment SIB to parse the information element (IE) within that SIB and apply its carried parameters. Taking SIB17bis as an example, it can have a total of 64 segments. When the base station broadcasts a segment of SIB17bis, it can carry the segment number (e.g., a value from 0 to 63) and an identifier indicating whether the segment is the last segment (e.g., "not last segment" or "last segment"). After the UE receives all the segments of SIB17bis, it can concatenate all segments according to their segment numbers and then decode the concatenated segments to obtain the final information element.

[0136] In these multi-segment SIBs, some SIBs are only valid in the Radio Resource Control (RRC) idle state or the RRC inactive state. During network search, the UE needs to clear all received segments of this part of the SIB and then re-receive all segments from the beginning. Taking SIB17bis as an example, the protocol stipulates that SIB17bis is only valid in the idle / inactive state, and all received segments must be cleared during network search. The relevant description of the protocol is as follows:

[0137] SIB17bis includes the configuration of tracking reference signal (TRS) resources for idle / inactive UEs.

[0138] Upon receiving SIB17bis, the UE should:

[0139] If the UE has stored at least one segment of SIB17bis, and the value label of SIB17bis has changed since the previous segment was stored:

[0140] >>Discard all stored segments;

[0141] Store this segment;

[0142] If all segments have been received:

[0143] >>Assemble the SIB17bis IE according to the received segments.

[0144] If the SIB17bis is not assembled within 3 hours, the UE should discard any storage segments of the SIB17bis. The UE should discard any storage segments of the SIB17bis during cell (re)selection.

[0145] When a UE transitions from RRC connected state to RRC idle state or RRC inactive state, a network search is required. This means that when the UE transitions from RRC connected state to RRC idle state or RRC inactive state, it needs to clear all received segments of SIB17bis and then re-receive all segments from the beginning. The time required to re-receive all segments is relatively long, which causes the UE to be unable to apply the parameters carried by the cells in SIB17bis in a timely manner. At the same time, the UE receives broadcasts for a longer period of time, and the power consumption also increases.

[0146] To this end, this application proposes a communication method, apparatus, and readable storage medium. After a UE receives one or more segments of a valid first system information block (SIB) in an RRC idle state or an RRC inactive state, when the UE transitions from an RRC connected state to an RRC idle state or an RRC inactive state, it can first determine whether the camping cell in the RRC idle state or the serving cell in the RRC connected state is the same cell, and determine whether the first SIB has changed. When the camping cell and the serving cell are the same cell, and the first SIB has not changed, the UE maintains the received first SIB segments without discarding (clearing) the received first SIB segments and then re-receiving all segments from the beginning. This allows for faster collection of the first SIB segments, enabling faster application of the first SIB parameters, reducing the UE's broadcast reception time, and lowering UE power consumption.

[0147] To better understand the communication method provided in the embodiments of this application, the technical solution of the communication method provided in the embodiments of this application will be described below with reference to more accompanying drawings.

[0148] To clearly describe the technical solution of this application, multiple embodiments will be used to illustrate the technical solution of this application, as detailed below. In this application, unless otherwise specified, the same or similar parts between various embodiments or implementations can be referenced mutually. In the various embodiments of this application, and in the various implementation methods / methods / implementations within each embodiment, unless otherwise specified or logically conflicting, the terminology and / or descriptions between different embodiments and between the various implementation methods / methods / implementations within each embodiment are consistent and can be mutually referenced. The technical features in different embodiments and the various implementation methods / methods / implementations within each embodiment can be combined according to their inherent logical relationships to form new embodiments, implementation methods, methods, or implementation approaches. The embodiments described below do not constitute a limitation on the scope of protection of this application.

[0149] Please see Figure 2 , Figure 2 This is a flowchart illustrating a communication method provided in an embodiment of this application. The method can be applied to a first communication device and may also involve a second communication device. For ease of understanding, the first communication device is exemplified as a terminal device (such as a UE), and the second communication device as an access network device (such as a base station). The terminal device can be one of the aforementioned... Figure 1a Any terminal or module applied to that terminal; or, the terminal device can be any of the aforementioned. Figure 1b Any UE in the above, such as a Relay UE or a Remote UE; or, the terminal device can be one of the aforementioned Figure 1c Any UE in the list, such as Source UE, Relay UE, or Target UE. That is to say, the above... Figure 1a , Figure 1b as well as Figure 1c The terminal devices in the middle can be used to support and execute Figure 2 The method flow shown includes steps S200-S202. Steps S200-S202 include the following:

[0150] S200: The UE receives one or more segments of the first system information block (SIB).

[0151] The first SIB is valid in the RRC idle state or the RRC inactive state. The first SIB supports multi-segment broadcasting by the base station. The one or more segments can be partial or complete segments of the first SIB. Optionally, the one or more segments can be received by the UE in the RRC idle state, the RRC inactive state, or the RRC connected state. Alternatively, the multiple segments can be received by the UE in different RRC states. For example, if there are six segments (segment numbers 0-5), the UE can receive some segments (e.g., segment 0) in the RRC connected state, some segments (e.g., segments 1 and 2) in the RRC idle state, and other segments (e.g., segments 3, 4, and 5) in the RRC inactive state. In this embodiment, the RRC state in which the UE receives the one or more segments is not specifically limited.

[0152] Optionally, the first SIB can be SIB28 in a 4G system, or SIB12, SIB17, SIB17bis or SIB23 in a 5G system, or other system information blocks that support multi-segment broadcasting, without any specific limitations.

[0153] Accordingly, when the base station transmits the first SIB, it needs to divide the complete first SIB into several smaller parts, each called a segment, thus obtaining several segments (including one or more of the aforementioned segments). These segments can then be transmitted to the UE within multiple scheduling cycles of the broadcast control channel. Optionally, when transmitting the first SIB, the base station can broadcast and distribute the segments to the UE sequentially according to their segment numbers, allowing the UE to receive the segments in order. Optionally, the base station can also broadcast and distribute multiple segments of the first SIB out of order to the UE. After receiving multiple segments, the UE can concatenate them sequentially according to their segment numbers. This embodiment does not specifically limit the transmission method of the first SIB segments.

[0154] Optionally, the base station can send the first SIB segment to the UE via a broadcast control channel (BCCH), a dedicated control channel (DCCH), or a common control channel (CCCH), without specific limitations. The broadcast control channel can correspond to the broadcast channel (BCH) or downlink shared channel (DL-SCH) in the transport channel. The dedicated control channel and common control channel can correspond to the transport channel DL-SCH. The transport channel BCH can correspond to the physical broadcast channel (PBCH) in the physical channel, and the transport channel DL-SCH can correspond to the physical downlink shared channel (PDSCH) in the physical channel. In this embodiment, the logical channel, transport channel, and physical channel used by the base station when sending the first SIB are not specifically limited.

[0155] S201: After transitioning from RRC connected state to RRC idle state or RRC inactive state, the UE receives the second SIB.

[0156] The second SIB may include first indication information and second indication information. The first indication information is used to indicate the first cell in which the UE camps in the RRC idle state or the RRC inactive state, and the second indication information is used to indicate whether the first SIB has changed.

[0157] Optionally, the second SIB can be SIB1. The first indication information can be the cell number of the first cell. When the UE transitions from RRC connected state to RRC idle state / RRC inactive state, it needs to select a cell to camp on, thereby ensuring access success rate and shortening access time. Therefore, after obtaining the first SIB, the UE can select the first cell indicated by the first indication information to camp on. The second indication information can be a value tag. The base station can use this parameter to indirectly indicate whether the first SIB has changed, allowing the UE to use this value tag to verify whether the previously obtained first SIB segment is still valid. For example, the value tag can range from 0 to 31 and has a length of 5 bits. When the first SIB changes, the base station can increment the previous value tag value by 1 and send the new value tag value to the UE through the first SIB. When the UE finds that the value tag value included in the first SIB is different from the previously stored value tag value, it can determine that the first SIB has changed and needs to reread the first SIB segment.

[0158] S202: When the first cell and the second cell where the UE camps in the RRC connected state are the same cell, and the first SIB has not changed, the UE maintains the one or more segments of the first SIB.

[0159] For ease of distinction, the cell where the UE camps in RRC idle or RRC inactive state is called the camping cell (i.e., the first cell), and the cell where the UE camps in RRC connected state is called the serving cell (i.e., the second cell). When the UE transitions from RRC connected state to RRC idle or RRC inactive state, if the camping cell selected by the UE in RRC idle or RRC inactive state is the same cell as the serving cell in RRC connected state, and the first SIB has not changed, the UE can maintain the received first SIB segments without discarding (clearing) the received first SIB segments and then re-receiving all segments from the beginning. This allows for faster acquisition of the first SIB segments, enabling faster application of the first SIB parameters, reducing the UE's broadcast reception time, and lowering UE power consumption.

[0160] Optionally, when the UE exits the RRC connection state, it can save the information of the serving cell (such as the cell number) and the previously received valuetag value, so that after the UE receives the second SIB, it can determine whether the camped cell and the previous serving cell are the same cell according to the first indication information, and compare the valuetag of the second indication information with the previously saved valuetag value to determine whether the first SIB has changed.

[0161] In one possible implementation, when the one or more segments are all segments of the first SIB, the UE can decode the one or more segments to apply the parameters in the first SIB. That is, when the UE transitions from RRC connected state to RRC idle state or RRC inactive state, if all segments of the first SIB have been collected, and the UE determines that the camped cell and serving cell are the same cell, and the first SIB has not changed, the UE can choose not to clear the segments of the first SIB, but instead concatenate these segments and decode them, and then apply the decoded information cells, such as configuring the physical layer.

[0162] In one possible implementation, when the one or more segments are partial segments of the first SIB, the UE can continue to receive other segments of the first SIB after exiting the RRC connected state until all segments are received and then decoded. That is, when the UE transitions from the RRC connected state to the RRC idle state or the RRC inactive state, if it has already received partial segments of the first SIB, and the UE determines that the camped cell and the serving cell are the same cell, and the first SIB has not changed, the UE can continue to receive the remaining segments until all segments are received, without clearing the segments of the first SIB. After receiving all segments, it can then splice and decode them, and then apply the decoded information cells.

[0163] Optionally, the UE can perform splicing and decoding after receiving all segments of the first SIB; or it can perform decoding after receiving each segment and apply it after decoding all segments. No specific limitation is made here.

[0164] Optionally, the UE can obtain segments of the first SIB by receiving broadcast messages, or by sending on-demand random access requests. For example, the first SIB has 64 segments (segment numbers 0-63). The UE can first receive a portion of the first SIB segments, such as the first 60 segments, with segment numbers 0-59, by receiving broadcast messages. When the UE transitions from RRC connected state to RRC idle state or RRC inactive state, if the UE's camped cell in the RRC idle state or RRC inactive state is the same cell as the serving cell in the RRC connected state, and the first SIB has not changed, the UE retains the 60 received segments instead of clearing them, and can continue to receive the remaining segments by receiving broadcast messages. The remaining number of segments is 4, with segment numbers 60-63. Alternatively, the UE can obtain the remaining segments by sending on-demand random access requests. Before this, the base station can change the scheduling mode of the first SIB from broadcast mode to on-demand mode, where the number of on-demand random access requests is the same as the number of remaining segments.

[0165] Optionally, the on-demand random access request sent by the UE for the remaining segments can be either a contention-free random access request or a contention-based random access request. For example, for contention-free random access, the base station can pre-configure resources for the first SIB and distribute the resource configuration to the UE. Subsequently, when the UE needs to obtain a segment of the first SIB, it can initiate a contention-free random access request using the pre-allocated resources. When the base station receives this contention-free random access request on the corresponding resources, it can determine that the UE needs a segment of the first SIB. Taking the example of the base station sending the segments of the first SIB to the UE in segment number order, in the above example, the base station has already broadcast the first 60 segments of the first SIB (e.g., segments 0-59). When responding to a contention-free random access request, the base station can continue to carry segment 60 of the first SIB in sequence, while also carrying an identifier that segment 60 is not the last segment of the first SIB (e.g., "notlastsegment"). For example, for contention-based random access, the UE must indicate in the request that it needs a segment of the first SIB, so that when the base station receives the contention-based random access request, it can determine that the UE needs a segment of the first SIB and carry segment 60 of the first SIB in the random access response, along with an identifier that segment 60 is not the last segment of the first SIB. Further, when the UE receives the random access response and obtains segment 60 of the first SIB, it can determine through the identifier that segment 60 is not the last segment of the first SIB, and can then continue to request segments of the first SIB from the base station by sending on-demand random access requests until all segments of the first SIB are obtained. For example, when segment 63 of the first SIB is obtained, it can determine through the identifier that segment 63 is the last segment of the first SIB (e.g., "last segment"). That is to say, an on-demand random access request can be used to request a segment of a multi-segment SIB.

[0166] Optionally, if the base station sends the first SIB segment to the UE out of order, the UE can determine which segment is missing and whether the last segment has been received based on the currently received segments. Thus, when sending the on-demand random access request, the UE can request the specific segment of the first SIB, for example, by indicating the first SIB and the segment number in the random access request, ensuring that the UE continues to complete all segments of the first SIB while maintaining the currently received segments.

[0167] In one possible implementation, when the UE's camping cell and serving cell are different cells, and / or the first SIB changes, the UE clears one or more segments of the first SIB. That is, after the UE transitions from RRC connected state to RRC idle state or RRC inactive state, if the camping cell selected by the UE in RRC idle state or RRC inactive state is different from the serving cell of the UE in RRC connected state, the first SIB can no longer be reused, and the UE can clear the received first SIB segments. Optionally, if the camping cell selected by the UE in RRC idle state or RRC inactive state is the same cell as the serving cell of the UE in RRC connected state, but the first SIB changes, the UE must also clear the received first SIB segments.

[0168] For ease of understanding, the following example illustrates the communication method provided in this application embodiment, using the processing flow where the UE has received all segments of the multi-segment SIB when exiting the RRC connection state as an example.

[0169] For example, see Figure 3 , Figure 3 This is a schematic diagram of the processing flow of a communication method provided in an embodiment of this application. The processing flow may include the following steps:

[0170] S301: After the UE is powered on and camped, it receives segments of the multi-segment SIB.

[0171] After the UE is powered on and camped, it is in the RRC idle state. Simultaneously, the network side schedules a multi-segment SIB, which can be broadcast to the UE. Correspondingly, the UE obtains the multi-segment SIB segments by receiving the broadcast. This multi-segment SIB is valid in the RRC idle state or the RRC inactive state.

[0172] S302: UE enters RRC connection state.

[0173] Optionally, after the UE is powered on and camped, it may send an RRC establishment request to the network side to establish an RRC connection due to reasons such as registration or the user needing to initiate services, and enter the RRC connected state from the RRC idle state.

[0174] S303: The UE continues to receive segments of the multi-segment SIB in the RRC connected state until all segments are received.

[0175] Optionally, after entering the RRC connection state, the UE continues to receive segments of the multi-segment SIB. This may be because the UE remains in the RRC connection state for a long time, or because the number of segments in the multi-segment SIB is small, allowing the UE to receive all remaining segments of the multi-segment SIB while in the RRC connection state. In other words, the UE receives some segments of the multi-segment SIB in step S301 and the remaining segments in step S303, thus receiving all segments of the multi-segment SIB before exiting the RRC connection state.

[0176] S304: The UE transitions from RRC connected state to RRC idle state or RRC inactive state.

[0177] Optionally, the UE can enter the RRC idle state or RRC inactive state by sending a message from the network side to notify the UE to switch from the RRC connected state to the RRC idle state or RRC inactive state; or the UE can switch from the RRC connected state to the RRC idle state or RRC inactive state autonomously.

[0178] S305: When the UE's camp cell and serving cell are the same cell, and the multi-segment SIB has not changed, the UE maintains the segmentation of the multi-segment SIB.

[0179] Optionally, when the UE enters the RRC idle state or RRC inactive state, the selected camp cell is the same cell as the serving cell when the UE is in the RRC connected state, and the multi-segment SIB has not changed, all segments of the multi-segment SIB previously received by the UE can continue to be reused by the UE. Therefore, the UE does not need to clear all segments of the previously received multi-segment SIB, but can instead splice these segments and decode them, thereby applying the decoded information cells, such as configuring the physical layer.

[0180] Optionally, the UE can perform splicing and decoding after receiving all segments of the first SIB; or it can perform decoding after receiving each segment and apply it after decoding all segments. No specific limitation is made here.

[0181] Optionally, when the UE's camped cell and serving cell are different cells, and / or the multi-segment SIB has changed, the UE can clear all segments of the previously received multi-segment SIB.

[0182] The following example illustrates the communication method provided in this application embodiment by taking the processing flow of the UE not receiving all segments of the multi-segment SIB when exiting the RRC connection state as an example.

[0183] For example, see Figure 4 , Figure 4 This is a schematic diagram of the processing flow of another communication method provided in an embodiment of this application. The processing flow may include the following steps:

[0184] S401: After the UE is powered on and camped, it receives segments of the multi-segment SIB.

[0185] The multi-segment SIB is valid in the RRC idle state or the RRC inactive state. The UE can obtain the segments of the multi-segment SIB by receiving broadcast messages.

[0186] S402: UE enters RRC connection state.

[0187] S403: The UE continues to receive segments of the multi-segment SIB in RRC connected state, but has not received all segments of the multi-segment SIB.

[0188] Optionally, after entering the RRC connected state, the UE continues to receive segments of the multi-segment SIB. This may be because the duration of the UE's RRC connected state is short, or because the number of segments in the multi-segment SIB is large, and the UE was unable to receive all the remaining segments of the multi-segment SIB while in the RRC connected state. That is to say, the UE received a portion of the multi-segment SIB segments in step S401, and also received a portion of the multi-segment SIB segments in step S403, leaving a portion of the multi-segment SIB segments that the UE has not yet received.

[0189] S404: The UE transitions from RRC connected state to RRC idle state or RRC inactive state.

[0190] S405: When the UE's camp cell and serving cell are the same cell, and the multi-segment SIB has not changed, the UE maintains the segments of the received multi-segment SIB.

[0191] Since the cell selected by the UE when entering the RRC idle state or RRC inactive state is the same cell as the serving cell when the UE is in the RRC connected state, and the multi-segment SIB has not changed, the segments of the multi-segment SIB previously received by the UE can continue to be reused by the UE. Therefore, the UE does not need to clear the segments of the multi-segment SIB previously received (including the segments received in steps S401 and S403).

[0192] S406: The UE continues to receive segments of the multi-segment SIB until all segments of the multi-segment SIB are received.

[0193] Optionally, while maintaining the previously received segments of the multi-segment SIB, the UE can continue to receive the remaining segments of the multi-segment SIB in the RRC idle state or RRC inactive state until all segments of the multi-segment SIB are received. Optionally, after receiving all segments of the multi-segment SIB, the UE can perform splicing and secondary decoding, and then apply the decoded information cells, such as configuring the physical layer. Optionally, when the UE is in the RRC idle state or RRC inactive state, it can obtain the remaining segments of the multi-segment SIB by receiving broadcast messages, or by sending on-demand random access requests. For example, the number of on-demand random access requests is the same as the number of remaining segments of the multi-segment SIB, that is, one on-demand random access request can be used to request one segment of the multi-segment SIB.

[0194] Optionally, the UE can perform splicing and decoding after receiving all segments of the first SIB; or it can perform decoding after receiving each segment and apply it after decoding all segments. No specific limitation is made here.

[0195] It should be noted that the UE may receive part or all segments of the multi-segment SIB when it is powered on and camped in the RRC idle state, and may stop receiving segments of the multi-segment SIB when it enters the RRC connected state; or, the UE may not receive segments of the multi-segment SIB when it is powered on and camped in the RRC idle state, but may receive part or all segments of the multi-segment SIB after entering the RRC connected state. In this embodiment, the RRC state in which the UE receives segments of the multi-segment SIB is not specifically limited, and no further examples are given here.

[0196] The foregoing describes the method provided in this application. In order to facilitate the implementation of the above-described solutions in the embodiments of this application, the embodiments of this application also provide corresponding devices or equipment.

[0197] This application divides the device into functional modules according to the above method embodiments. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated modules can be implemented in hardware or as software functional modules. It should be noted that the module division in this application is illustrative and only represents one logical functional division; other division methods may be used in actual implementation. The device of the embodiments of this application will be described below with reference to the accompanying drawings.

[0198] Please see Figure 5 , Figure 5 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application. The communication device 10 can be used to implement the function of the first communication device involved in any of the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments.

[0199] like Figure 5 As shown, the communication device 10 may include a receiving unit 100 and a processing unit 101. Optionally, the communication device 10 may further include a transmitting unit. The functions of each unit are as follows:

[0200] The receiving unit 100 is configured to receive one or more segments of the first system information block (SIB); the first SIB is valid in the Radio Resource Control (RRC) idle state or the RRC inactive state.

[0201] The receiving unit 100 is further configured to receive a second SIB after the first communication device transitions from the RRC connected state to the RRC idle state or the RRC inactive state; the second SIB includes first indication information and second indication information, the first indication information is used to indicate the first cell in which the first communication device camps in the RRC idle state or the RRC inactive state, and the second indication information is used to indicate whether the first SIB has changed.

[0202] Processing unit 101 is configured to maintain the one or more segments of the first SIB when the first cell and the second cell in which the first communication device receives service under the RRC connection state are the same cell and the first SIB has not changed.

[0203] In one possible implementation, the receiving unit 100 is specifically configured to receive one or more segments of the first SIB in the RRC idle state or RRC inactive state; the first communication device enters the RRC connected state and camps in the second cell.

[0204] In one possible implementation, the first communication device enters the RRC connection state and camps in the second cell; the receiving unit 100 is specifically used to receive one or more segments of the first SIB in the RRC connection state.

[0205] In one possible implementation, the receiving unit 100 is specifically configured to: receive a portion of the plurality of segments of the first SIB in the RRC idle state or RRC inactive state;

[0206] The first communication device enters the RRC connection state and camps in the second cell;

[0207] The receiving unit 100 is further configured to: receive another portion of the plurality of segments of the first SIB in the RRC connection state.

[0208] In one possible implementation, the processing unit 101 is further configured to clear one or more segments of the first SIB when the first cell and the second cell are different cells, and / or when the first SIB changes.

[0209] Optionally, the sending unit can be used to send messages to other communication devices, for example, to send an on-demand random access request to a base station.

[0210] It should be noted that the functions of each functional unit / module in the communication device described in the embodiments of this application can be found in the relevant descriptions in the above method embodiments, and will not be repeated here.

[0211] Understandably, the specific descriptions of the processing unit, sending unit, and receiving unit shown in the above device embodiments are merely examples. For the specific functions or execution steps of the processing unit, sending unit, and receiving unit, please refer to the description of any of the above method embodiments, which will not be detailed here.

[0212] The communication device according to embodiments of this application has been described above. The following describes possible product forms of the communication device. It should be understood that any device possessing the above-described features... Figure 5 Any form of the communication device described herein falls within the protection scope of the embodiments of this application. It should also be understood that the following description is merely illustrative and does not limit the form of the communication device in the embodiments of this application to this specific example.

[0213] In one possible implementation, the above Figure 5 In the communication device shown, the receiving unit 100 and the transmitting unit can be transceivers; or, the receiving unit 100 can be a receiver and the transmitting unit can be a transmitter; the processing unit 101 can be a processor, which can be used to process information received by the transceiver or generate information transmitted by the transceiver. The processor and the transceiver can be coupled, etc. The connection method between the processor and the transceiver is not limited in this embodiment. During the execution of the above method, the process of transmitting information can be understood as the process of the processor outputting the information. When outputting the information, the processor outputs the information to the transceiver so that the transceiver can transmit it. After the information is output by the processor, it may need to undergo other processing before reaching the transceiver. Similarly, the process of receiving information in the above method can be understood as the process of the processor receiving the input information. When the processor receives the input information, the transceiver receives the information and inputs it to the processor. Furthermore, after the transceiver receives the information, the information may need to undergo other processing before being input to the processor.

[0214] See Figure 6 , Figure 6This is a schematic diagram of another communication device provided in an embodiment of this application. The communication device 20 can be the communication device 10, or a chip therein. Figure 6 Only the main components of the communication device 20 are shown. In addition to the processor 1001, the communication device 20 may optionally further include a transceiver 1002, a memory 1003, or an input / output device (not shown).

[0215] The processor 1001 is mainly used to process communication protocols and communication data, control the entire communication device, execute software programs, and process the data of the software programs. The memory 1003 is mainly used to store software programs and data. The transceiver 1002 may include control circuitry and an antenna. The control circuitry is mainly used for converting baseband signals to radio frequency signals and processing radio frequency signals. The antenna is mainly used for transmitting and receiving radio frequency signals in the form of electromagnetic waves. Input / output devices, such as touchscreens, displays, and keyboards, are mainly used to receive user input data and output data to the user.

[0216] When the communication device is powered on, the processor 1001 can read the software program in the memory 1003, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be transmitted wirelessly, the processor 1001 performs baseband processing on the data to be transmitted and outputs the baseband signal to the radio frequency (RF) circuit. The RF circuit processes the baseband signal and transmits the RF signal outward in the form of electromagnetic waves through the antenna. When data is sent to the communication device, the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor 1001. The processor 1001 converts the baseband signal into data and processes the data.

[0217] In another implementation, the radio frequency circuitry and antenna can be set up independently of the processor performing baseband processing. For example, in a distributed scenario, the radio frequency circuitry and antenna can be arranged remotely, independent of the communication device.

[0218] Transceiver 1002 may include a receiver for performing a receiving function (or operation) and a transmitter for performing a transmitting function (or operation). The transceiver is also used for communicating with other devices / appliances via a transmission medium.

[0219] The processor 1001, transceiver 1002, and memory 1003 can be connected via a communication bus.

[0220] For example, when the communication device 20 is used to perform the steps, methods, or functions involved in the first communication device described above, the transceiver 1002 can be used to receive one or more segments of the first system information block (SIB); the first SIB is valid in the Radio Resource Control (RRC) idle state or the RRC inactive state; the transceiver 1002 is also used to receive a second SIB after the first communication device transitions from the RRC connected state to the RRC idle state or the RRC inactive state; the second SIB includes first indication information and second indication information, the first indication information is used to indicate the first cell in which the first communication device camps in the RRC idle state or the RRC inactive state, and the second indication information is used to indicate whether the first SIB has changed; the processor 1001 is used to maintain the one or more segments of the first SIB when the first cell and the second cell in which the first communication device receives service in the RRC connected state are the same cell, and the first SIB has not changed. Optionally, the memory 1003 can be used to store data necessary for the operation of the communication device and related data during data processing.

[0221] Understandably, further details regarding the processor and transceiver can be found above. Figure 5 The descriptions of the processing unit and the transmitting unit in the device embodiments involved will not be repeated here.

[0222] Optionally, the processor 1001 may include a transceiver for implementing receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, or interface circuit can be used for reading and writing code / data, or it can be used for transmitting or relaying signals.

[0223] Optionally, the processor 1001 may store instructions, which may be a computer program. The computer program, running on the processor 1001, causes the communication device 20 to perform the methods described in the above method embodiments. The computer program may be embedded in the processor 1001; in this case, the processor 1001 may be implemented in hardware.

[0224] In one implementation, the communication device 20 may include circuitry capable of performing the functions of transmitting, receiving, or communicating as described in the aforementioned method embodiments. The processor and transceiver described in this application can be implemented on integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed-signal ICs, application-specific integrated circuits (ASICs), printed circuit boards (PCBs), electronic devices, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal-oxide semiconductors (CMOS), n-metal-oxide-semiconductor (NMOS), p-type metal-oxide semiconductors (PMOS), bipolar junction transistors (BJTs), bipolar CMOS (BiCMOS), silicon-germanium (SiGe), gallium arsenide (GaAs), etc.

[0225] Understandably, the communication device shown in the embodiments of this application may also have more than Figure 6 This application does not limit the use of other components or other related elements. The methods performed by the processor and transceiver described above are merely examples; for the specific steps performed by the processor and transceiver, please refer to the description of the method embodiments above.

[0226] In another possible implementation Figure 5 In the communication device involved, the processing unit 101 can be one or more logic circuits; the receiving unit 100 and the transmitting unit can be input / output interfaces, or communication interfaces, or interface circuits, or interfaces, etc. Alternatively, the transmitting unit can be an output interface, and the receiving unit can be an input interface, with the transmitting unit and receiving unit integrated into one unit, such as an input / output interface. See also Figure 7 , Figure 7 This is a schematic diagram of the structure of another communication device provided in the embodiments of this application. For example... Figure 7As shown, the communication device 30 includes a logic circuit 901 and an interface 902. That is, the processing unit 101 can be implemented using the logic circuit 901, and the receiving unit 100 and the transmitting unit can be implemented using the interface 902. The logic circuit 901 can be a chip, processing circuit, integrated circuit, or system-on-chip (SoC) chip, etc., and the interface 902 can be a communication interface, input / output interface, pins, etc. For example, Figure 7 The above-mentioned communication device 30 is used as an example of a chip, which includes a logic circuit 901 and an interface 902.

[0227] In this embodiment, the logic circuit and the interface can also be coupled to each other. The specific connection method between the logic circuit and the interface is not limited in this embodiment.

[0228] For example, when the communication device 30 is used to perform the method, function, or step involved in the first communication device described above, the interface 902 is used to receive one or more segments of the first system information block (SIB); the first SIB is valid in the Radio Resource Control (RRC) idle state or the RRC inactive state; the interface 902 is also used to receive a second SIB after the first communication device transitions from the RRC connected state to the RRC idle state or the RRC inactive state; the second SIB includes first indication information and second indication information, the first indication information is used to indicate the first cell in which the first communication device camps in the RRC idle state or the RRC inactive state, and the second indication information is used to indicate whether the first SIB has changed; the logic circuit 901 is used to maintain the one or more segments of the first SIB when the first cell and the second cell in which the first communication device receives service in the RRC connected state are the same cell, and the first SIB has not changed.

[0229] Understandably, the specific descriptions of logic circuit 901 and interface 902 can also be found above. Figure 5 The descriptions of the processing unit, transmitting unit, and receiving unit involved in the device embodiments are not repeated here.

[0230] It is understood that the communication device shown in the embodiments of this application can implement the method provided in the embodiments of this application in hardware form or in software form, etc., and the embodiments of this application do not limit it in this way.

[0231] for Figure 7 For specific implementations of the various embodiments shown, please refer to the above embodiments, which will not be described in detail here.

[0232] In addition, this application also provides a computer program for implementing the operations and / or processes performed by the communication device 10, communication device 20, and communication device 30 in the method provided in this application.

[0233] This application also provides a readable storage medium storing computer code that, when executed on a computer, causes the computer to perform the operations and / or processes performed by the communication device 10, communication device 20, and communication device 30 in the method provided in this application.

[0234] This application also provides a computer program product, which includes computer code or a computer program that, when run on a computer, causes the operations and / or processes performed by communication device 10, communication device 20, and communication device 30 in the method provided in this application to be executed.

[0235] This application also provides a chip system including a processor for supporting the device in implementing the functions involved in any of the above embodiments, such as generating or processing information involved in the above communication methods. In one possible design, the chip system further includes a memory for storing necessary program instructions and data for the device. This chip system may be composed of chips or may include chips and other discrete devices.

[0236] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0237] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0238] In the several embodiments provided in this application, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, or it may be an electrical, mechanical or other form of connection.

[0239] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, Applied to a first communication device; the method includes: Receive one or more segments of the first system information block (SIB); the first SIB is valid in the Radio Resource Control (RRC) idle state or the RRC inactive state; After the first communication device transitions from the RRC connected state to the RRC idle state or the RRC inactive state, it receives the second SIB; the second SIB includes first indication information and second indication information, the first indication information is used to indicate the first cell in which the first communication device camps in the RRC idle state or the RRC inactive state, and the second indication information is used to indicate whether the first SIB has changed. When the first cell and the second cell where the first communication device is camped in the RRC connection state are the same cell, and the first SIB has not changed, the one or more segments of the first SIB are maintained.

2. The method as described in claim 1, characterized in that, The receiving of one or more segments of the first SIB includes: receiving the one or more segments of the first SIB in the RRC idle state or the RRC inactive state; The method further includes: entering the RRC connection state and residing in the second cell.

3. The method as described in claim 1, characterized in that, The receiving of one or more segments of the first SIB includes: Enter RRC connection state and camp on the second cell; In the RRC connection state, the first SIB receives one or more segments.

4. The method as described in claim 1, characterized in that, The segment for receiving the first SIB includes: Receive a portion of the plurality of segments of the first SIB in the RRC idle state or RRC inactive state; Enter the RRC connection state and camp on the second cell; In the RRC connection state, another portion of the plurality of segments of the first SIB is received.

5. The method according to any one of claims 1-4, characterized in that, Also includes: When the first cell and the second cell are different cells, and / or when the first SIB changes, the one or more segments of the first SIB are cleared.

6. A first communication device, characterized in that, include: The receiving unit is configured to receive one or more segments of a first system information block (SIB); the first SIB is valid in the Radio Resource Control (RRC) idle state or the RRC inactive state. The receiving unit is further configured to receive a second SIB after the first communication device transitions from the RRC connected state to the RRC idle state or the RRC inactive state; the second SIB includes first indication information and second indication information, the first indication information is used to indicate the first cell in which the first communication device camps in the RRC idle state or the RRC inactive state, and the second indication information is used to indicate whether the first SIB has changed; The processing unit is configured to maintain the one or more segments of the first SIB when the first cell and the second cell in which the first communication device receives service under the RRC connection state are the same cell and the first SIB has not changed.

7. The apparatus as claimed in claim 6, characterized in that, The receiving unit is specifically used to receive one or more segments of the first SIB in the RRC idle state or RRC inactive state; the first communication device enters the RRC connected state and camps in the second cell.

8. The apparatus as claimed in claim 6, characterized in that, The first communication device enters the RRC connection state and camps in the second cell; the receiving unit is specifically used to receive one or more segments of the first SIB in the RRC connection state.

9. The apparatus as claimed in claim 6, characterized in that, The receiving unit is specifically configured to: receive a portion of the plurality of segments of the first SIB in the RRC idle state or the RRC inactive state; The first communication device enters the RRC connection state and camps in the second cell; The receiving unit is further configured to: receive another portion of the plurality of segments of the first SIB in the RRC connection state.

10. The apparatus according to any one of claims 6-9, characterized in that, The processing unit is further configured to clear one or more segments of the first SIB when the first cell and the second cell are different cells, and / or when the first SIB changes.

11. A communication device, characterized in that, The device includes a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices and transmit them to the processor or to send signals from the processor to other communication devices, and the processor is used to implement the method as described in any one of claims 1-5 through logic circuits or executing code instructions.

12. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions, which, when executed by a communication device, implement the method as described in any one of claims 1-5.

13. A computer program, characterized in that, The computer program includes instructions that, when executed by a communication device, implement the method as described in any one of claims 1-5.

Images