Method and apparatus for non-cell-defined synchronization signal correlation

Abstract

Techniques and methods are described for methods and apparatus related to non-cell-defined synchronization signals. An exemplary communication method includes receiving, by a network device, configuration information from a network node; and operating, by the network device, a network by selectively activating a transmission operation according to the configuration information or a state of the network device.

Description

Technical Field

[0001] This patent document generally relates to digital wireless communications. Background Art

[0002] Mobile telecommunication technologies are moving the world towards an increasingly connected and networked society. Next generation systems and wireless communication technologies will need to support a wider range of use case characteristics and provide a more complex and precise range of access requirements and flexibility compared to existing wireless networks.

[0003] Long Term Evolution (LTE) is a standard developed by the Third Generation Partnership Project (3GPP) for wireless communications for mobile devices and data terminals. LTE Advanced (LTE-A) is a wireless communications standard that enhances the LTE standard. The fifth generation wireless system, known as 5G, advances the LTE and LTE-A wireless standards and is committed to supporting higher data rates, a large number of connections, ultra-low latency, high reliability, and other emerging business requirements. Summary of the invention

[0004] This patent document discloses technologies such as methods and devices for defining synchronization signals related to non-cells.

[0005] In one example aspect, a first wireless communication method is disclosed. The method includes: receiving, by a network device, configuration information from a network node; and operating a network by selectively activating a transmission operation according to the configuration information or a state of the network device.

[0006] In another example aspect, another wireless communication method is disclosed. The method includes sending, by a first network node, a message to a second network node, wherein the message includes information indicating a capacity status of a workload of the first network node.

[0007] In another example aspect, another wireless communication method is disclosed. The method includes: receiving, by a first network node, a message including information related to a capability status of a second network node; and performing, by the first network node, an operation based on the capability status.

[0008] In another example aspect, another wireless communication method is disclosed. The method includes sending, by a network node to a terminal node, configuration information regarding an extended discontinuous reception (eDRX) cycle for RAN paging, wherein the configuration information indicates suitability of a cycle length greater than a threshold.

[0009] In yet another example aspect, a wireless communication device is disclosed, the wireless communication device comprising a process configured or operable to perform the above method.

[0010] In yet another example aspect, a computer-readable storage medium is disclosed. The computer-readable storage medium stores codes, which, when executed by a processor, cause the processor to implement the above method.

[0011] The above and other aspects and implementations thereof are described in more detail in the drawings, the description and the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1 An example flow diagram for facilitating communications between a network device and a network is shown.

[0013] Figure 2 An example flow chart of another communication scenario between a terminal device and a network node is shown.

[0014] Figure 3 An example flow diagram for sending a message from a first network node to a second network node is shown.

[0015] Figure 4 An example flow chart for receiving a message by a network node and reacting based on an indication of the message is shown.

[0016] Figure 5 An example flow chart for sending a configuration between a first network node and a second network node is shown.

[0017] Figure 6 An example flow chart for receiving a message by a network node and reacting based on an indication of the message is shown.

[0018] Figure 7 An exemplary block diagram of a hardware platform that may be part of a network device or a communication device is shown.

[0019] Figure 8 An example of a wireless communication system including a base station (BS) and a user equipment (UE) based on some implementations of the disclosed technology is shown. DETAILED DESCRIPTION

[0020] The headings of the following sections are intended to aid understanding of the disclosed subject matter and do not limit the scope of the claimed subject matter in any way. Therefore, one or more features of one section of content may be combined with one or more features of another section of content. In addition, for the sake of clarity of explanation, 5G terminology is used, but the technology disclosed herein is not limited to 5G technology, but can be used in wireless systems that implement other protocols.

[0021] introduction

[0022] In 5G NR Release 17 (Rel-17), the 3rd Generation Partnership Project (3GPP) introduced a new tier of reduced capability (RedCap) devices. To help deploy RedCap devices, a specific barring framework was introduced in Rel-17 for RedCap devices. The barring framework provides protocol support to allow RedCap devices to know whether they are allowed to join a specific wireless network.

