Resource configuration method for transmission in inactive state

Abstract

Some aspects of the present disclosure introduce a new downlink (down link, DL) partial bandwidth (bandwidth part, BWP) and a new uplink (up link, UL) BWP for communication in the RRCINACTIVE state. In addition, aspects of the present application also provide general parameters for configuring the BWP, including, but not limited to, frequency location, bandwidth, sub-carrier spacing (SCS), and cyclic prefix (CP). Some aspects of the present application may support re-interpretation of generic parameters of the BWP to be used in the RRCINACTIVE state, such as generic parameters that may be configured for the RRCCONNECTED state. Some aspects of the present disclosure relate to implicit DL BWP handover in an RRCINACTIVE state in which a BWP identification (identity, ID) indication is not required as part of a handover mechanism.

Description

[0001] This application is a divisional of a Chinese patent application that entered the Chinese national stage on April 22, 2022, with an application date of October 23, 2020, Chinese patent application number 202080074347.4, and invention name “Resource configuration method for transmission in non-activated state”.

[0002] This application claims priority to U.S. patent application No. 16 / 664,340, filed on October 25, 2019, entitled “METHODS FOR RESOURCE CONFIGURATION FOR TRANSMISSION IN INACTIVE STATE,” the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present application relates generally to wireless communications and, in particular embodiments, to control signaling in wireless communication networks. Background Art

[0004] In some wireless communication networks, user equipment (UE) communicates wirelessly with a base station to send data to the base station and / or receive data from the base station. Wireless communication from a UE to a base station is called uplink (UL) communication. Wireless communication from a base station to a UE is called downlink (DL) communication. Wireless communication from a first UE to a second UE is called sidelink (SL) communication or device-to-device (D2D) communication.

[0005] In 3GPP New Radio (NR), a UE can operate in one of three states: RRC_IDLE, RRC_CONNECTED, and RRC_INACTIVE. In the RRC_CONNECTED state, the UE is connected to the network after the connection establishment process. In the RRC_IDLE state, the UE is not connected to the network, but the network knows that the UE exists in the network. When the UE is not communicating with the network, switching to the RRC_IDLE state helps save network resources and UE power (e.g., battery life). When the UE is not communicating with the network, the RRC_INACTIVE state also helps save network resources and UE power. However, unlike the RRC_IDLE state, when the UE is in the RRC_INACTIVE state, both the network and the UE store at least some configuration information to allow the UE to reconnect to the network faster.

[0006] Improved mechanisms for operating in the RRC_INACTIVE state would be beneficial to a communication system. Summary of the invention

[0007] According to a first aspect of the present application, a method is provided, the method comprising: in a radio resource control (RRC)_CONNECTED state, a user equipment (UE) determines configuration information for configuring a bandwidth part (BWP) for communication in an RRC_INACTIVE state. The method also comprises: the UE enters the RRC_INACTIVE state; the UE uses the configured BWP for communication in the RRC_INACTIVE state.

[0008] In some embodiments, determining configuration information for configuring the BWP to communicate in the RRC_INACTIVE state comprises receiving the configuration information.

[0009] In some embodiments, the configuration information explicitly defines BWP parameters of the configured BWP for communicating in the RRC_INACTIVE state.

[0010] In some embodiments, the configuration information indicates a BWP identity, the BWP identity identifying a previously configured BWP to be used for communicating in the RRC_INACTIVE state.

[0011] In some embodiments, the configuration information indicates that the configured BWP is the last active BWP of the UE in the RRC_CONNECTED state before the UE enters the RRC_INACTIVE state.

[0012] In some embodiments, the method further comprises: in the RRC_INACTIVE state, receiving downlink control information including scheduling information.

[0013] In some embodiments, the scheduling information includes: scheduling information for receiving downlink data in the RRC_INACTIVE state; or scheduling information for receiving paging information, including scheduling information for receiving downlink data in the RRC_INACTIVE state.

[0014] In some embodiments, the configured BWP for communicating in the RRC_INACTIVE state includes: the UE sending uplink data in the configured BWP for communicating in the RRC_INACTIVE state.

[0015] In some embodiments, the configuration information for configuring the BWP for communication in the RRC_INACTIVE state includes an extended cyclic prefix (CP).

[0016] In some embodiments, the extended CP is used for uplink BWP.

[0017] In some embodiments, the method further comprises: in the RRC_INACTIVE state, switching to the configured BWP for communicating in the RRC_INACTIVE state.

[0018] In some embodiments, the switching occurs when a predefined condition is met.

[0019] In some embodiments, the predefined condition is one of the following conditions: the configured BWP used for communicating in the RRC_INACTIVE state has a different frequency position and bandwidth or a different sub-carrier spacing (SCS) or a different cyclic prefix (CP) from control resource set 0 (CORESET 0); or the configured BWP used for communicating in the RRC_INACTIVE state does not include all resource blocks of CORESET 0, or has a different SCS or a different CP from CORESET 0.

[0020] In some embodiments, the method further comprises: in the RRC_INACTIVE state, switching from the configured BWP for communicating in the RRC_INACTIVE state to a control resource set 0 (CORESET 0).

[0021] According to a second aspect of the present application, a user equipment (UE) is provided, the user equipment comprising a processor and a computer-readable storage medium, the computer-readable storage medium storing computer-executable instructions. When the computer-executable instructions are executed by the processor, the UE performs the following operations: in a radio resource control (RRC)_CONNECTED state, determining configuration information for configuring a bandwidth part (BWP) for communication in an RRC_INACTIVE state; entering the RRC_INACTIVE state; using the configured BWP for communication in the RRC_INACTIVE state.

[0022] In some embodiments, the computer-executable instructions for determining configuration information for configuring the BWP to communicate in the RRC_INACTIVE state include computer-executable instructions for receiving the configuration information.

[0023] In some embodiments, the configuration information explicitly defines BWP parameters of the configured BWP for communicating in the RRC_INACTIVE state.

[0024] In some embodiments, the configuration information indicates a BWP identity, the BWP identity identifying a previously configured BWP to be used for communicating in the RRC_INACTIVE state.

[0025] In some embodiments, the configuration information indicates that the configured BWP for communicating in the RRC_INACTIVE state is the last active BWP of the UE in the RRC_CONNECTED state before the UE enters the RRC_INACTIVE state.

[0026] In some embodiments, in the RRC_INACTIVE state, when the computer-readable instructions are executed by the processor, the UE receives downlink control information including scheduling information.

[0027] In some embodiments, the scheduling information includes: scheduling information for receiving downlink data in the RRC_INACTIVE state; or scheduling information for receiving paging information, including scheduling information for receiving downlink data in the RRC_INACTIVE state.

[0028] In some embodiments, the computer-executable instructions for using the configured BWP for communicating in the RRC_INACTIVE state include computer-executable instructions for sending uplink data in the configured BWP for communicating in the RRC_INACTIVE state.

[0029] In some embodiments, the configuration information for configuring the BWP for communication in the RRC_INACTIVE state includes an extended cyclic prefix (CP), wherein the extended CP is used for an uplink BWP.

[0030] In some embodiments, in the RRC_INACTIVE state, the computer readable instructions, when executed by the processor, cause the UE to switch to the configured BWP for communicating in the RRC_INACTIVE state.

[0031] In some embodiments, the switching occurs when a predefined condition is met, wherein the predefined condition is one of the following conditions: the configured BWP used for communication in the RRC_INACTIVE state has a different frequency position and bandwidth or a different sub-carrier spacing (SCS) or a different cyclic prefix (CP) from control resource set 0 (CORESET 0); or the configured BWP used for communication in the RRC_INACTIVE state does not include all resource blocks of CORESET 0, or has a different SCS or a different CP from CORESET 0.

[0032] In some embodiments, in the RRC_INACTIVE state, when the computer readable instructions are executed by the processor, the UE is caused to switch from the configured BWP for communication in the RRC_INACTIVE state to a control resource set 0 (CORESET 0).

[0033] According to a third aspect of the present application, a method is provided, the method comprising: a network side device determines configuration information for configuring a bandwidth part (BWP) for communication in an RRC_INACTIVE state. The method further comprises: the network side device sends a signaling indicating suspension of a radio resource control (RRC)_CONNECTED state, so that a user equipment (UE) enters the RRC_INACTIVE state. The method further comprises: when the UE is in the RRC_INACTIVE state, the network side device communicates with the UE using the BWP configured for the RRC_INACTIVE state.

[0034] In some embodiments, the method further includes: the network side device sending the configuration information for configuring the RRC_INACTIVE state BWP for the UE to use for communicating in the RRC_INACTIVE state.

[0035] In some embodiments, the configuration information explicitly defines BWP parameters of the configured BWP for communicating in the RRC_INACTIVE state.

[0036] In some embodiments, the configuration information indicates a BWP identity, the BWP identity identifying a previously configured BWP to be used for communicating in the RRC_INACTIVE state.

[0037] In some embodiments, the configuration information indicates that the configured BWP is the last active BWP of the UE in the RRC_CONNECTED state before the UE enters the RRC_INACTIVE state.

[0038] In some embodiments, the method further includes: when the UE is in the RRC_INACTIVE state, sending downlink control information including scheduling information.

[0039] In some embodiments, the scheduling information includes: scheduling information for receiving downlink data in the RRC_INACTIVE state; or scheduling information for receiving paging information, including scheduling information for receiving downlink data in the RRC_INACTIVE state.

[0040] In some embodiments, using the configured BWP for communication in the RRC_INACTIVE state includes: receiving, by the network side device, uplink data in the configured BWP for communication in the RRC_INACTIVE state.

[0041] In some embodiments, the configuration information for configuring the BWP for communication in the RRC_INACTIVE state includes an extended cyclic prefix (CP).

[0042] In some embodiments, the extended cyclic prefix (CP) is used for an uplink BWP.

[0043] In some embodiments, the method further includes: when the UE is in the RRC_INACTIVE state, the network side device uses control resource set 0 (CORESET 0) to communicate in the RRC_INACTIVE state.

[0044] According to a fourth aspect of the present application, a network device is provided, the network device comprising a processor and a computer-readable storage medium, the computer-readable storage medium storing computer-executable instructions. When the computer-executable instructions are executed by the processor, the network device: determines configuration information for configuring a bandwidth part (BWP) for communication in an RRC_INACTIVE state; sends a signal indicating suspension of a radio resource control (RRC)_CONNECTED state, so that a user equipment (UE) enters the RRC_INACTIVE state; and when the UE is in the RRC_INACTIVE state, uses the BWP configured for the RRC_INACTIVE state to communicate with the UE.

[0045] In some embodiments, when the computer executable instructions are executed by the processor, the network side device sends the configuration information for configuring the RRC_INACTIVE state BWP for the UE to communicate in the RRC_INACTIVE state.

[0046] In some embodiments, the configuration information explicitly defines BWP parameters of the configured BWP for communicating in the RRC_INACTIVE state.

[0047] In some embodiments, the configuration information indicates a BWP identity, the BWP identity identifying a previously configured BWP to be used for communicating in the RRC_INACTIVE state.

[0048] In some embodiments, the configuration information indicates that the configured BWP for communicating in the RRC_INACTIVE state is the last active BWP of the UE in the RRC_CONNECTED state before the UE enters the RRC_INACTIVE state.

[0049] In some embodiments, in the RRC_INACTIVE state, when the computer-readable instructions are executed by the processor, the network side device sends downlink control information including scheduling information.

[0050] In some embodiments, the scheduling information includes: scheduling information for the UE to receive downlink data in the RRC_INACTIVE state; or scheduling information for the UE to receive paging information, including scheduling information for receiving downlink data in the RRC_INACTIVE state.

[0051] In some embodiments, the computer executable instructions that, when executed by the processor, cause the network side device to use the configured BWP for communicating in the RRC_INACTIVE state include computer executable instructions for receiving uplink data in the configured BWP for communicating in the RRC_INACTIVE state.

