A communication method, a communication device, and a communication system

Abstract

This application provides a communication method, communication device, and communication system, relating to the field of communication technology. The method includes: a first network device receiving a first message. The first message contains a target field indicating that a terminal device should receive information about ODSIB1. The first network device updates the conditions for the terminal device to access a first cell and / or updates the list of second cells associated with the first cell based on the target field. Updating the conditions for the terminal device to access the first cell can restrict access for some terminal devices that are not suitable for accessing the first cell, thereby saving energy for both the terminal device and the first network device. Updating the list of second cells associated with the first cell. The network device corresponding to the second cell is used to broadcast a wake-up signal configuration to the terminal device. This optimizes the second cell list, making it more effective at broadcasting the wake-up signal configuration to the terminal device, thereby enabling the terminal device to obtain ODSIB1 by sending an uplink wake-up signal.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method, communication device and communication system. Background Technology

[0002] In wireless network schemes based on self-organizing networks (SON), the base station sends request messages to request relevant information from terminal devices. The terminal devices then send response messages to the base station containing connection status and performance data (e.g., signal quality, interference, and handover information). The base station evaluates the current connection quality and the surrounding network environment based on the response messages. Based on the analysis results, the base station can dynamically optimize connection strategies, such as adjusting handover parameters, optimizing resource allocation, and improving coverage and signal quality.

[0003] Before a terminal device accesses the network, the concept of System Information Block 1 (SIB1) is involved. SIB1, as an important broadcast message, is primarily used to assist terminal devices in accessing the network. Currently, based on SIB1, a new scheme for optimizing network performance using On-Demand (OD) SIB1 has been developed. The main purpose is to prevent base stations from periodically broadcasting SIB1, but rather to broadcast it only when a terminal device has an access request. For example, when a terminal device sends a wakeup signal (WUS), it triggers the broadcast of SIB1, effectively reducing unnecessary transmissions and saving resources. However, the specific optimization scheme for ODSIB1 is currently unclear. Summary of the Invention

[0004] This application provides a communication method, communication device, and communication system. This solution improves the flexibility of transmission during the transmission of on-demand system information block 1 by using data reported by the terminal.

[0005] The technical solution is as follows:

[0006] In a first aspect, embodiments of this application provide a communication method, including: a first network device receiving a first message. The first message includes a target field, which is used to instruct a terminal device to receive ODSIB1 information. The first network device updates the conditions for the terminal device to access a first cell and / or updates a list of second cells associated with the first cell based on the target field. The first cell is a cell covered by the first network device. A network device corresponding to any second cell in the second cell list is used to broadcast a wake-up signal configuration of the first network device to the terminal device. The wake-up signal configuration is used by the terminal device to send an uplink wake-up signal to the first network device, and the uplink wake-up signal is used to trigger the first network device to send ODSIB1 to the terminal device.

[0007] In this application, a first network device receives a first message. Since the first message includes a target field, which instructs the terminal device to receive ODSIB1 information, the first network device can determine the terminal device's access information report for the first cell. The first network device can update the conditions for the terminal device to access the first cell based on the target field. This restricts access for some terminal devices that are not suitable for accessing the first cell, thereby reducing the number of failed access attempts and the number of times the first network device sends ODSIB1. Alternatively, the first network device can update the list of second cells associated with the first cell based on the target field. A second network device corresponding to any second cell in the second cell list broadcasts a wake-up signal configuration to the terminal device. This wake-up signal configuration is used by the terminal device to send an uplink wake-up signal to the first network device, instructing the first network device to send ODSIB1 to the terminal device. This optimizes the second cell list, making it more effective at broadcasting the wake-up signal configuration to the terminal device, thus enabling the terminal device to obtain ODSIB1 by sending the uplink wake-up signal.

[0008] In one possible implementation, the first network device updates the list of first cells containing the first cell based on the target field, and / or disables the network power-saving mode of the first cell. The network power-saving mode is used by the first network device to send ODSIB1 to the terminal device.

[0009] As an example, when too many terminal devices access the first cell, their signals may interfere with each other, preventing the first network device from correctly decoding these signals. Furthermore, too many terminal devices accessing the first cell may overload it, impacting network performance. Therefore, when too many terminal devices access the first cell, it is necessary to prevent the first cell from sending ODSIB1 to the terminal devices. Updating the list of first cells and / or disabling the network power-saving mode of the first cell can prevent the terminal devices currently accessing the first cell from sending ODSIB1, achieving energy-saving goals without affecting normal terminal device access.

[0010] In one possible implementation, the target field is used to indicate one or more of the following information: signal measurement results, random access response content, number of attempts, mobility status, location information, connection failure type, and the identifier of the first cell to which a connection was attempted.

[0011] In one possible implementation, before the first network device receives the first message, the method provided in this application embodiment further includes: the first network device establishing an RRC connection with the terminal device. The first network device then sends a second message to the terminal device through the RRC connection.

[0012] The second message is used to request the terminal device to provide information for receiving ODSIB1. This enables the terminal device to provide information for receiving ODSIB1.

[0013] In one possible implementation, the first network device receiving the first message includes: the first network device receiving the first message from a second network device. The second network device has a wake-up signal configuration, and there is an RRC connection between the second network device and the terminal device. Thus, the second network device with the wake-up signal configuration can be used to forward the first message, enabling the first network device to perform policy adjustments.

[0014] In one possible implementation, the method provided in this application further includes: a first network device receiving indication information from a second network device. The indication information is used to instruct the second network device to stop broadcasting wake-up signal configuration to the terminal device. In this way, by having the first network device stop broadcasting wake-up signal configuration, unnecessary ODSIB1 broadcasts are reduced.

[0015] In one possible implementation, the first network device receiving the first message includes: the first network device receiving the first message from the second network device. The second network device does not have a wake-up signal configuration, and the terminal device has an RRC connection with the second network device. Thus, the second network device, which does not have a wake-up signal configuration, can be used to forward the first message, enabling the first network device to perform policy adjustments.

[0016] In one possible implementation, the method provided in this application further includes: a first network device receiving a request message from a second network device. The request message is used to request the broadcast of a wake-up signal configuration to a terminal device. This allows the second network device to begin broadcasting the wake-up signal configuration, increasing its coverage and reducing the number of times the terminal device fails to access the first network device.

[0017] Secondly, embodiments of this application provide a communication method, comprising: a second network device sending a second message to a terminal device. The second message is used to request the terminal device to provide information for receiving ODSIB1 sent by a first network device. The second network device receives a first message from the terminal device. The first message includes a target field, which is used to indicate that the terminal device receives the ODSIB1 information. The second network device and the terminal device have an RRC connection. The second network device is used to broadcast a wake-up signal configuration of the first network device to the terminal device. The wake-up signal configuration is used by the terminal device to send an uplink wake-up signal to the first network device, and the uplink wake-up signal is used to trigger the first network device to send ODSIB1 to the terminal device.

[0018] In one possible implementation, the method provided in this application further includes: a second network device sending indication information to a first network device. The indication information is used to instruct the second network device to stop broadcasting the wake-up signal configuration of the first network device to the terminal device. The second network device has a wake-up signal configuration.

[0019] In another possible implementation, the second network device sends a request message to the first network device. The request message requests that the wake-up signal configuration of the first network device be broadcast to the terminal device. In this implementation, the second network device does not have a wake-up signal configuration. It is understood that after the second network device sends the request message to the first network device, the second network device may also receive a response message from the first network device, which includes the wake-up signal configuration of the first network device.

[0020] Thirdly, embodiments of this application provide a communication method, the method comprising: a terminal device receiving a second message from a first network device or a second network device. The second message is used to request the terminal device to provide information for receiving ODSIB1 sent by the first network device. The second network device is a network device configured to broadcast a wake-up signal of the first network device to the terminal device. The wake-up signal configuration is used by the terminal device to send an uplink wake-up signal to the first network device. The uplink wake-up signal is used to trigger the first network device to send ODSIB1 to the terminal device. The terminal device sends a first message to the first network device or the second network device, the first message including a target field, the target field being used to instruct the terminal device to receive the ODSIB1 information. The second network device may be a network device with a wake-up signal configuration or a network device without a wake-up signal configuration, but the second network device has the capability to broadcast the wake-up signal configuration of the first network device to the terminal device.

[0021] Fourthly, embodiments of this application provide a communication device that can implement the methods in the first aspect or any possible implementation of the first aspect, and therefore can also achieve the beneficial effects of the first aspect or any possible implementation of the first aspect. This communication device can be a first network device, or it can be an apparatus that supports the first network device in implementing the methods in the first aspect or any possible implementation of the first aspect, such as a chip applied in the first network device. This device can implement the above methods through software, hardware, or by hardware executing corresponding software.

[0022] Fifthly, embodiments of this application provide a communication device that can implement the methods in the second aspect or any possible implementation of the second aspect, and therefore can also achieve the beneficial effects of the second aspect or any possible implementation of the second aspect. This communication device can be a second network device, or it can be an apparatus that supports the second network device in implementing the methods in the second aspect or any possible implementation of the second aspect, such as a chip applied in the second network device. This device can implement the above methods through software, hardware, or by hardware executing corresponding software.

[0023] Sixthly, embodiments of this application provide a communication device that can implement the methods in the third aspect or any possible implementation of the third aspect, and thus also achieve the beneficial effects of the third aspect or any possible implementation of the third aspect. This communication device can be a terminal device, or an apparatus that supports the terminal device in implementing the methods in the third aspect or any possible implementation of the third aspect, such as a chip applied in the terminal device. This device can implement the above methods through software, hardware, or hardware executing corresponding software.

[0024] In a seventh aspect, embodiments of this application provide a computer-readable storage medium storing a computer program or instructions that, when executed on a computer, cause the computer to perform a communication method as described in any of the possible implementations of the first aspect.

[0025] Eighthly, embodiments of this application provide a computer-readable storage medium storing a computer program or instructions that, when executed on a computer, cause the computer to perform a communication method as described in any of the possible implementations of the second aspect.

[0026] Ninthly, embodiments of this application provide a computer-readable storage medium storing a computer program or instructions that, when executed on a computer, cause the computer to perform a communication method as described in any of the possible implementations of the third aspect to the third aspect.

[0027] In a tenth aspect, embodiments of this application provide a computer program product including instructions that, when executed on a computer, cause the computer to perform a communication method described in the first aspect or various possible implementations of the first aspect.

[0028] Eleventhly, embodiments of this application provide a computer program product including instructions that, when executed on a computer, cause the computer to perform a communication method described in the second aspect or various possible implementations of the second aspect.

[0029] In a twelfth aspect, embodiments of this application provide a computer program product including instructions that, when executed on a computer, cause the computer to perform a communication method described in the third aspect or various possible implementations of the third aspect.

[0030] In a thirteenth aspect, embodiments of this application provide a communication device for implementing various methods in various possible designs of any of the first, second, or third aspects described above. The communication device may be the first network device, or a device comprising the first network device, or a component (e.g., a chip) applied to the first network device. Alternatively, the communication device may be the second network device, or a device comprising the second network device, or a component (e.g., a chip) applied to the second network device. Alternatively, the communication device may be the terminal device, or a device comprising the terminal device, or a component (e.g., a chip) applied to the terminal device. The communication device includes modules and units corresponding to the methods described above. These modules and units may be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above.

