TW202214030A - Radio access method, user equipment, and base station - Google Patents

Abstract

A user equipment (UE) executes a radio access method. The aforementioned UE being an extended device type UE obtains, from a base station, connection indication information of a certain device type represented by device type related information of the aforementioned extended device type UE, determines an initial access scheme based on the aforementioned connection indication information, and performs an initial access procedure with the aforementioned base station according to the aforementioned initial access scheme.

Description

Radio access method, user equipment and base station

The present invention relates to the field of communication systems, and in particular, to a radio access method, user equipment, and base station.

Standards and technologies for wireless communication systems, such as third-generation (3G) mobile phones, are well known. This 3G standard and technology was developed by the Third Generation Partnership Project (3GPP). Third-generation wireless communications are widely developed to support jumbo cell phone communications. Communication systems and networks have developed into a broadband and mobile system. In a cellular wireless communication system, User Equipment (UE) is connected to a Radio Access Network (RAN) through a wireless link. The RAN includes a set of Base Stations (BSs) that provide wireless connections to user equipment in cells covered by the base stations, and an interface with the Core Network (CN) that provides overall network control. It will be appreciated that the RAN and CN each perform functions related to the overall network. The Third Generation Partnership Project developed the so-called Long Term Evolution (LTE) system, namely the Evolved Universal Mobile Telecommunication System Territorial Radio Access Network (E-UTRAN), Used in mobile access networks where a base station called an evolved NodeB (eNodeB or eNB) supports one or more macro cells. More recently, LTE is moving further towards so-called 5G or New Radio (NR) systems, in which one or more cells are supported by base stations called gNBs.

technical problem:

Reduced Capability (RedCap) devices are extended types of NR devices that can be applied to Industrial Wireless Sensor Networks (IWSN), smart cities, and wearable use cases. IWSN services have higher requirements than Low-Power Wide-Area Network (LPWAN) such as LTE-M or Narrow Band Internet of Things (NB-IoT), but lower than ultra-reliable and low Delayed communication (Ultra-Reliable And Low Latency Communication, URLLC) and enhanced mobile broadband (enhanced mobile broadband, eMBB). Details and specific requirements for different application examples are described in 3GPP TR 22.804, TS 22.104, TR 22.832 and TS 22.261.

To support RedCap NR devices, the following technical issues have been identified: l How to define and limit device access for this reduced capability - Consider defining a limited set of one or more device types, and consider how to ensure that these device types are only used for predetermined use cases. l How to define a function that allows networks and network operators to explicitly identify devices with reduced capabilities and, if necessary, to allow operators to restrict access operations initiated from the aforementioned RedCap NR devices.

An object of the present disclosure is to propose a radio access method, user equipment and base station.

In a first aspect, an embodiment of the present invention provides a radio access method executable in a base station, comprising: provide connection indication information for a specific device type represented by the device type related information for the user equipment (UE) of the extended device type; and According to the initial access scheme of the above-mentioned extended equipment type UE, the initial access procedure is performed with the above-mentioned extended equipment type UE.

In a second aspect, an embodiment of the present invention provides a radio access method executable in a user equipment (UE), comprising: Obtain, from the base station, the connection indication information of the specific device type represented by the device type related information of the above-mentioned extended device type UE; and determining an initial access plan based on the above connection indication information; and According to the above-mentioned initial access scheme, an initial access procedure is performed with the above-mentioned base station.

In a fifth aspect, an embodiment of the present invention provides a base station comprising a processor configured to invoke and execute a computer program stored in a memory, so as to cause a device mounted with the above chip to execute the above disclosure Methods.

In a sixth aspect, an embodiment of the present invention provides a user equipment (UE) comprising a processor configured to invoke and execute a computer program stored in a memory, so as to cause the device on which the above chip is installed to execute the above public method.

The disclosed methods can be programmed as computer-executable instructions stored in a non-transitory computer-readable medium. The non-transitory computer-readable medium, when loaded into a computer, instructs a processor of the computer to perform the disclosed method.

Non-transitory computer-readable media may include at least one of the group consisting of: hard disks, CD-ROMs, optical storage devices, magnetic storage devices, read-only memory, programmable read-only memory, erasable Erasable Programmable Read Only Memory (EPROM), Electrically Erasable Programmable Read Only Memory (EEPROM), and Flash Memory.

The disclosed methods can be programmed as a computer program product that causes a computer to perform the disclosed methods.

The disclosed methods can be programmed as a computer program that causes a computer to perform the disclosed methods.

Beneficial effects:

The method disclosed above provides: l The mechanism used to define the RedCap UE type. l Mechanism to restrict RedCap UEs to predetermined application instances when accessing telecommunication networks. Therefore, performance degradation caused by RedCap UE operating on eMBB application service can be avoided. l Identify devices of RedCap UE type: This function provides technical effects such as avoiding unnecessary network access attempts of RedCap UEs, reducing UE power consumption, and balancing network load. For example, the above network can distinguish RedCap UEs, and perform relatively loose scheduling and DL/UL data transmission during cell access and random access of RedCap UEs. l Cell-specific resources for RedCap UE include: a) initial access to resources; b) paging resources; and/or c) System information block (SIB) with index one (SIB1) or other system information (OSI) with index one.

One embodiment of the present invention provides RedCap UE identification based on various UE identification schemes during the initial access phase. One embodiment of the present invention provides RedCap UE identification based on various UE ID provisioning schemes during the RRC_IDLE and RRC_CONNECTED states. One embodiment of the present invention provides restricted access based on RedCap UE specific cell barring and access control. One embodiment of the present invention provides initial access resource management for RedCap UEs. One embodiment of the present invention provides adjustment of the initial DL or UL bandwidth part (BWP) for RedCap UEs.

One embodiment of the present invention provides a good effect of maintaining coexistence operation of NR RedCap UEs and NR Legacy UEs. One embodiment of the present invention allows operators to restrict access to NR RedCap UEs, ensure that NR RedCap UE types are only used for predetermined application instances, and reduce power consumption of NR RedCap UEs due to unnecessary cell access. In one embodiment of the present invention, the above-mentioned network can distinguish between RedCap UEs and non-RedCap UEs, and perform relaxed scheduling and DL/UL data transmission in cell access and random access procedures of RedCap UEs.

The technical matters, structural features, achieved objects and effects of the embodiments of the present invention will now be described in detail as follows with reference to the accompanying drawings. Specifically, the terms in the embodiments of the present invention are only for the purpose of describing a certain embodiment, rather than for limiting the present invention.

The device types in the above description may include various UE types, such as legacy UE types and non-legacy UE types. The aforementioned non-legacy UE types may be referred to as extended UE types, and may include the aforementioned reduced capability (RedCap) UE types or any other device types. Examples of other device types include Narrowband Internet of Things (NB-IoT), Machine Type Communication (MTC), or Low Power Wide Area Network (LPWAN) UEs.

Referring to Figure 1, a telecommunications system comprising a UE 10a, a UE 10b, a base station (BS) 20a and a network entity device 30 performs the disclosed method according to one embodiment of the present invention. Shown in Figure 1 is illustrative and not limiting, the system may include more UE, BS and CN entities. Connections between equipment and equipment elements are shown in the diagram as lines and arrows. The above-mentioned user equipment 10a may include a processor 11a, a memory 12a, and a transceiver 13a. The above-mentioned user equipment 10b may include a processor 11b, a memory 12b, and a transceiver 13b. The base station 20a may include a processor 21a, a memory 22a and a transceiver 23a. The above-mentioned network entity device 30 may include a processor 31 , a memory 32 , and a transceiver 33 . Each of the aforementioned processors 11a, 11b, 21a and 31 may be configured to implement the functions, routines and/or methods described in the description. The various layers of the Radio Interface Protocol may be implemented in the processors 11a, 11b, 21a and 31 described above. Each of the aforementioned memories 12a, 12b, 22a, and 32 is operable to store various programs and information for operating the associated processor. Each of the aforementioned transceivers 13a, 13b, 23a and 33 is operatively coupled to a connected processor to transmit and/or receive radio or wireline signals. The aforementioned base station 20a may be one of an eNB, a gNB or other type of radio node, and may configure radio resources for the aforementioned UE 10a and UE 10b. The above telecommunication system includes a plurality of 14 groups of UEs belonging to the extended UE type and a plurality of 15 groups of UEs belonging to the traditional UE type. The UEs belonging to the above-mentioned extended UE types in group 14 include UE 10a, while the UEs belonging to legacy UE types in group 15 include UE 10b.

Each of the aforementioned processors 11a, 11b, 21a, and 31 may include an application-specific integrated circuit (ASIC), other chip sets, logic circuits, and/or data processing devices. Each of the above-mentioned memories 12a, 12b, 22a and 32 may include a read-only memory (ROM), a random access memory (RAM), a flash memory, a memory card, a storage medium and/or other storage devices. Each of the above transceivers 13a, 13b, 23a and 33 may include a base frequency circuit and a radio frequency (RF) circuit to process radio frequency signals. When the present embodiment is implemented in software, the techniques described herein may be implemented using modules, programs, functions, entities, etc. that perform the functions described herein. These modules can be stored in memory and executed by the processor. The aforementioned memories may be implemented within the processor or external to the processor, where those aforementioned memories may be communicatively coupled to the processor by various means known in the art.

The above-mentioned network entity device 30 may be a node in the CN. CN may include LTE CN or 5G core (5GC), which includes User Plane Function (UPF), Session Management Function (SMF), Mobility Management Function (AMF), unified profile Unified Data Management (UDM), Policy Control Function (PCF), Control Plane (CP)/User Plane (UP) separation (CP/UP separation, CUPS), authentication server (Authentication Server, AUSF), Network Slice Selection Function (NSSF), and Network Exposure Function (NEF).

2, a radio access method for extended user equipment (UE) types may be performed in a base station (BS), eg, gNB 20, and extended equipment type UEs, eg, UE 10. An example of the above-described extended UE types may include reduced capability device type (RedCap) UEs. The device types of the above-mentioned RedCap UE types may be referred to as RedCap UEs. The above-mentioned legacy UE types may be referred to as legacy UEs. An example of the above-mentioned gNB 20 may include the above-mentioned BS 20a. An example of the aforementioned UE 10 may include the aforementioned RedCap UE 10a. Note that even though the above-mentioned gNB is described below as an example of a base station, the above-mentioned radio access method disclosed above can also be implemented in any other type of base station, such as an eNB or a beyond 5G base station. Examples of the above-mentioned extended UE types of UEs may include RedCap UEs, such as UE 10a. Examples of UEs in the above description may include one of the above UE 10a or UE 10b. Uplink (UL) transmission of control signals or data may be a transmission operation from the UE to the base station. Downlink (DL) transmission of control signals or data may be a transmission operation from the base station to the UE.

The above-mentioned UE provides equipment type related information of the extended equipment type UE (S1). The gNB receives equipment type related information of the extended equipment type UE (S2), and provides resource configuration for the extended equipment type UE based on the equipment type related information of the extended equipment type UE (S3). The above-mentioned gNB performs an initial access procedure with the above-mentioned extended equipment type UE according to the above-mentioned resource configuration of the above-mentioned extended equipment type UE (S4). The above-mentioned UE performs an initial access procedure with the above-mentioned gNB according to the above-mentioned resource configuration of the above-mentioned extended equipment type UE (S5).

The above-mentioned extended equipment type UE includes reduced capability user equipment (RedCap UE). The above-mentioned equipment type related information may explicitly include the UE identification information, equipment type or UE capability of the above-mentioned extended equipment type UE. The above-mentioned equipment type related information may include a predetermined preamble, a predetermined Physical Random Access Channel (PRACH) resource, a predetermined initial DL BWP or an initial UL BWP, so that the above-mentioned extended equipment type UE can The network sends the signal of the device type or UE capability, and the network can identify the device type or UE capability of the extended device type UE based on the device type related information. The above device types may be determined based on newly defined UE types or UE categories different from legacy UEs. The above-mentioned device type may be determined according to at least one newly defined UE capability which is different from the legacy UE. The above device types may be determined according to the UE capability parameter set for legacy UEs.

One embodiment of the extended device type may include a RedCap UE type, and one embodiment of the above-described extended device type of UE may include a RedCap UE of the aforementioned RedCap UE type. The aforementioned extended device types, such as the aforementioned RedCap UE types, may be defined in the telecommunication network using new UE types (ie, new UE categories) or new UE capability sets. The aforementioned telecommunication network may be a 3GPP compliant network. In the above description, the above-mentioned telecommunication network is referred to as a network, and may include a RAN and a CN, at least one of the above-mentioned RAN or the above-mentioned CN, or at least one of the above-mentioned base station 20a or the above-mentioned network entity device 30 . The implementation of the above-mentioned network for handling the above-mentioned extended device type (eg, the above-mentioned RedCap UE) represented by the above-mentioned new UE type and the above-mentioned new UE capability set is described in detail below. l Scheme 1: Define the above-mentioned extended device type, such as the above-mentioned RedCap UE type, as a new UE type or a new UE category.