[0052] In some embodiments, the configuration information for configuring the BWP for communication in the RRC_INACTIVE state includes an extended cyclic prefix (CP), wherein the extended CP is used for an uplink BWP.

[0053] In some embodiments, in the RRC_INACTIVE state, when the computer readable instructions are executed by the processor, the network side device uses control resource set 0 (CORESET 0) to communicate in the RRC_INACTIVE state. BRIEF DESCRIPTION OF THE DRAWINGS

[0054] In order to more fully understand the embodiments of the present application and their advantages, the following description is made by way of example with reference to the accompanying drawings, wherein:

[0055] Figure 1 is a schematic diagram of a communication system that can implement various embodiments of the present application;

[0056] Figure 2A and Figure 2B are block diagrams of exemplary user equipment and base stations provided in various aspects of the present application;

[0057] Figure 3 It is a block diagram of an air interface manager for configuring a software configurable air interface provided in one aspect of the present application;

[0058] FIG. 4A to FIG. 4D Four different examples of INACTIVE DL BWP configured after transitioning from RRC_CONNECTED state to RRC_INACTIVE state provided by various aspects of the present application are shown;

[0059] FIG. 5A to FIG. 5C Four different examples of INACTIVE DL BWP configured after transitioning from RRC_CONNECTED state to RRC_INACTIVE state provided by various aspects of the present application are shown;

[0060] Fig. 6A An example is shown when the DL BWP switching condition is met in the RRC_INACTIVE state provided by various aspects of the present application;

[0061] Figure 6B An example is shown when the DL BWP switching condition is not met in the RRC_INACTIVE state provided by various aspects of the present application;

[0062] Figure 7 is a signaling flow chart provided by various aspects of the present application, which shows the signaling for DCI-based DL data scheduling occurring between the UE and the base station when the UE is initially in the RRC_CONNECTED state and when the UE is released and enters the RRC_INACTIVE state;

[0063] Figure 8 is a signaling flow chart provided by various aspects of the present application, which shows the signaling for paging-based DL data scheduling occurring between the UE and the base station when the UE is initially in the RRC_CONNECTED state and when the UE is released and enters the RRC_INACTIVE state;

[0064] Fig. 9 is a signaling flow chart provided in other aspects of the present application, which shows signaling for UL data transmission in an INACTIVE UL BWP occurring between a UE and a base station when the UE is initially in an RRC_CONNECTED state and when the UE is released and enters an RRC_INACTIVE state;

[0065] Fig.10 and Fig.11 is a flow chart showing the method provided by various aspects of the present application. DETAILED DESCRIPTION

[0066] For illustrative purposes, specific exemplary embodiments are explained in more detail below with reference to the accompanying drawings.

[0067] The embodiments presented herein provide information sufficient to implement the claimed subject matter and illustrate methods of implementing such subject matter. After reading the following description in light of the accompanying drawings, those skilled in the art will understand the concepts of the claimed subject matter and will recognize that the application of these concepts is not specifically mentioned herein. It should be understood that these concepts and applications are within the scope of the present application and the appended claims.

[0068] In addition, it should be understood that any module, component, or device for executing instructions disclosed herein may include or otherwise access one or more non-transitory computer / processor readable storage media for storing information, such as computer / processor readable instructions, data structures, program modules, and / or other data. A non-exhaustive list of examples of non-transitory computer / processor readable storage media includes magnetic cassettes, magnetic tapes, disk storage or other magnetic storage devices, compact disc read-only memory (CD-ROM), digital video discs or digital versatile discs (i.e., DVDs), Blu-ray discs, and other optical disks. TM Optical disks, or other optical storage, volatile and non-volatile, removable and non-removable media implemented in any method or technology, random-access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other storage technology. Any of these non-transitory computer / processor storage media can be part of a device or can be accessed or connected by a device. Computer / processor readable / executable instructions for implementing the applications or modules described herein can be stored or otherwise saved by such non-transitory computer / processor readable storage media.

[0069] Figure 1 , Figure 2A , Figure 2B and Figure 3 Examples of networks and devices are shown in which any or all aspects of the present application may be implemented.

[0070] Figure 1 An exemplary communication system 100 is shown. In general, the system 100 enables multiple wireless elements or multiple wired elements to transmit data and other content. The purpose of the system 100 can be to provide content (voice, data, video, text) via broadcast, narrowcast, user device to user device, etc. The system 100 can operate efficiently by sharing resources such as bandwidth.

[0071] In this example, the communication system 100 includes electronic devices (EDs) 110a to 110c, radio access networks (RANs) 120a to 120b, a core network 130, a public switched telephone network (PSTN) 140, the Internet 150, and other networks 160. Figure 1 A certain number of such components or elements are shown in FIG. 1 , but any reasonable number of such components or elements may be included in system 100 .

[0072] EDs 110a to 110c are used to operate and / or communicate in the system 100. For example, EDs 110a to 110c are used to transmit and / or receive via a wireless communication channel. EDs 110a to 110c represent any end-user device suitable for wireless operation, and may include (or may be referred to as): user equipment (UE / user device), wireless transmit / receive unit (WTRU), mobile station, mobile user unit, cellular phone, station (STA), machine type communication (MTC) device, personal digital assistant (PDA), smart phone, laptop, computer, touch pad, wireless sensor or consumer electronic device.

[0073] exist Figure 1 In the embodiment, RAN 120a and 120b include base stations 170a and 170b, respectively. Base stations 170a and 170b are used to wirelessly connect to one or more of EDs 110a to 110c so as to access any other base stations 170a and 170b, core network 130, PSTN 140, Internet 150 and / or other networks 160. For example, base stations 170a and 170b may include (or may be) one or more of several common devices, such as base transceiver station (BTS), Node-B (NodeB), evolved NodeB (eNodeB), Home eNodeB, gNodeB, transmission and receive point (TRP), site controller, access point (AP) or wireless router. Any ED 110a to 110c may alternatively or additionally be configured to connect, access or communicate with any other base stations 170a and 170b, the Internet 150, the core network 130, the PSTN 140, other networks 160, or any combination thereof. The communication system 100 may include a RAN, such as RAN 120b, wherein the corresponding base station 170b accesses the core network 130 via the Internet 150, as shown.

[0074] EDs 110a to 110c and base stations 170a and 170b are examples of communication devices that may be used to implement some or all of the functions and / or embodiments described herein. Figure 1 In the illustrated embodiment, base station 170a is part of RAN 120a, which may include other base stations, base station controllers (BSC), radio network controllers (RNC), relay nodes, elements and / or devices. Any base station 170a, 170b may be a separate element, as shown, or multiple elements distributed in the corresponding RAN, and so on. Similarly, base station 170b is part of RAN 120b, which may include other base stations, elements and / or devices. Base stations 170a and 170b transmit and / or receive wireless signals in a specific geographic range or area, which is sometimes also referred to as a "cell" or "coverage area". The cell can be further divided into cell sectors, and base stations 170a and 170b can, for example, use multiple transceivers to provide services to multiple sectors. In some embodiments, there may be established micro cells or femto cells supported by wireless access technology. In some embodiments, multiple transceivers may be used for each cell using multiple-input multiple-output (MIMO) technology, etc. The number of RANs 120a and 120b shown is only exemplary. Any number of RANs may be considered when designing the communication system 100.

[0075] The base stations 170a and 170b communicate with one or more of the EDs 110a to 110c through one or more air interfaces 190 using wireless communication links such as radio frequency (RF), microwave, infrared (IR), etc. The air interface 190 may use any suitable wireless access technology. For example, the communication system 100 may implement one or more orthogonal or non-orthogonal channel access methods in the air interface 190, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA) or single-carrier FDMA (SC-FDMA).

[0076] The base stations 170a and 170b may implement Universal Mobile Telecommunication System (UMTS) terrestrial radio access (UTRA) to establish an air interface 190 using wideband CDMA (WCDMA). In this case, the base stations 170a and 170b may implement protocols such as High Speed ​​Packet Access (HSPA), Evolved HPSA (HSPA+), etc., wherein HSPA+ may optionally include High Speed ​​Downlink Packet Access (HSDPA) and / or High Speed ​​Uplink Packet Access (HSUPA). Alternatively, the base stations 170a and 170b may establish an air interface 190 using LTE, LTE-A, LTE-B and / or 5G New Radio (NR) through Evolved UTMS Terrestrial Radio Access (E-UTRA). It is expected that the communication system 100 can use multi-channel access functions, including the schemes described above. Other wireless technologies used to implement the air interface include IEEE 802.11, 802.15, 802.16, CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, IS-2000, IS-95, IS-856, global system for mobile communications (global system for mobile communications, GSM), Enhanced Data rates for GSM evolution (Enhanced Data rates for GSMEvolution, EDGE) and GSM / EDGE radio access network (GSM / EDGEradio access network, GERAN). Of course, other multiple access schemes and wireless protocols can be used.

[0077] The RANs 120a and 120b communicate with the core network 130 to provide various services, such as voice, data, and other services to the EDs 110a to 110c. The RANs 120a and 120b and / or the core network 130 may communicate directly or indirectly with one or more other RANs (not shown), which may or may not be directly served by the core network 130 and may or may not employ the same radio access technology as the RANs 120a and / or RANs 120b. The core network 130 may also serve as a gateway access between (i) the RANs 120a and 120b and / or the EDs 110a to 110c and (ii) other networks (e.g., the PSTN 140, the Internet 150, and other networks 160).

[0078] EDs 110a to 110c communicate with each other through one or more sidelink (SL) air interfaces 180 using wireless communication links such as radio frequency (RF), microwave, infrared (IR), etc. The SL air interface 180 may use any suitable wireless access technology. The SL air interface 180 may be substantially similar to the air interface 190 in which EDs 110a to 110c communicate with one or more of base stations 170a to 170c, or may be substantially different from the air interface 190. For example, the communication system 100 may implement one or more channel access methods in the SL air interface 180, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or single-carrier FDMA (SC-FDMA). In some embodiments, the SL air interface 180 may be implemented at least partially on an unlicensed spectrum.

[0079] In the present application, SL transmission between cooperative UEs can be "grant-free" transmission or as a data transmission mode performed without transmitting dynamic scheduling. Grant-free transmission is sometimes referred to as "configured grant", "no grant", "scheduling-free" or "no scheduling" transmission. For example, grant-free SL transmission can also be referred to as SL "grant-free transmission", "transmission without dynamic grant", "transmission without dynamic scheduling" or "transmission using configured grant".

[0080] Configured grant transmissions usually require the receiver to know the parameters and resources used by the transmitter for transmission. However, in the case of SL transmissions, the receiving UE usually does not know the configuration parameters of the transmitting UE, such as which UE is transmitting, the final destination of the data (e.g., another UE), the time domain and frequency domain communication resources used for transmission, and other control information. However, each method will bring corresponding overhead losses.

[0081] In addition, some or all of the EDs 110a to 110c may include functionality to communicate with different wireless networks over different wireless links using different wireless technologies and / or protocols. The EDs may communicate with a service provider or switch (not shown) and the Internet 150 over a wired communication channel, rather than (or in addition to) wireless communications. The PSTN 140 may include a circuit-switched telephone network for providing plain old telephone service (POTS). The Internet 150 may include computer networks and / or subnets (intranets), and include protocols such as the Internet Protocol (IP), the Transmission Control Protocol (TCP), and the User Datagram Protocol (UDP). The EDs 110a to 110c may be multi-mode devices capable of operating according to a variety of wireless access technologies, and include a plurality of transceivers required to support a variety of wireless access technologies.

[0082] Figure 2A and Figure 2B An exemplary device that can implement the methods and teachings provided by this application is shown. Specifically, Figure 2A An exemplary ED 110 is shown, Figure 2B An exemplary base station 170 is shown. These components may be used in system 100 or any other suitable system.