[0031] It should be understood that the communication device described in aspect thirteen above may further include: a bus and a memory, the memory being used to store code and data. Optionally, at least one processor communication interface and the memory are coupled to each other.

[0032] In a fourteenth aspect, embodiments of this application provide a communication device comprising at least one processor. The at least one processor is coupled to a memory, and when the communication device is in operation, the processor executes computer execution instructions or programs stored in the memory to cause the communication device to perform any of the various possible designs of the first aspect or any other aspect thereof. For example, the communication device may be a first network device, or a chip applied in a first network device.

[0033] In a fifteenth aspect, embodiments of this application provide a communication device comprising: at least one processor. The at least one processor is coupled to a memory, and when the communication device is in operation, the processor executes computer execution instructions or programs stored in the memory to cause the communication device to perform a method as described in the second aspect above, or any of the various possible designs of the second aspect. For example, the communication device may be a second network device, or a chip applied in a second network device.

[0034] In a sixteenth aspect, embodiments of this application provide a communication device comprising: at least one processor. The at least one processor is coupled to a memory, and when the communication device is in operation, the processor executes computer execution instructions or programs stored in the memory to cause the communication device to perform any of the methods described in the third aspect or any of the various possible designs of the third aspect. For example, the communication device may be a terminal device or a chip applied in a terminal device.

[0035] It should be understood that the memory described in any of aspects fourteen to sixteen can also be replaced by a storage medium, and the embodiments of this application do not limit this.

[0036] In one possible implementation, the memory described in any of aspects fourteen through sixteen can be internal to the communication device. Of course, the memory can also be located external to the communication device, but at least one processor can still execute computer execution instructions or programs stored in the memory.

[0037] In a seventeenth aspect, embodiments of this application provide a communication device comprising one or more modules for implementing the methods of any one of the first, second, and third aspects described above. The one or more modules may correspond to the various steps in the methods of any one of the first, second, and third aspects described above.

[0038] In an eighteenth aspect, embodiments of this application provide a chip system including a processor. The processor reads and executes a computer program stored in a memory to perform the methods of the first aspect and any possible implementation thereof. Optionally, the chip system may be a single chip or a chip module composed of multiple chips. Optionally, the chip system further includes a memory, which is connected to the processor via circuitry or wiring. Further optionally, the chip system includes a communication interface. The communication interface is used to communicate with other modules outside the chip.

[0039] In a nineteenth aspect, embodiments of this application provide a chip system including a processor. The processor reads and executes a computer program stored in a memory to perform the methods in the second aspect and any possible implementation thereof. Optionally, the chip system may be a single chip or a chip module composed of multiple chips. Optionally, the chip system further includes a memory, which is connected to the processor via a circuit or wire. Further optionally, the chip system also includes a communication interface. The communication interface is used to communicate with other modules outside the chip.

[0040] In a twentieth aspect, embodiments of this application provide a chip system including a processor. The processor reads and executes a computer program stored in a memory to perform the methods in the third aspect and any possible implementation thereof. Optionally, the chip system may be a single chip or a chip module composed of multiple chips. Optionally, the chip system further includes a memory, which is connected to the processor via circuitry or wiring. Further optionally, the chip system includes a communication interface. The communication interface is used to communicate with other modules outside the chip.

[0041] In a twentieth aspect, embodiments of this application provide a communication system comprising: a first network device and a terminal device. The first network device is configured to execute the methods of the first aspect and any possible implementation thereof. The terminal device is configured to execute the methods of the third aspect and any possible implementation thereof.

[0042] Optionally, the communication system may further include a second network device for performing the methods in the second aspect and any possible implementation thereof. The second network device may or may not have a wake-up signal configuration.

[0043] Any of the devices, computer storage media, computer program products, chips, or communication systems provided above are used to execute the corresponding methods provided above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects of the corresponding solutions in the corresponding methods provided above, and will not be repeated here. Attached Figure Description

[0044] Figure 1 This is a schematic diagram of the architecture of a communication system provided in an embodiment of this application;

[0045] Figure 2 This is a schematic diagram of a self-organizing network technology provided in an embodiment of this application;

[0046] Figure 3 This is a schematic diagram illustrating the interaction between a network device and a terminal device provided in an embodiment of this application;

[0047] Figure 4 This is a schematic diagram of the various data included in a UEInformationResponse provided in an embodiment of this application;

[0048] Figure 5 This is a schematic diagram of the various data included in a ConnEstFailReport provided in an embodiment of this application;

[0049] Figure 6 This is a schematic diagram of the various data included in a ra-ReportList provided in an embodiment of this application;

[0050] Figure 7 This is a schematic diagram of the various data included in a mobilityHistoryReport provided in an embodiment of this application;

[0051] Figure 8 This is a schematic diagram comparing the processes of conventional SIB1 and on-demand SIB1 provided in an embodiment of this application;

[0052] Figure 9 This is a flowchart illustrating an ODSIB1 provided in an embodiment of this application;

[0053] Figure 10 This is a schematic diagram illustrating the relationship between CellA and CellX and an NES cell, provided in an embodiment of this application.

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

[0055] Figure 12 This is a schematic diagram illustrating a specific implementation of a communication method provided in an embodiment of this application;

[0056] Figure 13 This is a schematic flowchart of a communication method for updating the wake-up signal configuration, provided in an embodiment of this application.

[0057] Figure 14 This is a schematic diagram of a communication method for updating the CellA list, provided in an embodiment of this application.

[0058] Figure 15 This is a schematic flowchart of a communication method for adjusting the NES mode state of an NES cell according to an embodiment of this application.

[0059] Figure 16 This is a schematic diagram of a communication method for a second network device to determine an adjustment strategy, provided in an embodiment of this application.

[0060] Figure 17 This is a schematic diagram of another communication method for a second network device to determine an adjustment strategy, provided in an embodiment of this application.

[0061] Figure 18 This is a schematic diagram of another communication method for a second network device to determine an adjustment strategy, provided in an embodiment of this application;

[0062] Figure 19 This is a schematic diagram of another communication method for a second network device to determine an adjustment strategy, provided in an embodiment of this application;

[0063] Figure 20This is a schematic diagram of an O-RAN architecture application framework provided in an embodiment of this application;

[0064] Figure 21 This is a schematic diagram of CU-DU-RU segmentation under an O-RAN architecture provided in an embodiment of this application;

[0065] Figure 22 This is a schematic diagram illustrating a specific implementation method for updating the NES mode status or updating the NES cell list of four types of NES cells provided in this application embodiment;

[0066] Figure 23 This is a schematic diagram of a communication device provided in an embodiment of this application;

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

[0068] Figure 25 This is a schematic diagram of a chip structure provided in an embodiment of this application. Detailed Implementation

[0069] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. In the description of the embodiments of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B; "and / or" in this text 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 existing alone, A and B existing simultaneously, and B existing alone. Furthermore, in the description of the embodiments of this application, "multiple" refers to two or more than two.

[0070] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this embodiment, unless otherwise stated, "a plurality of" means two or more.

[0071] 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 apparatus that includes a series of steps or units is not limited to the steps or units listed, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to such process, method, product, or apparatus.

[0072] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner to facilitate understanding.

[0073] It should be understood that in this application, "at least one (item)" means one or more. "More than one" means two or more. "At least two (items)" means two or three or more. "And / or" is used to describe the relationship between related objects, indicating that there can be three relationships. For example, "A and / or B" can mean: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural.

[0074] The character " / " generally indicates that the preceding and following objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any single or multiple items. For example, "at least one of a, b, or c" can be expressed as: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0075] Both "...when" and "if" indicate that a corresponding action will be taken under certain objective circumstances. They are not time limits, nor do they require a judgment action to be taken when the action is taken, nor do they imply any other limitations.

[0076] The steps involved in the method for allocating computing tasks provided in this application embodiment are merely examples. Not all steps are mandatory, nor are all contents in each piece of information or message mandatory. They can be added or removed as needed during use.

[0077] In this application, the same step or a step or message with the same function can be referenced and learned from each other in different embodiments.

[0078] The system 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 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.

[0079] To facilitate understanding of the technical solution of this application, the relevant terms involved in this application are introduced below.

[0080] 1. System Information Block 1 (SIB1): This block carries information related to whether a terminal device is allowed to access the cell and defines the scheduling of other system information.

[0081] 2. On-demand system information block 1 (ODSIB1): Some SIB1 content may not be broadcast periodically, but is sent only when requested by the terminal device.

[0082] 3. Uplink wake-up signal (UplinkWUS): Used by terminal devices to trigger network devices to broadcast ODSIB1, thereby reducing unnecessary transmissions by network devices and saving energy.

[0083] like Figure 1 As shown, Figure 1 This application provides a schematic diagram of the architecture of a communication system, which includes a terminal device 100 and at least one network device (e.g., network device 201). Optionally, it may also include network device 202 and / or network device 203.

[0084] Terminal device 100 can establish an RRC connection with any network device.

[0085] Network devices 202 and 203 are used to assist terminal device 100 in accessing the cell covered by network device 201. For example, the cell covered by network device 201 may be a network energy saving (NES) cell. Network devices 202 and 203 are used to send (e.g., broadcast) the wake-up signal configuration of network device 201 to terminal device 100. Either network device 202 or network device 203 has the wake-up signal configuration for network device 201, while the other network device does not. For example, if network device 202 has the wake-up signal configuration for network device 201, the cells covered by this network device are collectively referred to as Cell A; if network device 203 does not have the wake-up signal configuration for network device 201, the cells covered by this network device are collectively referred to as Cell X.

[0086] When terminal device 100 connects to network device 201, factors such as its location within the cell covered by the network device can affect the connection status and performance data between them. For example, when terminal device 100 connects to network device 201, its signal quality changes with the distance between it and network device 201. Furthermore, when terminal device 100 is located inside a building, its signal quality weakens due to obstacles such as walls. Therefore, terminal device 100 is involved in cell handover issues; for instance, as terminal device 100 moves, it may switch from connecting to network device 201 to connecting to network device 202.

[0087] In one possible embodiment, cell handover of terminal device 100 involves automatic neighbor relationship management (ANR). When terminal device 100 needs to handover a cell, the network device helps terminal device 100 select a suitable access target based on its own neighbor cell list. The neighbor cell list is dynamically adjusted using ANR technology; the network device automatically updates and optimizes the neighbor cell list based on information reported by terminal device 100 (e.g., signal quality).

[0088] ANR (Application Not Responsive) technology is a specific example of self-organizing network (SON) technology, which aims to optimize and manage the performance of wireless networks through automation. For example... Figure 2 As shown, the core functions of SON technology include: self-configuration, self-optimization, and self-healing.

[0089] Automatic configuration: During network deployment or expansion, SON technology can automatically configure newly added base stations or network devices, ensuring their rapid integration into the existing network environment. This reduces the complexity of manual configuration and accelerates network deployment time.

[0090] Automatic optimization: SON technology automatically optimizes network parameters, such as signal coverage, frequency allocation, power control, and load balancing, by analyzing network data in real time. This improves network performance and ensures users receive optimal connection quality and a more stable network experience.

[0091] Automatic Repair: When network failures or performance issues occur, SON technology can automatically detect problems and take measures to repair them. For example, it can adjust neighbor cell relationships or handover strategies to alleviate network congestion or resolve coverage blind spots, thereby reducing network outages and service quality degradation.