[0023] The concept of RedCap devices is also being advanced in the next release of 5G NR, known as Release 18 (Rel-18). For Rel-18 RedCap user equipment UE, the 5MHz baseband BB bandwidth is restricted for physical downlink shared channel or physical uplink shared channel PDSCH / PUSCH. In addition, the peak rate should also be subject to constraint relaxation (vLayers·Qm·f≥4). However, there is currently no solution available for access control for Rel-18 RedCap UEs. Therefore, a prohibition framework for Rel-18 RedCap UEs would benefit wireless system deployment in controlling the access of such UEs. However, no such prohibition framework exists.

[0024] To solve the above problem, part of the barring framework introduced in Rel-17 RedCap can be used for Rel-18 RedCap UE.

[0025] In addition, new barring parameters may be introduced as conditions for controlling access of Rel-18 RedCap UEs, such as eRedCapAccessAllowed-r18.

[0026] If the parameter is set to bar, the cell is considered to be barred.

[0027] Furthermore, for Rel-17 RedCap UE and non-RedCap UE, this parameter is ignored.

[0028] For Rel-17 RedCap UE, intraFreqReselectionRedCap and redCapAccessAllowed are introduced to control the cell selection / reselection of intraFreq / inter-frequency cells by RedCap UE when the cell is barred or regarded as barred.

[0029] Similarly, for Rel-18 RedCap UEs, separate parameters may be introduced to control cell selection / reselection to intra-frequency / inter-frequency cells.

[0030] For an eDRX cycle exceeding 10.24s in the RRC inactive state (RRC_INACTIVE), if some data is buffered in the RAN, some flow control mechanisms need to be considered.

[0031] When the RAN buffer is full or the amount of data in the RAN buffer reaches a threshold, the RAN may send an instruction to the UPF to stop sending MT data or to send a small amount of data.

[0032] In addition, when the amount of data in the RAN buffer does not reach a threshold or the RAN buffer is not full, if flow control is used, an indication to cancel flow control may be sent to the UPF.

[0033] This document provides solutions that can be implemented by various embodiments to solve the above problems, etc. These solutions are described as exemplary embodiments, each of which provides a collection of technical solutions that can be mixed and matched by actual implementation.

[0034] Example 1

[0035] In this embodiment, a barring framework for Rel-17 RedCap UE is introduced. First, the barred cell (cellBarred) in the MIB can be used for RedCap UE.

[0036] If cellBarred is set to barred, the cell will be considered barred, otherwise, if the SSB subcarrier offset (ssb-SubcarrierOffset) indicates that SIB1 is transmitted in the cell, the UE obtains SIB1.

[0037] Second, if intraFreqReselectionRedCap does not exist in SIB1, the cell is considered to be barred.

[0038] If intraFreqReselectionRedCap exists and if cellBarredRedCap1Rx exists in the obtained SIB1 and is set to be prohibited and the UE is equipped with 1 receive (Rx) branch; or if cellBarredRedCap2Rx exists in the obtained SIB1 and is set to be prohibited and the UE is equipped with 2 Rx branches; or if halfDuplexRedCapAllowed does not exist in the obtained SIB1 and the UE only supports half-duplex frequency division duplex FDD operation, the cell is considered to be prohibited.

[0039] The relevant parameters that can be used to control cell access are defined in Table 1 below:

[0040]

[0041] Table 1

[0042] The barring architecture for Rel-17 RedCap UEs may also be used for Rel-18 RedCap UEs.

[0043] In addition, since the bandwidth of Rel-18 RedCap UE is limited to 5 MHz, new barring parameters used for Rel-18 RedCap UE can be introduced to control the access of these UEs, such as eRedCapAccessAllowed-r18.

[0044] If it is set to be barred, the cell is considered to be barred, otherwise, if it is configured as not barred, the cell is allowed access.

[0045] A possible example is shown in Table 2:

[0046]

[0047] Table 2