For example, two or more new UE types may be defined for the RedCap UE types described above for RedCap UEs. In one embodiment, one RedCap UE type includes the lower complexity RedCap UE device type. One or more low-complexity RedCap UEs can use a new initial access scheme, for example, using a dedicated initial DL or UL bandwidth part (BWP) or dedicated radio resources for initial access, different from traditional NR initial storage. Take the DL/UL BWP or radio resources of the scheme. Examples and definitions of the above legacy NR initial access schemes are defined in TS38.213. In one embodiment, a RedCap UE type includes a higher complexity RedCap UE device type. One or more of the higher complexity RedCap UEs may use the legacy initial access scheme, which is the same as that described above for legacy UEs. l Scheme 2: Use the existing NR capability framework to define the above-mentioned extended device types, such as the above-mentioned RedCap UE type.

The above-mentioned UE capability of the above-mentioned extended equipment type UE may be stored in a mobility management function (AMF), the above-mentioned UE transmits the UE identification information of the above-mentioned extended equipment type UE, and the above-mentioned UE identification information is associated with the above-mentioned equipment type related information in the above-mentioned AMF. . The parameters and definitions used to represent NR capabilities are described in TS38.306. In one embodiment, the network defines one or more new capabilities dedicated to RedCap UEs in addition to existing NR capabilities, and uses the new capabilities and/or a combination of the new capabilities and current NR capabilities for RedCap UEs Defines the above RedCap UE type. In one embodiment, the aforementioned network uses a UE capability combination of current NR capabilities (ie, a special set of UE capabilities) to define the aforementioned RedCap UE types for RedCap UEs. Note that the above network may associate RedCap UE types with UE capabilities.

Embodiment 0-1:

Referring to FIG. 3 , one embodiment of the initial access of the RedCap UE (ie, the initial access procedure or radio access method of the RedCap UE) includes the following steps. l The above-mentioned network executes the UE capability identification procedure to identify and obtain the UE capability of the above-mentioned UE (S001). l The above-mentioned network determines a device type related to the above-identified UE capability, such as the above-mentioned RedCap UE type, according to the pre-configured mapping table defined by the above-mentioned network (S002). The above-mentioned preconfigured mapping table includes mappings between a plurality of device types and a plurality of UE capabilities. Each of the above preconfigured mapping tables associates a device type with a set of UE capabilities or capabilities. l If two or more device types are configured in the above mapping table, the above network performs RedCap UE type identification to identify the device type of the RedCap UE (S003). For example, the network determines whether the RedCap UE belongs to the device type of the low-complexity RedCap UE or the device type of the high-complexity RedCap UE. l The above-mentioned network determines whether the above-mentioned RedCap UE constitutes the device type of the above-mentioned low-complexity RedCap UE (S004). If the above-mentioned RedCap UE is the device type of the above-mentioned low-complexity RedCap UE, the above-mentioned network determines that the above-mentioned RedCap UE can execute a new initial access scheme of the above-mentioned low-complexity RedCap UE's device type. If the above-mentioned RedCap UE is a device type of the above-mentioned high-complexity RedCap UE, the above-mentioned network determines that the above-mentioned RedCap UE can perform the traditional initial access scheme of the device type of the traditional UE. l If the above-mentioned UE is identified as the device type of the above-mentioned low-complexity RedCap UE, the above-mentioned RedCap UE executes the above-mentioned new initial access scheme of the above-mentioned low-complexity RedCap UE device type (S005) l If the above-mentioned UE is not identified as the device type of the above-mentioned low-complexity RedCap UE, for example, the above-mentioned UE is identified as the above-mentioned device type of the above-mentioned high-complexity RedCap UE, the above-mentioned RedCap UE performs the same as the traditional UE. The above-mentioned initial access scheme ( S006).

Embodiment 1-1: Signaling device type related information during network registration:

Referring to FIG. 4 , an embodiment of the method with RedCap UE identification and configuration disclosed above is described in detail below. The above-mentioned device type related information may be included in an RRC connection request. l Step 1: During network registration, the above network requests or deduces the UE capability (or device type), stores the above UE capability (or device type) in the above AMF, and assigns an identification information to the above UE, It is called UE identification information, and the above-mentioned UE capability (or device type) is associated with the above-mentioned UE identification information allocated to the above-mentioned UE according to the corresponding equipment type mapping (S111). Examples of the above UE identification information may include a Radio Network Temporary Identifier (RNTI) or an International Mobile Subscriber Identification Number (IMSI). l Step 2: When a non-access stratum (NAS) connection is established between the UE and the AMF, the UE provides the UE identification information of the UE to the network in the RRC connection request (S112). The base station receives the UE identification information of the UE in the RRC connection request. l Step 3: The base station retrieves the UE capability (or device type) from the AMF according to the UE identification information (S113). l Step 4: After retrieving the above-mentioned UE capabilities, such as a set of UE capabilities (or device types) of the above-mentioned UEs, the above-mentioned base station configures the supported functions (or device types) for the above-mentioned UEs according to the above-mentioned UE capabilities (or equipment types) of the above-mentioned UEs. S114). Examples of the above UE capabilities may include the above UE's antenna number or bandwidth, or a combination thereof.

Embodiment 1-2: Sending a signal of device type related information in the RRC_CONNECTED state:

When an RRC connection is established between the above-mentioned base station and the above-mentioned extended equipment type UE, the above-mentioned base station sends a query request for the above-mentioned equipment type related information to the above-mentioned extended equipment type UE to the above-mentioned extended equipment type UE. The UE receives a query request for the equipment type related information of the extended equipment type UE from the base station, and transmits the equipment type related information of the extended equipment type UE to the base station in response to the query. The base station receives the equipment type related information of the extended equipment type UE to respond to the query request. For example, when an RRC connection is established between the above-mentioned gNB and the above-mentioned RedCap UE, the above-mentioned gNB sends a query request (for example, UEDeviceTypeEnquiry) about the UE capability (or device type) to the above-mentioned UE, and the above-mentioned UE sends the above-mentioned UE capability (or device type) to the above-mentioned gNB. device type) information (for example, UEDeviceTypeInformation) in response to the above query request.

Embodiment 1-3: Provide device type related information autonomously, for example, when the above-mentioned UE transitions from the RRC idle state (RRC_IDLE) or the RRC inactive state (RRC_INACTIVE) to the RRC connected state (RRC_CONNECTED), the device is delivered during the initial access Type ID. The above-mentioned equipment type related information may include a predetermined preamble, a predetermined physical random access channel (PRACH) resource, a predetermined initial DL BWP or initial UL BWP for the above-mentioned extended equipment type UE, so that the above-mentioned extended equipment type UE can implicitly The above-mentioned equipment type or UE capability signal is sent to the above-mentioned network, and the above-mentioned network can identify the equipment type or UE capability of the above-mentioned extended equipment type UE according to the above-mentioned equipment type related information. During the initial access period, when the above-mentioned extended equipment type UE transitions from the RRC idle state or the RRC inactive state to the RRC connected state, the above-mentioned UE transmits the above-mentioned equipment type related information to the above-mentioned base station. l The above-mentioned UE may autonomously provide its identification information and/or device type ID to the above-mentioned gNB using at least one of the following information: msgA for msg1, msg3 or two-step PRACH. Examples of the above identification information may include RNTI or IMSI. l Option 1: msg1: • In one embodiment, the above-mentioned UE autonomously provides the above-mentioned UE's device type related information, such as UE identification information, UE capability and/or device type ID, in the message msg1 to the above-mentioned gNB. For example, the above-mentioned RedCap UE may implicitly provide device type related information, using a predetermined preamble, a predetermined physical random access channel (PRACH) resource, a predetermined initial DL BWP or an initial UL BWP. A UE with a bandwidth less than 20MHz (eg, the above-mentioned low-complexity RedCap UE) may require the above-mentioned predetermined initial DL/UL BWP of the RedCap UE. l Option 2: msg3: • In one embodiment, the above-mentioned UE autonomously provides the above-mentioned equipment type related information of the above-mentioned UE to the above-mentioned gNB in the message msg3, such as UE identification information, UE capability and/or equipment type ID. Examples of the above-mentioned user identification information may include RNTI or IMSI. For example, when the above-mentioned RedCap UE transitions from the above-mentioned RRC_INACTIVE state or the above-mentioned RRC_IDLE state, the RedCap UE provides the above-mentioned gNB with an RNTI value and/or a device type ID. l Option 3: msg5: • In one embodiment, the above-mentioned UE autonomously provides the above-mentioned UE's device type related information, such as UE identification information, UE capability and/or device type ID, in the msg5 message to the above-mentioned gNB. For example, the RedCap UE provides the above-mentioned identification information, such as Temporary Mobile Subscriber Identity (TMSI), 5G-TMSI, or 5G-S-TMSI and/or device type ID, when the above-mentioned UE transitions from the above-mentioned RRC_IDLE state. l Option 4: msgA of 2-step PRACH: • In one embodiment, the above-mentioned UE autonomously provides the above-mentioned UE's equipment type related information, such as UE identification information, UE capability and/or equipment type ID, in the message msgA sent to the above-mentioned gNB. For example, the above-mentioned RedCap UE implicitly provides the above-mentioned gNB with the device type ID through msgA PRACH. Alternatively, the above-mentioned RedCap UE explicitly provides the above-mentioned gNB with the device type ID through the msgA PUSCH. The above-mentioned PUSCH is called a Physical Uplink Shared Channel (Physical Uplink Shared Channel, PUSCH).

Embodiments 1-4:

The above-mentioned network provides resource configuration for the above-mentioned extended equipment type UE based on the above-mentioned equipment type related information of the above-mentioned extended equipment type UE. For example, after retrieving the above-mentioned equipment type related information of the above-mentioned extended equipment type UE (such as the above-mentioned UE capability or the above-mentioned UE's equipment type), the above-mentioned network, such as the above-mentioned gNB, can be specially established for the above-mentioned RedCap UE after establishing an RRC connection , do one or more of the following for the above RedCap UE: l Configure the functions of the corresponding device types supported above for the above-mentioned RedCap UEs; l Configure coverage enhancement related functions for the above RedCap UEs; l Configure access control or cell restrictions for the above RedCap UEs; l Provide DL or UL BWP metrics for the above RedCap UEs; and l Determine the inter-UE multiplexing scheme between the above-mentioned RedCap UEs and legacy UEs.

When providing the resource configuration, after establishing an RRC connection for the extended equipment type UE, the base station performs one or more operations for the extended equipment type UE based on the equipment type related information of the extended equipment type UE. The above operations will be described in further detail below. l Configure the support functions for the above-mentioned corresponding device types for the above-mentioned RedCap UEs: The aforementioned network may configure the aforementioned supported functions for the aforementioned UE. The above-mentioned support function of the above-mentioned extended equipment type UE is associated with the above-mentioned equipment type related information of the above-mentioned extended equipment type UE in the random access procedure or after establishing an RRC connection for the above-mentioned extended equipment type UE. The above-mentioned supported functions of the above-mentioned UE include one or more of the following: n processing time; n Supported bandwidth; n supported subcarrier spacing (SCS); and n Supported duplex modes. The above-mentioned processing time capability of the above-mentioned UE includes the processing time of one or more of the following UE operations: n Preparation for Physical Downlink Shared Channel (PDSCH) decoding and HARQ-ACK feedback; n PDCCH decoding and PUSCH transmission preparation work; and n Preparation for PDCCH decoding and CSI feedback. According to the processing time capability of the UE, the network allocates processing time to the UE for PDSCH decoding, HARQ-ACK transmission, PUSCH transmission and Channel State Information (CSI) feedback of the UE. Hybrid Automatic Repeat Request (HARQ) feedback is referred to as HARQ-ACK, and can include an acknowledgment (ACK) or a negative acknowledgment (NACK). l Configure coverage enhancement related functions for the above RedCap UEs: The above network may configure coverage enhancement related functions for the above UE. The coverage enhancement related function of the extended equipment type UE is associated with the equipment type related information of the extended equipment type UE during the random access procedure or after establishing an RRC connection for the extended equipment type UE. The aforementioned coverage enhancement related functions of the aforementioned UE are preconfigured, or the aforementioned coverage enhancement related functions of the aforementioned UE are reconfigured by using RRC information or downlink control information (Downlink Control Information, DCI). The above coverage enhancement related functions include one or more of the following: n the number of repeated transmissions of the PUSCH or PUCCH transmission; and n Uplink power control for PUSCH or PUCCH transmission. The above-mentioned network, such as the above-mentioned gNB, can pre-configure the above-mentioned coverage enhancement related functions for the above-mentioned UE, such as repeat transmission times (repetition number) and/or uplink power control, or send RRC messages or downlink control information (DCI) to the above-mentioned UE. ) to configure the above-mentioned coverage enhancement related functions of the above-mentioned UE. l Configure access control or cell restrictions for the above RedCap UEs: The network may configure access control or cell restriction for the UE. The above-mentioned access control or cell restriction of the above-mentioned extended equipment type UE is associated with the above-mentioned equipment type related information in the system block information given to the above-mentioned extended equipment type UE. The above access control or cell restrictions include one or more of the following: n Access identification information of the above-mentioned RedCap UE with a specific device type; n the access class of the above-mentioned RedCap UE with a specific device type; and n Access priority of the above-mentioned RedCap UE with a specific device type. Based on operator policy, the aforementioned network may prevent UEs (eg, aforementioned RedCap UEs and/or legacy UEs) from accessing the aforementioned network using relevant barring parameters identified from aforementioned access attempts for each access attempt from aforementioned UEs Information differs from the access categories above. The network configures the prohibition parameter according to the access identification information and the access type. For example, the above UE is configured with the access identification information listed in TS 22.261, and each access class is defined by a combination of UE-related conditions and access attempt types listed in TS 22.261. In addition, the network may also configure the access priority of the RedCap UE, so as to realize the priority-based cell access in consideration of the system traffic load. l Provide DL/UL BWP indicators for the above RedCap UEs: The aforementioned network may provide the aforementioned UE with a DL or UL BWP indicator. The above-mentioned DL or UL BWP indicator of the above-mentioned extended equipment type UE is associated with the above-mentioned equipment type related information of the above-mentioned extended equipment type UE during a random access procedure or after establishing an RRC connection for the above-mentioned extended equipment type UE. The above DL/UL BWP metrics represent one or more of the following: n The default DL BWP of RedCap UE; n Initial DL/UL BWP of RedCap UE; n Active DL/UL BWP of the RedCap UE; and n RedCap UE's BWP timer. l Determine the inter-UE multiplexing scheme between the above RedCap UE and legacy UE: The above network may determine an inter-UE multiplexing scheme to multiplex the traffic of the RedCap UE and the traditional UE. The above-mentioned inter-UE multiplexing scheme of the above-mentioned extended equipment type UE is associated with the above-mentioned equipment type related information of the above-mentioned extended equipment type UE during a random access procedure or after establishing an RRC connection for the above-mentioned extended equipment type UE. The above multiplexing schemes include: n Scheme 1: The above network configures shared radio resources for the above RedCap UE and legacy UE: In an inter-UE multiplexing scheme, the RedCap UE and the legacy UE share the same radio resources allocated by the network. The above-mentioned radio resources include time-domain and frequency-domain radio resources allocated by the above-mentioned network (eg, the above-mentioned gNB). n Scheme 2: The above network configures dedicated radio resources for the RedCap UE: In an inter-UE multiplexing scheme, the aforementioned network (eg, the aforementioned gNB) allocates different sets of radio resources to the aforementioned RedCap UEs and legacy UEs. That is to say, in addition to allocating radio resources to traditional UEs, the above-mentioned network also allocates dedicated radio resources to the above-mentioned RedCap UEs. The above-mentioned radio resources include radio resources in the time domain and the frequency domain.

Implementation 2: Access Restrictions:

Referring to FIG. 5 , the above-mentioned gNB provides connection indication information of a specific device type represented by the above-mentioned equipment type related information of the above-mentioned extended equipment type UE ( S10 ). The above-mentioned specific equipment type includes the equipment type of the above-mentioned extended equipment type UE or the equipment type of the traditional UE. The above-mentioned connection indication information for a specific device type is transmitted in a broadcast information block, such as a Master Information Block (MIB) or SIB1. For the broadcast information in the physical broadcast channel (Physical Broadcast Channel, PBCH), in order to carry the connection indication information, the BCCH-MessageType of the BCCH-BCH-Message can be set to messageClassExtension or MIB. The UE obtains the connection indication information of the specific equipment type represented by the equipment type related information of the extended equipment type UE from the base station (S11), and determines an initial access plan according to the connection indication information (S12). The UE performs an initial access procedure with the gNB according to the initial access scheme ( S13 ). The above-mentioned gNB performs an initial access procedure according to the above-mentioned initial access scheme and the above-mentioned extended equipment type UE (S14).

The above-mentioned initial access scheme of the RedCap UE is related to the connection indication information and the configuration related to various initial access signals, parameters, operations, phases, radio resources, configuration, identification information, access restrictions and features of the above-mentioned RedCap UE. The above-mentioned connection indication information may include the above-mentioned resources, identification information, access restrictions and characteristics of the signal or configuration, and may be transmitted in the BCCH-BCH-Message, SSB, MIB, type 0 PDCCH, SIB1 and OSI to the above-mentioned extended equipment type UE. middle. The aforementioned parameters may include random access backoff parameters. Such resources may include access to networks, cells or frequencies. The implementation of the above-mentioned network to provide access restrictions to the above-mentioned RedCap UE is described in detail below. The above access restrictions include cell reservation, connection request rejection, and random access rejection.

Embodiment 2-1: Cell reservation (before sending RRC connection request):

The above-mentioned connection indication information includes access control information, and the above-mentioned extended equipment type UE decides whether to send a connection request according to the information. In one embodiment, the connection indication information of the specific device type in the broadcast information block may include cell prohibition information, access information of the specific device type of the current cell or at least one cell of a plurality of cells other than the current cell. Controls censorship of information or access to prohibited information. Embodiments of the above-described network to perform cell retention are described in detail below. Cell reservation includes broadcasting access control information in broadcast information blocks, such as master information blocks (MIBs) or SIBs. The above access control information may be referred to as a cell reservation instruction, and includes cell prohibition information, access control check information, and access prohibition information. When determining the above-mentioned initial access scheme, the above-mentioned extended equipment type UE may determine whether to send a connection request according to the above-mentioned connection indication information. For example, before sending any connection request to the above-mentioned gNB, the above-mentioned RedCap UE may evaluate the broadcast information block sent from the above-mentioned gNB, and determine whether it needs to send a connection request for this target service type (or application case) according to the above-mentioned broadcast information block . A UE's service type is sometimes referred to as the UE's application case described above. Implementations of the cell retention scheme include transmitting one or more of the following broadcast information blocks by the aforementioned network to carry access control information. l MIB; and l SIB1.

The above-mentioned broadcast information block has the parameter BCCH-BCH-MessageType, which can be set as messageClassExtension or MIB for the above-mentioned RedCap UE. Embodiments of cell retention protocols using MIB and SIB1 are detailed below: l MIB: The above network can be represented using broadcast information in the MIB: n Cell barring information for a device type (or service type), the cell barring information is the use of existing barring information elements (barring information elements) or RedCap UE-specific barring information elements (IE), that is, RedCap UE-specific combined use Indicated by cell-inhibited RRC messages. l SIB1: The above network can be represented using the broadcast information in SIB1: n access control check information, the above-mentioned RedCap UE can use the above-mentioned access control check information to determine when access prohibition check needs to be performed on a certain device type (or service type) of the above-mentioned RedCap UE; and/or n Access prohibition information for a device type (or service type), represented by RedCap UE-specific access identification information and/or access class.

The access control check information includes whether access prohibition check is required for the specific device type. That is, the UE 10 needs to decode the access prohibition information only when the access control check information prompts the UE 10 to read the access prohibition information. The above cell retention indications may indicate: l A certain service type or a certain device type of the above-mentioned RedCap UE can or cannot be served in the network; l A certain device type may or may not camp on the current cells of the above gNB; and/or l A certain device type may or may not be camped on other cells using a certain frequency or a different frequency.

The above-mentioned specific device types may include the above-mentioned RedCap UEs and/or the above-mentioned legacy UEs. The broadcast information block includes access control information for the frequency at which the specific device type accesses the current cell or at least one of a plurality of cells other than the current cell.

Embodiment 2-1-1 Example of cell retention step:

Referring to Figure 6, one embodiment of the above-disclosed method using cell retention is described in detail below. l When attempting to perform initial access to the current cell (S211), the above-mentioned RedCap UE evaluates the MIB of the above-mentioned current cell (S212). l The above-mentioned RedCap UE determines whether the above-mentioned cell supports the above-mentioned RedCap service type according to the above-mentioned MIB that has been evaluated (S213). If the above-mentioned cell does not support the above-mentioned RedCap service type, the above-mentioned RedCap UE attempts to perform initial access to other cells according to the information given in the above-mentioned MIB (S215). If the above-mentioned cell supports the above-mentioned RedCap service type, the above-mentioned RedCap UE checks whether the device type of the above-mentioned RedCap UE is prohibited by the current cell according to the above-mentioned cell reservation instruction (S214). If the above-mentioned device type of the above-mentioned RedCap UE has been prohibited by the above-mentioned current cell, the above-mentioned RedCap UE performs the above-mentioned step S215. If the above-mentioned device type of the above-mentioned RedCap UE is not prohibited by the above-mentioned current cell, the above-mentioned RedCap UE evaluates the information in SIB1 (S216). l According to the information in SIB1 (such as access control check information), notify the above-mentioned RedCap UE whether the above-mentioned access prohibition check needs to be performed (S217). If the above-mentioned access prohibition check is not required, the above-mentioned RedCap UE performs initial access in the above-mentioned current cell (S218). If the access prohibition check is required, the RedCap UE performs the access prohibition check by determining whether the service type of the RedCap UE is restricted by the access control in the current cell ( S219 ). If the above-mentioned service type of the above-mentioned RedCap UE is restricted by the above-mentioned access control in the above-mentioned current cell, the above-mentioned RedCap UE performs the above-mentioned S215. If the above-mentioned service type of the above-mentioned RedCap UE is not restricted by the above-mentioned access control of the above-mentioned current cell, the above-mentioned RedCap UE performs the above-mentioned step S218.

Embodiment 2-2: Connection request rejection for RRC connection request:

The connection indication information includes a request rejection of a connection request with a device type message sent from the extended device type UE to the base station. In one embodiment, when obtaining the above-mentioned connection indication information, the above-mentioned extended equipment type UE obtains a request rejection of the connection request with the equipment type sent from the above-mentioned extended equipment type UE to the above-mentioned base station. The above-mentioned gNB performs access restriction according to the connection type requested by the RedCap UE. The above-mentioned connection type is related to the device type of the above-mentioned RedCap UE, and is represented by the access identification information or the access type of the above-mentioned RedCap UE. l The above-mentioned RedCap UE provides the device type (or service type) when transmitting the RRC connection request to the above-mentioned gNB. That is, the above-mentioned RedCap UE sends an RRC connection request RRCConnectionRequest including the above-mentioned device type (or service type) to the above-mentioned gNB. l The above-mentioned gNB decides whether to provide or reject the above-mentioned request for the above-mentioned device type. The above-mentioned gNB sends an RRC connection rejection RRCConnectionReject to the above-mentioned RedCap UE when rejecting the above-mentioned request.

Embodiment 2-3: Random Access Restrictions:

The above-mentioned connection indication information includes the above-mentioned random access restrictions for the specific device type. In one embodiment, when obtaining the connection indication information, the UE of the extended device type obtains the random access restriction of the specific device type from the base station. If PRACH resources are shared between RedCap UE and legacy UE. To protect legacy UEs, the aforementioned network may provide the aforementioned RedCap UEs with one or more of the following settings during random access procedures: l A restricted PRACH preamble; l Restricted PRACH resources; l the reduced maximum number of PRACH attempts; and l Longer random access fallback time.

The above-mentioned restricted preamble is a RedCap UE-specific PRACH preamble, and may include a restricted preamble sequence or preamble format for the above-mentioned RedCap UE. The above-mentioned restricted PRACH resources are the time-frequency radio resources that the above-mentioned RedCap UEs are restricted for transmitting PRACH preambles and signals, and the above-mentioned RedCap UEs can transmit PRACH preambles and signals in the above-mentioned time-frequency radio resources. The maximum number of attempts of the above-mentioned reduced PRACH is represented by the parameter preambleTransMax. The above-mentioned parameter preambleTransMax is the maximum number of random access preamble transmissions performed by the above-mentioned RedCap UE before the above-mentioned RedCap UE declares failure. The above parameter preambleTransMax can be reduced to a smaller value than the conventional UE. The definition of the above parameter preambleTransMax can be found in TS 38.321.

The above network can provide the above-mentioned RedCap UE with a relatively long back-off time by selecting the random access back-off time according to the uniform distribution between 0 and the relatively long back-off parameter PREAMBLE_BACKOFF, so that the above-mentioned RedCap UE can perform preamble retransmission. The definition of the above fallback time can be found in TS 38.321.

Embodiment 3:

The above-mentioned initial access scheme of the above-mentioned extended equipment type UE is related to the configuration and connection indication information of various initial access radio resources and functions of the above-mentioned extended equipment type UE. The above-mentioned connection indication information may include the signaling or configuration of the above-mentioned resources and functions, and may be transmitted for the above-mentioned extended equipment type UE in BCCH-BCH-Message, SSB, MIB, type-0 PDCCH (type-0 PDCCH), SIB1 and OSI The above connection instructions. The above-mentioned initial access radio resources and functions may include control resource set 0 (ie, common control resource set common control resource set, controlResourceSetZero or CORESET#0) of the above-mentioned extended device type UE, search space 0 (ie common search space 0 or searchSpaceZero ), initial UL BWP, initial DL BWP, SIB1, OSI, SI scheduling, PRACH configuration, PRACH preamble, SCS, modulation and coding scheme (MCS), HARQ-ACK scheme, msg2/msg3/msg4 configuration, and fallback parameters. One embodiment of the present invention provides initial access and paging resources for the above-mentioned RedCap UEs, as well as initial access and paging resources for legacy UEs.

Embodiment 3-1: CORESET#0:

The common control resource set is called controlResourceSetZero or CORESET#0. In one embodiment, the above-mentioned network provides the above-mentioned RedCap UE with CORESET#0 resources. The above-mentioned CORESET#0 resources for the above-mentioned RedCap UE may include: l CORESET#0 resources shared by the above-mentioned RedCap UEs and legacy UEs; or l The CORESET#0 resource dedicated to the above-mentioned RedCap UE is separate from the CORESET#0 resource of the traditional UE.

The implementation of the above-mentioned CORESET#0 resource of the above-mentioned RedCap UE is detailed below:

CORESET#0 resources shared by the above RedCap UE and legacy UE: l When the above-mentioned network allocates the CORESET#0 resource shared by the above-mentioned RedCap UE and the traditional UE to the above-mentioned RedCap UE, the above-mentioned network can provide the above-mentioned same Type-0 physical downlink in the MIB for the above-mentioned RedCap UE and the traditional UE Control channel (PDCCH) configuration (eg, pdcch-ConfigSIB1). The above Type-0 PDCCH configuration pdcch-ConfigSIB1 includes the following configurations: n control resource set 0 (i.e. controlResourceSetZero); and n Search space 0 (ie searchSpaceZero). l Separated from the CORESET#0 resource of the traditional UE and dedicated to the CORESET#0 resource of the above-mentioned RedCap UE: When the above-mentioned network allocation is separate from the CORESET#0 resource of the legacy UE and is dedicated to the CORESET#0 resource of the above-mentioned RedCap UE, the above-mentioned network may provide the above-mentioned RedCap UE with another set of pdcch-ConfigSIB1 in the MIB, which is different from the traditional UE's CORESET#0 resource. pdcch-ConfigSIB1 in MIB is different. The above-mentioned RedCap UE receives and uses another set of pdcch-ConfigSIB1 in the above-mentioned MIB, including: n controlResourceSetZero of the above RedCap UE; and n searchSpaceZero for the above RedCap UE.

Embodiment 3-2: Information of System Information Block 1/Other System Information (SIB1/OSI) of RedCap UE:

In one embodiment, the network provides SIB1/OSI for the RedCap UE. The above-mentioned SIB1/OSI for the above-mentioned RedCap UE may include: l SIB1 content specific to RedCap UE; and l A set of OSI content dedicated to RedCap UE.

The above-mentioned connection indication information includes SIB1 or OSI, and the SIB1 or OSI includes a newly defined SIB1 or a newly defined SIB1 or an existing system information radio network temporary identifier (SI-RNTI) associated with the existing system information radio network temporary identifier (SI-RNTI). OSI content. In one embodiment, when obtaining the above-mentioned connection indication information, the above-mentioned extended equipment type UE uses the existing SI-RNTI of the above-mentioned extended equipment type UE to obtain SIB1 or OSI including SIB1 or OSI content newly defined for the extended equipment type UE. In another embodiment, when obtaining the connection indication information, the extended equipment type UE obtains the SIB1 or OSI including the existing SIB1 or OSI content of the extended equipment type UE using the specific SI-RNTI of the extended equipment type UE. In this case, the above-mentioned network may define and provide a separate SI-RNTI for the above-mentioned RedCap UE, called R-SI-RNTI, and provide the above-mentioned R-SI-RNTI to the above-mentioned RedCap UE. The above-mentioned RedCap UE uses the above-mentioned R-SI-RNTI to receive, de-scrambling, and obtain the above-mentioned SIB1 content dedicated to the RedCap UE and the above-mentioned OSI content dedicated to the RedCap UE. The above-mentioned SIB1 content or OSI content dedicated to RedCap UE may include one or more of the following: l PRACH configuration; l System Information (SI) scheduling information; and l Initial DL/UL BWP indication.

Embodiment 3-3: PRACH resources for RedCap UEs:

The foregoing network may provide a set of dedicated PRACH resources for the foregoing RedCap UE. For example, the above-mentioned dedicated PRACH resource set may include: l time-domain and frequency-domain radio resources for PRACH (i.e., a set of PRACH configurations for RedCap UEs); and/or l A preamble sequence (that is, a set of preambles for the above-mentioned RedCap UE). l A preamble format (that is, a set of preamble formats for the above-mentioned RedCap UE).

Embodiment 3-4: msg2/msg3/msg4 configuration for RedCap UE: The above connection indication information includes the RAR in msg2 associated with the RA-RNTI for the UE of the extended device type. In one embodiment, when determining the above-mentioned initial access scheme, the above-mentioned extended equipment type UE obtains a specific RA-RNTI for the above-mentioned extended equipment type UE to receive the RAR in msg2 of the above-mentioned extended equipment type UE. The above-mentioned RAR content in the above-mentioned msg2 of the above-mentioned extended equipment type UE may be different from the RAR in the above-mentioned msg2 of the conventional UE. The above-mentioned network may define and provide the configuration of msg2, msg3 and/or msg4 for the above-mentioned RedCap UE. The aforementioned network may define a random access RNTI (RA-RNTI) specific to the aforementioned RedCap UE, referred to as R-RA-RNTI. The above-mentioned RedCap UE uses the calculated R-RA-RNTI to receive and descramble codes, and obtain the above-mentioned random access response (random access response, RAR) dedicated to the RedCap UE. The above-mentioned separate RARs in msg2 dedicated to RedCap UEs may include: l msg3 PUSCH scheduling for the above-mentioned RedCap UE; and/or l The fallback parameter for the next PRACH transmission of the above RedCap UE.

The above-mentioned connection indication information includes the configuration of msg2, msg3 and/or msg4 for the above-mentioned extended equipment type UE. The configuration of msg2, msg3 and/or msg4 for the above-mentioned RedCap UE may be different from the above-mentioned configuration for the legacy UE and may include: l Radio resource allocation; l DL/UL BWP; l Subcarrier spacing (SCS); l Modulation and Coding Scheme (MCS) or repeat transmission for enhanced coverage (e.g. repeat transmission parameters for msg3 transmission); and/or l HARQ-ACK transmission scheme (for example, the number of repeated transmissions of PUCCH carrying HARQ-ACK or the HARQ-ACK feedback time related to the reception time of msg4 information.

The above-mentioned broadcast information block may include the initial UL BWP for the above-mentioned extended equipment type UE to send uplink information or hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback during initial access. The above-mentioned HARQ-ACK feedback scheme includes one or more of the following: l The number of repeated transmissions of the PUCCH carrying the HARQ-ACK; and l HARQ-ACK feedback time relative to the reception time of the msg4 message.

Embodiment 3-5: Paging resources for RedCap UEs:

The above connection indication information includes newly defining paging information associated with an existing paging RNTI (P-RNTI) for the extended equipment type UE or using the existing paging information associated with a specific P-RNTI of the extended equipment type UE. In one embodiment, when obtaining the above-mentioned connection indication information, the above-mentioned extended equipment type UE obtains the above-mentioned paging information newly defined for the above-mentioned extended equipment type UE by using the above-mentioned existing P-RNTI, or uses the specific P-RNTI of the above-mentioned extended equipment type UE. The RNTI obtains the above existing paging information. The foregoing network may define and provide paging resources for the foregoing RedCap UE. The aforementioned network may define and provide a P-RNTI specific to the aforementioned RedCap UE, called R-P-RNTI, and provide the aforementioned R-P-RNTI to the aforementioned RedCap UE. The above-mentioned RedCap UE uses the above-mentioned R-P-RNTI to receive, descramble and obtain the above-mentioned redcap UE-specific paging. The above-mentioned paging resources for the above-mentioned RedCap UE may include an initial DL BWP dedicated to the above-mentioned RedCap UE, different from the initial DL BWP for the legacy UE. The above-mentioned RedCap UE receives one or more of the following messages in the above-mentioned initial DL BWP dedicated to the above-mentioned RedCap UE: l paging information; and l Paging the short message in the DCI.

Embodiment 4: Initial configuration of RedCap UE:

The above-mentioned initial access scheme of the above-mentioned extended equipment type UE is related to the characteristics of the above-mentioned extended equipment type UE and the configuration connection indication information of various initial access radio resources. The above-mentioned connection indication information may include the signaling or configuration of the above-mentioned resources and functions, and the above-mentioned connection indication information may be transmitted in BCCH-BCH-Message, SSB, MIB, Type 0 PDCCH, SIB1 and OSI for the above-mentioned extended equipment type UE. The above-mentioned initial access radio resources and characteristics may include CORESET#0, searchSpaceZero, initial UL BWP, and initial DL BWP of the above-mentioned extended device type UE.

Embodiment 4-1: Initial DL BWP handover:

The above-mentioned RedCap UE performs the initial DL BWP handover after receiving the Type-0 PDCCH. The above-mentioned initial DL BWP of the above-mentioned extended equipment type UE may include the above-mentioned initial DL BWP that is the same as that of the legacy UE or an initial DL BWP that is different from that of the legacy UE. In one embodiment, if the bandwidth of the RedCap UE is larger than the synchronization signal block (SSB) and CORESET#0, the RedCap UE can share the same initial DL BWP with the legacy UE. Likewise, the above-mentioned RedCap UE and legacy UE may share the same SSB and CORESET#0. In one embodiment, the above-mentioned RedCap UE uses the same cell-defining SSB as the legacy UE to perform cell search and find the location of the above-mentioned initial DL BWP. In one embodiment, the above-mentioned RedCap UE uses the same CORESET#0 as that of the legacy UE, and the configuration of the above-mentioned CORESET#0 of the above-mentioned RedCap UE is the same as that provided by pdcch-ConfigSIB1 in the MIB to provide the configuration of CORESET#0 of the legacy UE. The above MIB includes the configuration of CORESET#0 resources of the above-mentioned extended equipment type UE, which is used to monitor the PDCCH of SIB1, receive the paging information of the above-mentioned extended equipment type UE or the downlink information of the above-mentioned extended equipment type UE during initial access. The above-mentioned RedCap UE uses pdcch-ConfigSIB1 to find the location of the Type-0 PDCCH common search space.

The above-mentioned RedCap UE uses the SI-RNTI for the above-mentioned RedCap UE to monitor and receive the Type-0 PDCCH. The above-mentioned SI-RNTI of the above-mentioned RedCap UE may include the same SI-RNTI as the legacy UE or a RedCap UE-specific SI-RNTI, such as the above-mentioned R-SI-RNTI. l Option 1: The above SI-RNTI is the same as the traditional UE: In the embodiment where the above-mentioned SI-RNTI of the above-mentioned RedCap UE is the same as the SI-RNTI of the traditional UE, the specific DL/UL BWP of the RedCap UE can be determined by the bandwidth part indicator (DL/UL BWP indicator) in the DCI of the Type-0 PDCCH start up. The above-mentioned network may provide the above-mentioned DL/UL BWP indicator. The above connection indication information includes the DL BWP indicator in the downlink control information (DCI) of the physical downlink control channel (PDCCH) type 0 or the DL BWP indicator in msg2 or msg4. The above-mentioned initial DL BWP of the above-mentioned extended equipment type UE is switched according to the above-mentioned DL BWP indicator in the DCI of the Type-0 PDCCH or in msg2 or msg4. Likewise, the initial UL BWP of the above-mentioned extended equipment type UE may be indicated using the UL BWP indicator in the DCI of the Type-0 PDCCH or the UL BWP indicator in msg2 or msg4. The above-mentioned initial UL BWP of the above-mentioned extended equipment type UE may be the same or different from that of the traditional UE. l Option 2: RedCap UE-specific SI-RNTI (eg R-SI-RNTI): In one embodiment, the above-mentioned SI-RNTI of the above-mentioned RedCap UE is the above-mentioned RedCap UE-specific SI-RNTI (eg, R-SI-RNTI), and the above-mentioned RedCap UE-specific DL/UL BWP may be scrambled by the above-mentioned R-SI-RNTI The DL/UL BWP indicator in DCI is activated.

If the above-mentioned DL BWP indicator is not defined in the DCI, the above-mentioned RedCap UE uses the same initial DL BWP as the legacy UE to receive SIB1. If the above-mentioned DL BWP indicator is defined in an instance of DCI, and the above-mentioned DL BWP indicator indicates that the initial DL BWP of the above-mentioned RedCap UE is different from the initial DL BWP of the legacy UE, the above-mentioned DL BWP is activated by the above-mentioned indicator, and the above-mentioned activated The resources used by the above-mentioned RedCap UE to receive SIB1 in the DL BWP are also provided in the corresponding DCI, for example, in the above-mentioned DCI example, the above-mentioned RedCap UE performs DL BWP handover and receives the RedCap UE-specific SIB1 in the above-mentioned RedCap UE-specific DL BWP .

Embodiment 4-1-1: Example of the above-mentioned initial DL BWP handover procedure of the RedCap UE:

Referring to FIG. 7 , one embodiment of the above-disclosed method for initial DL BWP handover of the above-mentioned RedCap UE is described in detail below. l The above-mentioned RedCap UE performs a cell search (S411) using the same above-mentioned cell definition SSB as the conventional UE. l The above-mentioned RedCap UE obtains the resource of CORESET#0 configured by pdcch-ConfigSIB1 in the MIB, which is the same as that of the traditional UE (S412). The above MIB is sent from the above gNB to the above RedCap UE. l The above-mentioned RedCap UE monitors the Type-0 PDCCH in the above-mentioned CORESET#0, and receives DCI from the above-mentioned gNB using a new SI-RNTI (such as the above-mentioned R-SI-RNTI) specific to the above-mentioned RedCap UE (S413). l The above-mentioned RedCap UE determines whether to perform the initial DL BWP handover according to the DL BWP in the above-mentioned DCI (S414). When the above-mentioned DL BWP indicator in the above-mentioned DCI indicates that the above-mentioned gNB has allocated a new initial DL BWP to the above-mentioned RedCap UE, the above-mentioned RedCap UE decides to perform the initial DL BWP handover to the above-mentioned new initial DL BWP. When the above-mentioned BWP indicator in the above-mentioned DCI does not indicate a new initial DL BWP for the above-mentioned RedCap UE, the above-mentioned RedCap UE decides not to perform the initial DL BWP handover and uses the same initial DL BWP as the legacy UE. l If the above-mentioned RedCap UE decides to perform the initial DL BWP handover, the above-mentioned RedCap UE receives the above-mentioned RedCap UE-specific SIB1 in the above-mentioned new initial DL BWP allocated to the above-mentioned RedCap UE by the above-mentioned gNB (S416). If the above-mentioned RedCap UE decides not to perform the initial DL BWP handover, the above-mentioned RedCap UE receives SIB1 in the same initial DL BWP as the legacy UE (S415).

Embodiment 4-2: DL BWP handover after receiving MIB:

In one embodiment, the MIB of the above-mentioned extended device type UE may be transmitted on the same or different radio resources of the cell-defined SSB as the legacy UE. The above-mentioned extended equipment type UE obtains the initial DL/UL BWP of the above-mentioned extended equipment type UE based on the above-mentioned cell-defined SSB. The above-mentioned cell-defined SSB points to the initial DL/UL BWP of the above-mentioned extended equipment type UE. Alternatively, the above-mentioned MIB for the above-mentioned extended equipment type UE may be transmitted on the radio resources of the non-cell-defined SSB associated with the legacy UE. The above-mentioned extended equipment type UE obtains the initial DL/UL BWP of the above-mentioned extended equipment type UE based on the above-mentioned non-cellular defined SSB. The above-mentioned non-cell-defined SSB points to the initial DL/UL BWP of the above-mentioned extended equipment type UE. In one embodiment, the bandwidth of the above-mentioned RedCap UE is larger than the SSB but smaller than CORESET#0, and the above-mentioned RedCap UE can perform DL/UL BWP switching after receiving the MIB. l The above RedCap UE performs cell search and locates the initial DL/UL BWP. The above-mentioned RedCap UE can use the same above-mentioned cell-defining SSB as the traditional UE for cell search. l The above-mentioned RedCap UE obtains the CORESET#0 resource according to the configuration different from that of the traditional UE. The location of CORESET#0 of the above-mentioned RedCap UE is provided by the MIB, and may be within the above-mentioned initial DL BWP, the same as the legacy UE, or within a RedCap UE-specific DL BWP different from the initial DL BWP of the legacy UE. In one embodiment, the CORESET#0 resource of the above-mentioned RedCap UE is located within the same initial DL BWP of the legacy UE. In one embodiment, the CORESET#0 resource of the above-mentioned RedCap UE is located in a RedCap UE-specific DL BWP that is different from the initial DL BWP of the legacy UE. In one embodiment, the DL BWP indicator in the MIB may indicate the aforementioned RedCap UE-specific DL BWP. n If the DL BWP indicator is not defined in the MIB, the above RedCap UE uses the same initial DL BWP as the legacy UE to locate CORESET#0. The initial DL BWP of the legacy UE is determined according to the above-mentioned resource location of CORESET#0. n If the RedCap UE-specific CORSET#0 resource is indicated in the above MIB, the above-mentioned RedCap UE-specific initial DL BWP can be derived from the above-mentioned RedCap UE-specific CORESET#0 resource location. n If the DL BWP indicator is defined in the MIB, and indicates that the additional DL BWP of the above-mentioned RedCap is different from the initial DL BWP of the legacy UE, the above-mentioned additional DL BWP of the above-mentioned RedCap is activated, and the above-mentioned gNB also provides the above for the above-mentioned activation The DL BWP locates the CORESET#0 resource. The above-mentioned additional DL BWP for the above-mentioned RedCap UE is referred to as the above-mentioned RedCap UE-specific DL BWP. l If the above CORESET#0 resource is located in the RedCap UE-specific DL BWP, the above-mentioned RedCap UE monitors the Type 0 PDCCH to receive SIB1 in the above-mentioned RedCap UE-specific DL BWP.

Embodiment 4-2-1: Example of DL BWP switching procedure after receiving MIB:

Referring to FIG. 8 , one embodiment of the above disclosed method of the DL BWP handover procedure after receiving the MIB will be described in detail below. l The above RedCap UE uses the cell definition SSB to perform cell search (S421). l The above-mentioned RedCap UE evaluates the MIB, which has a DL BWP indicator field, which is used to determine the above-mentioned CORESET#0 radio resources (referred to as CORESET#0 resources). The above-mentioned Redcap UE locates CORESET#0 according to the above-mentioned DL BWP indicator in the MIB (S422). l The above-mentioned RedCap UE determines whether the radio resource of the above-mentioned CORESET#0 is located in another DL BWP different from the original DL BWP of the legacy UE (S423). When the DL BWP indicator in the MIB indicates the new DL BWP of the RedCap UE, the RedCap UE determines that the radio resource of CORESET#0 is located in the new DL BWP of the RedCap UE, which is different from the initial DL BWP of the legacy UE. When the DL BWP indicator does not indicate the new DL BWP of the RedCap UE or the MIB does not have the DL BWP indicator, the RedCap UE determines that the radio resource of the CORESET#0 is located in the initial DL BWP of the legacy UE. l If the above-mentioned radio resource of the above-mentioned CORESET#0 is located in the above-mentioned new DL BWP of the above-mentioned RedCap UE that is different from the above-mentioned initial DL BWP, it is assumed that the above-mentioned new DL BWP is activated. The above-mentioned RedCap UE performs DL BWP handover to the above-mentioned activated DL BWP, locates CORESET#0 in the above-mentioned activated DL BWP (S425), and receives SIB1 in the above-mentioned activated DL BWP (S427). If the above-mentioned radio resource of the above-mentioned CORESET#0 is located within the initial DL BWP of the legacy UE, the above-mentioned RedCap UE locates CORESET#0 in the above-mentioned same initial DL BWP of the legacy UE (S424), and in the initial DL BWP of the legacy UE SIB1 is received (S426). l In S426 or S427, respectively, the above-mentioned RedCap UE receives the SIB1 defined for the above-mentioned RedCap UE by using the above-mentioned SI-RNTI or a specific RNTI (for example, the above-mentioned R-SI-RNTI) in the corresponding DL BWP.

Embodiment 4-3: Initial DL/UL BWP selection based on cell-defined SSB detached from legacy UE: l The aforementioned network may configure cell-defined SSB for the aforementioned RedCap UE to achieve one or more of the following goals: The bandwidth of CORESET#0 of the UE provides services for the above-mentioned RedCap UEs; n The above-mentioned RedCap UEs are served with the bandwidth of the SSB smaller than the traditional UE, but larger than the bandwidth of the specifically defined SSB of the above-mentioned RedCap UEs. n serve the aforementioned RedCap UEs with loose UE processing time during the initial access procedure; and n avoid initial access congestion with legacy UEs. l The above-mentioned RedCap UE performs a cell search on the cell-defined SSB defined for the above-mentioned RedCap UE, thus obtaining the above-mentioned initial DL/UL BWP position after the above-mentioned cell search. The frequency location of the above-mentioned RedCap-specific SSB can be defined according to the Global Synchronization Channel Number (GSCN) parameter in TS 38.104 or the absolute frequency SSB parameter in TS 38.331. l The above-mentioned RedCap UE obtains the CORESET#0 position, and uses the traditional UE method to obtain the CORESET#0 position, but only receives SIB1 in the initial DL/UL BWP dedicated to the above-mentioned RedCap UE. Compared with the traditional UE, the above-mentioned RedCap UE performs an independent initial access procedure and performs independent resource configuration during the initial access. l Table 1 shows the structure of the broadcast control channel (BCCH)-broadcast channel (BCH) message (BCCH-BCH-Message) in the above TS 38.331. For the cell-defined SSB used by the RedCap UE for cell search, in order to derive the SIB1 or initial access configuration, the BCCH-BCH-MessageType parameter in the above-mentioned physical broadcast channel (PBCH) of the cell-defined SSB is set to MIB. Table 1 BCCH-BCH-Message ::= SEQUENCE { message BCCH-BCH-MessageType } BCCH-BCH-MessageType ::= CHOICE { mib MIB, messageClassExtension SEQUENCE {} }

Embodiment 4-4: RedCap UE performs initial DL/UL BWP selection via non-cell-defined SSB:

For legacy UEs, non-cell-defined SSBs are used for RRM measurements. In 5G NR, there is a mechanism for the non-cell-defined SSB PBCH payload to point to the cell-defined SSB via the pdcch-ConfigSIB1 configuration bit in the aforementioned PBCH payload, since the aforementioned non-cell-defined SSB is not related to SIB1. In one embodiment, a similar mechanism can be employed to target RedCap specific cell-defined SSBs via cell-free defined SSBs. In this case, the above-described initial DL/UL BWP selection based on the cell-defined SSB in Embodiments 4-3 can be applied accordingly.

In another embodiment, the network may redefine the pdcch-ConfigSIB1 configuration bit or redefine other bits reserved for future use in the PBCH payload of the above non-cell-defined SSB to convey the SIB1 related information of the RedCap UE . In another embodiment, the aforementioned network may define a new MIB for the aforementioned RedCap UE. The above-mentioned new MIB is carried out in the physical broadcast channel (PBCH) of the above-mentioned non-cell-defined SSB, and has the BCCH-BCH-MessageType parameter set to messageClassExtension.

The non-cell-defined SSB of the traditional UE can be regarded as the cell-defined SSB of the above-mentioned RedCap UE. From a legacy UE perspective, the aforementioned RedCap UE performs a cell search on a non-cell defined SSB defined for legacy UEs. The cell-free defined SSB used for the above-mentioned RedCap UEs can also be used for channel measurements of legacy UEs. From the perspective of the RedCap UE, the above-mentioned RedCap UE derives the CORESET#0 position and receives SIB1' within the initial DL BWP corresponding to the cell-defined SSB of the above-mentioned RedCap UE. In this solution, initial access congestion on the same SSB for legacy UEs and RedCap UEs can be avoided.

Embodiment 5:

In one embodiment, the network performs device type identification and parameter configuration for the RedCap UE in a random access procedure.

Embodiment 5-1:

The above-mentioned network (such as the above-mentioned gNB) allocates the following one or more relevant parameters for transmitting a physical random access channel (PRACH) and sends a broadcast information block to the above-mentioned extended equipment type UE to indicate one or more of the following parameters for transmitting PRACH: Related parameters: l The initial UL BWP used for the above-mentioned extended equipment type UE; l PRACH resources for the above-mentioned extended device type UE; and l The preamble format used for the above-mentioned extended equipment type UE.

The network may determine initial UL BWP and/or physical random access channel (PRACH) resources for the RedCap UE, and use a broadcast information block such as SIB1 to indicate the RedCap UE's initial UL BWP and/or PRACH resources. The above-mentioned RedCap UE receives and determines the above-mentioned broadcast information block (eg SIB1) to obtain the above-mentioned initial UL BWP and/or the above-mentioned PRACH resource of the above-mentioned RedCap UE. The above PRACH radio resources include radio resources in the time domain and frequency domain of the initial UL BWP. The above-mentioned initial UL BWP of the above-mentioned RedCap UE may include the above-mentioned initial UL BWP dedicated to the above-mentioned RedCap UE, rather than the initial UL BWP of the legacy UE. Alternatively, the above-mentioned initial UL BWP of the above-mentioned RedCap UE may include the above-mentioned initial UL BWP shared by the above-mentioned RedCap UE and the legacy UE. Similarly, the above-mentioned gNB can configure a set of preamble formats suitable for RedCap UEs in the PRACH configuration through the broadcast information block.

Upon receipt of SIB1, the aforementioned RedCap UE determines: l the initial UL BWP of the above-mentioned RedCap UE indicated in the above-mentioned SIB1; and/or l PRACH resources of the above-mentioned RedCap UEs indicated in the above-mentioned SIB1; and/or l The preamble format of the above-mentioned RedCap UE indicated in the above-mentioned SIB1.

In one embodiment, the above-mentioned SIB1 may indicate: l Initial UL BWP dedicated to the above RedCap UE; or l The initial UL BWP shared by the above-mentioned RedCap UE and legacy UE.

In one embodiment, the above-mentioned SIB1 may indicate the above-mentioned PRACH resource of the above-mentioned RedCap UE. The above-mentioned PRACH resources of the above-mentioned RedCap UE may include: l PRACH resources shared by the above-mentioned RedCap UEs and legacy UEs; or l PRACH resources exclusively used for the above-mentioned RedCap UEs, not PRACH resources for the above-mentioned traditional UEs.

Embodiment 5-2:

The above-mentioned RedCap UE may transmit a Physical Random Access Channel (PRACH) signal through the initial UL BWP of the above-mentioned RedCap UE. The initial UL BWP of the above-mentioned RedCap UE may include an initial UL BWP dedicated to the above-mentioned RedCap UE that is different from the initial UL BWP of the legacy UE. The above-mentioned initial UL BWP dedicated to the above-mentioned RedCap UE may be referred to as a RedCap UE-specific initial UL BWP. Alternatively, the initial UL BWP of the above-mentioned RedCap UE may include the initial UL BWP shared by the above-mentioned RedCap UE and the legacy UE. Therefore, the above-mentioned RedCap UE can transmit the PRACH signal in the following ways: l Initial UL BWP dedicated to RedCap UE in SIB1; or l The above initial UL BWP which is the same as the initial UL BWP of the legacy UE.

In one embodiment, if the PRACH signal is transmitted on the same initial UL BWP as the legacy UE's initial UL BWP, the RedCap UE may use the preamble sequence of the RedCap UE with a specific device type in the PRACH signal. In one embodiment, the above-mentioned RedCap UE may transmit PRACH signals on the same initial UL BWP as the initial UL BWP of the legacy UE using PRACH resources of the RedCap UE with a specific device type. In another embodiment, the above-mentioned RedCap UE may transmit the PRACH signal on the above-mentioned initial UL BWP using the above-mentioned preamble sequence and the above-mentioned PRACH resource for the RedCap UE with a specific device type, and the above-mentioned initial UL BWP is the same as the initial UL BWP of the legacy UE. Same for BWP. When the above-mentioned initial UL BWP of the above-mentioned extended equipment type UE includes the above-mentioned initial UL BWP shared by the above-mentioned extended equipment type UE and the traditional UE, the above-mentioned network (for example, the above-mentioned gNB) configures one or more above-mentioned PRACH parameters for the above-mentioned extended equipment type UE : l the preamble sequence of the above-mentioned extended equipment type UE; or l PRACH resources used for PRACH transmissions initiated by UEs of the above extended device types.

Correspondingly, the above-mentioned network (eg, the above-mentioned gNB) may configure one or more of the above-mentioned initial UL BWP, the above-mentioned preamble sequence and the above-mentioned PRACH resource, so as to distinguish the above-mentioned RedCap UE from the traditional UE. The above-mentioned gNB can identify the device type of the above-mentioned RedCap UE according to the following conditions: l The initial UL BWP of the above UE; l the preamble sequence of the above UE; or l PRACH resources used for PRACH transmission of the above UE.

Embodiment 5-3:

The network (eg, gNB) determines and configures transmission parameters for downlink transmission to the extended equipment type UE during random access based on the equipment type related information of the extended equipment type UE. The above-mentioned gNB determines and configures a random access response (RAR) in the two-step random access (two-step random access) based on the above-mentioned identification equipment type of the above-mentioned extended equipment type UE, and taking into account the following one or more capabilities of the above-mentioned UE. , called msg2) and/or msg4 and/or msgB transmission parameters: l Expand the coverage requirements of the equipment type UE; l the processing time of the extended device type UE; and l Expand the supported bandwidth of the device type UE.

The above coverage can be represented by metrics such as maximum coupling loss (MCL), maximum path loss (MPL), and maximum isotropic loss (MIL). Examples and illustrative definitions of the above coverage can be found in TR 38.830. The above-mentioned processing time of the above-mentioned UE may include the time of the PDSCH processing procedure. Examples and illustrative definitions of the timing of the above PDSCH handlers can be found in TR 38.214. The time of the above-mentioned PDSCH processing procedure of the above-mentioned UE is the time that the above-mentioned UE needs to process the above-mentioned received PDSCH after the above-mentioned UE completes the above-mentioned PDSCH reception. The above-mentioned gNB transmits the RAR (ie msg2) to the above-mentioned RedCap UE according to the above-mentioned transmission parameters. The RAR transmitted by the above-mentioned gNB for the RedCap UE includes one or more of the following configurations: l Radio Network Temporary Identifier (RNTI) dedicated to the above-mentioned RedCap UE, such as Random Access Radio Network Temporary Identifier (RA-RNTI), called RedCap UE-specific RA-RNTI; l msg3 PUSCH scheduling for RedCap UE; l Backoff parameter for RedCap UE; l indication of the above-mentioned initial UL BWP for transmission of msg3 and/or msg5 from the above-mentioned RedCap UE; and l The above-mentioned RedCap UE is used to receive the above-mentioned initial DL BWP indication of msg4.

Embodiment 5-4:

The above-mentioned extended equipment type UE may send a msg3 message based on the configuration in the received RAR, and the above-mentioned equipment type related information of the above-mentioned extended equipment type UE is included in the above-mentioned msg3 message. In one embodiment, the above-mentioned RedCap UE sends msg3 according to the above-mentioned configuration in the received RAR. The above-mentioned RedCap UE may transmit the above-mentioned device type including the above-mentioned RedCap UE in the above-mentioned msg3 message.

Embodiment 5-5:

In one embodiment, the above-mentioned RedCap UE may perform one or more of the following operations to receive msg4: l start the random access contention resolution timer (eg ra-ContentionResolutionTimer) configured for the RedCap UE; and l Use the above-mentioned RedCap UE-specific RNTI to monitor and decode the PDCCH.

Embodiments 5-6:

In one embodiment, after receiving msg4, the above-mentioned RedCap UE may perform the following operations in response to the above-mentioned msg4 message: l Send HARQ-ACK for the above msg4 message based on the above PDSCH processing time capability specific to the RedCap UE.

Embodiments 5-7:

In one embodiment, the above-mentioned RedCap UE may send msg5 according to the above-mentioned configuration in the received msg4, and carry information related to the device type of the RedCap UE: the above-mentioned RedCap UE may include the above-mentioned device type of the above-mentioned RedCap UE in the above-mentioned msg5 message .

Embodiment 6:

Whenever the gNB receives the above-mentioned device type related information (such as the above-mentioned device type or the above-mentioned UE capability) in the above-mentioned random access procedure, the above-mentioned network may perform at least one of the following operations for the above-mentioned RedCap UE before establishing the RRC connection for the above-mentioned RedCap UE : l Configure the functions supported by the corresponding device type for the above RedCap UE; l Configure coverage enhancement related functions for the above RedCap UEs; l Configure access control or cell restrictions for the above RedCap UEs; l Provide DL/UL BWP metrics for the above RedCap UEs; and l Determine the multiplex transmission scheme between the above-mentioned RedCap UEs and legacy UEs.

When providing the resource configuration, the base station performs one or more operations for the extended equipment type UE based on the equipment type related information of the extended equipment type UE in the random access procedure of the extended equipment type UE. The above operations are described in further detail below: l Configure the above supported functions for the above RedCap UEs: The aforementioned network may configure the aforementioned supported functions for the aforementioned UE. In the random access procedure or after establishing an RRC connection for the above-mentioned extended equipment type UE, the above-mentioned support function of the above-mentioned extended equipment type UE is associated with the above-mentioned equipment type related information of the above-mentioned extended equipment type UE. The above UE features supported above include one or more of the following: n Extend the processing time capability of the device type UE; n Expand the bandwidth supported by the device type UE; n the SCS supported by the extended device type UE; and n The duplex mode supported by the extended device type UE. The processing time capability of the above-mentioned UE includes the processing time of one or more of the following UE operations: n Preparation for PDSCH decoding and HARQ-ACK feedback; n PDCCH decoding and PUSCH transmission preparation work; and n Preparation for PDCCH decoding and CSI feedback. According to the processing time capability of the UE, the network allocates processing time to the UE for operations such as PDSCH decoding, HARQ-ACK transmission, PUSCH transmission, and CSI feedback of the UE. l Configure coverage enhancement related functions for the above RedCap UEs: In order to expand the coverage of the above-mentioned RedCap UE, the above-mentioned network may configure coverage enhancement related functions for the above-mentioned RedCap UE. In the random access procedure or after establishing the RRC connection for the above-mentioned extended equipment type UE, the above-mentioned coverage enhancement related function of the above-mentioned extended equipment type UE is associated with the above-mentioned equipment type related information of the above-mentioned extended equipment type UE. The above-mentioned coverage enhancement-related functions of the above-mentioned UE may be pre-configured, or the above-mentioned coverage-enhancing-related functions of the above-mentioned UE may be reconfigured by using RRC information or downlink control information (DCI). The above coverage enhancement related functions include one or more of the following: n the number of repetitions of PUSCH and PUCCH transmissions; and n Uplink power control for PUSCH and PUCCH transmissions. The above-mentioned network may pre-configure the above-mentioned repeated transmission times for the above-mentioned UE, or send an RRC message or downlink control information (DCI) to the above-mentioned UE to configure the above-mentioned repeated transmission times of the above-mentioned UE. l Configure access control or cell access restrictions for the above RedCap UEs: The network may configure access control or cell access restrictions for the UE. The access control or cell access restriction of the extended equipment type UE is associated with the equipment type related information during the random access procedure of the extended equipment type UE. The above access control or cell access restrictions include one or more of the following: n Access identification information of the above-mentioned RedCap UE with a specific device type; n Access category of the above-mentioned RedCap UE with a specific device type; n Access priority of the above-mentioned RedCap UE with a specific device type; n PRACH resource limitation of the above RedCap UE; n the maximum number of PRACH attempts for the above RedCap UE; and n The fallback time of the above RedCap UE. Some of the device types described above may be represented by specific access identification information or access classes. Based on operator policy, the network may prevent UEs (eg, RedCap UEs and/or legacy UEs) from accessing the network using relevant barring parameters based on the access in each access attempt from the UE. Identification information and the above access categories vary. The network configures the prohibition parameters according to the access identification information and the access type. For example, in the above UE configuration the access identification information listed in TS 22.261 Table 6.22.2.2-1, each access class is determined by the conditions associated with the UE and the access attempts listed in TS 22.261 Table 6.22.2.3-1 A combination of types is defined. The above-mentioned PRACH resource limitation of the above-mentioned RedCap UE includes the above-mentioned PRACH radio resource of the above-mentioned RedCap UE. The above PRACH radio resources include radio resources in the time domain and frequency domain for initial UL BWP transmission. l Provide DL/UL BWP indicators for the above RedCap UEs: The aforementioned network may provide the aforementioned UE with a DL/UL BWP indicator. During the random access procedure or after establishing an RRC connection for the extended equipment type UE, the DL/UL BWP indicator of the extended equipment type UE is associated with the equipment type related information of the extended equipment type UE. The above DL/UL BWP metrics represent one or more of the following: n The default DL BWP of RedCap UE; n The initial UL/DL BWP of the RedCap UE; n RedCap UE-enabled DL/UL BWP; and n RedCap UE's BWP timer. l Determine the inter-UE multiplexing scheme between the above RedCap UE and traditional UE: The above-mentioned network may determine an inter-UE multiplexing scheme for multiplexing the traffic of the above-mentioned RedCap UE and the traditional UE. The inter-UE multiplexing scheme of the extended equipment type UE is associated with the equipment type related information of the extended equipment type UE during the random access procedure or after the RRC connection is established for the extended equipment type UE. The multiplexing schemes described above include: n Scheme 1: The above network configures shared radio resources for the above RedCap UE and legacy UE: In an inter-UE multiplexing scheme, the above-mentioned RedCap UEs and legacy UEs share the above-mentioned same radio resources allocated by the above-mentioned network (eg, the above-mentioned gNB). The above-mentioned radio resources include radio resources in the time domain and the frequency domain. n Scheme 2: The above network configures dedicated radio resources for the above RedCap UE: In an inter-UE multiplexing scheme, the aforementioned network (eg, the aforementioned gNB) allocates different radio resources to the aforementioned RedCap UEs and legacy UEs. That is to say, in addition to allocating radio resources to traditional UEs, the above-mentioned network also allocates dedicated radio resources to the above-mentioned RedCap UEs. The above-mentioned radio resources include radio resources in the time domain and the frequency domain.

FIG. 9 is a block diagram of an example system 700 for wireless communication in accordance with one embodiment of the present disclosure. The embodiments described herein may be implemented into the above-described systems using any suitably configured hardware and/or software. 9 shows the system 700 described above, including radio frequency (RF) circuitry 710, baseband circuitry 720, processing unit 730, memory/storage 740, display 750, camera 760, sensor 770, and input/output (I/O ) interface 780, interconnected as shown.

The processing unit 730 described above may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The aforementioned processors may include any combination of general-purpose processors and special-purpose processors, such as graphics processors and application processors. The processor may be coupled to the memory/storage and be configured to execute instructions stored in the memory/storage to cause various applications and/or operating systems to execute on the system.

The baseband circuit 720 described above may include circuits such as, but not limited to, one or more single-core or multi-core processors. The processor may include a baseband processor. The baseband circuits described above can handle various radio control functions, enabling them to communicate with one or more radio networks via radio frequency circuits. The aforementioned radio control functions may include, but are not limited to, signal modulation, encoding, decoding, radio frequency transfer, and the like. In some embodiments, the baseband circuitry described above may provide communications compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry may support integration with 5G NR, LTE, Evolved Universal Terrestrial Radio Access Network (EUTRAN), and/or other Wireless Metropolitan Area Networks (WMS). Network, WMAN), wireless local area network (Wireless Local Area Network, WLAN), wireless personal area network (Wireless Personal Area Network, WPAN) communication. Implementations of the above-described baseband circuits configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuits. In various implementations, the fundamental frequency circuit 720 described above may include circuitry to operate on signals that are not strictly considered fundamental frequencies. For example, in some embodiments, the fundamental frequency circuit may include circuitry that operates on a signal having an intermediate frequency between the fundamental frequency and the radio frequency.