[0092] As an example, such as Figure 3 As shown, terminal device 100 is connected to network device 201. Network device 201 sends a request message (e.g., UEInformationRequest) to terminal device 100, requesting relevant information from terminal device 100. Upon receiving the request message, terminal device 100 sends a response message (e.g., UEInformationResponse) to network device 201. The response message includes, but is not limited to, connection status and performance data of terminal device 100. Based on this data, network device 201 performs an in-depth analysis of the connection status of terminal device 100 to assess its current connection quality and the network environment. Based on the analysis results, network device 201 can dynamically optimize connection strategies, such as adjusting handover parameters, optimizing resource allocation, and improving coverage and signal quality.

[0093] like Figure 4 As shown, Figure 4 The following shows the various data items included in the UEInformationResponse. The following is an explanation of each data item included in the UEInformationResponse:

[0094] 1) measResultIdleEUTRA: Used to represent measurement results in the idle mode of the evolved universal terrestrial radio access (E-UTRA) technology in Long-Term Evolution (LTE), including the signal quality and strength measurements of neighboring cells by terminal equipment in the idle state.

[0095] 2) measResultIdleNR: Used to represent measurement results in 5G NR idle mode, including signal measurement data of neighboring cells by terminal equipment in NR idle state.

[0096] 3) logMeasReport: A measurement report used to record terminal device logs. This includes network performance data collected by the terminal device within a specified time period, such as signal strength and interference, for long-term analysis and network optimization.

[0097] 4) ConnEstFailReport: Used to record detailed data when a terminal device fails to establish a connection, indicating the problems encountered during the connection establishment process, including the cause of failure and the time of occurrence. It is used to diagnose connection problems and improve network connection stability, helping to analyze the cause of problems and improve network performance.

[0098] For example, such as Figure 5 As shown, ConnEstFailReport can include:

[0099] a)measResultFailedCell: Used to record the measurement results of the target cell when the connection fails, including information such as signal strength and signal quality, to help analyze whether the failure is related to the network quality of the target cell.

[0100] b)locationInfo: Used to provide geographic location information when a connection fails, making it easier to locate the problem area.

[0101] c) `measResultNeighCells`: This records the measurement results of neighboring cells when a connection fails. This information is used to assess the signal quality and availability of neighboring cells, and to analyze whether the handover failed or if there are problems with the signal in the neighboring cells.

[0102] d)numberOfConnFail: This indicates the number of times the terminal device failed to connect.

[0103] e) perRAInfoList: Contains detailed information related to the Random Access (RA) process. This includes details such as the time taken for each random access attempt, the resources used, and the results, helping to analyze the success or failure of random access.

[0104] f)timeSinceFailure: Used to indicate the time since the last connection failure.

[0105] 5) ra-ReportList: Used to represent records of the random access process. For example, the number of random access attempts, success rate, etc., used to analyze the performance and efficiency of random access.

[0106] For example, such as Figure 6 As shown, ra-ReportList can include:

[0107] a) Cell identification information: Used to identify the cell that the terminal device is attempting to connect to. For example, cellGlobalId and pci-arfcn.

[0108] b) Reason for Access (raPurpose): This describes the reason for random access. For example, initial access, handover, or resource request.

[0109] c)ra-InformationCommon: Used to represent resource information used during random access, including detailed data on time-domain and frequency-domain resources.

[0110] 6) Rlf-Report: Used to report wireless link failures. For example, it records situations where a terminal device experiences a wireless link interruption, including the cause and location of the failure.

[0111] 7) MobilityHistoryReport: A report used to represent the mobility history of a terminal device. For example, it records the history and frequency of handovers between different cells, which can be used to analyze the terminal device's mobility patterns and optimize handover strategies.

[0112] For example, such as Figure 7 As shown, the mobilityHistoryReport records a list of cells previously visited by the terminal, making it easy to track the terminal device's movement trajectory and handover history.

[0113] 8) lateNonCriticalExtension and nonCriticalExtension: Non-critical extension information, containing additional non-critical parameters or functions. This information does not affect core connectivity functions, but can provide additional data support for network optimization.

[0114] In the embodiments of this application, the terminal device 100 may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user apparatus.

[0115] Terminal device 100 can be a device that provides voice / data, such as a handheld device or vehicle-mounted device with wireless connectivity. Currently, examples of terminals include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving vehicles, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, wearable devices, terminal devices in 5G networks, or future public land mobile communication networks. Terminal devices in a network (PLMN), etc.

[0116] In the embodiments of this application, network device may refer to a radio access network (RAN) node (or device) that connects terminal device to wireless network. A base station can broadly encompass, or be replaced by, various names including: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitting point (TP), master station, auxiliary station, motor slide retainer (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), radio unit (RU), positioning node, etc. A base station can be a macro base station, micro base station, relay node, donor node, or similar entities, or combinations thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. A base station can also be a mobile switching center, equipment performing base station functions in D2D, V2X, and M2M communications, network-side equipment in 6G networks, and equipment performing base station functions in future communication systems. Base stations can support networks using the same or different access technologies. Optionally, RAN nodes can also be servers, wearable devices, vehicles, or in-vehicle equipment. For example, the access network equipment in vehicle-to-everything (V2X) technology can be a roadside unit (RSU).

[0117] In this embodiment, the process of establishing an initial connection between the terminal device 100 and the network device is called random access (RA), which is implemented through a random access channel (RACH). Random access is typically used for initial network access, handover, or resource requests during RRC idle states.

[0118] In one possible implementation, the basic process for random access by terminal device 100 includes:

[0119] Step 1: Terminal device 100 selects a cell.

[0120] As an example, terminal device 100 selects a target cell based on signal quality measurement results. For instance, terminal device 100 typically selects a cell with better signal strength for access.

[0121] Step 2: The terminal device 100 synchronizes with the reading of the community broadcast information.

[0122] As an example, after selecting a target cell, terminal device 100 receives the synchronization signal (SS) and broadcast information of that cell, and obtains system configuration information, including RACH configuration, through the broadcast information. The broadcast information can be the master information block (MIB) and system information block 1 (SIB1).

[0123] In this embodiment of the application, taking SIB1 as an example, SIB1 is an important broadcast message in wireless network technology. The information it carries includes, but is not limited to: public land mobile network (PLMN) information, such as network operator identification information; cell access parameters: cell identifier, access class restrictions (such as emergency call priority, priority access type); random access channel (RACH) configuration: random access parameters used by terminal device 100 when accessing the network; scheduling information: information that provides subsequent SIB (such as SIB2, SIB3) scheduling.

[0124] Step 3: Terminal device 100 selects RACH resources.

[0125] As an example, terminal device 100 selects appropriate random access resources based on the RACH configuration information in SIB1. For example, a random access preamble.

[0126] Step 4: Terminal device 100 sends a random access preamble to the network device.

[0127] As an example, terminal device 100 sends a random access preamble to the base station via RACH. The random access preamble indicates its request for access.

[0128] Step 5: Terminal device 100 receives a random access response (RAR) from the network device.

[0129] As an example, after detecting the preamble, the network device sends a RAR to the terminal device 100, which contains information such as uplink resource allocation.

[0130] Step 6: Terminal device 100 performs message transmission and authentication.

[0131] As an example, terminal device 100 uses allocated resources for message transmission and attaches a temporary identity of terminal device 100, such as a cell-radio network temporary identifier (C-RNTI), for network devices to identify.

[0132] Step 7: Complete random access.

[0133] As an example, after the network device verifies the identity of the terminal device 100, it completes the random access procedure, and the terminal device 100 establishes an initial connection with the network device.

[0134] In the aforementioned random access process, the network devices broadcast information periodically, which leads to unnecessary resource waste. Therefore, related technologies propose an optimization scheme, namely, on-demand system information block 1 (ODSIB1). In ODSIB1, network devices only broadcast when there is an access request from terminal device 100.

[0135] The ODSIB1 scheme can be implemented by a cell that supports network energy saving (NES) function. Specifically, the terminal device 100 triggers the broadcast of SIB1 only when it sends an uplink wake-up signal to the network device, thereby effectively reducing unnecessary transmissions and saving energy.

[0136] As an example, such as Figure 8 As shown in Figure (a), the network device directly sends SIB1 to the terminal device 100, and the terminal device 100 completes random access based on SIB1. However, as... Figure 8 As shown in Figure (b), the terminal device 100 first sends a wake-up signal to the network device. The network device sends SIB1 to the terminal device 100 based on the received wake-up signal, and the terminal device 100 completes random access based on SIB1.

[0137] When terminal device 100 needs to access network device, terminal device 100 needs to first obtain the wake-up signal configuration (WUS Configuration) of network device.

[0138] In one possible implementation, terminal device 100 needs to access the NES cell corresponding to the network device. The NES cell will send its own wake-up signal configuration to the surrounding cells in advance and entrust these cells to broadcast the wake-up signal configuration to terminal device 100. Among them, these cells responsible for helping the NES cell broadcast the wake-up signal configuration are collectively referred to as Cell A.

[0139] For example, such as Figure 9 As shown, when terminal device 100 needs to access an NES cell, it sends a wake-up signal (e.g., a random access preamble) to the NES cell via RACH according to the wake-up signal configuration obtained from Cell A. After receiving the wake-up signal, the NES cell sends a random access response to terminal device 100. If the random access response contains an information identifier indicating that SIB1 is about to be sent, the NES cell will then send SIB1 to terminal device 100. Correspondingly, after receiving the random access response, if it contains the information identifier indicating that SIB1 is about to be sent, terminal device 100 waits to receive SIB1.

[0140] The Cell A list corresponding to an NES cell is not fixed. It can be dynamically adjusted and optimized using information reported by the terminal device 100, combining SON and ANR technologies. For example, cells that may have the capability to broadcast wake-up signals for NES cells but have not yet received wake-up signal configurations can be added to the Cell A list; these cells are collectively referred to as CellX. Figure 10 As shown, Figure 10 This is a schematic diagram illustrating the relationship between CellA and CellX and the NES cell.

[0141] Based on the methods described in related technologies, the current existing technologies do not explicitly specify an optimization scheme for ODSIB1 transmission, which may lead to the inability to effectively achieve energy-saving goals or to hinder the connection of terminal devices.

[0142] Based on this, embodiments of this application provide a communication method in which a first network device dynamically optimizes the ODSIB1 transmission process based on data reported by a terminal device. The first network device can adjust the access threshold using location information and signal measurement results reported by the terminal device, and dynamically optimize the second cell list corresponding to the first network device based on successful terminal device access. This aims to reduce the number of terminal device access failures, reduce unnecessary ODSIB1 broadcasts, and optimize the configuration of the Cell A list.

[0143] In this application embodiment, the specific structure of the execution subject of a communication method is not particularly limited, as long as communication can be performed according to the communication method of this application by running a program that records the code of a communication method of this application embodiment. For example, the execution subject of a communication method provided in this application embodiment may be a functional module in a first network device that can call and execute a program, or a communication device applied in the first network device, such as a chip, chip system, integrated circuit, etc. These chips, chip systems, and integrated circuits may be disposed inside the first network device or may be independent of the first network device, and this application embodiment does not impose any restrictions. For example, the execution subject of a communication method provided in this application embodiment may be a functional module in a second or third network device that can call and execute a program, or a communication device applied in a second or third network device, such as a chip, chip system, integrated circuit, etc. These chips, chip systems, and integrated circuits may be disposed inside the second or third network device or may be independent of the second or third network device, and this application embodiment does not impose any restrictions. For example, the execution entity of a communication method provided in this application embodiment can be a functional module in a terminal device capable of calling and executing a program, or a communication device applied in the terminal device, such as a chip, chip system, integrated circuit, etc. These chips, chip systems, and integrated circuits can be located inside the terminal device or can be independent of the terminal device; this application embodiment does not impose any limitations.