[0083] like Figure 2A As shown, ED 110 includes at least one processor or processing unit 200. Processing unit 200 implements various processing operations of ED 110. For example, processing unit 200 can perform signal encoding, bit scrambling, data processing, power control, input / output processing, or any other function that enables ED 110 to operate in communication system 100. Processing unit 200 can also be used to implement some or all of the functions and / or embodiments detailed herein. Each processing unit 200 includes any suitable processing or computing device for performing one or more operations. For example, each processing unit 200 can include a microprocessor, a microcontroller, a digital signal processor, a field programmable gate array, or an application specific integrated circuit.

[0084] ED 110 also includes at least one transceiver 202. Transceiver 202 is used to modulate data or other content, wherein the data or other content is used to be transmitted through at least one antenna or network interface controller (NIC) 204. Transceiver 202 is also used to demodulate data or other content received by at least one antenna 204. Each transceiver 202 includes any suitable structure for generating signals for wireless or wired transmission and / or for processing signals received by wireless or wired means. Each antenna 204 includes any suitable structure for sending and / or receiving wireless or wired signals. One or more transceivers 202 can be used in ED 110. One or more antennas 204 can be used in ED 110. Although transceiver 202 is shown as a single functional unit, it can also be implemented using at least one transmitter and at least one separate receiver.

[0085] ED 110 also includes one or more input / output devices 206 or interfaces (e.g., a wired interface to Internet 150). One or more input / output devices 206 can interact with users or other devices in the network. Each input / output device 206 includes any suitable structure for providing information to or receiving information from a user, such as a speaker, microphone, keypad, keyboard, display, or touch screen, including network interface communications.

[0086] In addition, the ED 110 includes at least one memory 208. The memory 208 stores instructions and data used, generated, or collected by the ED 110. For example, the memory 208 may store software instructions or modules for implementing some or all of the functions and / or embodiments described herein and executed by the processing unit 200. Each memory 208 includes any suitable one or more volatile and / or non-volatile storage and retrieval devices. Any suitable type of memory may be used, for example, a random access memory (RAM), a read only memory (ROM), a hard disk, an optical disk, a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card.

[0087] like Figure 2BAs shown, the base station 170 includes at least one processing unit 250, at least one transmitter 252, at least one receiver 254, one or more antennas 256, at least one memory 258, and one or more input / output devices or interfaces 266. Transceivers not shown may be used instead of transmitters 252 and receivers 254. Scheduler 253 may be coupled to the processing unit 250. Scheduler 253 may be included in the base station 170 or may be operated separately from the base station 170. Processing unit 250 implements various processing operations of the base station 170, such as signal encoding, bit scrambling, data processing, power control, input / output processing, or any other function. Processing unit 250 may also be used to implement some or all of the functions and / or embodiments described in more detail herein. Each processing unit 250 includes any suitable processing device or computing device for performing one or more operations. Each processing unit 250 may include a microprocessor, a microcontroller, a digital signal processor, a field programmable gate array, or an application-specific integrated circuit, and the like.

[0088] Each transmitter 252 includes any suitable structure for generating signals for wireless or wired transmission with one or more EDs or other devices. Each receiver 254 includes any suitable structure for processing signals received wirelessly or wired from one or more EDs or other devices. Although shown as separate components, at least one transmitter 252 and at least one receiver 254 can be combined into a transceiver. Each antenna 256 includes any suitable structure for sending and / or receiving wireless signals or wired signals. Although the shared antenna 256 is shown here as coupled to the transmitter 252 and the receiver 254, one or more antennas 256 can be coupled to one or more transmitters 252, and one or more separate antennas 256 can be coupled to one or more receivers 254. Each memory 258 includes any suitable one or more volatile and / or non-volatile storage and retrieval devices, such as those described above in conjunction with ED 110. The memory 258 stores instructions and data used, generated or collected by the base station 170. For example, the memory 258 can store software instructions or modules for implementing some or all of the functions and / or embodiments described herein and executed by the processing unit 250.

[0089] Each input / output device 266 can interact with users or other devices in the network. Each input / output device 266 includes any suitable structure for providing information to a user or receiving / providing information from a user, including network interface communications.

[0090] Other details about UE 110 and base station 170 are known to those skilled in the art. Therefore, for the sake of clarity, these details are omitted here.

[0091] Figure 3 A schematic diagram of an air interface manager 300 for configuring a software configurable air interface 190 is shown. For example, the air interface manager 300 may be a module including a plurality of components or building blocks that define parameters of the air interface 190 and collectively specify the manner in which transmissions are made and / or received over the air interface 190. The air interface manager 300 may also or alternatively define parameters of the SL air interface 180 and collectively specify the manner in which transmissions are made and / or received over the SL air interface 180.

[0092] The components of the air interface manager 300 include at least one of a waveform component 305 , a frame structure component 310 , a multiple access scheme component 315 , a protocol component 320 , and a modulation and coding component 325 .

[0093] The waveform component 305 may specify the shape and form of the signal being transmitted. Waveform options may include orthogonal multiple access waveforms and non-orthogonal multiple access waveforms. Non-limiting examples of these waveform options include Single-Carrier (SC), Ultra Wideband (UWB), Frequency Modulated Continuous Wave (FMCW), Linear Frequency Modulated (LFM) waveform, Orthogonal Frequency Division Multiplexing (OFDM) waveform, Single-Carrier Frequency Division Multiple Access (SC-FDMA) waveform, Filtered OFDM (f-OFDM) waveform, Time Windowed OFDM waveform, Filter Bank Multicarrier (FBMC), Universal Filtered Multicarrier (UFMC), Generalized Frequency Division Multiplexing (GFDM) waveform, Wavelet Packet Modulation (WPM) waveform, Faster Than Nyquist (FTTM) waveform, and the like. Nyquist (FTN) waveform and a low peak to average power ratio waveform (Peak to Average Power Ratio Waveform, PAPR WF). In some embodiments, waveform options can be combined.

[0094] The frame structure component 310 may specify a configuration of a frame or a group of frames. The frame structure component 310 may indicate one or more of time, frequency, pilot signature, coding, or other parameters of a frame or a group of frames.

[0095] Non-limiting examples of frame structure options include the number of symbols in a slot, the number of slots in a frame, and the duration of each slot (sometimes referred to as a transmission time interval (TTI) or transmission time unit (TTU)). The frame structure component may also specify whether the slot is a configurable multi-level TTI, a fixed TTI, or a configurable single-level TTI. The frame structure component may also specify coexistence mechanisms for different frame structure configurations.

[0096] For some waveforms, such as certain OFDM-based waveforms, the frame structure component may also specify one or more associated waveform parameters, such as subcarrier spacing width, symbol duration, cyclic prefix (CP) length, channel bandwidth, guard band / subcarrier, and sampling size and frequency.

[0097] Additionally, the frame structure component 310 may also specify whether the frame structure is used in time division duplex communication or frequency division duplex communication.

[0098] In addition, the frame structure component 310 can also specify a transmission state and / or direction for each symbol in the frame. For example, each symbol can be independently configured as a downlink symbol, an uplink symbol, or a flexible symbol.

[0099] The specifications of the waveform component and the frame structure component are sometimes collectively referred to as “numerology.” Thus, the air interface 190 may include a system parameter component 330 that defines multiple air interface configuration parameters such as subcarrier spacing, CP length, symbol length, slot length, and number of symbols per slot.

[0100] These system parameters are also referred to as subcarrier spacing configurations, and are scalable because the subcarrier spacings of different system parameters are integer multiples of each other, and the time slot lengths of different system parameters are also integer multiples of each other. This scalable design of multiple system parameters provides implementation advantages, such as scalable total OFDM symbol duration in the context of time division duplex (TDD).

[0101] The frame can be configured using one or a combination of multiple scalable system parameters. For example, the system parameter of 60kHz subcarrier spacing has a relatively short OFDM symbol duration (because the OFDM symbol duration is inversely proportional to the subcarrier spacing), which makes the 60kHz system parameter particularly suitable for ultra-low latency communications, such as vehicle-to-any (V2X) communications. Another example of a system parameter with a relatively short OFDM symbol duration suitable for low latency communications is a system parameter of 30kHz subcarrier spacing. System parameters with 15kHz subcarrier spacing can be compatible with LTE. System parameters with 15kHz subcarrier spacing can be used as default system parameters for initial access to the network by a device. Such 15kHz system parameters can also be applied to broadband services. System parameters with 7.5kHz spacing have a relatively long OFDM symbol duration, which may be particularly beneficial for coverage enhancement and broadcasting. Other uses of these system parameters will be or become apparent to those of ordinary skill in the art. Among the four system parameters listed, the system parameters of 30kHz and 60kHz subcarrier spacing are more robust to Doppler spread (fast moving conditions) due to wider subcarrier spacing. It is also contemplated that different system parameters may use different values ​​for other physical layer parameters, such as the same subcarrier spacing and different cyclic prefix lengths. In addition, the subcarrier spacing may depend on the operating frequency band. For example, the subcarrier spacing in millimeter wave frequencies may be larger than the subcarrier spacing in low frequencies.

[0102] It is also contemplated that other subcarrier spacings may be used, such as larger or smaller subcarrier spacings. n Other subcarrier spacings that vary include 120 kHz and 3.75 kHz.

[0103] In other examples, more limited scalability may be achieved where two or more system parameters have subcarrier spacings that are integer multiples of the minimum subcarrier spacing, not necessarily a factor of 2. n Related. Examples include 15kHz, 30kHz, 45kHz, 60kHz subcarrier spacing.

[0104] In other examples, non-scalable subcarrier spacings that are not full integer multiples of the minimum subcarrier spacing, such as 15 kHz, 20 kHz, 30 kHz, 60 kHz, may be used.

[0105] OFDM-based signals can be used to send signals in which multiple system parameters coexist simultaneously. More specifically, multiple sub-band OFDM signals can be generated in parallel, each signal in a different sub-band, each sub-band having a different subcarrier spacing (and usually different system parameters). Multiple sub-band signals are combined into a single signal for transmission, such as downlink transmission. Optionally, multiple sub-band signals can be sent from separate transmitters, such as for uplink transmission of multiple electronic devices (EDs), which can be user equipment (UE).

[0106] The use of different system parameters can enable the air interface 190 to support the coexistence of a set of different use cases with various quality of service (QoS) requirements. These requirements can include different levels of latency or reliability tolerance and different bandwidth or signaling overhead requirements, etc. In one example, the base station can indicate to the ED an index representing the selected system parameter or a single parameter of the selected system parameter (e.g., subcarrier spacing). Based on this indication, the ED can determine the parameters in the selected system parameter based on other information, such as a lookup table of candidate system parameters stored in a memory.

[0107] Continuing with the description of the components in the air interface 190, the multiple access scheme component 315 can specify a way to grant channel access to one or more EDs. Non-limiting examples of multiple access technology options include technologies that define how EDs share common physical channels, such as Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Code Division Multiple Access (CDMA), Space Division Multiple Access (SDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), Low Density Signature Multicarrier Code Division Multiple Access (LDS-MC-CDMA), Non-Orthogonal Multiple Access (NOMA), Pattern Division Multiple Access (PDMA), Lattice Partition Multiple Access (LPMA), Resource Spread Multiple Access (RSMA), and Sparse Code Multiple Access (SCMA). In addition, multiple access technology options may include scheduled access, unscheduled access (also known as unlicensed access or configured grants), contention-based shared channel resources, non-contention-based shared channel resources, and cognitive radio-based access.

[0108] The protocol component 320 can specify the manner in which transmission and / or retransmission is to be performed. Non-limiting examples of transmission and / or retransmission mechanism options include mechanisms for specifying scheduling data pipe sizes and signaling mechanisms for transmission and / or retransmission.

[0109] The modulation and coding component 325 can specify how the information being sent can be encoded / decoded and modulated / demodulated for transmission / reception purposes. Coding can refer to methods of error detection and forward error correction. Non-limiting examples of coding options include Turbo trellis codes, Turbo product codes, fountain codes, low-density parity-check codes, and polar codes. Modulation can simply refer to Quadrature Amplitude Modulation (QAM) specified by a complex constellation (e.g., including modulation techniques and orders, such as 16QAM, 64QAM, etc.), or more specifically various types of advanced modulation methods, such as hierarchical modulation, multidimensional modulation, and low peak-to-average power ratio (PAPR) modulation.