[0048] In addition, if this parameter is introduced, the corresponding specification description is as follows:

[0049] Upon receiving SIB1, the UE shall:

[0050] 1>Store the acquired SIB1;

[0051] 1> If the UE is a RedCap UE or eRedCap UE and is in RRC idle state (RRC_IDLE) or RRC_INACTIVE, or if the RedCap UE or eRedCap UE is in RRC connected state (RRC_CONNECTED) while T311 is running:

[0052] 2> If intraFreqReselectionRedCap does not exist in SIB1:

[0053] 3> According to TS38.304

[20] , the cell is considered to be barred;

[0054] 3>If intraFreqReselectionRedCap is set to be allowed, prohibition is performed;

[0055] 2> Otherwise:

[0056] 3> if cellBarredRedCap1Rx is present in the obtained SIB1 and is set to be disabled and the UE is equipped with 1 Rx branch; or

[0057] 3> if cellBarredRedCap2Rx is present in the obtained SIB1 and is set to be prohibited and the UE is equipped with 2 Rx branches; or

[0058] 3> if halfDuplexRedCapAllowed is not present in the acquired SIB1 and the UE only supports half-duplex FDD operation; or

[0059] 3> If eRedCapAccessAllowed is present in the acquired SIB1 and is set to be prohibited:

[0060] 4> According to TS38.304

[20] , the cell is considered to be barred;

[0061] 4> Execute prohibition based on intraFreqReselectionRedCap specified in TS38.304

[20] .

[0062] Example 2

[0063] In this embodiment, we first introduce a barring framework for Rel-17 RedCap UE.

[0064] First, cellBarred in MIB can be used for RedCap UE. If cellBarred is set to be barred, the cell will be considered barred, otherwise, if ssb-SubcarrierOffset indicates that SIB1 is sent in the cell, the UE obtains SIB1.

[0065] Secondly, if intraFreqReselectionRedCap does not exist in SIB1, the cell is considered to be barred. If intraFreqReselectionRedCap exists and if cellBarredRedCap1Rx exists in the acquired SIB1 and is set to be barred and the UE is equipped with 1 Rx branch; or if cellBarredRedCap2Rx exists in the acquired SIB1 and is set to be barred and the UE is equipped with 2 Rx branches; or if halfDuplexRedCapAllowed does not exist in the acquired SIB1 and the UE only supports half-duplex FDD operation, the cell is considered to be barred. In other words, the following parameters can be used to control cell access.

[0066]

[0067] Table 3

[0068] The barring framework for Rel-17 RedCap UEs can also be used for Rel-18 RedCap UEs. In addition, since the Rel-18 RedCap UE bandwidth is limited to 5MHz, new barring parameters used for Rel-18 RedCap UEs can be introduced to control the access of these UEs, such as eRedCapAccessAllowed-r18. If it is set to barred, the cell is considered barred, otherwise, if it is configured as not barred, the cell is allowed to access.

[0069] A possible example is as follows:

[0070]

[0071] Table 4

[0072]

[0073]

[0074] Table 5

[0075] When eRedCapAccessAllowed is not broadcasted in the cell, the UE shall regard the cell as having a "barred" cell state for Rel-18 RedCap access.

[0076] In addition, if this parameter is introduced, the corresponding specification description is as follows:

[0077] Upon receiving SIB1, the UE shall:

[0078] 1>Store the acquired SIB1;

[0079] 1> If the UE is a RedCap UE or eRedCap UE and is in RRC_IDLE or RRC_INACTIVE, or if the RedCap UE or eRedCap UE is in RRC_CONNECTED while T311 is running:

[0080] 2> If intraFreqReselectionRedCap does not exist in SIB1:

[0081] 3> According to TS38.304

[20] , the cell is considered to be barred;

[0082] 3>If intraFreqReselectionRedCap is set to be allowed, prohibition is performed;

[0083] 2> Otherwise:

[0084] 3> If cellBarredRedCap1Rx is present in the acquired SIB1 and is set to be disabled and the UE is equipped with 1 Rx branch; or