The radio frequency circuit 710 described above may implement communication with a wireless network using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the aforementioned RF circuitry may include switches, filters, amplifiers, etc., to facilitate communication with the aforementioned wireless network. In various embodiments, the radio frequency circuit 710 described above may include circuitry to operate on signals not strictly considered to be at radio frequencies. For example, in some embodiments, radio frequency circuitry may include circuitry that operates on signals having an intermediate frequency between the fundamental frequency and the radio frequency.

In various embodiments, the transmitter circuits, control circuits or receiver circuits discussed above with respect to the UE, eNB or gNB may be embodied in whole or in part in one or more of radio frequency circuits, baseband circuits and/or processing units among them. As used herein, a "circuit" may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or combined) and/or perform a Or the memory (shared, dedicated or combined) of a plurality of software or firmware programs, combinational logic circuits and/or other suitable hardware elements that provide the described functions. In some embodiments, electronic device circuits may be implemented in one or more software or firmware modules, or circuit-related functions may be implemented in one or more software or firmware modules. In some embodiments, some or all of the baseband circuit, processing unit, and/or memory/storage components may be implemented together on a System On A Chip (SOC).

The memory/storage 740 described above may be used to load and store data and/or instructions, eg, for the systems described above. The memory/storage described above for one embodiment may comprise any combination of suitable volatile memory, such as dynamic random access memory (DRAM), and/or non-volatile memory, such as flash memory. In various implementations, the I/O interface 780 may include one or more user interfaces designed to allow a user to interact with the system and/or peripheral component interfaces designed to allow peripheral components to interact with the system. The user interface may include, but is not limited to, a physical keyboard or keypad, a trackpad, speakers, microphones, and the like. Peripheral component interfaces may include, but are not limited to, non-volatile memory ports, Universal Serial Bus (USB) ports, audio jacks, and power interfaces.