[0144] The following embodiments are described using a first network device as an example to illustrate a communication method. Unless otherwise specified, the solutions in the following embodiments can be combined.

[0145] like Figure 11 As shown, Figure 11 This illustration shows a flowchart of a communication method provided in an embodiment of this application. The method includes:

[0146] Step 1101: The first network device receives the first message. The first message includes a target field, which is used to instruct the terminal device to receive information from ODSIB1.

[0147] The area covered by the first network device is a cell. The first network device receiving the first message can also be regarded as the cell corresponding to the first network device receiving the first message.

[0148] In one possible embodiment, the first network device corresponds to an NES cell. The first network device receiving the first message can also be understood as the NES cell receiving the first message.

[0149] In one possible embodiment, the first message is a UEInformationResponse message. The target field in the first message is ODSIB1InfoResponse.

[0150] The information received by the terminal device from ODSIB1 refers to the relevant data of the terminal device during the process of accessing the first network device.

[0151] For example, a terminal device sends a wake-up signal to a first network device. The first network device then sends ODSIB1 to the terminal device based on the wake-up signal. The terminal device then connects to the first network device via random access and establishes an RRC connection. During this process, the relevant data from the terminal device may include: the time and connection information of the terminal device's access to the first network device, the terminal device's signal measurement results, the terminal device's mobility and location information, and the terminal device's status information.

[0152] The following explains the specific content of the information received by the terminal device from ODSIB1, taking the NES cell corresponding to the first network device as an example.

[0153] 1) Time and connection information.

[0154] As an example, time and connection information includes: rar-content, timestamp, from-cell-id, attempted-cell-id, connectionFailureType, numAttempts, ssb-index, and AttemptedBWP-Info.

[0155] Among them, rar-content is used to represent the random access response content, such as the SIB1 measurement window, backoff timer, etc.

[0156] The timestamp is used to record the specific date and time of the connection attempt.

[0157] The `from-cell-id` is used to represent the New Radio Doors Global Identifier (NCGI) of the currently connected cell. For example, if the currently connected cell is Cell A, Cell A includes the uplink wake-up signal configuration of the NES cell.

[0158] Here, `attempted-cell-id` represents the physical cell identifier (PCI) of the NES cell to which a connection was attempted, or the PCI and carrier frequency. It is understood that this is not NCGI because the terminal device may not be able to receive the SIB1 of the NES cell.

[0159] The attempt-result is used to record whether the SIB1 from the NES cell was successfully received.

[0160] The connectionFailureType is used to indicate the reason code for the connection failure. For example, the reason for failure might be "The terminal device did not receive the wake-up signal configuration" or "The terminal device sent a wake-up signal, but did not receive SIB1".

[0161] numAttempts is used to record the number of times the terminal device attempts to connect to the NES cell.

[0162] The ssb-index represents the synchronization signal and physical broadcast channel block (SSB) beam that the terminal device relies on during random access.

[0163] Among them, AttemptedBWP-Info is used to indicate the bandwidth portion that is attempted when sending a wake-up signal.

[0164] 2) Signal measurement results.

[0165] As an example, signal measurement results include measResult.

[0166] For example, measResult includes measurements of the reference signal received power (RSRP), reference signal received quality (RSRQ), and signal to interference plus noise ratio (SINR) of the NES cell currently being attempted to access.

[0167] 3) Mobility and location information.

[0168] As an example, mobility and location information includes mobilityState, LocationInfo, and mobilityPatterns.

[0169] Among them, mobilityState is used to report the mobility status of the terminal device, such as stationary, walking, or vehicle movement.

[0170] LocationInfo is used to record the distance information between the terminal device and the NES cell it is trying to access.

[0171] Among them, mobilityPatterns is used to report recent switching, reselection, and the movement trajectory of terminal devices.

[0172] 4) Status information of terminal devices.

[0173] As an example, the status information of a terminal device includes: ueMode.

[0174] Among them, ueMode is used to report the current operating mode of the terminal device, such as idle, connected, and power-saving modes.

[0175] Step 1102: The first network device updates the conditions for the terminal device to access the first cell based on the target field, and / or updates the list of second cells associated with the first cell.

[0176] The conditions for a terminal device to access the first cell may include, but are not limited to: when the signal quality of the terminal device is greater than or equal to a preset signal quality threshold, the first network device allows the terminal device to access the first cell; or, when the success rate of the terminal device's access attempt is greater than or equal to a preset success rate threshold, the first network device allows the terminal device to access the first cell; or, when the mobility state of the terminal device meets certain conditions, the first network device allows the terminal device to access the first cell; or, when the distance between the terminal device and the first network device is less than or equal to a preset distance threshold, the first network device allows the terminal device to access the first cell.

[0177] In one possible implementation of this application, if the first network device determines, based on the target field, that the terminal device meets the aforementioned first condition and can access the first cell, then the first network device may not update the conditions for the terminal device to access the first cell, thereby allowing the terminal device to access the first cell. Alternatively, if the first network device determines, based on the target field, that the terminal device meets the aforementioned first condition and can access the first cell, but the first network device does not want the terminal device to access the first cell, then it may update the conditions for the terminal device to access the first cell, for example, by raising the threshold for the terminal device to access the first cell, reducing the number of ineligible terminal devices accessing the NES cell, thereby reducing the power consumption of the NES cell.

[0178] As an example, the conditions for the first network device to update the terminal device's access to the first cell may include: increasing the preset signal quality threshold, increasing the preset success rate threshold, restricting the terminal device's mobility status, and decreasing the preset distance threshold between the terminal device and the first network device.

[0179] In another possible implementation of this application, if the first network device determines, based on the target field, that the terminal device does not meet the aforementioned first condition, i.e., the terminal device cannot access the first cell, then the first network device may not update the conditions for the terminal device to access the first cell. Alternatively, if the first network device determines, based on the target field, that the terminal device does not meet the aforementioned first condition and cannot access the first cell, but the first network device wants the terminal device to access the first cell, then it may update the conditions for the terminal device to access the first cell so that more terminal devices can access the NES cell. For example, the first network device may lower the threshold for terminal devices to access the first cell.

[0180] As an example, the conditions for updating the terminal device's access to the first cell may include: lowering the preset signal quality threshold, lowering the preset success rate threshold, relaxing the conditions for the terminal device's mobility status, and increasing the preset distance threshold between the terminal device and the first network device.

[0181] In one possible implementation of this application, the target field includes measResult. Based on the measurement results in measResult, if the first network device determines that the signal quality of multiple terminal devices is poor, the first network device can adjust access-related parameters to raise the entry threshold.

[0182] Among these, the access-related parameters can be the random access response window (ra-ResponseWindow) and the reference signal received power threshold (RSRP-Threshold). ra-ResponseWindow defines the window length of the RAR. RSRP-Threshold defines the threshold for triggering events.

[0183] For example, taking signal quality as the reference signal received power, a reference signal received power greater than or equal to AdBm indicates that the signal quality of the terminal device meets the requirements. The measResult display shows that the terminal devices already connected to the NES cell include Terminal 1, Terminal 2, Terminal 3, and Terminal 4, with reference signal received powers of adBm, bdBm, cdBm, and ddBm, respectively. Since b, c, and d are all less than AdBm, and a is greater than AdBm, it can be concluded that most terminals do not meet the signal quality requirements. Therefore, access-related parameters can be adjusted to prevent terminals with reference signal received power less than AdBm from being allowed to access the NES cell.

[0184] In one possible implementation of this application, the target field includes rar-content. The first network device adjusts the parameters used when sending SIB1, such as the SIB1 measurement window, based on the data in the rar-content.

[0185] In one possible implementation of this application, the target field includes numAttempts. Based on the measurement results in numAttempts, if the first network device determines that some terminal devices attempt to access the network a large number of times but have a low success rate, the first network device can raise the access threshold by adjusting the access-related parameters.

[0186] For example, if a terminal device attempts to access the network 5 times or more, and / or has a success rate of 50% or less, it indicates that the terminal device has weak signal quality. `numAttempts` shows that the number of access attempts and success rates for terminals 1, 2, 3, and 4 are (8, 75%), (3, 100%), (2, 50%), and (4, 25%), respectively. Terminals 1 and 4 have weak signal quality; therefore, the first network device can adjust the access-related parameters to prevent terminals with weak signal quality from accessing the NES cell.

[0187] In one possible implementation of this application, the target field includes mobilityState. The first network device determines the dynamic mobility status of the terminal device based on the data recorded in mobilityState, and dynamically adjusts the access threshold of the terminal device according to the mobility status.

[0188] For example, the first network device raises the entry threshold for terminal devices that are stationary or moving at low speeds by adjusting access-related parameters.

[0189] In one possible implementation of this application, the target field includes LocationInfo. Based on the measurement results in LocationInfo, the first network device determines that some terminal devices are too far from the first network device. The first network device then adjusts access-related parameters to raise the entry threshold.

[0190] For example, when the distance between the terminal device and the first network device is greater than or equal to X km, it indicates that the terminal device is far from the first network device and the connection quality is weak. LocaionInfo displays the distances between terminal 1, terminal 2, terminal 3, and terminal 4 and the first network device as A km, B km, C km, and D km, respectively. Since A and B are greater than X, and C and D are less than X, the first network device can restrict terminal 1 and terminal 2 from accessing the NES cell.

[0191] In this configuration, the network device corresponding to any second cell in the second cell list is used to broadcast the wake-up signal configuration of the first network device to the terminal device. The wake-up signal configuration is used by the terminal device to send an uplink wake-up signal to the first network device. The uplink wake-up signal instructs the first network device to send ODSIB1 to the terminal device.

[0192] It is understandable that the network device corresponding to the second cell is a second network device with a wake-up signal configuration.

[0193] The second cell list includes multiple second cells. Updating the second cell list can involve removing a second cell from the list or adding other cells with broadcast wake-up signal configuration capabilities to the second cell list.

[0194] For example, if the second cell is CellA, and there is a CellA in the CellA list that cannot broadcast the wake-up signal configuration to the terminal device, then it is necessary to remove this CellA from the CellA list.

[0195] For example, if there is a cell near the terminal device that has the ability to configure a wake-up signal, such as CellX, the first network device can add the cell to the CellA list.

[0196] In one possible implementation of this application, the first network device updates the Cell A list based on the connectionFailureType in the target field. If the failure reason indicated by connectionFailureType is "the first network device did not receive an uplink wake-up signal," it indicates that the current terminal device previously attempted to access a cell without a wake-up signal configuration, i.e., Cell X. In this case, the first network device can add Cell X to the Cell A list.

[0197] For example, after a terminal device accesses CellX1, since CellX1 belongs to CellX and does not have a wake-up signal configuration, the connectionFailureType indicates "the first network device has not received an uplink wake-up signal". At this time, the first network device can add CellX1 to the Cell A list.