[0085] 3> If cellBarredRedCap2Rx is present in the acquired SIB1 and is set to be prohibited and the UE is equipped with 2 Rx branches; or

[0086] 3> if halfDuplexRedCapAllowed does not exist in the acquired SIB1 and the UE only supports half-duplex FDD operation; or

[0087] 3> If eRedCapAccessAllowed exists in the obtained SIB1 and is set to be prohibited:

[0088] 4> According to TS38.304

[20] , the cell is considered to be barred;

[0089] 4> Based on the intraFreqReselectionRedCap specified in TS38.304

[20] , execution is prohibited.

[0090] Example 3

[0091] This embodiment discloses a signaling design in Rel-18, which allows RedCap UE to perform intra-frequency / inter-frequency reselection operations.

[0092] In Rel-17 RedCap, intraFreqReselectionRedCap and redCapAccessAllowed are introduced to control the cell selection / reselection of intra-frequency / inter-frequency cells by RedCap UEs when the cell is barred or regarded as barred.

[0093] The parameters are disclosed in the table below.

[0094]

[0095] Table 6

[0096] For Rel-18 RedCapUE, considering flexibility and special handling, separate parameters for intra-frequency / inter-frequency cell reselection are defined, such as intraFreqReselectioneRedCap-r18 and eRedCapAccessAllowed-r18.

[0097] Example 4

[0098] This embodiment discloses a prohibition mechanism design in Rel-18 for RedCap UE.

[0099] We first introduce the banning framework for Rel-17 RedCap UE.

[0100] First, cellBarred in MIB can be used for RedCap UE. If cellBarred is set to be barred, the cell will be considered barred, otherwise, if ssb-SubcarrierOffset indicates that SIB1 is sent in the cell, the UE obtains SIB1.

[0101] Secondly, if intraFreqReselectionRedCap does not exist in SIB1, the cell is considered to be barred. If intraFreqReselectionRedCap exists and if cellBarredRedCap1Rx exists in the acquired SIB1 and is set to be barred and the UE is equipped with 1 Rx branch; or if cellBarredRedCap2Rx exists in the acquired SIB1 and is set to be barred and the UE is equipped with 2 Rx branches; or if halfDuplexRedCapAllowed does not exist in the acquired SIB1 and the UE only supports half-duplex FDD operation, the cell is considered to be barred. In other words, the following parameters can be used to control cell access.

[0102] The parameters are disclosed in the table below.

[0103]

[0104] Table 7

[0105] For Rel-18 RedCapUE, cellBarred in MIB can be used similarly to Rel-17 RedCap / non-RedCapUE.

[0106] In addition, considering the access control flexibility, separate barring parameters can be used for Rel-18 RedCap UE, such as halfDuplexeRedCapAllowed-r18, cellBarredeRedCap1Rx-r18 and cellBarredeRedCap2Rx-r18. Considering that the bandwidth of Rel-18 RedCap UE can be limited to less than 5MHz, another parameter, such as eRedCapAccess-r18, can also be introduced.

[0107] These newly introduced parameters for Rel-18 RedCap UEs may be configured in SIB1 or other messages.

[0108] Example 5

[0109] This embodiment discloses a communication mechanism between a base station and a core network to effectively control the flow transmission on the base station side.

[0110] In some cases, the RAN can buffer the MT data from the CN. If the RAN buffering capacity is limited, the flow control between the RAN and the UPF needs to be considered.

[0111] When the RAN buffer is full or the amount of data in the RAN buffer reaches a threshold, the RAN may send an indication to the UPF to stop sending MT data or to send a small amount of data. Upon receiving the indication from the RAN, the UPF in the core network may send a confirmation message to the RAN. Next, the UPF may stop sending MT data to the RAN, or send a small amount of data. Alternatively, upon receiving the indication, the UPF may stop sending MT data to the RAN, or send a small amount of data, i.e., there is no confirmation indication to the RAN.