In various embodiments, the above-described sensor 770 may include one or more sensing devices to determine environmental conditions and/or location information related to the above-described system. In some embodiments, the aforementioned sensors may include, but are not limited to, gyroscope sensors, accelerometers, proximity sensors, ambient light sensors, and positioning units. The positioning unit described above may also be part of, or interact with, baseband circuitry and/or radio frequency circuitry to communicate with elements of a positioning network, such as global positioning system (GPS) satellites. In various embodiments, the display 750 described above may include a display such as a liquid crystal display and a touch screen display. In various embodiments, the above-described system 700 may be a mobile computing device, such as, but not limited to, a notebook computing device, a tablet computing device, a Netbook, an Ultrabook, a smart phone, and the like. In various implementations, the system may have more or fewer elements, and/or different architectures. Where appropriate, the methods described herein can be implemented as computer programs. The computer program may be stored on a storage medium, such as a non-transitory storage medium.

The above-described embodiments of the present disclosure are a combination of techniques/processes that can be employed in the 3GPP specification to create the final product.

Those of ordinary skill with the above-mentioned technologies will understand that each of the above-mentioned units, algorithms and steps described and disclosed in the above-mentioned embodiments of the present disclosure are implemented using electronic hardware or a combination of computer software and electronic hardware.

The elements mentioned above as separate elements for explanation may or may not be physically separate elements. The units mentioned above may or may not be physical units, that is, they may be located in one place or distributed over a plurality of network units. Some or all of the above units may be used depending on the purpose of the embodiment. Furthermore, each functional unit in each embodiment may be integrated into a processing unit, or be physically independent, or integrated into a processing unit having two or more units.