[0198] Optionally, the failure reason indicated by the connectionFailureType in the target field can also be "The terminal device failed to receive SIB1". In this case, the first network device can also adjust the transmit power of the first network device SIB1.

[0199] For example, if the first network device sends SIB1 with low transmission power to the terminal device, causing the connectionFailureType to indicate "The terminal device failed to receive SIB1", the first network device can increase the transmission power of SIB1.

[0200] Optionally, the first network device can also update the CellA list based on the number of access failures of CellA.

[0201] For example, if a Cell A fails to connect to the first network device a large number of times, the first network device will remove the Cell A from the Cell A list and request the Cell A to stop broadcasting the wake-up signal configuration.

[0202] In one possible implementation of this application, the first network device updates the CellA list based on the measResult in the target field. If the measResult includes signal measurement results of neighboring cells by the terminal device, and a cell not yet included in the CellA list is identified, then that cell is added to the CellA list.

[0203] For example, measResult includes the measurement results of the terminal device for cell 1, and cell 1 is not a cell in the CellA list. Therefore, the first network device adds cell 1 to the CellA list.

[0204] Optionally, updating the conditions for terminal devices to access the first cell and / or updating the list of second cells associated with the first cell can be considered as the first network device adjusting its policy. The first network device may also choose not to adjust its policy.

[0205] As an example, the first network device can set preset conditions to indicate the current network communication status. For example, the network communication status could be good or poor. When the target field indicates that the terminal device meets the preset conditions, i.e., the current network communication status is good, the first network device may not perform any policy adjustments, such as not changing the conditions for the terminal device to access the first cell. When the terminal device does not meet the preset conditions, i.e., the current network communication status is poor, the first network device will perform policy adjustments, such as raising the conditions for the terminal device to access the first cell.

[0206] For example, the first network device sets the following preset conditions: when the number of terminal devices with signal quality less than M is greater than N, it indicates poor network communication; conversely, when the number of terminal devices with signal quality less than M is less than or equal to N, it indicates good network communication. If the first network device determines, based on the target field, that the number of terminal devices with signal quality less than M is less than N, then the first network device does not change the conditions for the terminal devices to access the first cell. If the first network device determines, based on the target field, that the number of terminal devices with signal quality less than M is greater than N, then the first network device improves the conditions for the terminal devices to access the first cell.

[0207] In this application, a first network device receives a first message. Since the first message includes a target field, which instructs the terminal device to receive ODSIB1 information, the first network device can determine the terminal device's access report for the first cell. The first network device can update the conditions for the terminal device to access the first cell based on the target field. This restricts access for some terminal devices that are not suitable for accessing the first cell, thereby reducing the number of failed access attempts and the number of times the first network device sends ODSIB1. Alternatively, the first network device can update the list of second cells associated with the first cell based on the target field. A second network device corresponding to any second cell in the second cell list broadcasts a wake-up signal configuration to the terminal device. This wake-up signal configuration is used by the terminal device to send an uplink wake-up signal to the first network device, instructing the first network device to send ODSIB1 to the terminal device. This optimizes the second cell list, making it more effective at broadcasting the wake-up signal configuration to the terminal device, thus enabling the terminal device to obtain ODSIB1 by sending the uplink wake-up signal.

[0208] In one possible implementation of this application, the method provided in this application embodiment further includes: the first network device updating the list of first cells where the first cell is located according to the target field, and / or turning off the network power saving mode of the first cell.

[0209] In this context, the network power saving mode is used by the first network device to send ODSIB1 to the terminal device. The network power saving mode is also known as the ODSIB1 mode.

[0210] In this embodiment, when the number of terminal devices accessing the first cell reaches a preset threshold, the number of times the first network device broadcasts SIB1 on demand will increase, exceeding the number of times the first network device periodically broadcasts SIB1. This increases the energy consumption of the first network device, which is not conducive to resource conservation. Therefore, when the number of terminal devices accessing the first cell reaches the preset threshold, it is necessary to prevent the first cell from broadcasting ODSIB1 on demand.

[0211] The terminal device reaching the preset threshold can be due to the number of terminal devices accessing the first cell exceeding the preset threshold, or it can be due to other conditions, which are not limited in this embodiment.

[0212] As an example, the first network device can disable the network power-saving mode of the first cell. After disabling the network power-saving mode of the first cell, the first network device will periodically broadcast SIB1 to the terminal device, thus reducing the number of times the first network device broadcasts SIB1.

[0213] As another example, the first network device can update the first cell list. The first network device removes the first cell from the first cell list, so that the first cell no longer uses the network power-saving mode and instead periodically broadcasts SIB1 to the terminal device, thus reducing the number of times the first network device broadcasts SIB1.

[0214] In one possible implementation of this application, taking an example where a preset threshold is reached indicating an excessive number of terminal devices accessing the NES cell, the first network device determines, based on the data recorded in the `attempted-cell-id` field of the target field, that too many terminal devices are accessing the NES cell. In this case, the first network device either disables the NES mode of the NES cell or removes the NES cell from the NES cell list. Specifically, any cell in the NES cell list can enable NES mode, while cells not in the NES cell list cannot enable NES mode.

[0215] For example, the attempted-cell-id records N terminal devices attempting to access the NES cell. When it is determined that N exceeds the preset threshold of the NES mode of the NES cell, the first network device disables the NES mode of the NES cell.

[0216] In one possible implementation of this application, taking the case where the number of terminal devices accessing the network reaches a preset threshold as an example, the first network device determines, based on the data recorded in the timeStamp field of the target field, that too many terminal devices are trying to access the network during a certain time period. In this case, the first network device shuts down the NES mode of the NES cell during that time period.

[0217] For example, if the timeStamp records N terminal devices attempting to access the network between 12:00 and 15:00, and it is determined that N exceeds the preset threshold of the NES mode of the NES cell, the first network device will shut down the NES mode of the NES cell between 12:00 and 15:00.

[0218] In this embodiment of the application, the first message received by the first network device may come from the terminal device or from the second network device.

[0219] For example, the second network device can provide Figure 1 Network device 202 or network device 203 in the communication system shown.

[0220] Specifically, when the second network device is network device 202, the second network device has a wake-up signal configuration, and the second network device can directly broadcast the wake-up signal configuration to the terminal device.

[0221] It is understandable that when the second network device has a wake-up signal configuration, the cell corresponding to the second network device is the second cell.

[0222] For example, the NES cell pre-configures the wake-up signal for CellA and entrusts CellA to broadcast the wake-up signal configuration to the terminal device. The terminal device sends an uplink wake-up signal to the NES cell according to the received wake-up signal configuration, so that the NES cell sends ODSIB1.

[0223] Specifically, when the second network device is network device 203, the second network device does not have a wake-up signal configuration. The second network device needs to request the wake-up signal configuration from the first network device first, and after obtaining the wake-up signal configuration, broadcast the wake-up signal configuration to the terminal device.

[0224] For example, CellX first requests wake-up signal configuration from the NES cell. After receiving the request, the NES cell sends the wake-up signal configuration to CellX. It can be understood that once CellX obtains the wake-up signal configuration, CellX becomes Cell A.

[0225] Scenario 1) The first message received by the first network device comes from the terminal device.

[0226] In one possible implementation of this application, before the first network device receives the first message, the method provided in this embodiment further includes: the first network device establishing an RRC connection with the terminal device. The first network device sends a second message to the terminal device through the RRC connection. Correspondingly, the terminal device receives the second message from the first network device.

[0227] The second message is used to request the terminal device to provide information for receiving SIB1.

[0228] In one possible embodiment, the process of establishing an RRC connection between the terminal device and the first network device refers to the relevant description in the prior art described above, and will not be repeated here.

[0229] In one possible embodiment of this application, the first network device sends a second message to the terminal device, which can also be understood as the cell corresponding to the first network device sending a second message to the terminal device.

[0230] As an example, the second message is a UE Information Request message. The UE Information Request is used to request the terminal device to provide reporting information related to ODSIB1.

[0231] As another example, the second message includes a first field that requests the terminal device to provide reporting information related to ODSIB1. For instance, the first field in the second message could be "ODSIB1InfoRequest".

[0232] Scenario 2) The first message received by the first network device comes from the second network device, which has a wake-up signal configuration.

[0233] In one possible implementation of this application, the first network device receiving the first message includes: the first network device receiving a first message from a second network device. Correspondingly, the second network device sends the first message to the first network device.

[0234] The second network device is used to broadcast wake-up signal configuration to the terminal device, and the second network device has wake-up signal configuration. An RRC connection exists between the second network device and the terminal device.

[0235] As an example, the cell corresponding to the second network device is Cell A. The second network device sending the first message to the first network device can also be seen as Cell A sending the first message to the NES cell.

[0236] In one possible implementation, the wake-up signal configuration in the second network device originates from the first network device.

[0237] In scenario 2), before the first network device receives the first message from the second network device, the method provided in this application embodiment further includes:

[0238] Step 1: The second network device sends a second message to the terminal device. Correspondingly, the terminal device receives the second message from the second network device.

[0239] The second message is used to request the terminal device to provide information for receiving ODSIB1.

[0240] Step 2: The second network device receives the first message from the terminal device. Correspondingly, the terminal device sends the first message to the second network device.

[0241] The first message includes a target field, which is used to instruct the terminal device to receive information from the ODSIB1 of the first network device.

[0242] It is worth noting that the first message sent by the second network device to the first network device and the first message received by the second network device from the terminal device are the same message. In other words, the second network device is only used to forward the first message.

[0243] Optionally, the first message sent by the second network device to the first network device and the first message received by the second network device from the terminal device may be the same message or they may not be the same message. In other words, the second network device may process the received first message and then send another message, which is not limited in this embodiment.

[0244] In one possible implementation of this application, the method provided in this embodiment further includes: a first network device receiving indication information from a second network device.

[0245] The instruction information is used to instruct the second network device to stop broadcasting the wake-up signal configuration to the terminal device.

[0246] As an example, the second network device determines, based on the target field in the first message, that the second network device is no longer suitable for configuring the broadcast wake-up signal for the first network device, and sends an indication message to the first network device to instruct the second network device to stop configuring the broadcast wake-up signal for the first network device.

[0247] In one possible implementation, the target field includes numAttmpts. Based on the data in numAttmpts, the second network device determines that the number of failed attempts by the terminal device to access the first network device is too high. Therefore, it can be concluded that the second network device is not suitable for configuring the broadcast wake-up signal for the first network device and needs to stop configuring the broadcast wake-up signal.

[0248] For example, the data in numAttmpts indicates that the terminal device attempted to connect to the NES cell 10 times. Therefore, Cell A is no longer suitable for broadcast wake-up signal configuration. The second network device corresponding to Cell A sends an indication message to the NES cell, instructing it to stop broadcast wake-up signal configuration.

[0249] Scenario 3) The first message received by the first network device comes from the second network device, which does not have a wake-up signal configuration.

[0250] In one possible implementation of this application, the first network device receiving the first message includes: the first network device receiving a first message from a second network device. Correspondingly, the second network device sends the first message to the first network device.

[0251] The second network device is used to broadcast wake-up signal configuration to the terminal device; however, the second network device itself does not have wake-up signal configuration functionality. The terminal device and the second network device have an RRC connection.