[0112] In addition, when the amount of data in the RAN buffer does not reach the threshold or the RAN buffer is not full, if the data can be buffered in the RAN, an indication to cancel the flow control can be sent to the UPF. Then, once there is MT data, the UPF can send the MT data to the RAN.

[0113] The above thresholds can be configured by OAM.

[0114] Example 6

[0115] This embodiment discloses a communication mechanism between a base station and a user equipment to notify the user equipment of a specific support mechanism for RedCap UE in Rel-18.

[0116] In Rel-17 RedCap, eDRX is introduced for RRC_IDLE UE and RRC_INACTIVE UE. For RRC_IDLE UE, an eDRX cycle of up to 10487.56s can be configured, while for RRC_INACTIVE UE, an eDRX cycle of up to 10.24s can be configured.

[0117] In Rel-18 RedCap, an eDRX cycle longer than 10.24s may be introduced for RRC_INACTIVE UEs.

[0118] For Rel-18 RedCap UEs, firstly UE capabilities should be introduced, such as Rel-18 Extended DRX in RRC_INACTIVE. This capability is optional for the UE to support Rel-18 Extended DRX cycles up to 10485.76s and paging in Extended DRX in RRC_INACTIVE. Secondly, RRC parameters can also be introduced to control whether RRC_INACTIVE UEs are allowed to have Extended DRX longer than 10.24s, such as eDRXWithLongCycle-AllowedInactive. If eDRXWithLongCycle-AllowedInactive is not present, the UE shall stop using Extended Long DRX in RRC_INACTIVE.

[0119] A possible example for UE capabilities and RRC parameter definitions is as follows:

[0120]

[0121] Table 8

[0122]

[0123] Table 9

[0124] Figure 1 An example flow chart for facilitating communication between a network device and a network is shown. Operation 102 includes receiving, by the network device, configuration information from a network node. Operation 104 operates, by the network device, the network by selectively activating transmission operations according to the configuration information or state of the network device.

[0125] In some embodiments, when the network device has reduced capabilities and 1) the configuration information does not include the first parameter or 2) the configuration information includes a second parameter that is set to be disabled, the transmission operation is suppressed in the network. In some embodiments, the first parameter indicates whether the intra-frequency reselection operation is supported in the network. In some embodiments, Figure 1 The method described in further includes determining that only half-duplex FDD operation is supported, the configuration information includes the first parameter and does not include the third parameter. In some embodiments, Figure 1 The method described in further includes: when the configuration information includes the first parameter and does not include the third parameter, determining to equip an antenna. In some embodiments, Figure 1 The method described in further includes: when the configuration information includes the first parameter and does not include the third parameter, determining to equip two antennas. In some embodiments, Figure 1 The method described in also includes: when the configuration information does not include the first parameter or according to the pre-configured standard and the first parameter, determining to perform an intra-frequency reselection operation.

[0126] Figure 2 An example flow chart of another communication scenario between a terminal device and a network node is shown. Operation 602 includes receiving, by the terminal device, configuration information including a first parameter set and a second parameter set from the network node. Operation 604 includes operating the terminal device by selecting a parameter set from the first parameter set or the second parameter set based on 1) capabilities of the terminal device or 2) preconfigured rules.

[0127] In some embodiments, the first parameter set includes a plurality of parameters, wherein each parameter of the plurality of parameters has a corresponding parameter in a second parameter set. In some embodiments, the first parameter set is adopted when the terminal device is a reduced capability (RedCap) UE; wherein the second parameter set is adopted when the terminal device is an enhanced reduced capability (eRedCap) UE. In some embodiments, the selected parameter set includes a parameter indicating reselection between frequencies or within frequencies. In some embodiments, the selected parameter set includes a parameter indicating whether the network is prohibited for the terminal device to perform a reselection operation. In some embodiments, the selected parameter set includes a parameter indicating whether a specific frame structure is allowed in the current network.