If the software functional unit is implemented for use and sale as a product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution proposed by the present invention can be implemented in the form of a software product in a basic key part or in part. Alternatively, part of a technical project that benefits traditional technologies can be implemented as a software product. A software product in a computer is stored in a storage medium, and includes a plurality of commands for a computing device (such as a personal computer, a server, or a network device) to perform all or part of the steps disclosed in the embodiments of the present invention. Storage media include USB disks, removable hard disks, read only memory (ROM), random access memory (RAM), floppy disks or other types of media capable of storing code.

The method disclosed above provides: l Mechanism for defining the RedCap UE type. l Mechanisms to limit RedCap UEs in predetermined usage situations when accessing telecommunication networks. Therefore, the performance degradation of the eMBB caused by the RedCap UE working on the eMBB application service can be avoided. l Identify RedCap UE type devices: This function provides technical effects such as avoiding unnecessary network access attempts by RedCap UEs, reducing UE power consumption, and balancing network loads. For example, the above network can distinguish RedCap UEs, and perform relatively loose scheduling and DL/UL data transmission during cell access and random access of RedCap UEs. l Cell-specific resources for RedCap UE include: a) initial access to resources; b) paging resources; and/or c) System block (SIB1) or other system information (OSI) with index one.

One embodiment of the present invention provides RedCap UE identification based on various UE identification schemes during the initial access phase. One embodiment of the present invention provides RedCap UE identification based on various UE ID provisioning schemes during the RRC_IDLE and RRC_CONNECTED states. One embodiment of the present invention provides restricted access based on RedCap UE specific cell barring and access control. One embodiment of the present invention provides initial access resource management for RedCap UEs. One embodiment of the present invention provides initial DL/UL bandwidth part (BWP) adjustment for RedCap UEs.

One embodiment of the present invention provides a good effect of maintaining coexistence performance for NR RedCap UEs and NR Legacy UEs. One embodiment of the present invention allows operators to restrict access to NR RedCap UEs, ensure that NR RedCap UE types are only used for predetermined application instances, and reduce power consumption of NR RedCap UEs due to unnecessary cell access. In one embodiment of the present invention, the above-mentioned network can distinguish between RedCap UEs and non-RedCap UEs, and perform relaxed scheduling and DL/UL data transmission in cell access and random access procedures of RedCap UEs.

While the present disclosure has been described in connection with what are considered to be the most practical and preferred embodiments, it is to be understood that the present disclosure is not limited to the above-disclosed embodiments, but is intended to cover Various combinations are made with the broadest interpretation scope.

1: User equipment 2: gNB 3: gNB 4: Master Clock 5: Master Clock 10a: User Equipment 10b: User Equipment 11a: Processor 11b: Processor 12a: Memory 12b: Memory 13a: Transceiver 13b: Transceiver 20a: Base Station 210a: RTI Preferences 21a: Processor 22a: Memory 23a: Transceiver 30: Network entity equipment 31: Processor 32: Memory 33: Transceiver 700: System 710: Radio Frequency (RF) Circuits 720: Fundamental frequency circuit 730: Processing Unit 740: Memory/Storage 780: Input/Output Interface 770: Sensor 760: Camera 750: Monitor

In order to explain the embodiments of the present invention or related technologies more clearly, the following will briefly introduce the figures in each embodiment. Obviously, the accompanying drawings are only some embodiments of the present invention, and those of ordinary skill in the art can obtain other drawings based on these drawings without being limited by the premise. [Figure 1] illustrates a schematic diagram of a telecommunications system. [FIG. 2] A schematic diagram illustrating one embodiment of a radio access method for an extended device type UE by way of example. [FIG. 3] A schematic diagram illustrating an embodiment of a radio access method for a RedCap UE. [FIG. 4] A schematic diagram illustrating an embodiment of the above-disclosed method with RedCap UE identification and configuration. [FIG. 5] A schematic diagram illustrating one embodiment of a radio access method for an extended device type UE by way of example. [ FIG. 6 ] A schematic diagram illustrating an embodiment of the above-disclosed method with cell retention. [FIG. 7] A schematic diagram illustrating an embodiment of the above-disclosed method with initial DL BWP handover for the above-mentioned RedCap UE. [FIG. 8] A schematic diagram illustrating an embodiment of the above-disclosed method with a DL BWP handover procedure after receiving the MIB. [ FIG. 9 ] A schematic diagram illustrating a system for wireless communication according to an embodiment of the present disclosure.

Claims (80)