[0252] In scenario 3), before the first network device receives the first message from the second network device, the method provided in this application embodiment further includes:

[0253] Step 1: The second network device sends a second message to the terminal device. Correspondingly, the terminal device receives the second message from the second network device.

[0254] The second message is used to request the terminal device to provide information for receiving ODSIB1.

[0255] Step 2: The second network device receives the first message from the terminal device. Correspondingly, the terminal device sends the first message to the second network device.

[0256] The first message includes a target field, which is used to instruct the terminal device to receive information from the ODSIB1 of the first network device.

[0257] The specific implementation is the same as the second network device in scenario 2), and will not be described again here.

[0258] In one possible implementation of this application, the method provided in this embodiment further includes: a first network device receiving a request message from a second network device. Correspondingly, the second network device sends a request message to the first network device.

[0259] The request message is used to request that the wake-up signal configuration be broadcast to the terminal.

[0260] As an example, the second network device sends a request message to the first network device based on the target field in the first message, requesting configuration for broadcasting a wake-up signal for the first network device.

[0261] In one possible implementation, the target field includes connectionFailureType and numAttempts. The second network device determines, based on the data in connectionFailureType and numAttempts, that multiple terminal devices are attempting to access the first network device from the second network device, and sends a request message to the first network device.

[0262] For example, if an NES cell is in Cell X's neighbor cell list, Cell X sends a request message to the NES cell, requesting to start configuring the broadcast wake-up signal for the NES cell.

[0263] For example, if the NES cell is not in Cell X's neighbor cell list, Cell X will add the NES cell to the neighbor cell list and send a request message to the NES cell to request the start of configuration for broadcasting wake-up signals for the NES cell.

[0264] It is worth noting that CellX can determine the signal strength and location data of the terminal device based on the measResult and LocationInfo fields in the target field, and determine whether the NES cell can be added to its neighbor cell list.

[0265] The following is combined Figures 12-19 The specific implementation of the communication method is described below. In the specific methods of the following embodiments, the method provided by the embodiments of this application is described by taking the first cell corresponding to the first network device as NES cell, the second cell as CellA, and the cell corresponding to the second network device as CellA or CellX as examples.

[0266] like Figure 12 As shown, Figure 12 This is a schematic diagram illustrating a specific implementation of a communication method provided in an embodiment of this application. The communication method includes:

[0267] Step 1201: The first network device sends a second message to the terminal device. Correspondingly, the terminal device receives the second message from the first network device.

[0268] The second message is used to request the terminal device to provide report information related to ODSIB1.

[0269] For example, the second message is UEInformationRequest, which includes the ODSIB1 Information Request (ODSIB1InfoRequest) field. The ODSIB1InfoRequest field is used to request the terminal device to provide ODSIB1-related report information.

[0270] Understandably, prior to step 1202, the terminal device has already obtained the ODSIB1 of the NES cell by sending an uplink wake-up signal to the NES cell, and has established an RRC connection with the first network device serving the NES cell through random access. The uplink wake-up signal of the terminal device is configured by CellA broadcasting a wake-up signal to the terminal device.

[0271] In this application embodiment, the reporting information related to ODSIB1 includes, but is not limited to, the following: time and connection information, signal measurement results, mobility and location information, and terminal device status information.

[0272] Step 1202: The terminal device sends a first message to the first network device. Correspondingly, the first network device receives the first message from the terminal device.

[0273] The first message includes a target field, which is used to indicate report information related to ODSIB1.

[0274] For example, the first message is UEInformationResponse, the target field is ODSIB1InfoResponse, and ODSIB1InfoResponse includes report information related to ODSIB1. Specifically, UEInformationResponse includes ODSIB1InfoResponse.

[0275] Step 1203: The first network device determines the adjustment strategy based on the target field.

[0276] The adjustment strategies include, but are not limited to: updating the conditions for terminal devices to access NES cells, updating the CellA list, and updating the NES mode status of NES cells.

[0277] The specific implementation methods of the adjustment strategies are explained below.

[0278] like Figure 13 As shown, Figure 13 A flowchart illustrating the communication method for updating the wake-up signal configuration to adjust the strategy. The communication method includes:

[0279] Steps 1301 to 1302 are the same as steps 1201 to 1202 in the above embodiments, and will not be repeated here.

[0280] Step 1303: The first network device updates the conditions for the terminal device to access the NES cell based on the first message.

[0281] As an example, the first network device updates the conditions for the terminal device to access the first network device based on the information related to ODSIB1 in the target field, so as to raise the access threshold for the terminal device.

[0282] For example, the target field includes information such as measResult, rar-content, numAttempts, mobilityState, and LocationInfo. The specific content of this information is described in the above embodiments and will not be repeated here. The first network device updates the conditions for the terminal device to access the first network device based on the data in each piece of information.

[0283] For example, the conditions for updating the terminal device's access to the first network device include: increasing the preset signal quality threshold, increasing the preset success rate threshold, restricting the terminal device's movement status, and decreasing the preset distance threshold between the terminal device and the first network device. The specific implementation method is described in the above embodiments and will not be repeated here.

[0284] Step 1304: The first network device sends the updated wake-up signal configuration to CellA. Correspondingly, CellA receives the updated wake-up signal configuration from the first network device.

[0285] CellA can broadcast the received updated wake-up signal configuration to the terminal device, and the terminal device can send an uplink wake-up signal to the first network device according to the updated wake-up signal configuration.

[0286] Step 1305: CellA sends feedback information to the first network device. Correspondingly, the first network device receives the feedback information from CellA.

[0287] The feedback information is used to indicate that CellA has received the updated wake-up signal configuration. For example, the feedback information is "Acknowledge".

[0288] like Figure 14 As shown, Figure 14 This is a flowchart illustrating the communication method for adjusting the strategy to update the CellA list. The communication method includes:

[0289] Steps 1401 to 1402 are the same as steps 1201 to 1202 in the above embodiments, and will not be repeated here.

[0290] Step 1403: The first network device updates the CellA list according to the first message.

[0291] As an example, the CellA list may contain multiple CellA cells. One of these CellA cells may be unable to broadcast wake-up signal configuration to the terminal device; in this case, the CellA cell needs to be removed from the CellA list. Alternatively, if there is a neighboring cell 1 that can also broadcast wake-up signal configuration to the terminal device, then cell 1 can be added to the CellA list.

[0292] In one possible implementation, the first network device updates the CellA list based on the connectionFailureType in the target field. If the failure reason indicated by connectionFailureType is "the first network device did not receive an uplink wake-up signal", it indicates that the current terminal device once attempted to access a cell without a wake-up signal configuration, i.e., Cell X. In this case, the first network device can add Cell X to the CellA list.

[0293] Optionally, the failure reason indicated by the connectionFailureType in the target field can also be "The terminal device failed to receive ODSI B1". In this case, the first network device can also adjust the transmit power of the first network device when transmitting ODSI B1.

[0294] Optionally, the first network device can also update the CellA list based on the number of access failures of CellA.

[0295] In another possible implementation, the first network device updates the CellA list based on the measResult in the target field. If the measResult includes signal measurement results of neighboring cells by the terminal device, and the first network device identifies a cell whose signal quality does not yet meet preset conditions, then it adds that cell to the CellA list; otherwise, it does not add that cell to the CellA list.

[0296] like Figure 15 As shown, Figure 15 This is a flowchart illustrating the communication method for adjusting the strategy to update the NES mode state of an NES cell. The communication method includes:

[0297] Steps 1501 to 1502 are the same as steps 1201 to 1202 in the above embodiments, and will not be repeated here.

[0298] Step 1503: The first network device updates the NES cell list or disables the NES mode of the NES cells according to the first message.

[0299] One way to prevent NES cells from sending ODSIB1 to terminal devices is to either disable the NES mode of the NES cell or update the NES cell list.

[0300] For example, cell 1 is an NES cell and establishes an RRC connection with the terminal device. When cell 1 is not suitable for connection with the terminal device, the first network device turns off the NES mode of cell 1 so that cell 1 no longer sends ODSIB1 to the terminal device.

[0301] For example, cell 1 is an NES cell that establishes an RRC connection with the terminal device. When cell 1 is not suitable for connection with the terminal device, the first network device removes cell 1 from the NES cell list so that cell 1 no longer sends ODSIB1 to the terminal device.

[0302] In one possible implementation, the first network device determines that too many terminal devices are accessing the NES cell based on the data recorded in the attempted-cell-id field of the target field. If so, the first network device disables the NES mode of the NES cell or removes the NES cell from the NES cell list.

[0303] In one possible implementation, the first network device determines, based on the data recorded in the timeStamp field of the target field, that too many terminal devices attempt to access the network during a certain time period. In this case, the first network device disables the NES mode of the NES cell during that time period.

[0304] In one scenario provided in this application embodiment, an RRC connection is established between a terminal device and a second network device, and the second network device has a wake-up signal configuration.

[0305] In one possible implementation, the terminal device first attempts to access the NES cell. If the attempt fails, the terminal device can establish an RRC connection with Cell A. Alternatively, the terminal device can disconnect the RRC connection with the NES cell and then establish an RRC connection with Cell A, meaning the terminal device switches from the NES cell to Cell A.

[0306] like Figure 16 As shown, Figure 16 This illustration shows a communication method for a second network device to determine an adjustment strategy, provided in an embodiment of this application. The second network device has a wake-up signal configuration. The communication method includes:

[0307] Step 1601: The second network device sends a second message to the terminal device. Correspondingly, the terminal device receives the second message from the second network device.

[0308] The second message is used to request the terminal device to provide information for receiving ODSIB1.

[0309] Step 1602: The terminal device sends a third message to the second network device. Correspondingly, the second network device receives the third message from the terminal device.

[0310] The third message includes a target field, which is used to instruct the terminal device to receive information from the first network device's ODSIB1.

[0311] Step 1603: The second network device sends a first message to the first network device. Correspondingly, the first network device receives the first message from the second network device.

[0312] In this case, the first message in step 1603 and the third message in step 1602 can be the same message or different messages.

[0313] For example, when the second network device is only used to forward messages, the first message sent by the second network device to the first network device is the third message sent by the terminal device to the second network device. Alternatively, the second network device may process the third message before sending the first message to the first network device.

[0314] Step 1604: The first network device determines the adjustment strategy based on the first message.

[0315] The adjustment strategies include, but are not limited to: updating the wake-up signal configuration, updating the CellA list, updating the NES cell list, and disabling the NES mode of NES cells.

[0316] For specific implementation details, please refer to the following: Figures 13-15 The embodiments shown are not described in detail here.

[0317] like Figure 17 As shown, Figure 17 This illustration shows another communication method for a second network device to determine an adjustment strategy, provided in an embodiment of this application. The second network device has a wake-up signal configuration. The communication method includes:

[0318] Steps 1701 to 1702 are the same as steps 1601 to 1602 in the above embodiments, and will not be repeated here.

[0319] Step 1703: The second network device sends an instruction message to the first network device. Correspondingly, the first network device receives the instruction message from the second network device.

[0320] The instruction information is used to instruct the second network device to stop broadcasting wake-up signal configuration for the first network device.

[0321] As an example, the second network device determines, based on the target field in the first message, that the second network device is no longer suitable for configuring the broadcast wake-up signal for the first network device, and sends an indication message to the first network device to instruct the second network device to stop configuring the broadcast wake-up signal for the first network device.