[0128] Figure 3 An example flow diagram for sending a message from a first network node to a second network node is shown. Operation 502 comprises sending, by the first network node, a message to the second network node, wherein the message comprises information indicating a capacity status of a workload of the first network node.

[0129] In some embodiments, the operation includes stopping sending a type of data when a capability state indicating a capability of the first network node falls below a threshold. In some embodiments, the operation includes sending a type of data when a capability state indicating a capability of the first network node is above a threshold. Figure 3 The example also includes sending, by the first network node, a confirmation message to the second network node upon receiving the message.

[0130] Figure 4 An example flow chart for receiving a message by a network node and reacting based on an indication of the message is shown. Operation 602 includes receiving, by a first network node, a message including information related to a capability status of a second network node. Operation 604 includes performing, by the first network node, an operation based on the capability status.

[0131] In some embodiments, the operation includes stopping sending a type of data when a capability state indicating a capability of the first network node falls below a threshold. In some embodiments, the operation includes sending a type of data when a capability state indicating a capability of the first network node is above a threshold. Figure 4 The example also includes sending, by the first network node, a confirmation message to the second network node upon receiving the message.

[0132] Figure 5 An example flow diagram for sending configuration between a first network node and a second network node is shown. Operation 502 comprises sending, by a network node to a terminal node, configuration information regarding an extended discontinuous reception (eDRX) cycle for RAN paging, wherein the configuration information indicates applicability of a cycle length greater than a threshold.

[0133] In some embodiments, the threshold is 10.24 seconds. In some embodiments, the configuration information is an RRC parameter. In some embodiments, performing the communication operation includes: when the parameter is not included in the configuration information, determining to stop using the long eDRX mode. In some embodiments, performing the communication operation includes: when the parameter is included in the configuration information, determining to allow the long eDRX mode in the network.

[0134] Figure 6 An example flow chart for receiving a message by a network node and reacting based on an indication of the message is shown. Operation 602 includes receiving, by a first network node, a first request message including a key identifier and a user identifier, wherein the user identifier is associated with a communication device. Operation 604 includes determining, by the first network node, in response to the receiving, based on a decision rule, to selectively send one of: (a) a response message to a second network node, or (b) a second request message to a third network node.

[0135] In some embodiments, the threshold is 10.24 seconds. In some embodiments, the configuration information is an RRC parameter. In some embodiments, performing the communication operation includes: when the parameter is not included in the configuration information, determining to stop using the long eDRX mode. In some embodiments, performing the communication operation includes: when the parameter is included in the configuration information, determining to allow the long eDRX mode in the network.

[0136] Figure 7 An exemplary block diagram of a hardware platform 700 that may be part of a network device (e.g., a base station) or a communication device (e.g., a user equipment (UE)) is shown. The hardware platform 700 includes at least one processor 710 and a memory 705 having instructions stored thereon. The instructions, when executed by the processor 710, configure the hardware platform 700 to perform Figures 1 to 6 The operations described in the various embodiments described in the present patent document. Transmitter 715 transmits or sends information or data to another device. For example, a network device transmitter can send a message to a user device. Receiver 720 receives information or data transmitted or sent by another device. For example, a user device can receive a message from a network device.

[0137] The implementation described above will be applied to wireless communications. Figure 8 An example of a wireless communication system (e.g., a 5G or NR cellular network) including a base station 820 and one or more user equipments (UEs) 811, 812, and 813 is shown. In some embodiments, the UE uses a communication link to the network (sometimes referred to as an uplink direction, as shown by dashed arrows 831, 832, 833) to access the BS (e.g., the network), which then enables subsequent communication from the BS to the UE (e.g., shown in the direction from the network to the UE, sometimes referred to as a downlink direction, as shown by arrows 841, 842, 843). In some embodiments, the BS sends information to the UE (sometimes referred to as a downlink direction, as shown by arrows 841, 842, 843), and then the UE enables subsequent communication from the UE to the BS (e.g., shown in the direction from the UE to the BS, sometimes referred to as an uplink direction, as shown by dashed arrows 831, 832, 833). The UE can be, for example, a smart phone, a tablet, a mobile computer, a machine-to-machine (M2M) device, an Internet of Things (IoT) device, etc.