[0110] Since the air interface includes multiple components or building blocks, and each component may have multiple candidate technologies (also referred to herein as air interface capability options), the air interface manager 300 may configure and store a large number of different air interface protocol sets. Each air interface protocol set defines a respective air interface capability option set.

[0111] For example, in each air interface protocol set that defines a respective air interface capability option set, an air interface capability option is selected for each component or building block of the air interface. Different air interface protocol sets can be used to meet different transmission requirement sets, including transmission content, sending conditions, and receiving conditions.

[0112] According to the transmission requirements of a pair of communication sending and receiving devices, an air interface protocol set from different air interface protocol sets that best meets the transmission requirements can be selected from the air interface manager 300, and the air interface protocol set can be used for communication between the pair of communication sending and receiving devices.

[0113] In other embodiments, the air interface manager 300 can modify or update its components, protocol sets, or capability options. For example, the air interface manager 300 can replace the waveform component 305 and the frame structure component 310 with a single system parameter component 330. Conversely, the air interface manager 300 can separate the modulation and coding component 325 into a separate coding component and a separate modulation component. In addition, the air interface manager 300 is configurable so that new soft air interface configuration components developed in the future should be able to be used.

[0114] The air interface manager 300 may also update certain components to modify the capability options of any component. For example, the air interface manager 300 may update the modulation and coding component 325 to include a higher order modulation scheme.

[0115] By updating the stored components, protocol sets, and candidate options, the air interface manager 300 can flexibly and better adapt to different wireless traffic types and services. Modifying or updating the components, protocol sets, and candidate options can enable the air interface manager 300 to provide a suitable air interface protocol set for a business type or service, rather than providing an air interface protocol set that has been envisioned for ultra-reliable low latency communication (URLLC), enhanced mobile broadband (eMBB), and massive machine-type communication (mMTC).

[0116] As mentioned above, in 3GPP New Radio (NR), a UE may operate in one of the following three states: RRC_IDLE, RRC_CONNECTED, and RRC_INACTIVE.

[0117] The RRC_CONNECTED state is a non-limiting example of a connected or active state. A UE in the RRC_CONNECTED state is connected to a radio access network (RAN) and a core network (CN). For example, the UE may enter the RRC_CONNECTED state from the RRC_IDLE state after a connection establishment procedure or from the RRC_INACTIVE state after a connection recovery procedure. The RRC_CONNECTED state may be characterized as including the following features:

[0118] UE stores access stratum (AS) context;

[0119] Supports transmission of unicast data to and from UE;

[0120] At lower layers, UE-specific discontinuous reception (DRX) can be configured for the UE;

[0121] For UEs that support carrier aggregation (CA), support the use of special cells (SpCell)

[0122] Aggregate one or more secondary cells (SCells) to increase bandwidth;

[0123] For UEs supporting dual connectivity (DC), support for use with the master cell group (MCG)

[0124] Aggregated secondary cell group (SCG) to increase bandwidth;

[0125] Support network-controlled mobility within NR networks and to and from E-UTRA networks;

[0126] The UE monitors short messages with the paging radio network temporary identifier (P-RNTI) sent via downlink control information (DCI) (if configured);

[0127] The UE monitors the control channel associated with the shared data channel to determine whether data is scheduled for the UE;

[0128] UE provides channel quality and feedback information to the network;

[0129] UE performs neighbor cell measurements and measurement reporting;

[0130] UE obtains system information.

[0131] The RRC_IDLE state is a non-limiting example of an idle or disconnected state. A UE in the RRC_IDLE state is not connected to the RAN or CN, and the UE may need to perform an initial access procedure to establish a network connection and transition to the RRC_CONNECTED state. The RRC_IDLE state may be characterized as including the following features:

[0132] UE-specific DRX can be configured by the upper layers of the network;

[0133] UE controlled mobility based on network configuration;

[0134] UE monitors short messages with P-RNTI sent via DCI;

[0135] The UE monitors the paging channel for CN paging using the 5G system architecture evolution temporary mobile station identifier (5G-S-TMSI);

[0136] UE performs neighbor cell measurements and cell selection or cell reselection;

[0137] The UE obtains system information (SI) and can send an SI request (if configured).

[0138] The RRC_INACTIVE state is a non-limiting example of an inactive state. A UE in an inactive state uses fewer network resources and / or consumes less power than a UE in a connected state. This can extend the battery life of the UE. When the UE transitions to the inactive state, the UE and the network store the configuration information of the UE. This allows the UE to return to the connected state relatively quickly and efficiently. For example, the UE can use less signaling to transition from the inactive state to the connected state than to transition from the idle state to the connected state.

[0139] The RRC_INACTIVE state can be considered to be between the RRC_CONNECTED and RRC_IDLE states. In the RRC_INACTIVE state, at least a portion of the UE's AS context is stored by the UE and the network, which enables the network to communicate with the UE. Therefore, secure and fast signaling may occur between the network and the UE. In addition, a UE in the RRC_IDLE state may only support CN paging performed in the tracking area in which the UE is located. Conversely, in addition to CN paging, a UE in the RRC_INACTIVE state can also support RAN paging performed in the RAN notification area (RAN notification area, RNA) in which the UE is located. Because the number of cells covered by RNA is generally less than the tracking area, RAN paging in the RRC_INACTIVE state may result in less DL resource consumption and / or overhead. The RRC_INACTIVE state can be characterized as including the following features:

[0140] UE-specific DRX can be configured by the upper layers of the network or by the RRC layer;

[0141] UE controlled mobility based on network configuration;

[0142] The UE stores an inactive AS context which may be different from the AS context used in the RRC_CONNECTED state;

[0143] RAN-based notification areas are configured by the RRC layer;

[0144] UE monitors short messages with P-RNTI sent via DCI;

[0145] The UE monitors the paging channel for CN paging using 5G-S-TMSI and for RAN paging using FullI-RNTI;

[0146] UE performs neighbor cell measurements and cell selection or cell reselection;

[0147] The UE periodically performs RAN-based notification area updates when it moves outside the configured RAN-based notification area;

[0148] · The UE acquires the SI and may send an SI request (if configured).

[0149] The RRC_INACTIVE state is implemented in NR, but the inactive state can generally be implemented in any radio protocol or radio technology. Therefore, the inactive state is not limited to a specific radio protocol or radio technology. Similar comments apply to the idle state and the connected state.

[0150] The UE may transition from the connected state to the inactive state using the suspend procedure and transition back to the connected state using the resume procedure. The UE may also transition from the inactive state to the idle state using the release procedure. The transition from the connected state to the inactive state is invisible to the CN. Therefore, when the UE is in the inactive state, signaling and data exchange related to the UE may occur between the RAN and the CN. From the perspective of the CN, a UE in the inactive state is treated similarly to a UE in the connected state. For example, from the perspective of the CN, the UE may have two connection management (CM) states. The UE may be in either the CM-CONNECTED state or the CM-IDLE state. From the perspective of the RAN, a UE in the CM-IDLE state in the CN is in the RRC_IDLE state, while from the perspective of the RAN, a UE in the CM-CONNECTED state in the CN may be in the RRC_CONNECTED state or the RRC_INACTIVE state. Before the UE transitions from the connected state to the inactive state, the UE's security context and / or other parts of the UE's context are stored by the UE and the network. Therefore, the network can quickly and securely send signaling to the UE to transition from the inactive state to the connected state or the idle state.

[0151] In NR Rel-15, when the UE is in RRC_INACTIVE state or RRC_IDLE state, the UE monitors the paging common search space (CSS) set and receives paging signals on the physical downlink shared channel (PDSCH) in the control resource set (CORESET) with ID 0 (commonly referred to as CORESET 0). A CORESET is a physical resource set, such as a set of resource blocks (RBs) and multiple symbols of a physical downlink control channel (PDCCH) and other physical parameter sets that can be used to send PDCCH. The PDCCH may include downlink control information (DCI). The search space set provides all the parameters required for the UE to monitor the PDCCH. The CORESET can be configured separately and linked to a search space set that is part of the search space set configuration. Alternatively, the CORESET parameters can be configured directly as part of the search space set configuration. In addition to the CORESET parameters, the parameters provided in the search space set configuration may also include, but are not limited to: PDCCH monitoring period, PDCCH monitoring mode within a time slot, the number of time slots in which the search space set exists, the control channel element (CCE) aggregation level, the number of candidate PDCCHs for each aggregation level, the type of search space set (e.g., common search space (CSS) or UE-specific search space (USS)), and the DCI format to be monitored in the search space set.

[0152] In NR Rel-15, a bandwidth part (BWP) is a set of contiguous resource blocks (RBs) with given system parameters on a given carrier. The contiguous set of RBs of a BWP is identified by its frequency position and bandwidth. A BWP can be a DL BWP for DL ​​communication between a UE and a base station, or a UL BWP for UL communication between a UE and a base station. A UE-specific DL or UL BWP is configured for a UE using UE-specific high-layer signaling. In NR Rel-15, multiple DL BWPs and multiple UL BWPs can be configured for a UE, where a single DL BWP and a single UL BWP are active for the UE at a given time. The DL BWP can be cell-specific, such as a DL BWP defined by contiguous RBs of CORESET 0, which can be configured per cell through master information block (MIB) transmission, etc. The UL BWP can also be cell-specific, such as an initial UL BWP that can be configured per cell through system information block (SIB) transmission, etc.

[0153] For uplink (UL), 4-step RACH or (possibly) 2-step RACH may be supported for UEs in RRC_INACTIVE state, where UL transmissions are sent in the initial UL BWP.

[0154] CORESET 0 is intended to be used by all UEs for DL ​​communications at least during initial access to the cell, and may be used by many UEs to connect to the cell after initial access to the cell. Since CORESET 0 may span only a portion of the carrier bandwidth in the DL, restricting the use of CORESET 0 for DL ​​communications (e.g., DL data and DL control transmissions) in the RRC_INACTIVE state may overload the bandwidth of CORESET 0, as there may be many UEs with small packet traffic in the RRC_INACTIVE state.

[0155] The initial UL BWP is intended to be used by all UEs for UL communications at least during initial access to the cell, and may be used by multiple UEs that connect to the cell after initial access to the cell. Since the initial UL BWP may span only a portion of the carrier bandwidth in the UL, restricting the use of the initial UL BWP for UL communications (e.g., UL data and / or UL control and / or UL reference signal transmissions) in the RRC_INACTIVE state may overload the bandwidth of the initial UL BWP, as there may be many UEs with small packet traffic in the RRC_INACTIVE state.

[0156] The present application proposes a mechanism for configuring resources (frequency and time) for transmission in the RRC_INACTIVE state, thereby achieving more efficient and flexible resource management.

[0157] The currently supported air interface parameters in NR, such as cyclic prefix (CP) length, may not provide acceptable support for UL timing adjustment-free (TA) transmission for UEs in RRC_INACTIVE state.

[0158] Some aspects of the present application introduce a new DL BWP (referred to as INACTIVE DL BWP) for DL ​​communication in the RRC_INACTIVE state. In addition, a new UL BWP (referred to as INACTIVE UL BWP) is introduced for UL communication in the RRC_INACTIVE state. In addition, various aspects of the present application also introduce common parameters for configuring INACTIVE DL BWP or INACTIVE UL BWP, including but not limited to frequency location, bandwidth, subcarrier spacing (SCS) and CP.

[0159] An INACTIVE DL BWP or INACTIVE UL BWP may be dedicated to a specific UE served by the base station (UE-specific), dedicated to a specific group of UEs served by the base station (group-common), or apply to all UEs served by the base station (cell-specific BWP).