[0322] In one possible implementation, the target field includes numAttmpts. Based on the data in numAttmpts, the second network device determines that the number of failed attempts by the terminal device to access the first network device is too high. Therefore, it can be concluded that the second network device is not suitable for configuring the broadcast wake-up signal for the first network device and needs to stop configuring the broadcast wake-up signal.

[0323] Optionally, the second network device may also determine the enhanced broadcast wake-up signal configuration based on the target field in the first message.

[0324] For example, if the second network device determines that the connection failure is due to "the first network device did not receive the uplink wake-up signal" based on the result of the connectionFailureType record in the target field, then the second network device can increase the broadcast of the wake-up signal configuration, such as shortening the broadcast period or increasing the broadcast power.

[0325] If the second network device determines that the connection failure is due to "the terminal device not receiving SIB1", then the second network device sends a response message to the first network device, and the first network device determines an adjustment strategy based on the response message. The specific implementation method is the same as the embodiment described above where the first network device adjusts its strategy, and will not be repeated here.

[0326] Step 1704: The first network device sends a first feedback message to the second network device. Correspondingly, the second network device receives the first feedback message from the first network device.

[0327] In one scenario provided in this application embodiment, an RRC connection is established between a terminal device and a second network device, and the second network device does not have a wake-up signal configuration.

[0328] In one possible implementation, the terminal device first attempts to access the NES cell. If the terminal device fails to access the NES cell, it can establish an RRC connection with CellX. Alternatively, the terminal device can disconnect the RRC connection with the NES cell and then establish an RRC connection with CellX, meaning the terminal device switches from the NES cell to CellX.

[0329] like Figure 18 As shown, Figure 18This illustration shows another communication method for a second network device to determine an adjustment strategy, provided in an embodiment of this application. The second network device does not have a wake-up signal configuration. The communication method includes:

[0330] Steps 1801 to 1804 are the same as steps 1601 to 1604 in the above embodiments, and will not be repeated here.

[0331] like Figure 19 As shown, Figure 19 This illustration shows another communication method for a second network device to determine an adjustment strategy, provided in an embodiment of this application. The second network device does not have a wake-up signal configuration. The communication method includes:

[0332] Steps 1901 to 1902 are the same as steps 1801 to 1802 in the above embodiments, and will not be repeated here.

[0333] Step 1903: The second network device sends a request message to the first network device. Correspondingly, the first network device receives a request message from the third network device.

[0334] The request message is used to request the start of configuration for broadcasting a wake-up signal for the first network device.

[0335] As an example, the second network device sends a request message to the first network device based on the target field in the first message, requesting configuration for broadcasting a wake-up signal for the first network device.

[0336] In one possible implementation, the target field includes connectionFailureType and numAttempts. The third network device determines, based on the data in connectionFailureType and numAttempts, that multiple terminal devices are attempting to access the first network device from the second network device, and sends a request message to the first network device.

[0337] Step 1904: The first network device sends a second feedback message to the second network device. Correspondingly, the second network device receives the second feedback message from the first network device.

[0338] The above Figures 12-19 The embodiments shown are all applied to the 3GPP architecture. When the communication system architecture is O-RAN architecture, the steps of the above embodiments are also applicable.

[0339] like Figure 20 As shown, Figure 20This is a schematic diagram of the O-RAN architecture application framework provided in the embodiments of this application. The communication system includes a radio access network intelligent controller (RIC). The RIC includes near-real-time (near-RT) RICs and non-real-time (non-RT) RICs.

[0340] Near real-time RICs are used for model training and inference. For example, they can be used to train artificial intelligence (AI) models and then for inference. Near real-time RICs can obtain information from network devices and / or terminal devices via RAN nodes and / or terminals. This information can be used as training data or inference data.

[0341] The O-RAN node includes a centralized unit (CU), a centralized unit-control plane (CU-CP), a centralized unit-user plane (CU-UP), a distributed unit (DU), and a radio unit (RU). For example... Figure 21 The diagram shows the partitioning of CU-DU-RU under the O-RAN architecture.

[0342] The CU is used to implement the radio resource control (RRC) layer, packet data convergence protocol (PDCP) layer, service data adaptation protocol (SDAP) layer, and other control functions in the 3GPP standard.

[0343] The CU-CP, similar to the CU-CP in the NR system, is used to implement the functions of the RRC layer and the control plane functions of the PDCP layer. It is part of the CU.

[0344] CU-UP, similar to CU-UP in the NR system, is used to implement the functions of the SDAP layer and the user plane functions of the PDCP layer. It is part of the CU.

[0345] DU, based on low-layer function segmentation, is used to implement the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and Higher Physical Layer (PHY) in the 3GPP standard. The Higher Physical Layer functions include one or more of the following: forward error correction (FEC) encoding / decoding, scrambling / descrambling, or modulation / demodulation.

[0346] RU, based on low-layer function partitioning, is used to implement lower physical layer (Lower PHY) functions and radio frequency (RF) functions in the 3GPP standard. These lower PHY functions include one or more of the following: Fast Fourier Transform (FFT) / Inverse Fast Fourier Transform (IFFT) transformation, digital beamforming, or extraction and filtering of the Physical Random Access Channel (PRACH). It is similar to the Transmission Reception Point (TRP) or Remote Radio Head (RRH) in 3GPP, but includes lower PHY functions such as FFT / IFFT or PRACH extraction.

[0347] Optionally, near real-time RIC can deliver inference results to RAN nodes and / or terminals.

[0348] Optionally, inference results can be exchanged between the CU and DU, and / or between the DU and RU. For example, the near real-time RIC delivers the inference results to the DU, which then sends them to the RU. This enables near real-time intelligent management of the RAN. Through data collection and related operations on the E2 interface, near real-time control and optimization of O-RAN modules and resources are achieved.

[0349] Non-real-time RICs are used for model training and inference. For example, they are used to train AI models and then use those models for inference. Non-real-time RICs can obtain information from the network device side and / or the terminal device side from the RAN node and / or the terminal device side. This information can be used as training data or inference data, and the inference results can be delivered to the RAN node and / or the terminal device.

[0350] Optionally, inference results can be exchanged between CU and DU, and / or between DU and RU. For example, a non-real-time RIC can submit inference results to DU, which can then send them to RU.

[0351] Near real-time RICs and non-real-time RICs can also be configured as separate network elements. Optionally, near real-time RICs and non-real-time RICs can also be part of other devices.

[0352] For example, near real-time RICs are set in RAN nodes (e.g., CU, DU), while non-real-time RICs are set in OAM, cloud servers, core network devices, or other network devices.

[0353] In the O-RAN architecture, the NES cell in this application embodiment includes DU and CU.

[0354] In such Figure 12 In the communication method shown, since the DU is responsible for cell admission control, in step 1203, the DU of the NES cell updates the wake-up signal configuration to adjust the admission threshold.

[0355] In such Figure 13 In the communication method shown, since the CU is responsible for mastering the neighbor cell information, in step 1303, the CU of the NES cell is responsible for updating the Cell A list.

[0356] In such Figure 14 In the communication method shown, since both the DU and CU can be responsible for updating the NES mode state of the NES cell, in step 1403, the NES mode state of the NES cell can be updated by either the DU or the CU. Alternatively, since both the DU and CU can be responsible for updating the NES cell list, in step 1403, the NES cell list can be updated by either the DU or the CU.

[0357] In one possible implementation, such as Figure 22 The diagram shows a schematic representation of four specific implementation methods for updating the NES mode status or updating the NES cell list in an embodiment of this application.

[0358] like Figure 22 As shown in Figure (a), the NES cell list is updated by the CU, and the NES mode status of the NES cells is updated by the DU. Specific methods include:

[0359] Step 2201a: The terminal device sends a first message to the CU of the NES cell. Correspondingly, the CU of the NES cell receives the first message from the terminal device.

[0360] The first message includes a target field, which indicates the report information related to ODSIB1.

[0361] Step 2202a: The CU of the NES cell sends a first message to the DU. Correspondingly, the DU of the NES cell receives the first message from the CU.

[0362] Step 2203a: The CU of the NES cell updates the NES cell list according to the first message and sends the updated NES cell list to the DU. Correspondingly, the DU of the NES cell receives the updated NES cell list from the CU.

[0363] For example, the CU of an NES cell will remove the NES cell currently accessed by the terminal device from the NES cell list.

[0364] Step 2204a: The DU of the NES cell updates the NES mode status of the NES cell.

[0365] For example, the DU of an NES cell will turn off the NES mode of the NES cell to which the current terminal device is connected.

[0366] Step 2205a: The DU of the NES cell sends the NES cell in NES mode to the CU.

[0367] like Figure 22 As shown in Figure (b), the CU updates the NES cell list and the NES mode status of the NES cells. Specific methods include:

[0368] Steps 2201b to 2203b are the same as steps 2201a to 2203a in the above embodiments, and will not be repeated here.

[0369] Step 2204b: The CU of the NES cell updates the NES mode status of the NES cell.

[0370] For example, the CU of an NES cell will turn off the NES mode of the NES cell to which the current terminal device is connected.

[0371] like Figure 22 As shown in Figure (c), the DU updates the NES cell list and the NES mode status of the NES cells. Specific methods include:

[0372] Steps 2201c to 2202c are the same as steps 2201a to 2202a in the above embodiments, and will not be described again here.

[0373] Step 2203c: The DU of the NES cell updates the NES cell list based on the first message.

[0374] For example, the DU of an NES cell will remove the NES cell currently accessed by the terminal device from the NES cell list.

[0375] Step 2204c: The DU of the NES cell updates the NES mode status of the NES cell.

[0376] For example, the DU of an NES cell will turn off the NES mode of the NES cell to which the current terminal device is connected.

[0377] Step 2205c: The DU of the NES cell sends the NES cell in NES mode to the CU.

[0378] like Figure 22 As shown in Figure (d), the NES cell list is updated by the DU, and the NES mode status of the NES cells is updated by the CU. Specific methods include:

[0379] Steps 2201d to 2202d are the same as steps 2201a to 2202a in the above embodiments, and will not be repeated here.

[0380] Step 2203d: The DU of the NES cell updates the NES cell list based on the first message.

[0381] For example, the DU of an NES cell will remove the NES cell currently accessed by the terminal device from the NES cell list.

[0382] Step 2204d: The CU of the NES cell updates the NES mode status of the NES cell based on the first message.

[0383] For example, the CU of an NES cell will turn off the NES mode of the NES cell to which the current terminal device is connected.

[0384] In such Figure 17 In the communication method shown, since both the CU and DU of CellA can decide whether to stop configuring the NES cell broadcast wake-up signal, in step 1703, the CU or DU of CellA sends an indication message.

[0385] In such Figure 19 In the communication method shown, since both the CU and DU of CellX can request to configure the NES cell broadcast wake-up signal, in step 1903, the CU or DU of CellX sends a request message.