[0138] It should be understood that this document discloses multiple communication mechanism designs for RedCap UE in Rel-18. The RedCap device, also known as NF-light, is a new device platform that utilizes an optimized design for middle-level use cases to bridge the gap in capabilities and complexity between the extremes in 5G. Compared with other devices, due to the optimization of the design, the RedCap device can effectively support transmission in both the downlink and uplink, respectively. Due to the advantages of the RedCap device and certain limitations of such devices, how RedCap is adapted to the 5G system becomes a problem. Rel-17 has certain designs to limit the activities of RedCap UEs in certain networks. Such a design does not exist in Rel-18. It should be understood that this document provides multiple mechanisms involving Rel-18 RedCap UEs to 1) incorporate the Rel-17 prohibited cell design into Rel-18, and 2) effectively control the flow between the base station and the core network, and 3) allow the RedCap UE to act based on the received configuration information.

[0139] The disclosed and other embodiments, modules and functional operations described herein may be implemented in digital electronic circuit systems, or in computer software, firmware or hardware, including the structures disclosed herein and their structural equivalents, or a combination of one or more of them. The disclosed and other embodiments may be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a computer-readable medium for execution by a data processing device or for controlling the operation of the data processing device. The computer-readable medium may be a machine-readable storage device, a machine-readable storage substrate, a memory device, a material composition that implements a machine-readable propagation signal, or a combination of one or more of them. The term "data processing device" includes all devices, equipment and machines for processing data, including, for example, a programmable processor, a computer, or multiple processors or computers. In addition to hardware, the device may also include code that creates an execution environment for the computer program in question, for example, code that constitutes a processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them. A propagation signal is an artificially generated signal, such as a machine-generated electrical, optical or electromagnetic signal, which is generated to encode information for transmission to a suitable receiver device.

[0140] A computer program (also referred to as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program may be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple collaborative files (e.g., files storing one or more modules, subroutines, or code portions). A computer program may be deployed to execute on one or more computers that are located at one site, or distributed across multiple sites and interconnected by a communication network.

[0141] The processes and logic flows described herein may be performed by one or more programmable processors running one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows may also be performed by, and apparatus may be implemented as, special purpose logic circuitry, such as an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit).

[0142] For example, processors suitable for computer program execution include both general-purpose microprocessors and special-purpose microprocessors and any one or more processors of any type of digital computer. Typically, the processor will receive instructions and data from a read-only memory or a random access memory or both. The basic elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Typically, the computer will also include or be operably coupled to one or more large-capacity storage devices (e.g., magnetic disks, magneto-optical disks, or optical disks) for storing data to receive data from it or to transfer data to it or both. However, the computer may not need to have such a device. Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media, and memory devices, including, for example: semiconductor memory devices, such as EPROM, EEPROM, and flash memory devices; magnetic disks, such as internal hard disks or removable disks; magneto-optical disks; and CD ROM and DVD-ROM disks. The processor and memory may be supplemented by or incorporated into a dedicated logic circuit system.

[0143] Although many details are included herein, these should not be interpreted as limitations on the scope of the claimed invention or the scope that may be claimed, but rather as descriptions of specific features of specific embodiments. Certain features described herein in the context of a separate embodiment may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments. In addition, although features may be described above as working in certain combinations and even initially claimed as such, one or more features from the claimed combination may be deleted from the combination in some cases, and the claimed combination may be for a sub-combination or a variant of a sub-combination. Similarly, although operations are depicted in a particular order in the accompanying drawings, this should not be understood as requiring that these operations be performed in the particular order shown or in sequence, or that all of the operations shown be performed to achieve the desired result.

[0144] Only a few examples and implementations are disclosed. Variations, modifications, and enhancements may be made to the described examples and implementations and other implementations based on what is disclosed.

Claims