[0160] With the above configuration, every UE-specific DL reception or UL transmission in the RRC_INACTIVE state occurs within the INACTIVE DL (UL) BWP.

[0161] In some embodiments, this configuration may result in new BWP configuration parameters.

[0162] The advantage of using INACTIVE DL BWP or INACTIVE UL BWP for RRC_INACTIVE state is that efficient resource management can be achieved for data transmission in RRC_INACTIVE state, for example, because the network may not be limited to using only CORETSET 0 for DL ​​communication with a UE in RRC_INACTIVE state or using only the initial UL BWP for UL communication with a UE in RRC_INACTIVE state.

[0163] Some aspects of the present application may support reinterpretation of configuration parameters of the BWP to be used in the RRC_INACTIVE state (eg, common parameters of the BWP), which may be configured for the RRC_CONNECTED state.

[0164] This reinterpretation of a BWP configured for another state (e.g., RRC_CONNECTED state) to be used in the RRC_INACTIVE state can be dedicated to a specific UE served by the base station (UE-specific) or to a specific group of UEs served by the base station (group-common), or applied to all UEs served by the base station (cell-specific BWP).

[0165] Some embodiments of the configuration mechanisms described above result in new UE behaviors with respect to some existing BWP configuration parameters.

[0166] Some embodiments of the configuration mechanisms described above result in defining a new CP length for the UL.

[0167] Being able to reinterpret parameter information for the RRC_INACTIVE state based on parameter information from another state may be advantageous because the reinterpretation may not require any significant changes to the currently used radio resource control mechanisms.Another benefit of this approach may be that it supports longer CPs for ULTA-free transmissions in the RRC_INACTIVE state.

[0168] Some aspects of the present disclosure relate to implicit DL BWP switching in RRC_INACTIVE state, where no BWP identifier (ID) indication is required as part of the switching mechanism.

[0169] Some embodiments relate to defining conditions for DL ​​BWP switching in RRC_INACTIVE state. Some embodiments relate to implicit DL BWP switching before receiving unicast or multicast PDSCH. Some embodiments relate to autonomous DL BWP switching after receiving unicast or multicast PDSCH.

[0170] Some embodiments relate to defining conditions for UL BWP switching in RRC_INACTIVE state. Some embodiments relate to implicit UL BWP switching before sending PUSCH. Some embodiments relate to autonomous UL BWP switching after sending PUSCH.

[0171] Some embodiments of the configuration mechanisms described above result in defining new UE behaviors regarding DCI-based DL scheduling and / or paging-based DL scheduling.

[0172] Some embodiments of the configuration mechanism described above result in defining a new BWP switching delay for the RRC_INACTIVE state.

[0173] Controlling various aspects of DL BWP switching in the RRC_INACTIVE state may enable efficient resource management for data transmission in the RRC_INACTIVE state, reducing UE power consumption by adjusting the radio frequency bandwidth (RF BW) and supporting different system parameters for paging and transmission of unicast DL data.

[0174] Example 1-0

[0175] Some aspects of the present application relate to configuring common parameters of BWP for RRC_INACTIVE state. The RRC_INACTIVE state may also be referred to as the INACTIVE BWP state.

[0176] Some embodiments of the present application provide configuration for a UE-specific DL BWP or a UE-specific UL BWP. Some embodiments of the present application provide configuration for a group-common DL BWP or a group-common UL BWP.

[0177] In some embodiments, the configuration is an explicit configuration of BWP parameters. For example, the DL or UL BWP is explicitly configured in the ServingCellConfig parameters or in the RRCRelease message sent as part of activating the RRC Connection Suspend.

[0178] In some embodiments, the DL or UP BWP may be implicitly configured.

[0179] In a first example of implicitly implemented configuration, a DL or UL BWP is configured by indicating a BWP-Id. The BWP-Id identifies a DL or UL BWP that has been previously configured for a suspended connection in the ServingCellConfig parameter or in the RRCRelease. In some embodiments, this can be achieved by pointing to one of the DL or UL BWPs in the downlinkBWP-ToAddModList parameter or the uplinkBWP-ToAddModList parameter.

[0180] In a second example, the DL BWP for the RRC_INACTIVE state is based on the active DL BWP used by the UE, wherein the UE receives a physical downlink shared channel (PDSCH) including an RRC_RELEASE message in the RRC_CONNECTED state to suspend the RRC connection.

[0181] In a third example, the DL BWP for the RRC_INACTIVE state is based on the last active DL BWP of the UE before transitioning to the RRC_INACTIVE state.

[0182] FIG. 4A to FIG. 4D Four different examples of an INACTIVE DL BWP configured after transitioning from the RRC_CONNECTED state to the RRC_INACTIVE state are shown. In each figure, the horizontal axis corresponds to time, increasing from left to right, and the vertical axis corresponds to frequency. The various blocks shown in the figures represent frequency resources of the BWP.

[0183] exist Figure 4A 4, two BWPs are shown in the time portion indicating being in the RRC_CONNECTED state. The first BWP is CORESET 0 410, or more specifically, a set of contiguous RBs of CORESET 0 410. The second BWP is the last active DL BWP 420. The two BWPs occupy different sets of RBs. After the UE transitions from the RRC_CONNECTED state to the RRC_INACTIVE state, the UE uses a single DL BWP, which is identified as INACTIVE DL BWP 430. In this case, the INACTIVE DL BWP 430 occupies the same set of RBs as the last active DL BWP 420, which does not overlap with the set of RBs occupied by CORESET 0 410.

[0184] exist Figure 4B , the time portion indicating being in the RRC_CONNECTED state shows CORESET 0 410 and the last active DL BWP 420. The two BWPs partially overlap in frequency. After the UE transitions from the RRC_CONNECTED state to the RRC_INACTIVE state, the INACTIVE DL BWP 430 is shown as occupying the same RB set as the last active DL BWP 420, which has some overlap with the RB set occupied by CORESET 0 410.

[0185] exist Figure 4C, the time portion indicating being in the RRC_CONNECTED state shows CORESET 0 410 and the last active DL BWP 420. The last active DL BWP 420 includes the entire RB set of CORESET 0 410. After the UE transitions from the RRC_CONNECTED state to the RRC_INACTIVE state, the INACTIVE DL BWP 430 is shown as occupying the same RB set as the last active DL BWP 420, which completely overlaps with the RB set occupied by CORESET 0 410.

[0186] exist Figure 4D , the time portion indicating being in the RRC_CONNECTED state shows CORESET 0 410 and the last active DL BWP 420. The last active DL BWP 420 falls entirely within the RB set of CORESET 0 410. After the UE transitions from the RRC_CONNECTED state to the RRC_INACTIVE state, the INACTIVE DL BWP 430 is shown as occupying the same RB set as the last active DL BWP 420, which is within the RB set occupied by CORESET 0 410.

[0187] In a fourth example, the UL BWP for the RRC_INACTIVE state is based on the last active UL BWP of the UE before transitioning to the RRC_INACTIVE state.

[0188] Some embodiments of the present application provide configuration of a cell-specific INACTIVE DL BWP or a cell-specific INACTIVE UL BWP for the RRC_INACTIVE state.

[0189] In the first example, CORESET 0 (i.e., a contiguous RB set) starting from the RB with the lowest index and ending with the RB with the highest index among the RBs of CORESET 0 is configured as a cell-specific INACTIVE DL BWP. In another example, a contiguous RB set of a CORESET for a Type0-PDCCH CSS set can be configured as a cell-specific INACTIVE DL BWP.

[0190] In a second example, the initial DL or UL BWP used by the UE when the UE is in RRC_CONNECTED state is used as a cell-specific INACTIVE DL or UL BWP in RRC_INACTIVE state.

[0191] In a third example, the INACTIVE DL or UL BWP for RRC_INACTIVE state is configured in the system information block (SIB1), i.e., in servingCellConfigCommonSIB. For example, the INACTIVE DL or UL BWP for RRC_INACTIVE state in the RRC information element DownlinkConfigCommonSIB or UplinkConfigCommonSIB in servingCellConfigCommonSIB.

[0192] In a fourth example, an INACTIVE DL or UL BWP for the RRC_INACTIVE state is configured in a new system information block (SIBx), which is specifically used for configuration related to data transmission in the RRC_INACTIVE state, where x≠1 is an integer.

[0193] Example 1-1

[0194] In some embodiments, further restrictions may be imposed on the location and bandwidth of the INACTIVE BWP. Such further restrictions may limit flexibility to avoid UE retuning RF in RRC_INACTIVE state.

[0195] In some embodiments, the INACTIVE DL BWP includes all RBs of CORESET 0. Figure 4C It is also a representative example of this special situation.

[0196] In some embodiments, the INACTIVE UL BWP includes all RBs of the initial UL BWP.

[0197] Example 1-2

[0198] In some embodiments, further restrictions may be imposed on the sub-carrier spacing (SCS) and cyclic prefix (CP) parameters of the INACTIVE BWP. A possible advantage of these embodiments is that system parameter changes of the UE in the RRC_INACTIVE state may be avoided, thereby limiting the complexity of the operations implemented by the UE and / or the UE in the RRC_INACTIVE state.

[0199] In some embodiments, the INACTIVE DL BWP has the same SCS and the same CP as CORESET 0. In one example, the INACTIVE DL BWP has the same SCS and CP as those used for physical downlink control channel (PDCCH) reception in the CORESET of the Type0-PDCCH CSS set.

[0200] In some embodiments, the INACTIVE UL BWP has the same SCS and the same CP as the INACTIVE UL BWP.

[0201] Example 2-1

[0202] Some embodiments of the present application provide a reinterpretation of BWP common parameters to apply to a BWP to be used in the RRC_INACTIVE state.

[0203] One specific example is reinterpreting the CP length. One specific use of reinterpreting the CP length may be for UL BWP in RRC_INACTIVE state.

[0204] In some embodiments, when the extended CP length is indicated in the BWP configuration, the UE may use the following interpretation. When the UE is in the RRC_CONNECTED state, the normal CP with the SCS is used for the BWP, and when the UE is in the RRC_INACTIVE state, the extended CP with the SCS is used for the BWP. In one example, the above interpretation may only apply when the SCS is not 60kHz.

[0205] In some embodiments, regardless of the CP length configuration of the SCS in the RRC_CONNECTED state, the extended CP length is always used with the SCS configured in the RRC_INACTIVE state.

[0206] The above-described embodiments regarding CP length may be applicable to any BWP configuration alternatives in Embodiments 1-0, 1-1, and 1-2.

[0207] In some embodiments, new extended CP values ​​are defined for various SCSs. In some embodiments, extended CP values ​​may be used for SCSs for which extended CP values ​​were not previously defined (i.e., other than 60kHz). A specific example may be indicating an extended CP in the configuration of an initial UL BWP. For example, an extended CP for a particular SCS is determined such that the number of OFDM symbols per time slot for the SCS with the extended CP is equal to 12, while the number of OFDM symbols per time slot for the SCS with the normal CP is equal to 14. A specific example of an extended CP for an SCS is a CP length equal to 25% of the OFDM symbol duration corresponding to the SCS, where the OFDM symbol duration is equal to the inverse of the SCS value.

[0208] Example 2-2

[0209] Another specific example of reinterpreting common parameters is reinterpreting the bandwidth and position of the BWP. The flexibility of reinterpreting these parameters is somewhat limited to avoid the UE to re-tune the RF in the RRC_INACTIVE state.

[0210] In some embodiments, in the case of a UE-specific INACTIVE DL BWP, if the UE-specific INACTIVE DL BWP does not include all RBs of CORESET 0, the DL BWP to be used in the RRC_INACTIVE state may be defined by the RBs spanned by the UE-specific INACTIVE DL BWP and CORESET 0.

[0211] Figures 5A to 5C and Figure 4C Four different examples of INACTIVE DL BWPs configured after transitioning from the RRC_CONNECTED state to the RRC_INACTIVE state are shown. In each figure, the horizontal axis corresponds to time, increasing from left to right, and the vertical axis corresponds to frequency. The various blocks shown in the figure represent frequency resources of different BWPs.