A radio access method, executable in a base station, comprising: provide connection indication information for a specific device type represented by the device type related information for the extended device type user equipment (UE); and According to the initial access scheme of the above-mentioned extended equipment type UE, the initial access procedure is performed with the above-mentioned extended equipment type UE. The radio access method according to claim 1, wherein the equipment type related information includes UE identification information, equipment type or UE capability of the extended equipment type UE, or a predetermined preamble, a predetermined physical random number of the extended equipment type UE Access Channel (PRACH) resources, Predetermined initial Uplink/Downlink (DL/UL) Bandwidth Part (BWP), Predetermined Synchronization Signal Block (SSB). The radio access method according to claim 1, wherein the specific device type includes the device type of the extended device type UE or the device type of the legacy UE. The radio access method of claim 3, wherein the extended equipment type UE comprises a reduced capability user equipment (RedCap UE). The radio access method according to claim 1, wherein the connection indication information of the specific device type is transmitted in a broadcast information block of MIB, SIB1 or OSI. The radio access method according to claim 5, wherein the parameter BCCH-BCH-MessageType of the broadcast information block is set to messageClassExtension or MIB. The radio access method according to claim 5, wherein the connection indication information of the specific device type in the broadcast information block includes a specific device in the current cell or at least one of a plurality of cells other than the current cell Type of cell prohibition information, access control check information, or access prohibition information. The radio access method of claim 7, wherein the access control check information includes whether or not an access prohibit check is required for the specific device type. The radio access method according to claim 7, wherein said specific device type is represented by specific access identification information or access class. 8. The radio access method of claim 7, wherein said broadcast information block includes access control information for said specific device type to access a frequency at least one of a current cell or a plurality of cells other than said current cell. The radio access method according to claim 7, wherein the connection indication information includes access control information, and the extended equipment type UE decides whether to send a connection request according to the information. The radio access method according to claim 7, wherein the connection indication information includes a request rejection of a connection request with a device type sent from the extended device type UE to the base station. The radio access method of claim 7, wherein the connection indication information includes random access restrictions for the specific device type. 14. The radio access method of claim 13, wherein said random access restriction includes restricted PRACH preamble, restricted PRACH resources, reduced maximum number of PRACH attempts, or longer backoff time. The radio access method according to claim 1, wherein the connection indication information includes SIB1 or OSI, including SIB1 associated with the existing System Information Radio Network Temporary Identifier (SI-RNTI) and newly defined for the extended equipment type UE Or OSI content, or SIB1 or OSI that includes existing SIB1 or OSI content but is associated with a specific SI-RNTI for the extended device type UE. The radio access method of claim 15, wherein said SIB1 or OSI content includes one or more of the following: PRACH configuration; SI scheduling information; and Initial UL BWP. The radio access method according to claim 1, wherein the connection indication information includes newly defined paging information related to an existing paging RNTI (P-RNTI) for an extended equipment type UE or a specific P-RNTI related to an extended equipment type UE. Existing paging information. The radio access method of claim 1, wherein the connection indication information includes the RAR in msg2 associated with the RA-RNTI of the extended equipment type UE. 19. The radio access method according to claim 18, wherein the content of said RAR in said msg2 for said extended equipment type UE is different from that of RAR in said msg2 for legacy UE. The above radio access method according to claim 19, wherein the content of said RAR for said extended equipment type UE comprises one or more of the following: msg3 Physical Uplink Shared Channel (PUSCH) scheduling for the above-mentioned extended equipment type UEs; and Fallback parameters for the above extended device type UEs. The radio access method according to claim 1, wherein the connection indication information content includes a configuration of msg2, msg3 and/or msg4 for the UE of the extended equipment type, the configuration including one or more of the following: radio transmission resource allocation; Uplink Bandwidth Part (UL BWP); Downlink Bandwidth Part (DL BWP); subcarrier spacing (SCS); Modulation and coding scheme (MCS); Repeat transmission parameters for msg3 transmission; Backoff parameters for the next Physical Random Access Channel (PRACH) transmission; and A HARQ-ACK feedback scheme. The radio access method of claim 21, wherein the HARQ-ACK feedback scheme includes one or more of the following: the number of repeated transmissions of the PUCCH carrying the HARQ-ACK; and HARQ-ACK feedback time relative to the reception time of the msg4 message. The radio access method according to claim 5, wherein the MIB includes a configuration of CORESET#0 resources of the UE of the extended equipment type, for enabling the UE of the extended equipment type to monitor the PDCCH of the SIB1, for receiving the information of the UE of the extended equipment type Paging information or downlink messages used to receive the above-mentioned extended equipment type UE during initial access. 24. The radio access method according to claim 23, wherein the configuration of the CORESET#0 resource for the extended device type UE may be the same as or different from the legacy UE. The radio access method according to claim 23, wherein the configuration of the CORESET#0 resource includes the configuration of the control resource set 0 and the search space 0. 6. The radio access method according to claim 5, wherein said MIB includes information of initial downlink bandwidth part (DL BWP) of said extended equipment type UE, which can be used to receive SIB1, paging information of said extended equipment type UE or initial Downlink messages for the above-mentioned extended equipment type UEs during access. The radio access method of claim 1, wherein the connection indication information includes a DL BWP indicator in downlink control information (DCI) of a physical downlink control channel (PDCCH) type 0 or in msg2 or msg4. The radio access method according to claim 26 or 27, wherein the initial DL BWP of the extended equipment type UE includes the same initial DL BWP as the legacy UE or an initial DL BWP different from the legacy UE. The radio access method of claim 5, wherein the content of the broadcast information block includes an initial UL BWP for the extended equipment type UE to transmit uplink information or Hybrid Automatic Repeat Request (HARQ) during initial access Acknowledgement (HARQ-ACK) feedback. The radio access method according to claim 1, wherein the content of the connection indication information includes the initial UL BWP indicated by the UL BWP indicator used in the DCI of the Type-0 PDCCH or in msg2 or msg4. The radio access method according to claim 29 or 30, wherein the initial UL BWP of the extended equipment type UE may be the same as or different from the legacy UE. 6. The radio access method of claim 5, wherein the MIB of the extended device type UE is carried on a radio resource different from the cell-defined SSB of the conventional UE. The radio access method of claim 32, wherein the cell-defined SSB points to the information of the initial DL BWP or the initial UL BWP of the UE of the extended equipment type. The radio access method of claim 5, wherein the MIB of the extended device type UE is carried on radio resources that are non-cell-defined SSB for legacy UEs. The radio access method according to claim 34, wherein said non-cell-defined SSB points to an initial DL BWP or an initial UL BWP of said extended equipment type UE. A base station comprising: A processor configured to invoke and execute a computer program stored in memory to cause a device on which said chip is mounted to perform said method of any one of claims 1 to 35. A wafer comprising: A processor configured to invoke and execute a computer program stored in memory to cause a device on which said chip is mounted to perform said method of any one of claims 1 to 35. A computer-readable storage medium having stored therein a computer program, wherein the computer program causes a computer to perform the above-mentioned method of any one of claims 1 to 35. A computer program product comprising a computer program, wherein said computer program causes a computer to perform said method of any one of claims 1 to 35. A computer program, wherein said computer program causes a computer to perform said method of any one of claims 1 to 35. A radio access method, executable in an extended equipment type user equipment (UE), comprising: Obtain from the base station the connection indication information of the specific device type represented by the device type related information of the above-mentioned extended device type UE; and determine an initial access plan based on the above-mentioned connection instruction information; and According to the above-mentioned initial access scheme, an initial access procedure is performed with the above-mentioned base station. The radio access method according to claim 41, wherein the equipment type related information includes UE identification information, equipment type or UE capability of the extended equipment type UE, or a predetermined preamble, a predetermined physical random number of the extended equipment type UE Access Channel (PRACH) resources, Predetermined initial Uplink/Downlink (DL/UL) Bandwidth Part (BWP), Predetermined Synchronization Signal Block (SSB). The radio access method according to claim 41, wherein the specific device type includes the device type of the extended device type UE or the device type of the legacy UE. The radio access method of claim 43, wherein said extended equipment type UE comprises a reduced capability user equipment (RedCap UE). The radio access method according to claim 41, wherein the connection indication information of the specific device type is transmitted in a broadcast information block of MIB, SIB1 or OSI. The radio access method of claim 45, wherein the broadcast information block has a parameter BCCH-BCH-MessageType set to messageClassExtension or MIB. The radio access method according to claim 45, wherein the connection indication information of the specific device type in the broadcast information block includes a specific device in the current cell or at least one of a plurality of cells other than the current cell Type of cell prohibition information, access control check information, or access prohibition information. The radio access method of claim 47, wherein said access control check information includes whether or not an access prohibition check is required for said specific device type. The radio access method of claim 47, wherein said specific device type is represented by specific access identification information or access class. 48. The radio access method of claim 47, wherein said broadcast information block includes access control information for said specific device type to access the frequency of at least one of the current cell or a plurality of cells other than said current cell. The radio access method according to claim 47, wherein when determining the initial access scheme, the extended equipment type UE determines whether to send a connection request according to the connection indication information. The radio access method according to claim 47, wherein upon obtaining the connection indication information, the extended equipment type UE obtains a request rejection of a connection request with a device type sent from the extended equipment type UE to the base station. The radio access method according to claim 47, wherein when obtaining the connection indication information, the extended equipment type UE obtains the random access restriction of the specific equipment type from the base station. The radio access method of claim 53, wherein said random access restriction includes restricted PRACH preamble, restricted PRACH resources, reduced maximum number of PRACH attempts, or longer backoff time. The radio access method according to claim 41, wherein when obtaining the connection indication information, the method for obtaining the SIB1 or the OSI by the extended equipment type UE comprises using the existing System Information Radio Network Temporary Identifier (SI-RNTI) to obtain The newly defined SIB1 or OSI content of the extended equipment type UE, or the existing SIB1 or OSI content obtained using the specific SI-RNTI of the extended equipment type UE. The radio access method of claim 55, wherein said SIB1 or OSI content includes one or more of the following: PRACH configuration; SI scheduling information; and Initial UL BWP. The radio access method according to claim 41, wherein when obtaining the connection indication information, the extended equipment type UE obtains the newly defined paging information of the extended equipment type UE using an existing paging RNTI (P-RNTI) or uses the extended equipment type UE specific P-RNTI to obtain existing paging information. The radio access method of claim 41, wherein when determining the initial access scheme, the extended equipment type UE uses a specific RA-RNTI calculated by the extended equipment type UE to receive the RAR in msg2 of the extended equipment type UE . The radio access method of claim 58, wherein the content of the RAR in the msg2 for the extended equipment type UE is different from the RAR in the msg2 for the legacy UE. The above-mentioned radio access method according to claim 59, wherein the content of the above-mentioned RAR for the above-mentioned extended equipment type UE comprises one or more of the following: msg3 Physical Uplink Shared Channel (PUSCH) scheduling for the above-mentioned extended equipment type UEs; and Fallback parameters for the above extended device type UEs. The radio access method according to claim 41, wherein the connection indication information content includes a configuration of msg2, msg3 and/or msg4 for the UE of the extended equipment type, the configuration including one or more of the following: radio transmission resource allocation; Uplink Bandwidth Part (UL BWP); Downlink Bandwidth Part (DL BWP); subcarrier spacing (SCS); Modulation and coding scheme (MCS); Repeat transmission parameters for msg3 transmission; Backoff parameters for the next Physical Random Access Channel (PRACH) transmission; and A HARQ-ACK feedback scheme. The radio access method of claim 61, wherein the HARQ-ACK feedback scheme comprises one or more of the following: the number of repeated transmissions of the PUCCH carrying the HARQ-ACK; and HARQ-ACK feedback time relative to the reception time of the msg4 message. The radio access method according to claim 45, wherein the MIB includes a configuration of CORESET#0 resources of the UE of the extended equipment type, which is used for the UE of the extended equipment type to monitor the PDCCH of the SIB1 and receive the paging information of the UE of the extended equipment type Or used to receive downlink messages of the above-mentioned extended equipment type UE during initial access. The above-mentioned radio access method according to claim 63, wherein the above-mentioned CORESET#0 resource configuration for the extended device type UE may be the same as or different from the legacy UE. The radio access method according to claim 63, wherein the configuration of the CORESET#0 resource includes the configuration of the control resource set 0 and the search space 0. The radio access method according to claim 45, wherein said MIB includes information of initial downlink bandwidth part (DL BWP) of said extended equipment type UE, which can be used to receive SIB1, paging information or initial Downlink messages for the above-mentioned extended equipment type UEs during access. The radio access method according to claim 66, wherein said initial DL BWP of said extended equipment type UE is in Downlink Control Information (DCI) according to Type-0 Physical Downlink Control Channel (PDCCH) or in msg2 or It is switched by the DL BWP indicator in msg4. The radio access method according to claim 66 or 67, wherein the initial DL BWP of the extended equipment type UE includes the same initial DL BWP as the legacy UE or an initial DL BWP different from the legacy UE. The radio access method of claim 45, wherein the content of the broadcast information block includes an initial UL BWP for the extended equipment type UE to transmit uplink information or Hybrid Automatic Repeat Request (HARQ) during initial access Acknowledgement (HARQ-ACK) feedback. The radio access method according to claim 41, wherein the content of the connection indication information includes an initial UL BWP indicated by a UL BWP indicator used in DCI of Type-0 PDCCH or in msg2 or msg4. The above-mentioned radio access method according to claim 69 or 70, wherein the above-mentioned initial UL BWP of the above-mentioned extended equipment type UE may be the same as or different from the above-mentioned legacy UE. The radio access method of claim 45, wherein the MIB of the extended device type UE is carried on a radio resource different from the cell-defined SSB of the legacy UE. The radio access method according to claim 72, wherein the UE of the extended equipment type obtains the information of the initial DL BWP or the initial UL BWP of the UE of the extended equipment type based on the cell-defined SSB. 46. The radio access method of claim 45, wherein said MIB of said extended equipment type UE is carried on radio resources that are non-cell-defined SSB for legacy UEs. The radio access method according to claim 74, wherein the UE of the extended equipment type obtains the information of the initial DL BWP or the initial UL BWP of the UE of the extended equipment type based on the non-cell defined SSB. A user equipment (UE) comprising: A processor configured to invoke and execute a computer program stored in memory to cause a device on which said chip is mounted to perform said method of any one of claims 41 to 75. A wafer comprising: A processor configured to invoke and execute a computer program stored in memory to cause a device on which said chip is mounted to perform said method of any one of claims 41 to 75. A computer-readable storage medium having stored therein a computer program, wherein the computer program causes a computer to perform the above-mentioned method of any one of claims 41 to 75. A computer program product comprising a computer program, wherein said computer program causes a computer to perform said method of any one of claims 41 to 75. A computer program, wherein said computer program causes a computer to perform said method of any one of claims 41 to 75.

Images