1. A wireless communication method, comprising: Receiving, by the network device, configuration information from the network node; as well as A network is operated by the network device by selectively activating a transmission operation according to the configuration information or a state of the network device.

2. The method of claim 1, wherein the transmission operation is avoided in the network when the network device has reduced capabilities and 1) the configuration information does not include a first parameter or 2) the configuration information includes a second parameter that is set to be disabled.

3. The method of claim 2, wherein the first parameter indicates whether intra-frequency reselection operation is supported in the network.

4. The method according to claim 2, further comprising: When the configuration information includes the first parameter and does not include the third parameter, it is determined that only half-duplex FDD operation is supported.

5. The method according to claim 2, further comprising: When the configuration information includes the first parameter but does not include the third parameter, it is determined that one antenna is equipped.

6. The method according to claim 2, further comprising: When the configuration information includes the first parameter but does not include the third parameter, it is determined that two antennas are equipped.

7. The method according to claim 1, further comprising: When the configuration information does not include the first parameter or according to a preconfigured standard and the first parameter, determining to perform an intra-frequency reselection operation.

8. A communication method, comprising: Receiving, by the terminal device from the network node, configuration information including a first parameter set and a second parameter set; as well as The terminal device is operated by selecting a parameter set from the first parameter set or the second parameter set based on 1) capabilities of the terminal device or 2) preconfigured rules.

9. The method of claim 8, wherein the first parameter set includes a plurality of parameters, wherein each parameter of the plurality of parameters has a corresponding parameter in the second parameter set.

10. The method of claim 8, wherein the first parameter set is adopted when the terminal device is a reduced capability (RedCap) UE; wherein the second parameter set is adopted when the terminal device is an enhanced reduced capability (eRedCap) UE.

11. The method of claim 8, wherein the selected parameter set includes a parameter indicating inter-frequency or intra-frequency reselection.

12. The method of claim 8, wherein the selected parameter set includes a parameter indicating whether the network is prohibited for the terminal device to perform a reselection operation.

13. The method according to claim 8, wherein the selected parameter set includes a parameter indicating whether a certain frame structure is allowed in the current network.

14. A communication method, comprising: A message is sent by a first network node to a second network node, wherein the message includes information indicating a capacity status of a workload of the first network node.

15. A wireless communication method, comprising: receiving, by the second network node, a message sent from the first network node, the message including information related to a capability status of the first network node; as well as An operation is performed by the second network node based on the capability status.

16. The method of claim 15, wherein the operations include: When the capability status indicating the capability of the first network node drops below a threshold, sending of a type of data is stopped.

17. The method of claim 15, wherein the operations include: When the capability status indicative of a capability of the first network node is above a threshold, a type of data is sent.

18. The method according to claim 14 or 15, further comprising: When receiving the message, the first network node sends a confirmation message to the second network node.

19. A wireless communication method, comprising: receiving, by a terminal device, configuration information regarding an extended discontinuous reception (eDRX) cycle for a core network, wherein the configuration information indicates applicability of a cycle length greater than a threshold; as well as The terminal device performs a communication operation based on the configuration information.

20. A wireless communication method, comprising: Configuration information about an extended discontinuous reception (eDRX) cycle for RAN paging is sent by a network node to a terminal node, wherein the configuration information indicates applicability of a cycle length greater than a threshold.

21. The method of claim 19 or 20, wherein the threshold is 10.24 seconds.

22. The method according to claim 19 or 20, wherein the configuration information is an RRC parameter.

23. The method of claim 19, wherein performing a communication operation comprises: When the parameter is not included in the configuration information, it is determined to stop using the long eDRX mode.

24. The method of claim 19, wherein performing a communication operation comprises: When the parameter is included in the configuration information, it is determined that the long eDRX mode is allowed in the network.

25. An apparatus for communication, comprising: A processor configured to implement the method according to any one of claims 1 to 24.

26. A computer-readable storage medium having codes stored thereon, which, when executed by a processor, cause the processor to implement the method according to any one of claims 1 to 24.

Images