[0212] exist Figure 5A5, two transmission resources are shown in the time portion indicating being in the RRC_CONNECTED state. The first BWP is CORESET 0 510, or more specifically, a set of contiguous RBs of CORESET 0 510. The second BWP is the last active DL BWP 520. The two BWPs occupy different sets of RBs. After the UE transitions from the RRC_CONNECTED state to the RRC_INACTIVE state, the UE uses a single BWP, which is identified as INACTIVE DL BWP 530. In this case, the INACTIVE DL BWP 530 occupies an RB set that contains the RB set of the last active DL BWP 520, which occupies the RB set of CORESET 0 510, and the RBs separating BWPs 510 and 520.

[0213] exist Figure 5B , the time portion indicating being in the RRC_CONNECTED state shows CORESET 0 510 and the last active DL BWP 520. BWPs 510 and 520 partially overlap in frequency. After the UE transitions from the RRC_CONNECTED state to the RRC_INACTIVE state, INACTIVE DL BWP 530 is shown as occupying an RB set that includes the RBs of the last active DL BWP 520 and CORESET 0 510.

[0214] exist Figure 5C , the time portion indicating being in the RRC_CONNECTED state shows CORESET 0 510 and the last active DL BWP 520. The RB set of the last active DL BWP 520 falls entirely within the RB set of CORESET 0 510. After the UE transitions from the RRC_CONNECTED state to the RRC_INACTIVE state, the INACTIVE DL BWP 530 is shown as occupying the RB set containing CORESET 0 510, which also contains the RB set of the last active DL BWP 520.

[0215] See again Figure 4C, indicating that the time portion in the RRC_CONNECTED state shows CORESET 0 410 and the last active DL BWP 420. The last active DL BWP 420 occupies the entire RB set of CORESET 0 410. After the UE transitions from the RRC_CONNECTED state to the RRC_INACTIVE state, the INACTIVE DL BWP 430 is shown as occupying an RB set that includes the last active DL BWP 420 and also includes RBs of CORESET 0 410.

[0216] In some embodiments, in the case of a UE-specific INACTIVE UL BWP, if the UE-specific INACTIVE UL BWP does not include all resource blocks of the initial UL BWP, the UL BWP to be used in the RRC_INACTIVE state may be defined by the RBs spanned by the UE-specific INACTIVE UL BWP and the initial UL BWP.

[0217] Some aspects of the present application relate to implicit DL BWP switching in RRC_INACTIVE state. In some embodiments, there is no BWP ID indication in the scheduling command for such switching.

[0218] Example 3-1

[0219] In some embodiments, for DL ​​unicast / multicast transmissions in RRC_INACTIVE state, DL BWP switching is always assumed.

[0220] In some embodiments, DL BWP switching is assumed for DL ​​unicast / multicast transmission in RRC_INACTIVE state only if conditions are met. The following includes several examples of non-limiting DL BWP switching conditions.

[0221] In the first condition, the INACTIVE DL BWP has a different frequency position and bandwidth or a different SCS or a different CP length than CORESET 0.

[0222] In the second condition, the INACTIVE DL BWP does not include all RBs of CORESET 0, or has a different SCS or a different CP than CORESET 0.

[0223] In some embodiments, for UL transmissions in RRC_INACTIVE state, UL BWP switching is always assumed.

[0224] In some embodiments, UL BWP switching is assumed for UL transmissions in RRC_INACTIVE state only if conditions are met. The following includes several examples of non-limiting UL BWP switching conditions.

[0225] In the first condition, the INACTIVE UL BWP has a different frequency position and bandwidth or a different SCS or a different CP length than the initial UL BWP.

[0226] In the second condition, the INACTIVE UL BWP does not include all RBs of the initial UL BWP, or has a different SCS or a different CP than the initial UL BWP.

[0227] Fig. 6A An example is shown when the DL BWP switching condition is met in the RRC_INACTIVE state, for example, regarding the second condition. Fig. 6A 6, the horizontal axis corresponds to time, increasing from left to right, and the vertical axis corresponds to frequency. The various blocks shown in the figure represent DL BWPs. The first DL BWP is CORESET 0 610, which is shown to include PDCCH 612. The second DL BWP is INACTIVE DL BWP 620, which is shown to include PDSCH 622. Another occurrence of CORESET 0 630 is also shown in the figure.

[0228] exist Fig. 6A In FIG. 6 , the switching condition is met because the INACTIVE DL BWP 620 does not include all RBs of CORESET 0 610. The INACTIVE DL BWP 620 does not include all RBs of CORESET 0 610, so the base station uses an appropriate K0 value (i.e., K0=5) that is greater than the switching delay, because the base station also knows that the switching condition is met, and the base station should give the UE enough time to perform the switching. K0 represents the offset (e.g., the number of time slots) between the time slot in which the PDCCH containing the DCI is received and the time slot in which the PDSCH is scheduled.

[0229] Figure 6B An example is shown when the DL BWP switching condition is not met in the RRC_INACTIVE state, for example, regarding the second condition. Figure 6B 6, the horizontal axis corresponds to time, increasing from left to right, and the vertical axis corresponds to frequency. The first DL BWP is CORESET 0 610, shown as including PDCCH 612. The second DL BWP is INACTIVE DL BWP 620, shown as including PDSCH 622.

[0230] exist Figure 6BIn FIG. 6 , the switching condition is not satisfied because the INACTIVE DL BWP 620 includes all RBs of CORESET 0 610 .

[0231] A switching delay defining the delay between switching from one BWP to another BWP may be applied. In some embodiments, such a switching delay may be based on a value specified in a telecommunication standard document.

[0232] Example 3-2

[0233] In some embodiments, before receiving DL data in the RRC_INACTIVE state (or sending UL data in the RRC_INACTIVE state), a predetermined delay called BWP switching delay is provided to the UE to accommodate the switching of the DL (or UL BWP). In some embodiments, the BWP switching delay may be specified in a telecommunications standard document. A possible advantage of these embodiments is that sufficient time may be provided to the UE to perform the operations required for the UE to switch its DL (or UL BWP) in the RRC_INACTIVE state.

[0234] Two examples of DL scheduling are DCI-based DL scheduling and paging-based DL scheduling.

[0235] Figure 7 7 is a signaling flow diagram 700 showing signaling for DCI-based DL data scheduling occurring between a UE 701 and a base station 702 when the UE 701 is initially in an RRC_CONNECTED state 705 and then the UE 701 is released and enters an RRC_INACTIVE state 707 .

[0236] Initially, UE 701 is in RRC_CONNECTED state 705. Base station 702 sends (710) an INACTIVE DL BWP configuration to UE 701. At a subsequent point in time, base station 702 sends (715) an RRCrelease to suspend the connection to UE 701. After receiving the release, UE 701 transitions to RRC_INACTIVE state 707. While UE is in RRC_INACTIVE state 707, base station 702 sends (720) a DCI in CORESET 0 that schedules DL data. After receiving the DCI, if the switching condition is met, UE 701 switches (725) to the INACTIVE DL BWP. Base station 702 sends (730) DL data in the INACTIVE DL BWP. After receiving the DL data, if the switching is performed in 725, UE 801 switches (735) the DL BWP from the INACTIVE DL BWP to CORESET 0.

[0237] When receiving DCI, UE 701 is in an inactive state. In some cases, DCI includes a CRC scrambled by an RNTI dedicated to UE 701 and the inactive state. The RNTI dedicated to a specific UE and the inactive state is referred to as "I-RNTI" in this article. Because I-RNTI is dedicated to the inactive state, I-RNTI is not used to scramble the CRC of DCI in the connected or idle state. In some implementations, UE 701 is in RRC_INACTIVE state and DCI adopts DCI format 1_0. DCI includes a CRC scrambled by the I-RNTI of UE 701. I-RNTI is different from paging RNTI (Paging RNTI, P-RNTI), and when UE 701 is in RRC_CONNECTED or RRC_IDLE state, I-RNTI is not used to scramble the CRC of DCI.

[0238] A UE in an inactive state monitors DCI with a CRC scrambled with its own I-RNTI. The UE stores its own I-RNTI so that it can descramble the CRC and use the CRC to check whether the decoding of the DCI is successful. Since the I-RNTI is dedicated to a specific UE, any other UE in the same network or service area will have a different I-RNTI. Other UEs may not store the I-RNTI of a specific UE, so other UEs may not be able to descramble the CRC of the DCI.

[0239] The DCI includes resource allocation in a resource allocation bit field for data transmission. Thus, the DCI may be or include notification of data scheduling.

[0240] Based on the resource allocation, UE 701 may receive scheduled data transmission on PDSCH. When receiving data transmission, UE 701 is in an inactive state. The data transmission may be a unicast transmission or a multicast transmission.

[0241] The network can use paging messages to facilitate the transition of the UE from an idle state or from an inactive state to a connected state. For example, a paging message can be received by paging a physical DL shared channel (paging PDSCH). The network initiates the paging process by sending a paging message at the UE's paging opportunity. The network can address multiple UEs with a single paging message by including multiple UE identities (IDs) in the paging record carried by the paging message. A paging record is a set of UE IDs corresponding to the UEs that the network is paging. In the 3GPP NR specification TS38.331, an example of a paging record is the PagingRecord parameter, and an example of a UE ID is the UE-Identity parameter.

[0242] According to one aspect of the present application, unicast or multicast data transmission to and from a UE in an inactive state is scheduled by paging. The UE may be notified of the data transmission using a paging DCI or an indication in a paging message. The data transmission may then be received in a paging message or in a further transmission scheduled by the paging message.

[0243] In some embodiments, a UE in an idle or inactive state monitors a paging search space to find a physical DL control channel (PDCCH) containing a paging DCI. An example of a paging DCI in NR is a DCI format 1_0 with a cyclic redundancy check (CRC) scrambled or masked with a P-RNTI. UEs in an idle or inactive state know the P-RNTI, so they are able to descramble or demask the CRC and use the CRC to check whether the decoding of DCI format 1_0 is successful. In addition to other information, DCI format 1_0 includes one or both of scheduling information for a short message and a paging message. The scheduling information for the paging message may include resource allocations with frequency domain resource allocations, time domain resource allocations, virtual resource blocks (VRB) to physical resource blocks (PRB) mappings, modulation and coding schemes (MCS) and / or transport block (TB) scaling. For example, DCI format 1_0 with CRC scrambled by P-RNTI may include any or all of the following bit fields:

[0244] Short message indicator: 2 digits in length;

[0245] Short message: 8 characters in length;

[0246] Frequency domain resource allocation for paging messages - length is bits, among which, It can be equal to the size of control resource set (CORESET) 0 (if only short messages are carried, this bit field is reserved);

[0247] Time domain resource allocation for paging messages - length is 4 bits (if only short messages are carried, this bit field is reserved);

[0248] VRB to PRB mapping of paging messages - 1 bit in length (this bit field is reserved if only short messages are carried);

[0249] MCS of paging message: 5 bits in length (this bit field is reserved if only short messages are carried);

[0250] TB scaling of paging messages - length is 2 bits (if only short messages are carried, this field is reserved);

[0251] Reserved bits: Length is 6 bits.

[0252] In the case where the paging DCI contains resource allocation for the paging message, the UE that receives the paging DCI continues to receive the scheduled paging message according to the resource allocation. When a UE in an idle state receives a paging message, the UE can determine whether any UE ID contained in each paging record of the paging message matches the specific ID assigned to the UE by the upper layer of the network. In NR, 5G-S-TMSI is used as the UE ID for paging UEs in the RRC_IDLE state. If the UE ID in the paging record matches the specific ID of the UE, the UE can initiate a connection to the network by forwarding the specific ID of the UE and the access type (if any) to the upper layer, that is, transitioning to a connected state. The access type of the UE can be included in the 3GPP NR specification TS38.331 as an accessType parameter.

