Communication method, communication device, communication system, storage medium, and program product
Patent Information
- Application Number
- PCT/CN2025/093846
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-09
- Publication Date
- 2026-11-12
Smart Images

Figure CN2025093846_12112026_PF_FP_ABST
Abstract
Description
Communication methods, communication equipment, communication systems, storage media and software products Technical Field
[0001] This disclosure relates to the field of communication technology, and in particular to a communication method, communication device, communication system, storage medium, and program product. Background Technology
[0002] In the field of communication technology, in order to save power consumption of terminal equipment, a low power wake-up receiver (LP-WUR) has been introduced. The LP-WUR is used to listen for the lower power wake-up signal (LP-WUS) so that the terminal's main transceiver (MR) can be woken up after the LP-WUS is detected. After the main transceiver is woken up, it can perform subsequent paging procedures. Summary of the Invention
[0003] This disclosure provides a communication method, communication device, communication system, storage medium, and program product.
[0004] According to a first aspect of the present disclosure, a communication method is provided, wherein the method is performed by a core network device, the method comprising: sending first information to a terminal or an access network device, the first information being used to determine whether to use LP-WUS.
[0005] According to a second aspect of the present disclosure, a communication method is provided, wherein the method is performed by an access network device, the method comprising: sending first information to a terminal, the first information being used to determine whether to use LP-WUS.
[0006] According to a third aspect of the present disclosure, a communication method is provided, wherein the method is performed by a terminal, the method comprising: receiving first information sent by a core network device or an access network device, the first information being used to determine whether to use a low-power wake-up signal LP-WUS.
[0007] According to a fourth aspect of the present disclosure, a communication method is provided, wherein the method is performed by a communication system, the method comprising: a core network device or an access network device sending first information to a terminal; wherein the first information is used to determine whether to use LP-WUS.
[0008] According to a fifth aspect of the present disclosure, a communication device is provided, wherein the communication device is used to perform the communication method provided by the first aspect, the second aspect, or the third aspect.
[0009] According to a sixth aspect of the present disclosure, a communication system is provided, wherein the communication system includes a terminal, an access network device, and a core network device, the core network device being configured to implement the communication method provided in the first aspect, the access network device being configured to implement the communication method provided in the second aspect, and the terminal being configured to implement the communication method provided in the third aspect.
[0010] According to a seventh aspect of the present disclosure, a storage medium is provided, wherein the storage medium stores instructions that, when executed on a communication device, cause the communication device to perform the communication method provided by the first aspect, the second aspect, or the third aspect.
[0011] According to an eighth aspect of the present disclosure, a program product is provided that, when executed by a communication device, causes the communication device to perform the communication method provided by the first aspect, the second aspect, or the third aspect.
[0012] In the technical solution provided by the embodiments of this disclosure, the core network device can control the terminal or access network device to use or disable LP-WUS by sending first information to the terminal or access network device. This enables the core network device to control the terminal or access network device to disable LP-WUS in some scenarios where it is not suitable to use LP-WUS (e.g., emergency calls), thereby reducing service latency caused by the terminal or access network device using LP-WUS.
[0013] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit the embodiments of this disclosure. Attached Figure Description
[0014] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments of the invention and, together with the description, serve to explain the principles of the embodiments of the invention.
[0015] Figure 1 is a schematic diagram of the architecture of a communication system according to an exemplary embodiment;
[0016] Figure 2A is an interactive schematic diagram of a communication method according to an exemplary embodiment;
[0017] Figure 2B is a schematic diagram of an interaction of a communication method according to an exemplary embodiment;
[0018] Figure 2C is an interactive schematic diagram of a communication method according to an exemplary embodiment;
[0019] Figure 3 is an interactive schematic diagram of a communication method according to an exemplary embodiment;
[0020] Figure 4A is a schematic diagram of the structure of a network device according to an exemplary embodiment;
[0021] Figure 4B is a schematic diagram of the structure of a network device according to an exemplary embodiment;
[0022] Figure 4C is a schematic diagram of the structure of a terminal according to an exemplary embodiment;
[0023] Figure 5A is a schematic diagram of the structure of a communication device according to an exemplary embodiment;
[0024] Figure 5B is a schematic diagram of the structure of a chip according to an exemplary embodiment. Detailed Implementation
[0025] This disclosure provides a communication method, communication device, communication system, storage medium, and program product.
[0026] In a first aspect, embodiments of this disclosure provide a communication method, wherein the method is executed by a core network device, the method comprising: sending first information to a terminal or an access network device, the first information being used to determine whether to use LP-WUS.
[0027] In the above embodiments, the core network device can control the terminal or access network device to use or disable LP-WUS by sending first information to the terminal or access network device. This enables the core network device to control the terminal or access network device to disable LP-WUS in some scenarios where it is not suitable to use LP-WUS (e.g., emergency calls), thereby reducing service latency caused by the terminal or access network device using LP-WUS.
[0028] In conjunction with some embodiments of the first aspect, in some embodiments, the first information is also used to determine whether to use a paging packet method based on terminal ID to determine the paging packet information of the terminal.
[0029] In the above embodiments, the core network device can also use the first information to indicate whether the terminal or access network device uses a paging packet method based on the terminal ID, thereby controlling the paging packet method used by the terminal or access network device. This allows for adjusting the control method for disabling LP-WUS on the terminal or access network device when different paging packet methods are used, thus enabling the core network device to effectively control the disabling of LP-WUS on the terminal or access network device.
[0030] In conjunction with some embodiments of the first aspect, in some embodiments, the first information sent by the core network device to the terminal is used to indicate at least one of the following: the first terminal does not use LP-WUS; the first terminal does not use LP-WUS in at least one first tracking area (TA); the first terminal does not use LP-WUS in a first area or a first cell of at least one first TA; the first area is the signal coverage area of the designated access network device; wherein the first terminal is a terminal designated by the core network device.
[0031] In the above embodiments, the core network device can use the first information to instruct the first terminal to disable LP-WUS, or use the first information to instruct the first terminal to disable the first TA of LP-WUS, or use the first information to instruct the first terminal to disable the first area or the first cell of LP-WUS. This enables different scenarios in which the terminal is explicitly instructed to disable LP-WUS through the first information. In this way, adverse effects such as service delay caused by the terminal using LP-WUS in the above scenarios can be effectively avoided, which is conducive to the core network device efficiently controlling the terminal to disable LP-WUS.
[0032] In conjunction with some embodiments of the first aspect, in some embodiments, the first information sent by the core network device to the terminal is used to indicate a first triggering condition; when the first triggering condition is met, the terminal does not use LP-WUS.
[0033] In the above embodiments, the core network device can use the first information to inform the terminal of the first triggering condition, so that the terminal disables LP-WUS when the first triggering condition is met. Thus, the first triggering condition indicated by the first information implicitly indicates the situation of disabling LP-WUS. In this way, the terminal can flexibly determine whether to disable LP-WUS based on the real-time network conditions and its own network environment, which is beneficial for the core network device to accurately control the terminal to disable LP-WUS.
[0034] In conjunction with some embodiments of the first aspect, in some embodiments, the first triggering condition includes at least one of the following: the wake-up latency supported by the terminal is greater than a first threshold; the offset between the LP-WUS configured by the access network device and the paging timing PO is greater than a second threshold; the offset corresponding to the LP-WUS monitored by the terminal is greater than a third threshold.
[0035] In the above embodiments, since the scenarios indicated by the first triggering condition all lead to significant service latency, the core network equipment sets the first triggering condition so that the terminal stops using LP-WUS when the first triggering condition is met, thereby reducing service latency.
[0036] In conjunction with some embodiments of the first aspect, in some embodiments, the first information is also used by the terminal to determine that LP-WUS is not used during the execution of the first service.
[0037] In the above embodiments, the core network device sends first information to the terminal, enabling the terminal to adjust its LP-WUS usage strategy during the execution of the first service, so as to better adapt to the network environment and service requirements and reduce service latency caused by inappropriate use of LP-WUS.
[0038] In conjunction with some embodiments of the first aspect, in some embodiments, the first information sent by the core network device to the access network device is used to indicate at least one of the following: LP-WUS is not used for a first terminal; the first terminal is a terminal designated by the core network device; LP-WUS is not used for a first type of terminal; the first type of terminal is a terminal performing a first service.
[0039] In the above embodiments, the core network device sends first information to the access network device to inform the access network device of the first terminal or the first type of terminal that disables LP-WUS, so that the access network device can accurately manage the use of LP-WUS by the first terminal or the first type of terminal, thereby effectively avoiding adverse effects such as service delay caused by the access network device using LP-WUS on the first terminal or the first type of terminal that is not suitable for using LP-WUS.
[0040] In conjunction with some embodiments of the first aspect, in some embodiments, the first information sent by the core network device to the access network device is used to indicate a second triggering condition, and when the second triggering condition is met, the access network device does not use LP-WUS for the first terminal or the first type of terminal.
[0041] In the above embodiments, the core network device can use the first information to inform the access network device of the second triggering condition, so that the access network device stops using LP-WUS on the first terminal or the first type of terminal when the second triggering condition is met. Thus, the second triggering condition indicated by the first information implicitly indicates the situation of disabling LP-WUS. In this way, the access network device can flexibly determine whether to disable LP-WUS according to the real-time network conditions, which is beneficial for the core network device to accurately control the access network device to disable LP-WUS.
[0042] In conjunction with some embodiments of the first aspect, in some embodiments, the second triggering condition includes: the offset between the LP-WUS configured by the access network device and the paging timing PO is greater than a fourth threshold.
[0043] In the above embodiments, since the scenarios indicated by the second triggering condition all lead to significant service latency, the core network device sets the second triggering condition so that the access network device stops using LP-WUS when the second triggering condition is met, thereby reducing service latency.
[0044] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes: receiving second information sent by a terminal or access network device, the second information being used to indicate the wake-up latency supported by the terminal; sending first information to the terminal or access network device, including: sending the first information to the terminal or access network device based on the second information.
[0045] In the above embodiments, the core network device can receive second information sent by the terminal or the access network device to know the wake-up latency supported by the terminal based on the second information, so as to determine whether LP-WUS needs to be disabled according to the wake-up latency supported by the terminal. This allows the core network device to take into account the wake-up latency of the terminal when controlling the use of LP-WUS, and thus control the terminal to disable LP-WUS when it is not suitable for the terminal to use LP-WUS, thereby reducing latency.
[0046] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes: receiving third information sent by an access network device, the third information being used to indicate at least one offset value between the LP-WUS configured by the access network device and the paging timing PO; the third information is also used by the core network device to determine the first information.
[0047] In the above embodiments, the core network device can receive third information sent by the access network device to obtain at least one offset value configured by the access network device based on the third information, so as to determine whether LP-WUS needs to be disabled according to the at least one offset value configured by the access network device. This allows the core network device to take into account the configuration of the offset value between the LP-WUS listening time and the paging time PO when controlling the use of LP-WUS, so as to control the terminal to disable LP-WUS when the offset value configuration is not suitable for using LP-WUS, thereby reducing latency.
[0048] In conjunction with some embodiments of the first aspect, in some embodiments, the third information is sent by the access network device when the offset value is greater than the fifth threshold.
[0049] In the above embodiments, the third information is sent by the access network device when the offset value is greater than the fifth threshold. On the one hand, this allows the core network device to know the configuration of the offset value in a timely manner when the offset value configured by the access network device is greater than the fifth threshold. This is beneficial for the core network device to control the terminal to disable LP-WUS when the configuration of the offset value is not suitable for using LP-WUS. On the other hand, it can also reduce unnecessary interactions between the core network device and the access network device when the offset value configured by the access network device is small, thereby reducing message overhead.
[0050] In conjunction with some embodiments of the first aspect, in some embodiments, the third information is also used to indicate whether the access network device supports the use of a paging packet method based on terminal ID.
[0051] In the above embodiments, the third information is used to inform the core network device of the access network device's support capability for paging packet mode based on terminal ID, so that the core network device can determine whether LP-WUS needs to be disabled based on the support capability indicated by the third information. This allows the core network device to take into account the access network device's support capability for paging packet mode based on terminal ID when controlling the use of LP-WUS, and thus determine whether to control the access network device or terminal to disable LP-WUS through the first information.
[0052] Secondly, embodiments of this disclosure provide a communication method, which is executed by an access network device. The method includes: sending first information to a terminal, the first information being used to determine whether to use LP-WUS.
[0053] In the above embodiments, the access network device can control the terminal to use or disable LP-WUS by sending first information to the terminal, thereby enabling the access network device to control the terminal to disable LP-WUS in some scenarios where it is not suitable to use LP-WUS (such as emergency calls), so as to reduce service latency caused by the terminal using LP-WUS.
[0054] In conjunction with some embodiments of the second aspect, in some embodiments, the first information is also used to determine whether to use a paging packet method based on terminal ID to determine the terminal's paging packet information.
[0055] In conjunction with some embodiments of the second aspect, in some embodiments, the first information is used to indicate at least one of the following: the second terminal does not use LP-WUS; the second terminal is a terminal designated by the access network device; the first type of terminal does not use LP-WUS; the first type of terminal is a terminal performing the first service.
[0056] In the above embodiments, the access network device sends first information to the terminal to inform the terminal of the second terminal or the first type of terminal that has disabled LP-WUS, so that the terminal can accurately know whether it needs to disable LP-WUS, thereby effectively avoiding adverse effects such as service delay caused by the use of LP-WUS by the second terminal or the first type of terminal that is not suitable for using LP-WUS.
[0057] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes: receiving first information sent by a core network device.
[0058] In the above embodiments, the access network device can receive first information sent by the core network device to know the LP-WUS disabling status based on the first information sent by the core network device. This allows the access network device to send first information to the terminal to control the terminal to use or disable LP-WUS. In scenarios where LP-WUS is not suitable (e.g., emergency calls), the access network device can accurately control the terminal to disable LP-WUS under the instruction of the core network device, thereby reducing service latency caused by the terminal using LP-WUS.
[0059] In conjunction with some embodiments of the second aspect, in some embodiments, the first information sent by the core network device is used to indicate at least one of the following: LP-WUS is not used for a first terminal; the first terminal is a terminal designated by the core network device; LP-WUS is not used for a first type of terminal; the first type of terminal is a terminal performing a first service.
[0060] In conjunction with some embodiments of the second aspect, in some embodiments, the first information sent by the core network device to the access network device is used to indicate a second triggering condition, and when the second triggering condition is met, the access network device does not use LP-WUS for the first terminal or the first type of terminal.
[0061] In conjunction with some embodiments of the second aspect, in some embodiments, the second triggering condition includes: the offset between the LP-WUS configured by the access network device and the paging timing PO is greater than a fourth threshold.
[0062] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes: receiving second information sent by a terminal or core network device, the second information being used to indicate the wake-up latency supported by the terminal; and sending first information to the terminal, including: sending the first information to the terminal based on the second information.
[0063] In the above embodiments, the access network device can receive second information sent by the terminal or the core network device to know the wake-up latency supported by the terminal based on the second information, so as to determine whether LP-WUS needs to be disabled according to the wake-up latency supported by the terminal. This allows the access network device to take into account the wake-up latency of the terminal when controlling the use of LP-WUS, and thus control the terminal to disable LP-WUS when it is not suitable for the terminal to use LP-WUS, thereby reducing latency.
[0064] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes: sending third information to the core network device, the third information being used to indicate at least one offset value between the LP-WUS configured by the access network device and the paging timing PO; the third information is also used by the core network device to determine the first information.
[0065] In conjunction with some embodiments of the second aspect, in some embodiments, sending third information to the core network device includes: determining that the configured offset value is greater than a fifth threshold, and then sending the third information to the core network device.
[0066] In conjunction with some embodiments of the second aspect, in some embodiments, the third information is also used to indicate whether the access network device supports the use of a paging packet method based on terminal ID.
[0067] Thirdly, embodiments of this disclosure provide a communication method, wherein the method is executed by a terminal, the method comprising: receiving first information sent by a core network device or an access network device, the first information being used to determine whether to use a low-power wake-up signal LP-WUS.
[0068] In the above embodiments, the terminal can receive first information sent by the core network device or the access network device to determine whether to use or disable LP-WUS based on the first information. This enables the terminal to disable LP-WUS under the control of the core network device or the access network device in some scenarios where it is not suitable to use LP-WUS (e.g., emergency calls), thereby reducing service latency caused by the terminal using LP-WUS.
[0069] In conjunction with some embodiments of the third aspect, in some embodiments, the first information is further used to determine whether to use a paging packet method based on the terminal identifier ID to determine the terminal's paging packet information.
[0070] In conjunction with some embodiments of the third aspect, in some embodiments, the first information sent by the core network device is used to indicate at least one of the following: the first terminal does not use LP-WUS; the first terminal does not use LP-WUS in at least one first tracking area (TA); the first terminal does not use LP-WUS in a first area or a first cell of at least one first TA; the first area is the signal coverage area of the designated access network device; wherein the first terminal is a terminal designated by the core network device.
[0071] In conjunction with some embodiments of the third aspect, in some embodiments, the first information sent by the core network device is used to indicate a first triggering condition; the method further includes: determining that the first triggering condition is met and stopping the use of LP-WUS.
[0072] In conjunction with some embodiments of the third aspect, in some embodiments, the first triggering condition includes at least one of the following: the wake-up latency supported by the terminal is greater than a first threshold; the offset between the LP-WUS configured by the access network device and the paging timing PO is greater than a second threshold; the offset corresponding to the LP-WUS monitored by the terminal is greater than a third threshold.
[0073] In conjunction with some embodiments of the third aspect, in some embodiments, the first information is also used by the terminal to determine that LP-WUS is not used during the execution of the first service.
[0074] In conjunction with some embodiments of the third aspect, in some embodiments, the first information sent by the access network device is used to indicate at least one of the following: the second terminal does not use LP-WUS; the second terminal is a terminal designated by the access network device; the first type of terminal does not use LP-WUS; the first type of terminal is a terminal performing the first service.
[0075] In conjunction with some embodiments of the third aspect, in some embodiments, the first information is sent by the access network device or the core network device based on the second information, which is used to indicate the wake-up latency supported by the terminal.
[0076] In conjunction with some embodiments of the third aspect, in some embodiments, the first information is sent by the core network device based on the third information sent by the access network device, the third information being used to indicate at least one offset value between the LP-WUS configured by the access network device and the paging timing PO.
[0077] In conjunction with some embodiments of the third aspect, in some embodiments, the third information is sent by the access network device when it determines that the configured offset value is greater than the fifth threshold.
[0078] In conjunction with some embodiments of the third aspect, in some embodiments, the third information is also used to indicate whether the access network device supports the use of a paging packet method based on terminal ID.
[0079] Fourthly, embodiments of this disclosure provide a communication method, which is executed by a communication system. The method includes: a core network device or an access network device sending first information to a terminal; wherein the first information is used to determine whether to use LP-WUS.
[0080] Fifthly, embodiments of this disclosure provide a communication device, wherein the communication device is used to perform the communication method provided in the first, second, or third aspects.
[0081] In a sixth aspect, embodiments of this disclosure provide a communication system, wherein the communication system includes a terminal, an access network device, and a core network device, the core network device being configured to implement the communication method provided in the first aspect, the access network device being configured to implement the communication method provided in the second aspect, and the terminal being configured to implement the communication method provided in the third aspect.
[0082] In a seventh aspect, embodiments of this disclosure provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the communication method provided in the first, second, or third aspect.
[0083] Eighthly, embodiments of this disclosure provide a program product that, when executed by a communication device, causes the communication device to perform the communication method provided in the first, second, or third aspect.
[0084] In a ninth aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the communication method described in an optional implementation of the first, second, or third aspect.
[0085] It is understood that the aforementioned communication equipment, communication system, storage medium, program product, etc., are all used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.
[0086] This disclosure provides a communication method, a communication device, a communication system, a storage medium, and a program product. In some embodiments, the terms "communication method," "information processing method," and "information indication method" can be used interchangeably.
[0087] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments. In all embodiments of this disclosure, unless otherwise specified or logically conflicting, the terminology and / or descriptions between the embodiments are consistent and can be mutually referenced. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.
[0088] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.
[0089] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.
[0090] In the embodiments disclosed herein, "multiple" refers to two or more.
[0091] In some embodiments, the terms “at least one of A or B, at least one of A and B”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.
[0092] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of whether there is a branch B); in some embodiments, B (execute B regardless of whether there is a branch A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, both A and B are executed. The same applies when there are more branches such as A, B, C, etc.
[0093] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execute A regardless of whether a branch B exists); in some embodiments, B (execute B regardless of whether a branch A exists); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, and C.
[0094] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.
[0095] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.
[0096] In some embodiments, terms such as "time / frequency" and "time-frequency domain" refer to the time domain and / or frequency domain.
[0097] In some embodiments, terms such as “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “when…”, “if…”, etc. can be used interchangeably. These descriptions all refer to the device making a corresponding action under certain objective circumstances. They do not necessarily limit the time, nor do they require the device to make a judgment action when implementing it, nor do they mean that there must be other limitations.
[0098] In some embodiments, the terms “greater than,” “greater than or equal to,” “not less than,” “more than,” “more than or equal to,” “not less than,” “higher than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.
[0099] In some embodiments, devices, etc., may be interpreted as physical or virtual, and their names are not limited to those described in the embodiments. Terms such as “device,” “equipment,” “circuit,” “network element,” “network function,” “network device,” “function,” “node,” “unit,” “section,” “system,” “network,” “chip,” “chip system,” “entity,” and “subject” are interchangeable.
[0100] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).
[0101] In some embodiments, the terms "access network device (AN device)," "radio access network device (RAN device)," "base station (BS)," "radio base station," "fixed station," "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "serving cell," "carrier," "component carrier," and "bandwidth part (BWP)" can be used interchangeably.
[0102] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", "subscriber station", "mobile unit", "subscriber unit", "wireless unit", "remote unit", "mobile device", "wireless device", "wireless communication device", "remote device", "mobile subscriber station", "access terminal", "mobile terminal", "wireless terminal", "remote terminal", "handset", "user agent", "mobile client", and "client" can be used interchangeably.
[0103] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, embodiments of this disclosure can also be applied to structures where communication between access network devices, core network devices, or network devices and terminals is replaced by communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, and uplink link, downlink, etc., can be replaced with sidelink link.
[0104] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, core network device, or network device may also be configured to have all or some of the functions of the terminal.
[0105] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.
[0106] In some embodiments, data, information, etc., may be obtained with the user's consent.
[0107] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.
[0108] Figure 1 is a schematic diagram of the architecture of a communication system according to an exemplary embodiment. As shown in Figure 1, the communication system 100 includes a terminal 101, an access network device 102, and a core network device 103.
[0109] In some embodiments, terminal 101 includes, for example, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, and wireless terminal device in smart home, but is not limited thereto.
[0110] In some embodiments, the access network device is, for example, a node or device that connects a terminal to a wireless network. The access network device may include, but is not limited to, at least one of the following in a 5G system: evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), node B (NB), home node B (HNB), home evolved node B (HeNB), radio backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in 6G system, open RAN, cloud RAN, base station in other communication systems, and access node in Wi-Fi system.
[0111] In some embodiments, the technical solutions of this disclosure can be applied to the open RAN architecture. In this case, the interfaces between or within access network devices involved in the embodiments of this disclosure can be transformed into internal interfaces of open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.
[0112] In some embodiments, the access network device 102 may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.
[0113] In some embodiments, the core network device 103 may be a single device including one or more network functions, or it may be multiple devices or a group of devices, each including all or part of one or more network functions. Network functions may be virtual or physical. The core network may include, for example, at least one of the following: evolved packet core (EPC), 5G core network (5GCN), 6G core network (6GCN), and next-generation core (NGC).
[0114] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions provided in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in this disclosure are also applicable to similar technical problems.
[0115] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1 are illustrative. The communication system may include all or some of the main bodies in FIG1, or may include other main bodies outside of FIG1. The number and form of each main body are arbitrary. The connection relationship between the main bodies is illustrative. The main bodies may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.
[0116] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), Super 3G, IMT-Advanced, 4th Generation Mobile Communication System (4G), 5G, 5G New Radio (NR), 6G, Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Future Generation Radio Access (FX), Global System for Mobile Communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra-Wideband (UWB), Bluetooth, and public terrestrial mobile communication networks. Land Mobile Networks (PLMNs), device-to-device (D2D) systems, machine-to-machine (M2M) systems, Internet of Things (IoT) systems, vehicle-to-everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).
[0117] In some embodiments, the power saving features of Release 16 (R16) introduce a power saving signal for connected terminals, namely a wake-up signal (WUS) or downlink control information (DCI) for power saving (DCP). In one embodiment, the WUS signal is a low-power detection signal. If the terminal detects the WUS signal, it means that it needs to listen to the physical downlink control channel (PDCCH). If the terminal does not detect the WUS signal, it skips listening to the PDCCH.
[0118] In the power-saving features of Release 17 (R17), for idle-state discontinuous reception (DRX) scenarios, power-saving signals (e.g., PEI) are typically configured before the paging occasion (PO). If the terminal does not detect the power-saving signal, it can skip the paging DCI; otherwise, it needs to listen to the paging DCI. Furthermore, R17 enhances the connected state by introducing a PDCCH skipping mechanism. This means that PDCCH skipping is carried in the DCI to notify the user to skip a period of listening or to switch search space groups.
[0119] In some embodiments, in the power-saving mechanism of R16 or R17, regardless of the type of power-saving signal, the terminal's modem is required to detect the power-saving signal. However, in release 18 (i.e., R18), it is desirable to introduce a separate transceiver (e.g., LP-WUR) to receive the power-saving signal, and the terminal's modem or MR can only be woken up after this separate transceiver is woken up; otherwise, the modem or MR will remain in a sleep state.
[0120] In some embodiments, after the terminal is woken up by a power-saving signal (e.g., LP-WUS), it will listen to the subsequent PO or listen to PEI.
[0121] In some embodiments, two paging packet methods are defined: the first is network-assigned subgrouping, where the core network directly assigns the paging packet ID. The second is UE-ID-based subgrouping, where the terminal selects its paging packet using a modulo operation based on its terminal ID.
[0122] In some embodiments, a certain amount of time is required for paging message detection when the terminal wakes up based on LP-WUS, i.e., wake-up latency. Three wake-up latencies are introduced to address this latency: 70ms, 500ms, and 900ms.
[0123] In some embodiments, the network side can configure up to two offset values, which are the offsets between the LP-WUS listening time and the PO or PEI. If the network side configures one offset value, the terminal selects the LP-WUS corresponding to the offset value greater than its capability for listening, based on its capability (i.e., the wake-up latency supported by the terminal). If the network side configures two offset values, the terminal selects the LP-WUS corresponding to the smaller offset value among the multiple offset values greater than its capability for listening. In other words, the terminal can only select the LP-WUS corresponding to the offset value greater than its capability for listening; otherwise, if the offset value configured by the network side is small, for example, if the offset value is less than the wake-up latency supported by the terminal, the terminal will not be able to wake up in time.
[0124] In some embodiments, the offset values configured in the access network equipment are unknown to the core network, leading to the inability to meet the needs of specific services. For example, for emergency call services, after a user initiates an emergency call and the terminal is released to a connectionless state while waiting for a network call, a large offset value configured in the access network equipment may result in significant service latency. Therefore, under certain configurations, LP-WUS is no longer suitable for terminals with specific service requirements. Thus, for terminals with specific service needs, the use of LP-WUS should be disabled.
[0125] Figure 2A is an interactive schematic diagram of a communication method according to an exemplary embodiment. As shown in Figure 2A, this disclosure relates to a communication method for a communication system 100. The method includes steps S2101 to S2104.
[0126] In step S2101, the terminal sends the second information to the core network equipment.
[0127] In some embodiments, the terminal may send second information to the access network device, and the access network device may then send the second information to the core network device.
[0128] In some embodiments, the core network device receives second information sent by the terminal, but is not limited thereto. In some embodiments, the core network device may receive second information from the terminal forwarded by the access network device.
[0129] In some embodiments, the second information can be used to indicate the wake-up latency supported by the terminal. In some embodiments, the terminal can inform the core network device of its supported wake-up latency by sending the second information to the core network device.
[0130] In some embodiments, the wake-up latency can be the time interval between waking the terminal based on a power-saving signal and the terminal detecting a paging message. In one embodiment, for a terminal in a disconnected state, after detecting a power-saving signal, the terminal needs a relatively long time to wake up the MR and complete the time-frequency synchronization of the MR; this time is the wake-up latency. Only after completing the time-frequency synchronization of the MR can the terminal detect the PDCCH on the PO and the PDSCH scheduled by the PO.
[0131] In some embodiments, the power-saving signal may include, but is not limited to, LP-WUS.
[0132] In some embodiments, the second information can be used to indicate the terminal's support capability for multiple wake-up delays configured on the network side. In some embodiments, multiple wake-up delays are pre-configured on the network side, and the terminal can use the second information to inform the core network device of its support capability for the multiple wake-up delays configured on the network side.
[0133] In step S2102, the access network device sends third information to the core network device.
[0134] In some embodiments, the core network device may receive third information sent by the access network device.
[0135] In some embodiments, the third information may be used to indicate at least one offset value configured by the access network device for the terminal to use a power-saving signal. In some embodiments, the offset value may be a time offset between the monitoring time of the power-saving signal and the PI.
[0136] In some embodiments, the power-saving signal may include, but is not limited to, LP-WUS.
[0137] In some embodiments, the third information may be used to indicate at least one offset value between the LP-WUS and PO configured by the access network device. In some embodiments, the offset value may be the time interval between the LP-WUS listening time and the PO.
[0138] In some embodiments, the access network device may inform the core network device of at least one offset value configured by sending a third message to the core network device.
[0139] In some embodiments, the third information can be used to indicate the offset value of the power-saving signal configured for one or more cells. In this case, the notification granularity when the access network device notifies the core network device of its configured offset value can be cell-level, that is, the access network device notifies the core network device of the offset value configured for each cell.
[0140] In some embodiments, the third information can be used to indicate the offset value of one or more power-saving signals configured by the access network device. In this case, the notification granularity when the access network device notifies the core network device of its configured offset value can be at the access network device level, that is, the access network device notifies the core network device of its own configured offset value. In some embodiments, the third information can be used to indicate the statistics of the offset values of the power-saving signals configured by the access network device. In this case, the third information does not need to indicate a specific offset value, but rather indicates that the access network device has configured a larger offset value or a smaller offset value.
[0141] In some embodiments, if the offset value configured by the access network device is greater than a fifth threshold, the access network device may send third information to the core network device. In some embodiments, the fifth threshold may be determined according to a protocol agreement. In some embodiments, the fifth threshold may be configured by the core network device.
[0142] In some embodiments, considering that a large offset value configured by the access network device may lead to a large service delay, the access network device may send third information to the core network device when its own configured offset value is greater than the fifth threshold, so that the core network device can determine whether to use LP-WUS based on the third information.
[0143] In some embodiments, the third information may also be used to indicate whether the access network device supports a paging packet method based on the terminal ID. In some embodiments, the paging packet method may include: a paging packet method based on the core network allocation and a paging packet method based on the terminal ID.
[0144] In some embodiments, the paging packet allocation method based on the core network involves the core network directly allocating paging packet IDs to the terminal. In some embodiments, the paging packet allocation method based on the terminal ID involves the access network device indicating the total number of paging packets to the terminal, the terminal performing a modulo operation on its own terminal ID, and determining its own paging packet based on the result.
[0145] In some embodiments, the access network device may send a first message to the core network device, and the first message may include third information. In some embodiments, the access network device may send the third information to the core network device by sending the first information to the core network device.
[0146] In some embodiments, the first message may include, but is not limited to, an NG setup request message and an NG configuration update message.
[0147] In step S2103, the core network device sends the first information to the terminal.
[0148] In some embodiments, the core network device may send first information to the access network device, and the access network device may send the first information to the terminal.
[0149] In some embodiments, the terminal may receive first information sent by the core network device, but is not limited thereto. In some embodiments, the terminal may receive first information from the core network device forwarded by the access network device.
[0150] In some embodiments, the terminal may be a first terminal designated by the core network equipment. In some embodiments, the first terminal may be a terminal performing a first service. In some embodiments, the first service may be a service with high latency requirements, i.e., the first service may be a latency-sensitive service. In some embodiments, the first service may include, but is not limited to, an emergency call service.
[0151] In some embodiments, the terminal may be a non-connected terminal.
[0152] In some embodiments, the terminal may be a connected terminal. In some embodiments, for a connected terminal, the core network device may also instruct the terminal to use LP-WUS by sending first information to the terminal.
[0153] In some embodiments, the first information can be used to determine whether to use LP-WUS. In some embodiments, the terminal can determine whether to use LP-WUS based on the first information sent by the core network device. In some embodiments, the core network device can control the terminal to use or not use LP-WUS by sending the first information to the terminal.
[0154] In some embodiments, the first information can be used to determine whether to disable LP-WUS. In some embodiments, the terminal can determine whether to disable LP-WUS based on the first information sent by the core network device. In some embodiments, the core network device can control the terminal to use or disable LP-WUS by sending the first information to the terminal.
[0155] In some embodiments, different values of the first information can be used to indicate whether the terminal uses LP-WUS. In some embodiments, the first information has a first value indicating that the terminal does not use LP-WUS. In some embodiments, the first information has a second value indicating that the terminal uses LP-WUS.
[0156] In some embodiments, the core network device can control whether a terminal uses or does not use LP-WUS by sending a first message with different values to the terminal. In some embodiments, when the core network device requires the terminal to disable LP-WUS, the core network device can send the first message with a first value to the terminal. In some embodiments, when the core network device does not require the terminal to disable LP-WUS, the core network device can send the first message with a second value to the terminal.
[0157] In some embodiments, the first information may be used to instruct the terminal not to use LP-WUS. In some embodiments, the first information may be used to instruct the terminal to disable LP-WUS.
[0158] In some embodiments, the core network device can control whether the terminal uses or does not use LP-WUS by sending first information to the terminal.
[0159] In some embodiments, if the core network device requires the terminal to disable LP-WUS, the core network device may send first information to the terminal. In some embodiments, if the core network device does not require the terminal to disable LP-WUS, the core network device may not send the first information to the terminal.
[0160] In some embodiments, the first information can also be used to determine whether to use a terminal ID-based paging packet method to determine the terminal's paging packet information. In some embodiments, the core network device can control whether the terminal uses LP-WUS by using the first information used to indicate whether to use a terminal ID-based paging packet method.
[0161] In some embodiments, when the first information indicates that the terminal does not use the terminal ID-based paging packet method to determine the terminal's paging packet information, the terminal can only use the core network-assigned paging packet method to determine the paging packet information. If the core network device does not assign a paging packet ID to the terminal, the terminal cannot know its own paging packet and therefore cannot listen to LP-WUS within the corresponding time window. If the core network device assigns a paging packet ID to the terminal, the terminal can listen to LP-WUS within the time window corresponding to its own paging packet. In this case, the core network device can control whether the terminal uses or does not use LP-WUS by assigning a paging packet ID to the terminal.
[0162] In some embodiments, when the first information instructs the terminal to use a paging packet method based on the terminal ID to determine the terminal's paging packet information, even if the core network device does not assign a paging packet ID to the terminal, the terminal can still determine the paging packet ID of its own paging packet and thus listen to LP-WUS in the time window corresponding to the paging packet.
[0163] In some embodiments, the first information can be used to instruct a first terminal not to use LP-WUS. In some embodiments, the core network device can instruct the terminal not to use LP-WUS by sending the first information to the terminal.
[0164] In some embodiments, the first information may be used to indicate that a first terminal does not use LP-WUS within at least one first TA. In some embodiments, the first TA may be a TA designated by a core network device. In some embodiments, the first information may include first indication information, which may be used to indicate one or more first TAs. In some embodiments, the first indication information may be used to indicate one or more TA lists, which include one or more first TAs.
[0165] In some embodiments, the first information may be used to instruct the first terminal not to use LP-WUS within a first area of at least one first TA. In some embodiments, the first area may be the signal coverage area of an access network device specified within the first TA.
[0166] In some embodiments, the first information may be used to instruct the first terminal not to use LP-WUS in a first cell within at least one first TA. In some embodiments, the first cell may be a cell specified within the first TA.
[0167] In some embodiments, the first information may be used to indicate a first triggering condition. In some embodiments, the first triggering condition may be a triggering condition that causes the terminal to stop using LP-WUS. In some embodiments, the terminal does not use LP-WUS when the first triggering condition is met.
[0168] In some embodiments, the first triggering condition may also be a triggering condition that causes the terminal to stop using the terminal ID-based paging packet method. In some embodiments, when the first triggering condition is met, the terminal does not use the terminal ID-based paging packet method to determine paging packet information.
[0169] In some embodiments, the first triggering condition may include at least one of the following: the wake-up latency supported by the terminal is greater than a first threshold; the offset between the listening time of the LP-WUS configured by the access network device and the PO is greater than a second threshold; the offset corresponding to the LP-WUS listened to by the terminal is greater than a third threshold.
[0170] In some embodiments, the offset value corresponding to the LP-WUS monitored by the terminal can be an offset value selected by the terminal based on its own capabilities. In some embodiments, the offset value selected by the terminal is greater than the wake-up latency supported by the terminal.
[0171] In some embodiments, the core network device may send the first information to the terminal based on the second information. In some embodiments, the description of the second information can be found in the description of the second information in step S2101, and will not be repeated here.
[0172] In some embodiments, the second information can be used by the core network device to determine the first information. In some embodiments, the core network device can determine whether LP-WUS needs to be disabled based on the wake-up latency supported by the terminal indicated by the second information, thereby determining the first information. In one embodiment, if the core network device determines based on the second information that the wake-up latency supported by the terminal is greater than a first threshold, the core network device can send the first information to the terminal to instruct the terminal not to use LP-WUS.
[0173] In some embodiments, the core network device can determine on its own whether the terminal needs to disable LP-WUS, thereby eliminating the need for the terminal to send a second message to the core network device. In this case, step S2101 can be omitted.
[0174] In some embodiments, the core network device may send the first information to the terminal based on the third information. In some embodiments, the description of the third information can be found in the description of the third information in step S2102, and will not be repeated here.
[0175] In some embodiments, the third information can be used by the core network device to determine the first information.
[0176] In some embodiments, the core network device may determine whether LP-WUS needs to be disabled based on at least one offset value of the access network configuration indicated by the third information, thereby determining the first information.
[0177] In some embodiments, when the core network device receives third information sent by the access network device, the core network device can determine whether LP-WUS needs to be disabled based on at least one offset value of the access network device configuration indicated by the third information, thereby determining the first information. In one embodiment, if the core network device determines, based on the third information, that at least one offset value of the access network device configuration is greater than a second threshold, the core network device can send the first information to the terminal to instruct the terminal not to use LP-WUS.
[0178] In some embodiments, the core network device can determine whether it needs to send first information to the terminal to indicate whether the terminal uses LP-WUS based on the access network device's support capability for terminal ID-based paging packet mode as indicated by third information. In some embodiments, if the access network device does not support terminal ID-based paging packet mode, the core network device can control whether the terminal uses LP-WUS by whether or not it assigns a paging packet ID to the terminal; in this case, the core network device does not need to send first information to the terminal. In some embodiments, if the access network device supports terminal ID-based paging packet mode, the core network device can determine paging packet information by sending first information to the terminal to indicate that the terminal does not use terminal ID-based paging packet mode, thereby controlling whether the terminal uses LP-WUS by whether or not it assigns a paging packet ID to the terminal. In some embodiments, if the access network device supports terminal ID-based paging packet mode, the core network device can control whether the terminal uses LP-WUS by sending first information to the terminal to indicate whether or not it uses LP-WUS.
[0179] In some embodiments, the core network device can determine on its own whether the terminal needs to use LP-WUS, thereby eliminating the need for the access network device to send third information to the core network device. In this case, step S2102 can be omitted.
[0180] In some embodiments, the core network device may send first information to the terminal based on second information and third information. In some embodiments, the core network device may determine the wake-up latency supported by the terminal based on the second information and determine at least one offset value configured by the access network device based on the third information. This allows the core network device to determine the offset value selected by the terminal, and to determine whether the terminal uses LP-WUS based on the selected offset value, thereby determining the content of the first information to be sent to the terminal. In one embodiment, if the core network device determines, based on the second and third information, that the offset value selected by the terminal is greater than a third threshold, the core network device may send first information to the terminal to indicate that the terminal does not use LP-WUS.
[0181] In step S2104, the terminal determines that it will not use LP-WUS based on the first information.
[0182] In some embodiments, the terminal may determine whether to use LP-WUS based on the information content of the first information. In some embodiments, when the terminal receives the first information having a first value, the terminal may determine not to use LP-WUS. In some embodiments, when the terminal receives the first information, the terminal may determine not to use LP-WUS.
[0183] In some embodiments, if the first information indicates that the first terminal does not use LP-WUS, the terminal may choose not to use LP-WUS.
[0184] In some embodiments, if the first information indicates that the first terminal will not use LP-WUS within at least one first TA, the terminal may stop using LP-WUS after entering at least one first TA. In some embodiments, the terminal may continue using LP-WUS after leaving at least one first TA.
[0185] In some embodiments, if the first information indicates that the first terminal does not use LP-WUS within a first area of at least one first TA, the terminal may stop using LP-WUS after entering the first area of at least one first TA. In some embodiments, the terminal may continue using LP-WUS after leaving the first area of at least one first TA.
[0186] In some embodiments, if the first information indicates that the first terminal does not use LP-WUS within a first cell of at least one first TA, the terminal may stop using LP-WUS after entering the first cell of at least one first TA. In some embodiments, the terminal may continue using LP-WUS after leaving the first cell of at least one first TA.
[0187] In some embodiments, when the first information indicates a first triggering condition, the terminal can determine whether to use LP-WUS based on whether the first triggering condition is met. In some embodiments, when the terminal determines that the first triggering condition is met, the terminal does not use LP-WUS. In some embodiments, when the wake-up latency supported by the terminal is greater than a first threshold, the terminal determines that the first triggering condition is met, and the terminal does not use LP-WUS. In some embodiments, when the offset between the listening time of LP-WUS configured by the access network device and the PO is greater than a second threshold, the terminal determines that the first triggering condition is met, and the terminal does not use LP-WUS. In some embodiments, when the offset value selected by the terminal based on its own capabilities is greater than a third threshold, the terminal determines that the first triggering condition is met, and the terminal does not use LP-WUS.
[0188] In some embodiments, if the terminal determines that it will not use LP-WUS, the terminal may listen to PO based on the configured DRX period.
[0189] In some embodiments, if the first information indicates that a paging packet method based on the terminal ID is not used, the terminal may use a paging packet method based on the core network allocation to determine its own paging packet information. In this case, if the core network device has allocated a paging packet ID to the terminal, the terminal determines that LP-WUS can be used. If the core network device has not allocated a paging packet ID to the terminal, the terminal may determine that LP-WUS is disabled.
[0190] In some embodiments, step S2104 may be omitted if the terminal determines that LP-WUS can be used based on the first information.
[0191] In some embodiments, the term "information" may be used interchangeably with terms such as "message," "signal," "signaling," "report," "configuration," "indication," "instruction," "command," "channel," "parameter," "field," and "data."
[0192] In some embodiments, the term "send" may be used interchangeably with terms such as "transmit," "report," or "transmit."
[0193] The communication method involved in the embodiments of this disclosure may include at least one of steps S2101 to S2104. For example, step S2103 may be implemented as a standalone embodiment, steps S2103 and S2104 may be implemented as standalone embodiments, steps S2102 to S2104 may be implemented as standalone embodiments, and steps S2101, S2103 and S2104 may be implemented as standalone embodiments, but are not limited thereto.
[0194] In some embodiments, steps S2101, S2102 and S2104 are optional, and one or more of these steps may be omitted or substituted in different embodiments.
[0195] In some embodiments, step S2101 is optional, and one or more of these steps may be omitted or substituted in different embodiments.
[0196] In some embodiments, step S2102 is optional, and one or more of these steps may be omitted or substituted in different embodiments.
[0197] In some embodiments, steps S2101 and S2102 may be interchanged.
[0198] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.
[0199] Figure 2B is a schematic diagram of an interaction of a communication method according to an exemplary embodiment. As shown in Figure 2B, this disclosure relates to a communication method for a communication system 100. The method includes steps S2201 to S2204.
[0200] In step S2201, the terminal sends the second information to the core network equipment.
[0201] In some embodiments, other optional implementations of step S2201 can be found in the optional implementations of step S2101 in FIG2A and other related parts in the embodiments involved in FIG2A, which will not be repeated here.
[0202] In step S2202, the access network device sends third information to the core network device.
[0203] In some embodiments, other optional implementations of step S2202 can be found in the optional implementations of step S2102 in FIG2A and other related parts in the embodiments involved in FIG2A, which will not be repeated here.
[0204] In step S2203, the core network device sends the first information to the access network device.
[0205] In some embodiments, the access network device may receive first information sent by the core network device.
[0206] In some embodiments, the first information can be used to determine whether to use LP-WUS. In some embodiments, the access network device can determine whether to use LP-WUS based on the first information sent by the core network. In some embodiments, the core network device can control the access network device to use or not use LP-WUS by sending the first information to the access network device.
[0207] In some embodiments, the first information can be used to determine whether to disable LP-WUS. In some embodiments, the access network device can determine whether to disable LP-WUS based on the first information sent by the core network device. In some embodiments, the core network device can control the access network device to use or disable LP-WUS by sending the first information to the access network device.
[0208] In some embodiments, different values of the first information can be used to indicate whether the access network device uses LP-WUS. In some embodiments, the first information has a first value indicating that the access network device does not use LP-WUS. In some embodiments, the first information has a second value indicating that the access network device uses LP-WUS.
[0209] In some embodiments, the core network device can control the access network device to use or not use LP-WUS by sending first information with different values to the access network device. In some embodiments, when the core network device requires the access network device to disable LP-WUS, the core network device can send first information with a first value to the access network device. In some embodiments, when the core network device does not require the access network device to disable LP-WUS, the core network device can send first information with a second value to the access network device.
[0210] In some embodiments, the first information may be used to instruct the access network device not to use LP-WUS. In some embodiments, the first information may be used to instruct the access network device to disable LP-WUS.
[0211] In some embodiments, the core network device can control whether the access network device uses or does not use LP-WUS by sending first information to the access network device.
[0212] In some embodiments, if the core network device requires the access network device to disable LP-WUS, the core network device may send first information to the access network device. In some embodiments, if the core network device does not require the access network device to disable LP-WUS, the core network device may not send the first information to the access network device.
[0213] In some embodiments, the first information can also be used to determine whether to use a terminal ID-based paging packet method to determine the terminal's paging packet information. In some embodiments, the core network device can control the access network device to use or not use LP-WUS by using the first information used to indicate whether to use a terminal ID-based paging packet method.
[0214] In some embodiments, when the first information indicates that the access network device does not use the terminal ID-based paging packet method, the access network device will not send the total number of paging packets to the terminal. Therefore, the terminal can only use the core network-assigned paging packet method to determine paging packet information. If the core network device does not assign a paging packet ID to the terminal, the terminal cannot know its own paging packet and therefore cannot listen for LP-WUS within the corresponding time window. If the core network device assigns a paging packet ID to the terminal, the terminal can listen for LP-WUS within the time window corresponding to its own paging packet. In this case, the core network device can control whether the access network device uses or does not use LP-WUS for the terminal by assigning a paging packet ID to the terminal.
[0215] In some embodiments, when the first information instructs the access network device to use a paging packet method based on the terminal ID, even if the core network device does not assign a paging packet ID to the terminal, the terminal can determine the paging packet ID of its own paging packet based on the interaction between the terminal and the access network device, and thus listen to LP-WUS in the time window corresponding to the paging packet.
[0216] In some embodiments, the first information is used to indicate that LP-WUS is not used for the first terminal. In some embodiments, the core network device can instruct the access network device not to use LP-WUS for the first terminal by sending the first information to the access network device.
[0217] In some embodiments, the first terminal may be a terminal designated by the core network equipment. In some embodiments, the first information may include: identification information of the first terminal.
[0218] In some embodiments, the first information is used to indicate that LP-WUS is not used for a first type of terminal. In some embodiments, the core network device can instruct the access network device not to use LP-WUS for a first type of terminal by sending the first information to the access network device.
[0219] In some embodiments, the first type of terminal may be a terminal performing the first service. In some embodiments, the first service may be a service with high latency requirements, i.e., the first service may be a latency-sensitive service. In some embodiments, the first service may include, but is not limited to, an emergency call service.
[0220] In some embodiments, the first information may include second indication information, which indicates a first type of terminal. In some embodiments, since the distinction between terminal types is related to the type of service being performed by the terminal, and the access network device cannot know the type of service being performed by the terminal, the access network device cannot know which terminals are of the first type. In this case, the core network device can inform the access network device of the first type of terminals through the first information, so that the access network device does not use LP-WUS for the first type of terminals.
[0221] In some embodiments, the first information may be used to indicate a second triggering condition. In some embodiments, the second triggering condition may be a triggering condition that causes the access network device to stop using LP-WUS for the first terminal or the first type of terminal. In some embodiments, when the second triggering condition is met, the access network device does not use LP-WUS for the first terminal or the first type of terminal.
[0222] In some embodiments, the second triggering condition may also be a triggering condition that causes the access network device to stop using the terminal ID-based paging packet method. In some embodiments, when the second triggering condition is met, the access network device does not use the terminal ID-based paging packet method.
[0223] In some embodiments, the second triggering condition may include: the offset between the LP-WUS configured by the access network device and the PO is greater than a fourth threshold. In some embodiments, if the offset between the listening time of the LP-WUS configured by the access network device and the PO is greater than the fourth threshold, it indicates that the offset configured by the access network device is large. In this case, if the access network device uses LP-WUS to wake up the terminal, it can easily lead to significant service latency. Therefore, the core network device can use the first information to inform the access network device of the second triggering condition, so that the access network device can stop using LP-WUS when the second triggering condition is met, thereby reducing service latency.
[0224] In some embodiments, the first information sent by the core network device to the access network device can be used to indicate that LP-WUS will not be used for a first terminal or a first type of terminal within all signal coverage areas of the access network device. In this case, the granularity of not using LP-WUS indicated by the first information can be at the access network device level.
[0225] In some embodiments, the first information sent by the core network device to the access network device may be used to indicate that LP-WUS is not used for a first terminal or a first type of terminal within one or more cells. In this case, the granularity of not using LP-WUS indicated by the first information may be at the cell level.
[0226] In some embodiments, the core network device may send the first information to the access network device based on the second information. In some embodiments, the description of the second information can be found in the description of the second information in step S2101, and will not be repeated here.
[0227] In some embodiments, the second information can be used by the core network device to determine the first information. In some embodiments, the core network device can determine whether LP-WUS needs to be disabled based on the wake-up latency supported by the terminal indicated by the second information, thereby determining the first information. In one embodiment, if the core network device determines based on the second information that the wake-up latency supported by the terminal is greater than a first threshold, the core network device can send the first information to the access network device to instruct the access network device not to use LP-WUS for the terminal.
[0228] In some embodiments, the core network device can determine on its own whether the access network device uses LP-WUS for the terminal, thereby eliminating the need for the terminal to send the second information to the core network device. In this case, step S2201 can be omitted.
[0229] In some embodiments, the core network device may send the first information to the access network device based on the third information. In some embodiments, the description of the third information can be found in the description of the third information in step S2102, and will not be repeated here.
[0230] In some embodiments, the third information can be used by the core network device to determine the first information.
[0231] In some embodiments, the core network device may determine whether LP-WUS needs to be disabled based on at least one offset value of the access network configuration indicated by the third information, thereby determining the first information.
[0232] In some embodiments, when a core network device receives third information from an access network device, the core network device can determine whether LP-WUS needs to be disabled based on at least one offset value configured by the access network device indicated by the third information, thereby determining the first information. In one embodiment, if the core network device determines, based on the third information, that at least one offset value configured by the access network device is greater than a second threshold, the core network device can send the first information to the access network device to instruct the access network device not to use LP-WUS for the terminal.
[0233] In some embodiments, the core network device can determine whether to send first information to the access network device to instruct whether the access network device uses LP-WUS based on the access network device's support capability for terminal ID-based paging packet mode indicated by third information. In some embodiments, if the access network device does not support terminal ID-based paging packet mode, the core network device can control whether the access network device uses LP-WUS for the terminal by whether or not to assign a paging packet ID to the terminal; in this case, the core network device does not need to send first information to the access network device. In some embodiments, if the access network device supports terminal ID-based paging packet mode, the core network device can send first information to the access network device to instruct the access network device not to use terminal ID-based paging packet mode, thereby controlling whether the access network device uses LP-WUS by whether or not to assign a paging packet ID to the terminal. In some embodiments, if the access network device supports terminal ID-based paging packet mode, the core network device can control whether the access network device uses LP-WUS by sending first information to the access network device to instruct the access network device to use or disable LP-WUS.
[0234] In some embodiments, the core network device can determine on its own whether the access network device uses LP-WUS for the terminal, thereby eliminating the need for the access network device to send third information to the core network device. In this case, step S2202 can be omitted.
[0235] In some embodiments, the core network device may send first information to the access network device based on second information and third information. In some embodiments, the core network device may determine the wake-up latency supported by the terminal based on the second information and determine at least one offset value configured by the access network device based on the third information. This allows the core network device to determine the offset value selected by the terminal, and to determine whether the terminal uses LP-WUS based on the selected offset value, thereby determining the content of the first information sent to the access network device. In one embodiment, if the core network device determines, based on the second and third information, that the offset value selected by the terminal is greater than a third threshold, the core network device may send the first information to the access network device to instruct the access network device not to use LP-WUS for the terminal.
[0236] In step S2204, the access network device determines not to use LP-WUS based on the first information.
[0237] In some embodiments, the access network device may determine whether to use LP-WUS based on the information content of the first information. In some embodiments, when the access network device receives the first information having a first value, the access network device may determine not to use LP-WUS. In some embodiments, when the access network device receives the first information, the access network device may determine not to use LP-WUS.
[0238] In some embodiments, if the first information indicates that LP-WUS is not used for the first terminal, the access network device may not use LP-WUS for the first terminal. In one embodiment, the access network device may determine the first terminal based on the first information and stop using LP-WUS to wake up the first terminal. In this case, the access network device may configure a DRX cycle for the first terminal so that the first terminal can listen for PO based on the DRX cycle.
[0239] In some embodiments, if the first information indicates that LP-WUS is not used for a first type of terminal, the access network device may not use LP-WUS for the first type of terminal. In one embodiment, the access network device may determine the first type of terminal based on the first information and stop using LP-WUS to wake up the first type of terminal. In this case, the access network device may configure a DRX cycle for the first type of terminal so that the first type of terminal can listen for PO based on the DRX cycle.
[0240] In some embodiments, when the first information indicates a second triggering condition, the access network device can determine whether to use LP-WUS based on whether the second triggering condition is met. In some embodiments, when the access network device determines that the second triggering condition is met, the access network device does not use LP-WUS. In some embodiments, when the offset between the listening time of the LP-WUS configured by the access network device and the PO is greater than a fourth threshold, the access network device determines that the second triggering condition is met, and the access network device may not use LP-WUS for the first terminal or the first type of terminal.
[0241] In some embodiments, when the access network device determines that LP-WUS is not used, the access network device can configure a DRX cycle for the terminal so that the terminal can listen to PO based on the configured DRX cycle.
[0242] In some embodiments, the access network device may also determine, based on the first information, not to use a paging packet method based on the terminal ID. In some embodiments, the access network device may use a paging packet method based on the core network allocation to determine the paging packet information.
[0243] In some embodiments, step S2204 may be omitted if the access network device determines that LP-WUS is possible based on the first information.
[0244] In some embodiments, the term "information" may be used interchangeably with terms such as "message," "signal," "signaling," "report," "configuration," "indication," "instruction," "command," "channel," "parameter," "field," and "data."
[0245] In some embodiments, the term "send" may be used interchangeably with terms such as "transmit," "report," or "transmit."
[0246] The communication method involved in the embodiments of this disclosure may include at least one of steps S2201 to S2204. For example, step S2203 may be implemented as a standalone embodiment, steps S2203 and S2204 may be implemented as standalone embodiments, steps S2202 to S2204 may be implemented as standalone embodiments, and steps S2201, S2203 and S2204 may be implemented as standalone embodiments, but are not limited thereto.
[0247] In some embodiments, steps S2201, S2202, and S2204 are optional, and one or more of these steps may be omitted or substituted in different embodiments.
[0248] In some embodiments, step S2201 is optional, and one or more of these steps may be omitted or substituted in different embodiments.
[0249] In some embodiments, step S2202 is optional, and one or more of these steps may be omitted or substituted in different embodiments.
[0250] In some embodiments, steps S2201 and S2202 may be interchanged.
[0251] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.
[0252] Figure 2C is a schematic diagram of an interaction of a communication method according to an exemplary embodiment. As shown in Figure 2C, this disclosure relates to a communication method for a communication system 100. The method includes steps S2301 to S2303.
[0253] In step S2301, the terminal sends the second information to the access network device.
[0254] In some embodiments, the access network device may receive second information sent by the terminal.
[0255] In some embodiments, the access network device may receive second information sent by the core network device. In some embodiments, after receiving the second information sent by the terminal, the core network device may send the second information to the access network device.
[0256] In some embodiments, the second information can be used to indicate the wake-up latency supported by the terminal. In some embodiments, the terminal can inform the access network device of its supported wake-up latency by sending the second information to the access network device.
[0257] In some embodiments, the wake-up latency can be the time interval between waking the terminal based on a power-saving signal and the terminal detecting a paging message. In one embodiment, for a terminal in a disconnected state, after detecting a power-saving signal, the terminal needs a relatively long time to wake up the MR and complete the time-frequency synchronization of the MR; this time is the wake-up latency. Only after completing the time-frequency synchronization of the MR can the terminal detect the PDCCH on the PO and the PDSCH scheduled by the PO.
[0258] In some embodiments, the power-saving signal may include, but is not limited to, LP-WUS.
[0259] In some embodiments, the second information can be used to indicate the terminal's support capability for multiple wake-up delays configured on the network side. In some embodiments, multiple wake-up delays are pre-configured on the network side, and the terminal can use the second information to inform the access network device of its support capability for the multiple wake-up delays configured on the network side.
[0260] In some embodiments, the terminal may also send a fourth message to the access network device, the fourth message being used to indicate whether the terminal supports LP-WUS.
[0261] In some embodiments, the fourth information can also be used to indicate the terminal's desired offset value. In some embodiments, the fourth information can be used by the access network device to configure the offset value corresponding to LP-WUS for the terminal. In some embodiments, the terminal can inform the access network device of its desired offset value through the fourth information, so that the access network device can refer to the terminal's desired offset value as the offset value between the terminal's LP-WUS listening time and the PO.
[0262] In some embodiments, the terminal may send UE assistance information (UAI) to the access network device, which carries fourth information.
[0263] In some embodiments, in the Evolution Node B Dual Connectivity (EN-DC) scenario, the terminal can carry the fourth information through the signaling of the secondary node (SN) (e.g., signaling radio bearer 3 (SRB3)).
[0264] In some embodiments, in a multi-radio dual connectivity (MR-DC) scenario, if the master node (MN) is configured to allow the terminal to use LP-WUS, the terminal can directly carry the fourth information through the MN's signaling (e.g., signaling radio bearer 1, SRB1). If the SN is configured to allow the terminal to use LP-WUS, the terminal can directly carry the fourth information through the SN's signaling (e.g., SRB3); otherwise, the terminal can transmit the fourth information to the MN and forward it to the SN through the MN.
[0265] In step S2302, the access network device sends the first information to the terminal.
[0266] In some embodiments, the terminal may receive first information sent by the access network device.
[0267] In some embodiments, the terminal may be a second terminal designated by the access network device.
[0268] In some embodiments, the terminal may be a non-connected terminal.
[0269] In some embodiments, the terminal may be a connected terminal. In some embodiments, for a connected terminal, the access network device may also instruct the terminal to use LP-WUS by sending first information to the terminal.
[0270] In some embodiments, the first information can be used to determine whether to use LP-WUS. In some embodiments, the terminal can determine whether to use LP-WUS based on the first information sent by the access network device. In some embodiments, the access network device can control the terminal to use or not use LP-WUS by sending the first information to the terminal.
[0271] In some embodiments, the first information can be used to determine whether to disable LP-WUS. In some embodiments, the terminal can determine whether to disable LP-WUS based on the first information sent by the access network device. In some embodiments, the access network device can control the terminal to use or disable LP-WUS by sending the first information to the terminal.
[0272] In some embodiments, different values of the first information can be used to indicate whether the terminal uses LP-WUS. In some embodiments, the first information has a first value indicating that the terminal does not use LP-WUS. In some embodiments, the first information has a second value indicating that the terminal uses LP-WUS.
[0273] In some embodiments, the access network device can control whether a terminal uses or does not use LP-WUS by sending first information with different values to the terminal. In some embodiments, when the access network device requires the terminal to disable LP-WUS, the access network device can send first information with a first value to the terminal. In some embodiments, when the access network device does not require the terminal to disable LP-WUS, the access network device can send first information with a second value to the terminal.
[0274] In some embodiments, the first information may be used to instruct the terminal not to use LP-WUS. In some embodiments, the first information may be used to instruct the terminal to disable LP-WUS.
[0275] In some embodiments, the access network device can control whether the terminal uses or does not use LP-WUS by sending first information to the terminal.
[0276] In some embodiments, if the access network device requires the terminal to disable LP-WUS, the access network device may send first information to the terminal. In some embodiments, if the access network device does not require the terminal to disable LP-WUS, the access network device may not send the first information to the terminal.
[0277] In some embodiments, the first information can also be used to determine whether to use a paging packet method based on the terminal ID to determine the terminal's paging packet information. In some embodiments, the paging packet method may include: a paging packet method allocated by the core network and a paging packet method based on the terminal ID. In some embodiments, the access network device can control whether the terminal uses LP-WUS by using the first information used to indicate whether to use a paging packet method based on the terminal ID.
[0278] In some embodiments, when the first information indicates that the terminal does not use the terminal ID-based paging packet method to determine the terminal's paging packet information, the terminal can only use the core network-assigned paging packet method to determine the paging packet information. If the core network device does not assign a paging packet ID to the terminal, the terminal cannot know its own paging packet and therefore cannot listen to LP-WUS within the corresponding time window. If the core network device assigns a paging packet ID to the terminal, the terminal can listen to LP-WUS within the time window corresponding to its own paging packet. In this case, the core network device can control whether the terminal uses or does not use LP-WUS by assigning a paging packet ID to the terminal.
[0279] In some embodiments, the first information can be used to instruct a second terminal not to use LP-WUS. In some embodiments, the access network device can instruct the terminal not to use LP-WUS by sending the first information to the terminal.
[0280] In some embodiments, the first information can be used to indicate that a first type of terminal does not use LP-WUS. In some embodiments, the access network device can indicate that a first type of terminal does not use LP-WUS by sending the first information to the terminal. In some embodiments, the terminal can determine whether it belongs to the first type of terminal based on the first information, thereby determining whether to use LP-WUS.
[0281] In some embodiments, the first type of terminal may be a terminal performing the first service. In some embodiments, the first service may be a service with high latency requirements, i.e., the first service may be a latency-sensitive service. In some embodiments, the first service may include, but is not limited to, an emergency call service.
[0282] In some embodiments, the first information may indicate a third triggering condition. In some embodiments, the third triggering condition may be a triggering condition that causes the terminal to stop using LP-WUS. In some embodiments, the terminal does not use LP-WUS when the third triggering condition is met.
[0283] In some embodiments, the third triggering condition may also be a triggering condition that causes the terminal to stop using the terminal ID-based paging packet method. In some embodiments, when the third triggering condition is met, the terminal does not use the terminal ID-based paging packet method to determine paging packet information.
[0284] In some embodiments, the third triggering condition may include at least one of the following: the wake-up latency supported by the terminal is greater than the first threshold; the offset value corresponding to the LP-WUS being monitored by the terminal is greater than the third threshold.
[0285] In some embodiments, the offset value corresponding to the LP-WUS monitored by the terminal can be an offset value selected by the terminal based on its own capabilities. In some embodiments, the offset value selected by the terminal is greater than the wake-up latency supported by the terminal.
[0286] In some embodiments, the access network device may also send first information to the terminal based on at least one offset value configured by itself. In some embodiments, the access network device determines whether the terminal uses LP-WUS based on at least one offset value configured by itself, and then determines the information content of the first information to be sent to the terminal. In one embodiment, if at least one offset value configured by the access network device is greater than a second threshold, the access network device may send first information to the terminal to indicate that the terminal does not use LP-WUS.
[0287] In some embodiments, the access network device may send the first information to the terminal based on the second information. In some embodiments, the description of the second information can be found in the description of the second information in step S2301, and will not be repeated here.
[0288] In some embodiments, the second information can be used by the access network device to determine the first information. In some embodiments, the access network device can determine whether LP-WUS needs to be disabled based on the wake-up latency supported by the terminal indicated by the second information, thereby determining the first information. In one embodiment, if the access network device determines based on the second information that the wake-up latency supported by the terminal is greater than a first threshold, the access network device can send the first information to the terminal to instruct the terminal not to use LP-WUS.
[0289] In some embodiments, the access network device can determine the wake-up latency supported by the terminal based on the second information, and determine the offset value selected by the terminal based on at least one offset value configured by itself and the wake-up latency supported by the terminal, so as to determine whether the terminal uses LP-WUS based on the offset value selected by the terminal, thereby determining the first information. In one embodiment, if the access network device determines, based on the second information and at least one offset value configured by itself, that the offset value selected by the terminal is greater than a third threshold, the access network device can send the first information to the terminal to indicate that the terminal does not use LP-WUS.
[0290] In some embodiments, the access network device can determine whether the terminal needs to disable LP-WUS without the terminal sending the second information to the access network device. In this case, step S2301 can be omitted.
[0291] In some embodiments, before the access network device sends the first information to the terminal, the access network device may receive the first information sent by the core network device. In some embodiments, when the access network device receives the first information sent by the core network device, it may transparently forward the first information to the terminal. In some embodiments, when the access network device receives the first information sent by the core network device, it may regenerate the first information based on its own configuration information and the first information sent by the core network device, and send the regenerated first information to the terminal.
[0292] In step S2303, the terminal determines that it will not use LP-WUS based on the first information.
[0293] In some embodiments, the terminal may determine whether to use LP-WUS based on the information content of the first information. In some embodiments, when the terminal receives the first information having a first value, the terminal may determine not to use LP-WUS. In some embodiments, when the terminal receives the first information, the terminal may determine not to use LP-WUS.
[0294] In some embodiments, if the first information indicates that the second terminal does not use LP-WUS, the terminal may not use LP-WUS.
[0295] In some embodiments, if the first information indicates that the first type of terminal does not use LP-WUS, the terminal does not use LP-WUS during the execution of the first service.
[0296] In some embodiments, when the first information indicates a third triggering condition, the terminal can determine whether to use LP-WUS based on whether the third triggering condition is met. In some embodiments, the terminal does not use LP-WUS when it determines that the third triggering condition is met. In some embodiments, the terminal does not use LP-WUS when it determines that the third triggering condition is met if the wake-up latency supported by the terminal is greater than a first threshold. In some embodiments, the terminal does not use LP-WUS when it determines that the third triggering condition is met if the offset value selected by the terminal based on its own capabilities is greater than a third threshold.
[0297] In some embodiments, if the terminal determines that it will not use LP-WUS, the terminal may listen to PO based on the configured DRX period.
[0298] In some embodiments, if the first information indicates that a paging packet method based on the terminal ID is not used, the terminal may use a paging packet method based on the core network allocation to determine its own paging packet information. In this case, if the core network device has allocated a paging packet ID to the terminal, the terminal determines that LP-WUS can be used. If the core network device has not allocated a paging packet ID to the terminal, the terminal may determine that LP-WUS is disabled.
[0299] In some embodiments, step S2303 may be omitted if the terminal determines that LP-WUS can be used based on the first information.
[0300] In some embodiments, the term "information" may be used interchangeably with terms such as "message," "signal," "signaling," "report," "configuration," "indication," "instruction," "command," "channel," "parameter," "field," and "data."
[0301] In some embodiments, the term "send" may be used interchangeably with terms such as "transmit," "report," or "transmit."
[0302] The communication method involved in the embodiments of this disclosure may include at least one of steps S2301 to S2303. For example, step S2301 may be implemented as a standalone embodiment, and steps S2301 and S2303 may be implemented as standalone embodiments, but are not limited thereto.
[0303] In some embodiments, steps S2302 and S2303 are optional, and one or more of these steps may be omitted or substituted in different embodiments.
[0304] In some embodiments, step S2302 is optional, and one or more of these steps may be omitted or substituted in different embodiments.
[0305] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.
[0306] Figure 3 is an interactive schematic diagram of a communication method according to an exemplary embodiment. As shown in Figure 3, the embodiments of this disclosure relate to a communication method, which includes step S3101.
[0307] In step S3101, the core network device or access network device sends the first information to the terminal.
[0308] In some embodiments, the terminal may receive first information sent by the core network device. In some embodiments, the terminal may receive first information sent by the access network device.
[0309] In some embodiments, the first information is used to determine whether to use LP-WUS.
[0310] In some embodiments, the first information is further used to determine whether to use a paging packet method based on terminal ID to determine the terminal's paging packet information.
[0311] In some embodiments, the first information sent by the core network device to the terminal is used to indicate at least one of the following: the first terminal does not use LP-WUS; the first terminal does not use LP-WUS in at least one first tracking area (TA); the first terminal does not use LP-WUS in a first area or a first cell of at least one first TA; the first area is the signal coverage area of the designated access network device; wherein the first terminal is a terminal designated by the core network device.
[0312] In some embodiments, the first information sent by the core network device to the terminal is used to indicate a first triggering condition; when the first triggering condition is met, the terminal does not use LP-WUS.
[0313] In some embodiments, the first triggering condition includes at least one of the following: the wake-up latency supported by the terminal is greater than a first threshold; the offset between the LP-WUS configured by the access network device and the paging timing PO is greater than a second threshold; and the offset corresponding to the LP-WUS monitored by the terminal is greater than a third threshold.
[0314] In some embodiments, the first information is also used for the terminal to determine that LP-WUS is not used during the execution of the first service.
[0315] In some embodiments, the first information sent by the access network device to the terminal is used to indicate at least one of the following: the second terminal does not use LP-WUS; the second terminal is a terminal designated by the access network device; the first type of terminal does not use LP-WUS; the first type of terminal is a terminal performing the first service.
[0316] In some embodiments, the core network device may also send first information to the access network device.
[0317] In some embodiments, the first information sent by the core network device to the access network device is used to indicate at least one of the following: LP-WUS is not used for a first terminal; the first terminal is a terminal designated by the core network device; LP-WUS is not used for a first type of terminal; the first type of terminal is a terminal performing a first service.
[0318] In some embodiments, the first information sent by the core network device to the access network device is used to indicate a second triggering condition, and when the second triggering condition is met, the access network device does not use LP-WUS for the first terminal or the first type of terminal.
[0319] In some embodiments, the second triggering condition includes: the offset between the LP-WUS configured by the access network device and the paging timing PO is greater than a fourth threshold.
[0320] In some embodiments, the core network device receives second information sent by a terminal or access network device, the second information indicating the wake-up latency supported by the terminal. In some embodiments, the core network device sends first information to the terminal or access network device based on the second information.
[0321] In some embodiments, the core network device receives third information sent by the access network device, the third information indicating at least one offset value between the LP-WUS configured by the access network device and the paging timing PO. In some embodiments, the third information is also used by the core network device to determine first information.
[0322] In some embodiments, the third information is sent by the access network device when the offset value is greater than the fifth threshold.
[0323] In some embodiments, the third information is also used to indicate whether the access network device supports the use of a paging packet method based on the terminal ID.
[0324] To better understand the embodiments of this disclosure, the following exemplary embodiments will be used to further illustrate this disclosure.
[0325] In this text, LP-WUS is a low-power wake-up signal. However, the protection mode described in this text can also be extended to other power-saving signals.
[0326] Example 1: The base station notifies the core network of its LP-WUS configuration.
[0327] In some embodiments, the base station notifies the core network of the offset value configured for the terminal to use a power-saving signal; wherein, at least one offset value may be included.
[0328] In some embodiments, the base station notifies the core network of the offset value configured for the terminal to use a power-saving signal. The notification granularity may be to notify the configuration of each cell.
[0329] In some embodiments, the base station notifies the core network of the offset value configured for the terminal to use a power-saving signal. The notification granularity can be base station granularity, i.e., the notification granularity is relatively coarse, such as only indicating the offset value of a configuration under that base station. Specifically, it can be based on the average of the configuration offset values of multiple cells.
[0330] In some embodiments, the base station notifies the core network of the statistics of the offset value configured for the terminal to use a power-saving signal. For example, it does not need to indicate the specific offset value, but only whether a larger offset value or a smaller offset value is configured.
[0331] In some embodiments, the base station only notifies the core network if its configured offset value is within a set range, for example, if the base station configures an offset value greater than 1 second, the base station notifies the core network.
[0332] In some embodiments, the base station may also notify the core network whether it supports UE-ID-based paging packet mode.
[0333] In some embodiments, the base station may use an NG setup request message to notify the core network.
[0334] In some embodiments, the base station uses an Access Network Configuration Update (RAN configuration update) message to notify the core network.
[0335] Therefore, if the base station notifies the core network of its configured offset value, the core network can estimate the latency caused by waking up the terminal, determine whether it will have an adverse impact on the service, and make a decision to enable the power-saving signal for the terminal.
[0336] Example 2: The core network notifies the base station whether to use LP-WUS or whether to use a paging packet method based on UE-ID.
[0337] In some embodiments, the core network instructs the base station not to use LP-WUS for a particular terminal.
[0338] In some embodiments, the core network instructs base stations not to use LP-WUS for a certain type of terminal.
[0339] In some embodiments, the core network instructs the base station to not use LP-WUS at a granular level, which can be either not using it across the entire base station or at a finer granular level, such as whether or not it is used in a specific cell.
[0340] In some embodiments, a certain type of terminal may be a terminal that is performing a certain service, such as a terminal that is making an emergency call.
[0341] In some embodiments, the core network may notify the base station based on auxiliary information obtained from the terminal. In some embodiments, the auxiliary information may be used to indicate the terminal's ability to support different wake-up latencies.
[0342] In some embodiments, the core network can obtain auxiliary information from the terminal. In some embodiments, the core network can obtain auxiliary information based on NAS signaling sent by the terminal.
[0343] Example 3: The core network notifies the base station whether to use the LP-WUS triggering condition or the triggering condition based on the UE-ID paging packet method.
[0344] In some embodiments, the core network notifies the base station that if the offset value configured by the base station is greater than a predetermined threshold, then LP-WUS should not be used for users making emergency calls.
[0345] Example 4: The core network notifies the terminal whether to use LP-WUS or whether to use a paging packet method based on UE-ID.
[0346] In some embodiments, the core network instructs the terminals not to use LP-WUS for a particular terminal.
[0347] In some embodiments, the core network instructs a terminal that, for a given terminal, LP-WUS will not be used in certain TAs or certain TA lists.
[0348] In some embodiments, the core network instructs a terminal that, for a particular terminal, LP-WUS will not be used within the signal coverage area of a base station in certain TAs or a certain TA list, or within a certain cell.
[0349] In some embodiments, the core network may include additional conditions when instructing a terminal, such as that a terminal performing a certain service, for example, when making an emergency call, cannot use LP-WUS or cannot use UE-ID-based paging packet mode.
[0350] Example 5: The core network notifies the terminal whether to use the LP-WUS triggering condition or the triggering condition based on the UE-ID paging packet method.
[0351] In some embodiments, the core network notifies the terminal that if the wake-up latency supported by the terminal is greater than threshold 1, the offset value configured by the base station must be greater than threshold 2, the terminal cannot use LP-WUS, or the terminal cannot use the paging packet method based on UE-ID.
[0352] In some embodiments, if the offset value selected by the terminal based on its own capabilities is greater than a threshold of 3, for example 1 second, then the terminal cannot use LP-WUS, or the terminal cannot use the paging packet method based on UE-ID.
[0353] Example 6: The base station notifies the terminal whether to use LP-WUS or whether to use a paging packet method based on UE-ID.
[0354] In some embodiments, the base station notifies the terminal that LP-WUS will not be used for a particular terminal.
[0355] In some embodiments, the base station notifies the terminal that LP-WUS will not be used for a certain type of terminal.
[0356] In some embodiments, a certain type of terminal may be a terminal performing a certain service, such as a terminal making an emergency call. In one embodiment, the base station may instruct the terminal not to use LP-WUS when making an emergency call.
[0357] In some embodiments, the base station notification terminal may use system broadcast signaling to make a notification.
[0358] In some embodiments, the base station may notify the terminal based on auxiliary information obtained from the core network.
[0359] In one embodiment, for a connected terminal, the network can also notify the terminal to use LP-WUS.
[0360] In one embodiment, the terminal reports to the network whether it supports LP-WUS capability.
[0361] In one embodiment, the terminal reports its preferred time offset to the network, so that the network can reasonably configure the time offset between LP-WUS and paging opportunity (PO).
[0362] In one embodiment, the terminal reports its preferred time offset to the network using UAI signaling.
[0363] In one embodiment, for the EN-DC scenario, the terminal can directly inform the network terminal to report its preferred time offset through the signaling bearer of the secondary node (SN), such as SRB3.
[0364] In one embodiment, for an MR-DC scenario, if the master node (MN) is configured to allow the terminal to use LP-WUS, the terminal can directly inform the network terminal to report its preferred time offset via the MN's signaling bearer, such as SRB1. If the SN is configured to allow the terminal to use LP-WUS, the terminal can directly inform the network terminal to report its preferred time offset via the SN's signaling bearer (if SRB3 is configured), such as SRB3. Otherwise, the terminal can transmit to the MN through a transparent box, and then forward it to the SN through the MN.
[0365] In some embodiments, other optional implementations of the various steps in the communication method shown in this disclosure can be found in the related parts of the embodiments involved in FIG2A, FIG2B, FIG2C and FIG3, and will not be repeated here.
[0366] This disclosure also proposes an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, an apparatus is proposed that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Furthermore, another apparatus is proposed that includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.
[0367] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through a configuration file, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.
[0368] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a CPU, microprocessor, graphics processing unit (GPU) (which can be understood as a microprocessor), or digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented as an ASIC or PLD, such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), tensor processing unit (TPU), deep learning processing unit (DPU), etc.
[0369] Figure 4A is a schematic diagram of the structure of a network device according to an exemplary embodiment. The network device 4100 is used to perform any of the above methods. In some embodiments, as shown in Figure 4A, the network device 4100 may include a transceiver module 4101; the transceiver module 4101 is configured to send first information to a terminal or access network device, the first information being used to determine whether to use LP-WUS. Optionally, the transceiver module is used to perform at least one of the communication steps such as sending and / or receiving performed by the core network device in any of the above methods. Optionally, the network device 4100 may further include a processing module, which is used to perform at least one of the other steps performed by the core network device in any of the above methods, which will not be described in detail here.
[0370] In some embodiments, the first information is further used to determine whether to use a paging packet method based on terminal ID to determine the terminal's paging packet information.
[0371] In some embodiments, the first information sent by the core network device to the terminal is used to indicate at least one of the following: the first terminal does not use LP-WUS; the first terminal does not use LP-WUS in at least one first tracking area (TA); the first terminal does not use LP-WUS in a first area or a first cell of at least one first TA; the first area is the signal coverage area of the designated access network device; wherein the first terminal is a terminal designated by the core network device.
[0372] In some embodiments, the first information sent by the core network device to the terminal is used to indicate a first triggering condition; when the first triggering condition is met, the terminal does not use LP-WUS.
[0373] In some embodiments, the first triggering condition includes at least one of the following: the wake-up latency supported by the terminal is greater than a first threshold; the offset between the LP-WUS configured by the access network device and the paging timing PO is greater than a second threshold; and the offset corresponding to the LP-WUS monitored by the terminal is greater than a third threshold.
[0374] In some embodiments, the first information is also used for the terminal to determine that LP-WUS is not used during the execution of the first service.
[0375] In some embodiments, the first information sent by the core network device to the access network device is used to indicate at least one of the following: LP-WUS is not used for a first terminal; the first terminal is a terminal designated by the core network device; LP-WUS is not used for a first type of terminal; the first type of terminal is a terminal performing a first service.
[0376] In some embodiments, the first information sent by the core network device to the access network device is used to indicate a second triggering condition, and when the second triggering condition is met, the access network device does not use LP-WUS for the first terminal or the first type of terminal.
[0377] In some embodiments, the second triggering condition includes: the offset between the LP-WUS configured by the access network device and the paging timing PO is greater than a fourth threshold.
[0378] In some embodiments, the transceiver module is further configured to receive second information sent by a terminal or access network device, the second information being used to indicate the wake-up latency supported by the terminal; and to send first information to the terminal or access network device, including: sending the first information to the terminal or access network device based on the second information.
[0379] In some embodiments, the transceiver module is further configured to receive third information sent by the access network device, the third information being used to indicate at least one offset value between the LP-WUS configured by the access network device and the paging timing PO; the third information is also used by the core network device to determine the first information.
[0380] In some embodiments, the third information is sent by the access network device when the offset value is greater than the fifth threshold.
[0381] In some embodiments, the third information is also used to indicate whether the access network device supports the use of a paging packet method based on the terminal ID.
[0382] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, which may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver.
[0383] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module.
[0384] In some embodiments, the processing module can be interchanged with the processor, and the transceiver module can be interchanged with the transceiver.
[0385] Figure 4B is a schematic diagram of the structure of a network device according to an exemplary embodiment. The network device 4200 is used to perform any of the above methods. In some embodiments, as shown in Figure 4B, the network device 4200 may include a transceiver module 4201; the transceiver module 4201 is configured to send first information to a terminal, the first information being used to determine whether to use LP-WUS. Optionally, the transceiver module is used to perform at least one of the communication steps such as sending and / or receiving performed by the access network device in any of the above methods. Optionally, the network device 4200 may further include a processing module, which is used to perform at least one of the other steps performed by the access network device in any of the above methods, which will not be described in detail here.
[0386] In some embodiments, the first information is further used to determine whether to use a paging packet method based on terminal ID to determine the terminal's paging packet information.
[0387] In some embodiments, the first information is used to indicate at least one of the following: the second terminal does not use LP-WUS; the second terminal is a terminal designated by the access network device; the first type of terminal does not use LP-WUS; the first type of terminal is a terminal performing the first service.
[0388] In some embodiments, the transceiver module is further configured to receive first information sent by the core network device.
[0389] In some embodiments, the first information sent by the core network device is used to indicate at least one of the following: LP-WUS is not used for a first terminal; the first terminal is a terminal designated by the core network device; LP-WUS is not used for a first type of terminal; the first type of terminal is a terminal performing a first service.
[0390] In some embodiments, the first information sent by the core network device to the access network device is used to indicate a second triggering condition, and when the second triggering condition is met, the access network device does not use LP-WUS for the first terminal or the first type of terminal.
[0391] In some embodiments, the second triggering condition includes: the offset between the LP-WUS configured by the access network device and the paging timing PO is greater than a fourth threshold.
[0392] In some embodiments, the transceiver module is further configured to receive second information sent by a terminal or core network device, the second information being used to indicate the wake-up latency supported by the terminal; and to send first information to the terminal, including: sending the first information to the terminal based on the second information.
[0393] In some embodiments, the transceiver module is further configured to send third information to the core network device, the third information being used to indicate at least one offset value between the LP-WUS configured by the access network device and the paging timing PO; the third information is also used by the core network device to determine the first information.
[0394] In some embodiments, the transceiver module is further configured to send third information to the core network device if it determines that the configured offset value is greater than the fifth threshold.
[0395] In some embodiments, the third information is also used to indicate whether the access network device supports the use of a paging packet method based on the terminal ID.
[0396] Figure 4C is a schematic diagram of a terminal according to an exemplary embodiment. Terminal 4300 may include a transceiver module 4301, configured to receive first information sent by a core network device or an access network device, the first information being used to determine whether to use a low-power wake-up signal (LP-WUS). Optionally, the transceiver module may perform at least one of the communication steps, such as sending and / or receiving, performed by the terminal in any of the above methods; further details are omitted here. Optionally, terminal 4300 may also include a processing module, which may perform at least one of the other steps performed by the terminal in any of the above methods; further details are omitted here.
[0397] In some embodiments, the first information is further used to determine whether to use a paging packet method based on the terminal identifier ID to determine the terminal's paging packet information.
[0398] In some embodiments, the first information sent by the core network device is used to indicate at least one of the following: the first terminal does not use LP-WUS; the first terminal does not use LP-WUS in at least one first tracking area (TA); the first terminal does not use LP-WUS in a first area or a first cell of at least one first TA; the first area is the signal coverage area of the designated access network device; wherein the first terminal is a terminal designated by the core network device.
[0399] In some embodiments, the first information sent by the core network device is used to indicate a first triggering condition; the processing module is configured to determine that the first triggering condition is met and stop using LP-WUS.
[0400] In some embodiments, the first triggering condition includes at least one of the following: the wake-up latency supported by the terminal is greater than a first threshold; the offset between the LP-WUS configured by the access network device and the paging timing PO is greater than a second threshold; and the offset corresponding to the LP-WUS monitored by the terminal is greater than a third threshold.
[0401] In some embodiments, the first information is further used for the terminal to determine that LP-WUS is not used during the execution of the first service.
[0402] In some embodiments, the first information sent by the access network device is used to indicate at least one of the following: the second terminal does not use LP-WUS; the second terminal is a terminal designated by the access network device; the first type of terminal does not use LP-WUS; the first type of terminal is a terminal performing the first service.
[0403] In some embodiments, the first information is sent by the access network device or the core network device based on the second information, which is used to indicate the wake-up latency supported by the terminal.
[0404] In some embodiments, the first information is sent by the core network device based on the third information sent by the access network device, the third information being used to indicate at least one offset value between the LP-WUS configured by the access network device and the paging timing PO.
[0405] In some embodiments, the third information is sent by the access network device when it determines that the configured offset value is greater than the fifth threshold.
[0406] In some embodiments, the third information is also used to indicate whether the access network device supports the use of a paging packet method based on the terminal ID.
[0407] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, which may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver.
[0408] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module.
[0409] In some embodiments, the processing module can be interchanged with the processor, and the transceiver module can be interchanged with the transceiver.
[0410] Figure 5A is a schematic diagram illustrating the structure of a communication device according to an exemplary embodiment. The communication device 5100 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 5100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.
[0411] As shown in Figure 5A, the communication device 5100 is used to execute any of the above methods. In some embodiments, the communication device 5100 includes one or more processors 5101. The processor 5101 may be a general-purpose processor or a special-purpose processor, such as a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 5100 is used to execute any of the above methods. Optionally, one or more processors 5101 are used to invoke instructions to cause the communication device 5100 to execute any of the above methods.
[0412] In some embodiments, the communication device 5100 further includes one or more transceivers 5103. When the communication device 5100 includes one or more transceivers 5103, the transceiver 5103 performs at least one of the communication steps such as sending and / or receiving in the above-described method, and the processor 5101 performs at least one of the other steps. In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., can be used interchangeably; the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.
[0413] In some embodiments, the communication device 5100 further includes one or more memories 5102 for storing data and / or instructions. Optionally, one or more processors 5101 are used to invoke instructions stored in the memory 5102 to cause the communication device 5100 to perform any of the above methods. Optionally, all or part of the memory 5102 may also be located outside the communication device 5100. In an optional embodiment, the communication device 5100 may include one or more interface circuits 5104. Optionally, the interface circuit 5104 is connected to the memory 5102 and can be used to receive data and / or instructions from the memory 5102 or other devices, and can be used to send data and / or instructions to the memory 5102 or other devices. For example, the interface circuit 5104 can read data and / or instructions stored in the memory 5102 and send the data and / or instructions to the processor 5101.
[0414] The communication device 5100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 5100 described in this disclosure is not limited thereto, and the structure of the communication device 5100 may not be limited by FIG. 5A. The communication device may be a standalone device or may be part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include storage components for storing data, programs and / or instructions; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.
[0415] Figure 5B is a schematic diagram of a chip structure according to an exemplary embodiment. For cases where the communication device 5100 can be a chip or a chip system, please refer to the schematic diagram of the chip 5200 shown in Figure 5B, but it is not limited thereto.
[0416] Chip 5200 includes one or more processors 5201. Chip 5200 is used to perform any of the methods described above.
[0417] In some embodiments, chip 5200 further includes one or more interface circuits 5202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 5200 further includes one or more memories 5203 for storing data and / or instructions. Optionally, all or part of the memories 5203 may be located outside of chip 5200. Optionally, the interface circuit 5202 is connected to the memories 5203, and the interface circuit 5202 can be used to receive data and / or instructions from the memories 5203 or other devices, and the interface circuit 5202 can be used to send data and / or instructions to the memories 5203 or other devices. For example, the interface circuit 5202 can read data and / or instructions stored in the memories 5203 and send the data and / or instructions to the processor 5201.
[0418] In some embodiments, the interface circuit 5202 performs at least one of the communication steps, such as sending and / or receiving, in the above-described method. For example, the interface circuit 5202 performing the communication steps, such as sending and / or receiving, in the above-described method means that the interface circuit 5202 performs data and / or instruction interaction between the processor 5201, the chip 5200, the memory 5203, or the transceiver device. In some embodiments, the processor 5201 performs at least one of the other steps.
[0419] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.
[0420] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.
[0421] This disclosure also proposes a program product, including a program and / or instructions, which, when executed by a communication device, cause the communication device to perform any of the above methods. Optionally, the program product is a computer program product. Optionally, the program product is stored on the storage medium.
[0422] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.
[0423] Other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of the invention are indicated by the following claims.
[0424] It should be understood that the present invention is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.
Claims
1. A communication method, wherein, Performed by core network equipment, the method includes: Send first information to the terminal or access network device, the first information being used to determine whether to use LP-WUS.
2. The method according to claim 1, wherein, The first information is also used to determine whether to use a paging packet method based on terminal ID to determine the paging packet information of the terminal.
3. The method according to claim 1 or 2, wherein, The first information sent by the core network device to the terminal is used to indicate at least one of the following: The first terminal does not use LP-WUS; The first terminal does not use the LP-WUS within at least one first tracking area (TA); The first terminal does not use the LP-WUS in at least one first area or first cell of the first TA; the first area is the signal coverage area of the designated access network equipment. The first terminal is the terminal designated by the core network equipment.
4. The method according to any one of claims 1 to 3, wherein, The first information sent by the core network device to the terminal is used to indicate a first triggering condition; when the first triggering condition is met, the terminal does not use the LP-WUS.
5. The method according to claim 4, wherein, The first triggering condition includes at least one of the following: The wake-up latency supported by the terminal is greater than the first threshold. The offset between the LP-WUS configured in the access network device and the paging timing PO is greater than the second threshold. The offset value corresponding to the LP-WUS monitored by the terminal is greater than the third threshold.
6. The method according to any one of claims 1 to 5, wherein, The first information is also used by the terminal to determine that it will not use the LP-WUS during the execution of the first service.
7. The method according to claim 1 or 2, wherein, The first information sent by the core network device to the access network device is used to indicate at least one of the following: The LP-WUS is not used for the first terminal; the first terminal is a terminal designated by the core network equipment. The LP-WUS is not used for the first type of terminal; the first type of terminal is the terminal that is performing the first service.
8. The method according to claim 7, wherein, The first information sent by the core network device to the access network device is used to indicate a second triggering condition. When the second triggering condition is met, the access network device does not use the LP-WUS for the first terminal or the first type of terminal.
9. The method according to claim 8, wherein, The second triggering condition includes: The offset between the LP-WUS configured in the access network device and the paging timing PO is greater than the fourth threshold.
10. The method according to any one of claims 1 to 9, wherein, The method further includes: The terminal or the access network device receives second information, which is used to indicate the wake-up latency supported by the terminal. Sending the first information to the terminal or access network device includes: Based on the second information, the first information is sent to the terminal or the access network device.
11. The method according to any one of claims 1 to 10, wherein, The method further includes: The core network device receives third information sent by the access network device, the third information being used to indicate at least one offset value between the LP-WUS configured by the access network device and the paging timing PO; the third information is also used by the core network device to determine the first information.
12. The method according to claim 11, wherein, The third piece of information is sent by the access network device when the offset value is greater than the fifth threshold.
13. The method according to claim 11 or 12, wherein, The third piece of information is also used to indicate whether the access network device supports the use of paging packets based on terminal ID.
14. A communication method, wherein, Performed by an access network device, the method includes: Send first information to the terminal, the first information being used to determine whether to use LP-WUS.
15. The method according to claim 14, wherein, The first information is also used to determine whether to use a paging packet method based on terminal ID to determine the paging packet information of the terminal.
16. The method according to claim 14 or 15, wherein, The first information is used to indicate at least one of the following: The second terminal does not use the LP-WUS; the second terminal is a terminal designated by the access network device. The first type of terminal does not use the LP-WUS; the first type of terminal is the terminal that is performing the first service.
17. The method according to any one of claims 14 to 16, wherein, The method further includes: Receive the first information sent by the core network device.
18. The method according to claim 17, wherein, The first information sent by the core network device is used to indicate at least one of the following: The LP-WUS is not used for the first terminal; the first terminal is a terminal designated by the core network equipment. The LP-WUS is not used for the first type of terminal; the first type of terminal is the terminal that is performing the first service.
19. The method according to claim 18, wherein, The first information sent by the core network device to the access network device is used to indicate a second triggering condition. When the second triggering condition is met, the access network device does not use the LP-WUS for the first terminal or the first type of terminal.
20. The method according to claim 19, wherein, The second triggering condition includes: The offset between the LP-WUS configured in the access network device and the paging timing PO is greater than the fourth threshold.
21. The method according to any one of claims 14 to 20, wherein, The method further includes: Receive second information sent by the terminal or core network device, the second information being used to indicate the wake-up latency supported by the terminal; Sending the first information to the terminal includes: Based on the second information, the first information is sent to the terminal.
22. The method according to any one of claims 14 to 21, wherein, The method further includes: Send a third message to the core network device, the third message being used to indicate at least one offset value between the LP-WUS configured by the access network device and the paging timing PO; the third message is also used by the core network device to determine the first message.
23. The method according to claim 22, wherein, The sending of third information to the core network equipment includes: If the configured offset value is determined to be greater than the fifth threshold, the third information is sent to the core network device.
24. The method according to claim 22 or 23, wherein, The third piece of information is also used to indicate whether the access network device supports the use of paging packets based on terminal ID.
25. A communication method, wherein, The method, executed by a terminal, includes: The system receives first information sent by a core network device or an access network device, the first information being used to determine whether to use the Low Power Wake-up Signal (LP-WUS).
26. The method of claim 25, wherein, The first information is also used to determine whether to use a paging packet method based on the terminal identifier ID to determine the paging packet information of the terminal.
27. The method according to claim 25 or 26, wherein, The first information sent by the core network device is used to indicate at least one of the following: The first terminal does not use LP-WUS; The first terminal does not use the LP-WUS within at least one first tracking area (TA); The first terminal does not use the LP-WUS in at least one first area or first cell of the first TA; the first area is the signal coverage area of the designated access network equipment. The first terminal is the terminal designated by the core network equipment.
28. The method according to any one of claims 25 to 27, wherein, The first information sent by the core network device is used to indicate the first triggering condition; The method further includes: Once the first triggering condition is determined to be met, the use of the LP-WUS is stopped.
29. The method according to claim 28, wherein, The first triggering condition includes at least one of the following: The wake-up latency supported by the terminal is greater than the first threshold. The offset between the LP-WUS configured in the access network device and the paging timing PO is greater than the second threshold. The offset value corresponding to the LP-WUS monitored by the terminal is greater than the third threshold.
30. The method according to any one of claims 27 to 29, wherein, The first information is also used by the terminal to determine that it will not use the LP-WUS during the execution of the first service.
31. The method according to claim 25 or 27, wherein, The first information sent by the access network device is used to indicate at least one of the following: The second terminal does not use the LP-WUS; the second terminal is a terminal designated by the access network device. The first type of terminal does not use the LP-WUS; the first type of terminal is the terminal that is performing the first service.
32. The method according to any one of claims 25 to 31, wherein, The first information is sent by the access network device or the core network device based on the second information, which is used to indicate the wake-up latency supported by the terminal.
33. The method according to any one of claims 25 to 32, wherein, The first information is sent by the core network device based on the third information sent by the access network device, the third information being used to indicate at least one offset value between the LP-WUS configured by the access network device and the paging timing PO.
34. The method according to claim 33, wherein, The third piece of information is sent by the access network device when it determines that the configured offset value is greater than the fifth threshold.
35. The method according to claim 33 or 34, wherein, The third piece of information is also used to indicate whether the access network device supports the use of paging packets based on terminal ID.
36. A communication method, wherein, Performed by a communication system, the method includes: The core network device or access network device sends first information to the terminal; wherein the first information is used to determine whether to use LP-WUS.
37. A communication device, wherein, The communication device is used to perform the communication method according to any one of claims 1 to 13, 14 to 24, or 25 to 35.
38. A communication system, characterized in that, The device includes a terminal, an access network device, and a core network device, wherein the core network device is configured to implement the communication method of any one of claims 1 to 13, the access network device is configured to implement the communication method of any one of claims 14 to 24, and the terminal is configured to implement the communication method of any one of claims 25 to 35.
39. A storage medium storing instructions, characterized in that, When the instructions are executed on the communication device, the communication device performs the communication method as described in any one of claims 1 to 13, 14 to 24, or 25 to 35.
40. A program product comprising at least one of a program and instructions, characterized in that, When at least one of the programs or instructions is executed by the communication device, it implements the steps of the communication method according to any one of claims 1 to 13, 14 to 24, or 25 to 35.