[0386] The above mainly describes the solutions of the embodiments of this application from the perspective of interaction between various network elements. It is understood that each network element, such as a terminal or network device, includes corresponding structures and / or software modules to perform the above functions in order to achieve them. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0387] This application embodiment can divide functional units according to the terminal device and network device described above. For example, each function can be divided into separate functional units, or two or more functions can be integrated into one processing unit. The integrated unit can be implemented in hardware or as a software functional unit. It should be noted that the unit division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0388] The above combination Figures 11-22 The methods described in the embodiments of this application have been explained. The communication apparatus provided in the embodiments of this application for executing the above methods is described below. Those skilled in the art will understand that the methods and apparatus can be combined with and referenced in each other, and the communication apparatus provided in the embodiments of this application can execute the steps performed by the network controller and the terminal in the above analysis method.

[0389] When using integrated units Figure 23 The communication device involved in the above embodiments is shown. The communication device 250 may include a communication module 2301 and a processing module 2302.

[0390] In an alternative implementation, the communication device 230 may further include a storage module 2303 for storing the program code and data of the communication device.

[0391] On one hand, the communication device 230 is a management service module, or a chip applied in a management service module. In this case, the communication module 2301 is used to support communication between the communication device and external network elements (e.g., a third party). For example, the communication module 2301 is used to perform the send / receive operations of the management service module in the above method embodiments. The processing module 2302 is used to perform the processing operations of the management service module in the above method embodiments.

[0392] In one example, the communication module 2301 is used to perform the above embodiments. Figure 6 The processing actions performed by the management service module in steps 601 to 603.

[0393] The processing module 2302 can be a processor or controller, such as a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, etc. The communication module can be a transceiver, transceiver circuitry, or communication interface, etc. The storage module can be a memory.

[0394] When the processing module 2302 is a processor 2401 or a processor 2405, the communication module 2301 is a transceiver 2403, and the storage module 2303 is a memory 2402, the communication device involved in this application can be... Figure 24 The communication device shown.

[0395] Figure 24 This illustration shows a schematic diagram of the hardware structure of a communication device according to an embodiment of this application. The hardware structures of the terminal device and network device in this embodiment can be referenced as follows: Figure 24 The structure shown is that the communication device includes a processor 2401, a communication line 2404, and at least one transceiver. Figure 24 (The illustration is merely exemplary, using transceiver 2403 as an example only).

[0396] The processor 2401 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of programs according to the present application.

[0397] Communication line 2404 may include a path for transmitting information between the aforementioned components.

[0398] Transceiver 2403 is a device that uses any transceiver-like device to communicate with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc.

[0399] Optionally, the communication device may also include a memory 2402.

[0400] Memory 2402 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. Memory 2402 may exist independently and be connected to processor 2401 via communication line 2404. Memory 2402 may also be integrated with processor 2401.

[0401] The memory 2402 stores computer execution instructions for implementing the scheme of this application, and its execution is controlled by the processor 2401. The processor 2401 executes the computer execution instructions stored in the memory 2402, thereby implementing the communication method provided in the following embodiments of this application.

[0402] Optionally, the computer execution instructions in the embodiments of this application may also be referred to as application code, and the embodiments of this application do not specifically limit this.

[0403] In a specific implementation, as one example, the processor 2401 may include one or more CPUs, for example... Figure 24 CPU0 and CPU1 in the CPU.

[0404] In a specific implementation, as one example, the communication device may include multiple processors, for example... Figure 24 Processors 2401 and 2402 are mentioned. Each of these processors can be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. Here, "processor" can refer to one or more devices, circuits, and / or processing cores used to process data (e.g., computer program instructions).

[0405] Figure 25 This is a schematic diagram of the structure of chip 250 provided in an embodiment of this application. Chip 250 includes one or more (including two) processors 2510 and communication interfaces 2530.

[0406] Optionally, the chip 250 also includes a memory 2540, which may include read-only memory and random access memory, and provides operation instructions and data to the processor 2510. A portion of the memory 2540 may also include non-volatile random access memory (NVRAM).

[0407] In some implementations, memory 2540 stores elements such as execution modules or data structures, or subsets thereof, or extended sets thereof.

[0408] In this embodiment of the application, the corresponding operation is executed by calling the operation instructions stored in the memory 2540 (the operation instructions can be stored in the operating system).

[0409] One possible implementation is that the terminal and network devices have similar structures, and different devices can use different chips to achieve their respective functions.

[0410] The processor 2510 controls the processing operations of any terminal or network device. The processor 2510 can also be referred to as a central processing unit (CPU).

[0411] Memory 2540 may include read-only memory and random access memory, and provides instructions and data to processor 2510. A portion of memory 2540 may also include NVRAM. For example, in an application, memory 2540, communication interface 2530, and memory 2540 are coupled together via bus system 2520, which, in addition to a data bus, may also include a power bus, control bus, and status signal bus, etc. However, for clarity, in... Figure 25 The general labeled all buses as Bus System 2520.

[0412] The methods disclosed in the embodiments of this application can be applied to or implemented by the processor 2510. The processor 2510 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware in the processor 2510 or by instructions in the form of software. The processor 2510 may be a general-purpose processor, a digital signal processor (DSP), an ASIC, a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory 2540. Processor 2510 reads the information in memory 2540 and completes the steps of the above method in conjunction with its hardware.

[0413] The communication module described above can be a communication interface of the device, used to receive signals from other devices. For example, when the device is implemented as a chip, the communication module is the communication interface used by the chip to receive or send signals from other chips or devices.

[0414] On the one hand, a computer-readable storage medium is provided, in which instructions are stored, which, when executed, implement as follows: Figure 11 The function performed by the first network device.

[0415] On the one hand, a computer program product including instructions is provided, wherein the computer program product includes instructions that, when executed, implement such... Figure 11 The function performed by the first network device.

[0416] On the one hand, a chip is provided for use in a computing network controller. The chip includes at least one processor and a communication interface, the communication interface being coupled to the at least one processor. The processor is used to execute instructions to achieve, for example... Figure 11 The function performed by the first network device.

[0417] This application provides a communication system, which includes a management service module and a computing platform. The management service module is used to implement, for example,... Figure 11 The function is performed by the first network device. The computing platform includes multiple computing nodes, which are used to execute computing tasks corresponding to service requests.

[0418] The explanations and beneficial effects of the relevant content in any of the communication devices provided above can be found in the corresponding method embodiments provided above, and will not be repeated here.

[0419] In this embodiment, the terminal device or network device includes a hardware layer, an operating system layer running on top of the hardware layer, and an application layer running on top of the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also called main memory). The operating system can be any one or more computer operating systems that implement business processing through processes, such as Linux, Unix, Android, iOS, or Windows. The application layer includes applications such as browsers, address books, word processing software, and instant messaging software. Furthermore, this embodiment does not specifically limit the specific structure of the execution entity of the method provided in this embodiment, as long as it can communicate according to the method provided in this embodiment by running a program that records the code of the method provided in this embodiment. For example, the execution entity of the method provided in this embodiment can be a terminal device or a network device, or a functional module in the terminal device or network device that can call and execute a program.

[0420] Furthermore, various aspects or features of this application can be implemented as methods, apparatus, or articles of manufacture using standard programming and / or engineering techniques. The term "article of manufacture" as used herein encompasses a computer program accessible from any computer-readable device, carrier, or medium. For example, computer-readable media may include, but are not limited to: magnetic storage devices (e.g., hard disks, floppy disks, or magnetic tapes), optical discs (e.g., compact discs (CDs), digital versatile discs (DVDs), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memory (EPROMs), cards, sticks, or key drives, etc.). Additionally, the various storage media described herein may represent one or more devices and / or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and / or carrying instructions and / or data.

[0421] It should be understood that the processor mentioned in the embodiments of this application can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor.

[0422] It should also be understood that the memory mentioned in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM).

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

[0424] It should be noted that the memories described herein are intended to include, but are not limited to, these and any other suitable types of memories.

[0425] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0426] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0427] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0428] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0429] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0430] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0431] 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, The method includes: Receive a first message, the first message including a target field, the target field being used to instruct the terminal device to receive information from ODSIB1; Based on the target field, update the conditions for the terminal device to access the first cell, or update the list of second cells associated with the first cell; The first cell is the area covered by the first network device. The second network device corresponding to any second cell in the second cell list is used to broadcast a wake-up signal configuration to the terminal device. The wake-up signal configuration is used by the terminal device to send a wake-up signal to the first network device. The wake-up signal is used to instruct the first network device to send ODSIB1 to the terminal device.

2. The method according to claim 1, characterized in that, The method further includes: Based on the target field, update the list of first cells where the first cell is located, and / or, turn off the network power saving mode of the first cell, the network power saving mode being used by the first network device to send ODSIB1 to the terminal device.

3. The method according to claim 1 or 2, characterized in that, Before receiving the first message, the method further includes: Establish an RRC connection with the terminal device; A second message is sent to the terminal device via the RRC connection. The second message is used to request the terminal device to provide information for receiving SIB1.

4. The method according to claim 1 or 2, characterized in that, The receipt of the first message includes: The first message is received from a second network device, the second network device having the wake-up signal configuration, and the second network device having an RRC connection with the terminal device.

5. The method according to claim 4, characterized in that, The method further includes: The device receives an instruction from the second network device, the instruction being used to instruct the second network device to stop broadcasting the wake-up signal configuration to the terminal device.

6. The method according to claim 1 or 2, characterized in that, The receipt of the first message includes: The terminal device receives the first message from a second network device, which does not have the wake-up signal configuration, and the terminal device has an RRC connection with the second network device.

7. The communication method according to claim 6, characterized in that, The method further includes: A request message is received from the second network device, the request message being used to request that the wake-up signal configuration be broadcast to the terminal device.

8. A communication method, characterized in that, The method includes: Send a second message to the terminal device, the second message being used to request the terminal device to provide information on receiving ODSIB1 sent by the first network device; A first message is received from the terminal device, the first message including a target field, the target field being used to instruct the terminal device to receive information from the ODSIB1.

9. The communication method according to claim 8, characterized in that, The method further includes: Send an instruction message to the first network device, the instruction message being used to instruct the cessation of broadcasting the wake-up signal configuration of the first network device to the terminal device; or... A request message is sent to the first network device, the request message being used to request the broadcast of the wake-up signal configuration of the first network device to the terminal device.

10. A communication method, characterized in that, The method includes: The terminal device receives a second message from a first network device or a second network device, the second message being used to request the terminal device to provide information about receiving ODSIB1 sent by the first network device; the second network device is a network device used to broadcast the wake-up signal configuration of the first network device to the terminal device; the wake-up signal configuration is used by the terminal device to send an uplink wake-up signal to the first network device, the uplink wake-up signal being used to trigger the first network device to send ODSIB1 to the terminal device. A first message is sent to the first network device or the second network device. The first message includes a target field, which is used to instruct the terminal device to receive information from ODSIB1.

11. A communication device, characterized in that, The device includes: a communication module and a processing module; Wherein, the processing module is used to perform the processing action in the method according to any one of claims 1 to 7, and the communication module is used to perform the receiving or sending action in the method according to any one of claims 1 to 7; or, The processing module is used to perform the processing action in the method of claim 8 or 9, and the communication module is used to perform the receiving or sending action in the method of claim 8 or 9; or... The processing module is used to perform the processing action in the method of claim 10, and the communication module is used to perform the receiving or sending action in the method of claim 10.

12. A communication system, characterized in that, The communication system includes: a first network device and a terminal device; Wherein, the first network device is used to implement the method according to any one of claims 1 to 7, and the terminal device is used to implement the method according to claim 10.

Images