[0253] When a UE in an inactive state receives a paging message, the UE can determine whether the UE ID contained in each paging record of the paging message matches the FullI-RNTI stored by the UE. The FullI-RNTI is a 40-bit string that is configured to the UE during the RRC suspension process. For example, according to the 3GPP NR specification TS38.331, the FullI-RNTI can be configured in the SuspendConfig field of the RRCRelease information element (IE), which is configured to the UE to suspend the RRC connection and transition the UE from the RRC_CONNECTED state to the RRC_INACTIVE state.

[0254] Conventional control signaling mechanisms do not support (non-paging) DL data transmission to or from a UE in an inactive state, except for transmissions completed as part of the state transition process from the inactive state to the connected state. According to these conventional control signaling mechanisms, when the UE is in an inactive state and no procedure for resuming a connection is performed, the only DCI format monitored by the UE is the paging DCI. For example, the only DCI format monitored by a UE in the RRC_INACTIVE state is DCI format 1_0 with a CRC scrambled by the P-RNTI. However, conventional paging DCI does not support:

[0255] Non-paging DL data scheduling;

[0256] Notification of non-paging DL data scheduling;

[0257] SL data scheduling; or

[0258] UL data scheduling.

[0259] Figure 8 8 is a signaling flow diagram 800 showing signaling for paging-based DL data scheduling occurring between a UE 801 and a base station 802 when the UE 801 is initially in an RRC_CONNECTED state 805 and then the UE 801 is released and enters an RRC_INACTIVE state 807 .

[0260] Initially, UE 801 is in RRC_CONNECTED state 805. Base station 802 sends (810) an INACTIVE DL BWP configuration to UE 801. At a subsequent point in time, base station 802 sends (815) an RRCrelease to suspend the connection to UE 801. After receiving the release, UE 801 transitions to RRC_INACTIVE state 807. While UE 801 is in RRC_INACTIVE state 807, base station 802 sends (820) a DCI in CORESET 0 scheduling paging. Then, base station 802 sends (822) a paging message in CORESET 0, which includes scheduling information for DL ​​data. After receiving the paging message, if the switching conditions are met, UE 801 switches (825) to the INACTIVE DL BWP. Base station 802 sends (830) DL data in the INACTIVE DL BWP. After receiving the DL data, if a handover is performed in 825 , the UE 801 switches ( 835 ) the DL BWP from the INACTIVE DL BWP to the CORESET 0 .

[0261] Fig. 9 9 is a signaling flow diagram 900 showing signaling occurring between the UE 901 and the base station 902 for UL data transmission in an INACTIVE UL BWP when the UE 901 is initially in the RRC_CONNECTED state 905 and then the UE 1001 is released and enters the RRC_INACTIVE state 907 .

[0262] Initially, UE 901 is in RRC_CONNECTED state 905. Base station 902 sends (910) an INACTIVE UL BWP configuration to UE 901. At a subsequent point in time, base station 902 sends (915) an RRCrelease to suspend the connection to UE 901. After receiving the release, UE 901 transitions to RRC_INACTIVE state 907. While UE is in RRC_INACTIVE state 907, if a switching condition is met, UE 901 switches (920) to INACTIVE UL BWP. UE 901 sends (925) UL data in INACTIVE DL BWP. After sending DL data, if a switching is performed in 920, UE 901 switches (930) the UL BWP from INACTIVE UL BWP to initial BWP.

[0263] In case of DCI-based DL scheduling, the UE can obtain resource assignment (RA) by decoding the DCI received in the PDCCH. The start time of BWP switching can be the end of the kth symbol of time slot n containing the PDCCH. The value of k can be predefined, such as k=3, or the value can be configured by higher layers.

[0264] If the UE detects DCI in the PDCCH that schedules unicast / multicast PDSCH for a UE in RRC_INACTIVE state and the DL BWP switching conditions in the RRC_INACTIVE state are met, the UE does not need to receive or transmit in the cell during the time period from the end of the kth symbol of the time slot in which the UE receives the PDCCH to the start of the time slot indicated by the time slot offset value of the time domain resource allocation field in the DCI.

[0265] If the UE detects DCI in the PDCCH that schedules unicast / multicast PUSCH for a UE in RRC_INACTIVE state and the UL BWP switching conditions in the RRC_INACTIVE state are met, the UE does not need to receive or transmit in the cell during the time period from the end of the kth symbol of the time slot in which the UE receives the PDCCH to the start of the time slot indicated by the time slot offset value of the time domain resource allocation field in the DCI.

[0266] Therefore, if switching to a new BWP, the UE expects to schedule the corresponding PDSCH with an appropriate delay on or after time slot n, i.e. n+T INACTIVE_BWPswitchDelay , where T INACTIVE_BWPswitchDelay Defined as the number of time slots and may be predefined or configured to the UE by higher layers.

[0267] When the DL BWP switching conditions in the RRC_INACTIVE state are met, the UE will perform DCI-based DL scheduling in a specific manner.

[0268] After the UE receives the DL scheduling PDCCH on DL time slot n, the UE can receive the PDSCH on the INACTIVE DL BWP in the first DL time slot after the start of the DL time slot, that is, n+T INACTIVE_BWPswitchDelay , where T INACTIVE_BWPswitchDelay is the DLBWP switching delay (in number of time slots).

[0269] Reference again Fig. 6A , time slot n is shown at PDCCH 612 within CORESET 0 610 and T INACTIVE_BWPswitchDelay Displayed as 4 time slots.

[0270] When in RRC_INACTIVE state, the UE does not expect the time domain resource allocation field to provide a slot offset value for PDSCH reception that is less than the UE's predetermined delay for DCI-based active DL BWP changes. The time domain resource allocation field can be detected as part of DCI format 1_0 with a CRC scrambled by the I-RNTI. Fig. 6A In the example of , the time domain resource allocation offset of K0 satisfies the DL BWP switching delay used by the UE for the active DL BWP change based on DCI, because K0>T INACTIVE_BWPswitchDelay .

[0271] In case of paging-based DL scheduling, when the UE obtains resource allocation by decoding the paging payload, it may take some time for the UE to process the paging transport block (TB) and obtain the resource allocation. The starting symbol / slot for BWP switching can be the first symbol of slot n, which has an offset T from the last slot n containing the DL scheduling command (i.e., paging TB). PagingProcessingDelay ,Right now Among them, T PagingProcessingDelay and T INACTIVE_BEPswitchDelayPaging Measured in milliseconds.

[0272] T PagingProcessingDelay The value of may be predefined by a higher layer or configured to the UE.

[0273] When the DL BWP switching conditions in the RRC_INACTIVE state are met, the UE shall perform paging-based DL scheduling in a specific manner.

[0274] After the UE receives the DL scheduling paging message, the UE can receive PDSCH on the INACTIVEDL BWP in the first DL time slot after the start of the DL time slot, that is, Where, DL slot n is the last slot containing the paging message, T PagingProcessingDelay (in milliseconds) is the length of the paging processing delay, T INACTIVE_BWPswithDelayPaging (in milliseconds) is the time taken by the UE to perform BWP switching in RRC_INACTIVE state, and "NR Slot length" is the time slot length (in milliseconds) of the system parameter of the paging message, or the larger value between the paging SCS and the SCS of the INACTIVE DL BWP.

[0275] When in the RRC_INACTIVE state, the UE does not expect the time domain resource allocation field in the paging message to contain a time slot offset value for PDSCH reception that is less than a predetermined delay for the UE to change the active DL BWP based on paging.

[0276] Example 3-3

[0277] According to another aspect of the present application, a mechanism for autonomous DL BWP switching after receiving DL data in RRC_INACTIVE state is provided.

[0278] In some embodiments, the UE switches back to CORESET 0 after receiving the PDSCH.

[0279] A switching delay for autonomous switching may be included. The switching delay is considered as an offset from the last slot n containing the DL PDSCH.

[0280] The switching delay may include the PDSCH processing delay T INACTIVE_PDSCHprocessingDelay and DL BWP switching delay T INACTIVE_BWPswithDelayPDSCH The amount.

[0281] When the DL BWP switching conditions in the RRC_INACTIVE state are met, after the UE receives the DL PDSCH, the UE can receive PDSCH / PDCCH on CORESET 0 in the first DL time slot after the start of the DL time slot, that is, n+ Among them, DL time slot n is the last time slot containing PDSCH, T INACTIVE_PDSCHprocessingDelay (in milliseconds) is the length of the PDSCH processing delay, T INACTIVE_BWPswitchDelayPDSCH (in milliseconds) is the time taken by the UE to perform BWP switching in RRC_INACTIVE state, and "NR Slot length" is the slot length of the system parameter of PDSCH (in milliseconds), or the larger value between PDSCH SCS and SCS of CORESET 0.

[0282] Reference again Fig. 6AExample showing the delay from the start of the INACTIVE DL BWP until the switch back to CORESET 0630

[0283] If a UE receives unicast or multicast PDSCH in RRC_INACTIVE state, then after receiving PDSCH from the end of the last slot containing PDSCH, the UE is not expected to transmit or receive for a duration equal to the delay required by the UE for active DL BWP change.

[0284] Although DL and UL transmissions are described above, data transmissions may be SL transmissions instead. A UE may send or receive SL transmissions on a physical SL shared channel (PSSCH).

[0285] Fig.10 A flow chart 1000 is shown of a method that may be used by a UE for downlink communication with a network device, uplink communication with a network device, or sidelink communication with another UE.

[0286] In step 1010, while in the RRC_CONNECTED state, the UE determines configuration information for configuring a BWP for communication in the RRC_INACTIVE state. In some embodiments, determining the configuration information may include the UE implicitly determining how the UE should be configured based on information known to the UE. In some embodiments, the configuration information may be derived from information known to the UE by indicating that the configured BWP for downlink communication in the RRC_INACTIVE state is control resource set 0 (CORESET 0), or may indicate that the configured BWP is the last active BWP of the UE in the RRC_CONNECTED state before the UE entered the RRC_INACTIVE state. In some embodiments, the configuration information may be derived from information known to the UE by indicating that the configured BWP for uplink communication in the RRC_INACTIVE state is the initial UL BWP, or may indicate that the configured BWP is the last active BWP of the UE in the RRC_CONNECTED state before the UE entered the RRC_INACTIVE state.

[0287] In some embodiments, determining the configuration information may include: the UE receives explicit configuration information from the network about how the UE should be configured. In some embodiments, when the UE receives the configuration information, the configuration information may explicitly define BWP parameters of a configured BWP for communication in the RRC_INACTIVE state. In some embodiments, when the UE receives the configuration information, the configuration information may indicate a BWP identifier that identifies a previously configured BWP to be used for communication in the RRC_INACTIVE state. In some embodiments, the UE receives the configuration in a ServingCellConfig parameter or in a RRCRelease message sent as part of activating an RRC connection suspension. In some embodiments, the UE receives the configuration in a system information block (SIB1) or a system information block other than SIB1 for transmission in the RRC_CONNECTED state (SIBx).

[0288] In step 1020, the UE enters the RRC_INACTIVE state. In some embodiments, this is a result of the UE receiving signaling indicating suspension of the RRC_CONNECTED state.

[0289] In step 1030, the UE uses the configured BWP for communication in the RRC_INACTIVE state.

[0290] Step 1040 is an optional step, comprising: when in the RRC_INACTIVE state, the UE switches to a configured BWP for communication in the RRC_INACTIVE state. In some embodiments, the switching occurs when a predefined condition is met. The predefined condition may be one of the following conditions: the configured BWP for communication in the RRC_INACTIVE state has a different frequency position and bandwidth or a different sub-carrier spacing (SCS) or a different cyclic prefix (CP) from CORESET 0; or the configured BWP for communication in the RRC_INACTIVE state does not include all resource blocks of CORESET 0, or has a different SCS or a different CP from CORESET 0. The predefined condition may be one of the following conditions: the configured BWP for communication in the RRC_INACTIVE state has a different frequency position and bandwidth or a different subcarrier spacing (SCS) or a different cyclic prefix (CP) from the initial UL BWP; or the configured BWP for communication in the RRC_INACTIVE state does not include all resource blocks of the initial UL BWP, or has a different SCS or a different CP from the initial UL BWP.

[0291] In another optional step 1050, while in the RRC_INACTIVE state, the UE switches from the configured BWP for communicating in the RRC_INACTIVE state to CORESET 0 for DL ​​or the initial UL BWP for UL.

[0292] Communications that may be received in the RRC_INACTIVE state may include downlink control information including scheduling information for further communications. In some embodiments, the scheduling information includes scheduling information for receiving downlink data while in the RRC_INACTIVE state. In some embodiments, the scheduling information includes scheduling information for sending uplink data while in the RRC_INACTIVE state.

[0293] In some embodiments, the configuration information for configuring the BWP for communication in the RRC_INACTIVE state includes an extended CP. The extended CP may be used for the uplink BWP.

[0294] Fig.11 A flowchart 1100 of a method that can be used by a network side device such as a base station to perform downlink communication with a UE or uplink communication with a UE is shown.

[0295] The first step 1105 includes: the network side device determines configuration information for configuring a bandwidth part (BWP) for communication in the RRC_INACTIVE state. The network side device and the UE work together, so the network side device determines the configuration information so that the UE is correctly configured to receive when the network side sends. The network side device does not necessarily need to explicitly send the configuration information, as described in the optional step 1110 below, because the UE can infer the configuration information, as described in the above examples in this specification.

[0296] Step 1110 (which may be considered an optional step) includes: the network side device sends configuration information for configuring the BWP for the UE to use for communication in the RRC_INACTIVE state. In some embodiments, the configuration information may include explicit configuration information from the network on how the UE should be configured. In some embodiments, the configuration information may explicitly define BWP parameters of a configured BWP for communication in the RRC_INACTIVE state. In some embodiments, the configuration information indicates a BWP identifier, which identifies a previously configured BWP to be used for communication in the RRC_INACTIVE state. In some embodiments, the UE receives the configuration in a ServingCellConfig parameter or in a RRCRelease message sent as part of activating an RRC connection suspension. In some embodiments, the UE receives the configuration in SIB1 or SIBx other than SIB1.

[0297] In step 1120, the network side device sends a signaling indicating to suspend the RRC_CONNECTED state, so that the UE enters the RRC_INACTIVE state.

[0298] In step 1130, when the UE is in the RRC_INACTIVE state, the network side device communicates with the UE using the BWP configured for the RRC_INACTIVE state.

[0299] Communications that may be received in the RRC_INACTIVE state may include downlink control information including scheduling information for further communications. In some embodiments, the scheduling information includes scheduling information for receiving downlink data while in the RRC_INACTIVE state. In some embodiments, the scheduling information includes scheduling information for sending uplink data while in the RRC_INACTIVE state.

[0300] In some embodiments, the configuration information for configuring the BWP for communication in the RRC_INACTIVE state includes an extended CP. The extended CP may be used for the uplink BWP.

[0301] It should be understood that one or more steps in the embodiment method provided herein can be performed by corresponding units or modules. For example, data can be sent by a sending unit or a sending module. Data can be received by a receiving unit or a receiving module. Data can be processed by a processing unit or a processing module. Each unit / module can be hardware, software, or a combination thereof. For example, one or more units / modules can be integrated circuits, such as field programmable gate arrays (FPGA) or application-specific integrated circuits (ASIC). It should be understood that if these modules are software, these modules can be retrieved in whole or in part by a processor as needed, retrieved individually or collectively for processing, retrieved in one or more instances as needed, and these modules themselves can include instructions for further deployment and instantiation.

[0302] Although combinations of features are shown in the illustrated embodiments, not all features need to be combined to achieve the advantages of the various embodiments of the present application. In other words, a system or method designed according to an embodiment of the present application does not necessarily include all features shown in any of the drawings or all parts schematically shown in the drawings. In addition, selected features of an exemplary embodiment can be combined with selected features of other exemplary embodiments.

[0303] Although the present application has been described with reference to illustrative embodiments, this specification is not to be interpreted in a limiting sense. Various modifications and combinations of the illustrative embodiments and other embodiments of the present application will be apparent to those skilled in the art with reference to this specification. Therefore, the appended claims are intended to cover any such modifications or embodiments.

Claims

1. A communication method, characterized in that: include: In a radio resource control connected RRC_CONNECTED state, receiving configuration information, the configuration information is used to configure a downlink partial bandwidth DL BWP for downlink data communication in a radio resource control inactive RRC_INACTIVE state; Entering the RRC_INACTIVE state; In the RRC_INACTIVE state, the DL BWP configured based on the configuration information for downlink data communication in the RRC_INACTIVE state is used.

2. The method according to claim 1, characterized in that The configuration information includes BWP parameters for the DL BWP.

3. The method according to claim 1 or 2, characterized in that: The configuration information includes implicitly or explicitly configured BWP parameters for the DL BWP.

4. The method according to any one of claims 1 to 3, characterized in that: The configuration information includes a BWP identifier that identifies the DLBWP.

5. The method according to any one of claims 1 to 4, characterized in that: The configuration information indicates that the DL BWP used for downlink data communication in the RRC_INACTIVE state is the last DL BWP of the electronic device in the RRC_CONNECTED state before the electronic device enters the RRC_INACTIVE state.

6. The method according to any one of claims 1 to 5, characterized in that: Also includes: In the RRC_INACTIVE state, downlink control information including scheduling information is received.

7. The method according to claim 6, characterized in that The scheduling information includes: Scheduling information for receiving downlink data in the RRC_INACTIVE state; or The scheduling information is used to receive paging information, wherein the scheduling information includes scheduling information for receiving downlink data in the RRC_INACTIVE state.

8. The method according to any one of claims 1 to 7, characterized in that: Using the DL BWP for downlink data communication in the RRC_INACTIVE state includes: sending downlink data in the DL BWP for downlink data communication in the RRC_INACTIVE state.

9. The method according to any one of claims 1 to 8, characterized in that: The configuration information includes one or more of an extended cyclic prefix CP, a subcarrier spacing SCS, a frequency domain position and a bandwidth.

10. The method according to claim 8, characterized in that The CP is an extended CP.

11. The method according to any one of claims 1 to 10, characterized in that: Before using the DL BWP for downlink data communication in the RRC_INACTIVE state, the method further includes: the electronic device, in the RRC_INACTIVE state, switching to the DLBWP for downlink data communication in the RRC_INACTIVE state.

12. The method according to claim 11, characterized in that The switching occurs when a predefined condition is met.

13. The method according to claim 12, characterized in that The predefined condition is one of the following conditions: The DL BWP used for downlink data communication in the RRC_INACTIVE state has a different frequency position and bandwidth or a different subcarrier spacing SCS or a different cyclic prefix CP than that of control resource set 0 (CORESET 0); or The DL BWP used for downlink data communication in the RRC_INACTIVE state does not include all resource blocks of CORESET 0, or has an SCS different from that of CORESET 0 or a different CP.

14. The method according to claim 13, characterized in that Also includes: In the RRC_INACTIVE state, the DL BWP used for downlink data communication in the RRC_INACTIVE state is switched to CORESET 0.

15. The method according to any one of claims 1 to 14, characterized in that: The DL BWP is user equipment UE-specific, group-specific or cell-specific.

16. The method according to any one of claims 1 to 15, characterized in that: Also includes: A physical downlink shared channel PDSCH is received, where the PDSCH includes an RRCRelease message in the RRC_CONNECTED state.

17. The method according to any one of claims 1 to 16, characterized in that: The configuration information is carried in the RRCRelease message or the new system information block SIBx.

18. An electronic device, characterized in that: The method comprises a processing unit configured to execute the method according to any one of claims 1 to 17.

19. A communication method, characterized in that: include: Determine configuration information for configuring a downlink partial bandwidth DL BWP for downlink data communication in a radio resource control inactive RRC_INACTIVE state; Sending a signaling indicating suspension of the radio resource control connection RRC_CONNECTED state, so that the recipient of the signaling enters the RRC_INACTIVE state; When a recipient of the signaling is in the RRC_INACTIVE state, communicating with the recipient using the DL BWP configured for the RRC_INACTIVE state.

20. The method according to claim 19, characterized in that The configuration information includes BWP parameters for the DL BWP.

21. The method according to claim 19 or 20, characterized in that The configuration information includes implicitly or explicitly configured BWP parameters for the DL BWP.

22. The method according to any one of claims 19 to 21, characterized in that: The configuration information includes a BWP identifier identifying the DL BWP.

23. The method according to any one of claims 19 to 22, characterized in that: The configuration information indicates that the DL BWP used for downlink data communication in the RRC_INACTIVE state is the last DL BWP of the receiver in the RRC_CONNECTED state before the receiver enters the RRC_INACTIVE state.

24. The method according to any one of claims 19 to 23, characterized in that: Also includes: The configuration information for configuring the RRC_INACTIVE state DL BWP is sent.

25. The method according to any one of claims 19 to 24, characterized in that Also includes: When the receiving party is in the RRC_INACTIVE state, downlink control information including scheduling information is sent.

26. The method according to claim 25, characterized in that The scheduling information includes: scheduling information for receiving downlink data in the RRC_INACTIVE state; or scheduling information for receiving paging information, including scheduling information for receiving downlink data in the RRC_INACTIVE state.

27. The method according to any one of claims 19 to 26, characterized in that Using the DL BWP for downlink data communication in the RRC_INACTIVE state includes receiving downlink data in the DL BWP for downlink data communication in the RRC_INACTIVE state.

28. The method according to any one of claims 19 to 27, characterized in that The configuration information includes one or more of a cyclic prefix CP, a subcarrier spacing SCS, a frequency domain position and a bandwidth.

29. The method according to claim 28, characterized in that The CP is an extended CP.

30. The method according to any one of claims 19 to 29, characterized in that Also includes: When the receiving side is in the RRC_INACTIVE state, a control resource set 0 (CORESET 0) is used to communicate in the RRC_INACTIVE state.

31. The method according to any one of claims 19 to 30, characterized in that: The DL BWP is UE-specific, group-specific or cell-specific.

32. The method according to any one of claims 19 to 31, characterized in that: Also includes: A physical downlink shared channel PDSCH is sent, where the PDSCH includes the RRCRelease message in the RRC_CONNECTED state.

33. The method according to any one of claims 19 to 32, characterized in that: The configuration information is carried in the RRCRelease message or the new system information block SIBx.

34. A network side device, characterized in that: Comprising a processing unit, the processing unit is used to execute the method according to any one of claims 19 to 33.

35. A communication method, characterized in that: include: In a radio resource control connected RRC_CONNECTED state, receiving configuration information, the configuration information is used to configure a downlink partial bandwidth DL BWP for downlink data communication in a radio resource control inactive RRC_INACTIVE state; Entering the RRC_INACTIVE state; In the RRC_INACTIVE state, the DL BWP configured based on the configuration information for downlink data communication in the RRC_INACTIVE state is used.

36. The method according to claim 35, characterized in that The configuration information includes BWP parameters for the DL BWP.

37. The method according to claim 35 or 36, characterized in that The configuration information includes implicitly or explicitly configured BWP parameters for the DL BWP.

38. An electronic device, characterized in that: Comprising a processing unit, the processing unit is used to execute the method according to any one of claims 35 to 37.

39. A computer-readable storage medium, characterized in that: The readable storage medium is used to store computer-executable instructions, and when the computer-executable instructions are executed by a processor, they are used to execute the method of any one of claims 1 to 17, 19 to 33, and 35 to 37.

40. A computer program product, characterized in that Comprising a computer program for performing the method of any one of claims 1 to 17, 19 to 33, 35 to 37 when the computer executable instructions are executed by a processor.

Images