Paging method for internet-of-things device, and wireless communication devices

Abstract

The present disclosure provides a paging method for Internet-of-Things devices, the method comprising: a base station sends to Internet-of-Things devices a paging message and / or configuration information of an uplink scheduling grant, wherein short Internet-of-Things device identifiers in the paging message are in one-to-one correspondence with time-frequency resources allocated by means of the uplink scheduling grant in the configuration information, such that there is no need of dynamic DCI to schedule uplink scheduling grants of Internet-of-Things devices. Since Internet-of-Things device group local identifiers in the paging message are in one-to-one correspondence with the time-frequency resources allocated by means of the uplink scheduling grant in the configuration information, and the Internet-of-Things device group local identifiers belong to one Internet-of-Things device group, the paging message can be used for processing the group of Internet-of-Things devices, thus saving a large amount of signaling in the paging message.

Description

Paging method and wireless communication device for Internet of Things devices Technical Field

[0001] The present disclosure relates to the field of wireless communications, and in particular to a paging method and wireless communication device for an Internet of Things device. Background Art

[0002] In recent years, the Internet of Things (IoT) has garnered widespread attention in the wireless communications field. People expect more "things" to be connected to improve productivity and enhance living comfort. Further reductions in the size, complexity, and power of IoT devices will enable the deployment of billions, or even tens of billions, of IoT devices, serving a wide range of applications and providing added value across the entire value chain. However, it is impossible to power all IoT devices with batteries that require manual replacement or recharging. This leads to high maintenance costs, serious environmental concerns, and even safety risks for certain use cases, such as wireless sensors in the power and oil industries. Currently, most existing wireless communication devices are powered by batteries that require manual replacement or recharging. The automation and digitization of various industries are opening up many new markets, necessitating new IoT technologies that support battery-free devices without energy storage capabilities or devices with energy storage capabilities that do not require manual replacement or recharging. These devices must have a reasonably compact form factor to be effective in their target use cases. Since existing technologies cannot meet all the requirements of these use cases, a paging method and wireless communication device for IoT devices are needed to improve upon existing technologies.

[0003] Summary of the Invention

[0004] The technical problem to be solved by the present invention is to provide a paging method for IoT devices in response to the above-mentioned defects of the prior art, aiming to solve the problem that the prior art cannot meet all the requirements of the target use case.

[0005] According to one aspect of the present disclosure, a paging method for an IoT device is provided, which is executed on the IoT device. The paging method includes:

[0006] Receive a paging message and / or configuration information, wherein the paging message includes a short IoT device identifier or an IoT device group local identifier; the configuration information includes an uplink scheduling authorization, the time-frequency resources allocated by the uplink scheduling authorization correspond one-to-one with the IoT device identifier or the time-frequency resources allocated by the uplink scheduling authorization correspond one-to-one with the IoT device group local identifier, the short IoT device identifier is used to page the IoT device in paging, and the IoT device group local identifier is an identifier corresponding to several IoT devices in an IoT device group.

[0007] According to one aspect of the present disclosure, a paging method for an Internet of Things device is provided, which is executed by a base station. The paging method includes:

[0008] Sending paging messages and / or configuration information of uplink scheduling authorization, wherein the paging message includes a short IoT device identifier or an IoT device group local identifier; the time-frequency resources allocated by the uplink scheduling authorization in the configuration information correspond one-to-one to the IoT device identifier or the time-frequency resources allocated by the uplink scheduling authorization correspond one-to-one to the IoT device group local identifier, the short IoT device identifier is used to page the IoT device in paging, and the IoT device group local identifier is the identifier corresponding to several IoT devices in an IoT device group.

[0009] According to one aspect of the present disclosure, a wireless communication device is provided, comprising a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to perform the steps in the data processing method as described in any one of the above items.

[0010] Beneficial effects of the present invention: In the present disclosure, the base station sends a paging message and / or configuration information of an uplink scheduling authorization to an IoT device. Since the short IoT device identifier in the paging message corresponds one-to-one to the time-frequency resources allocated by the uplink scheduling authorization in the configuration information, there is no need for dynamic DCI scheduling of the uplink scheduling authorization of the IoT device; since the IoT device group local identifier in the paging message corresponds one-to-one to the time-frequency resources allocated by the uplink scheduling authorization in the configuration information, the IoT device group local identifier belongs to an IoT device group, so the paging message can be processed for a group of IoT devices, which can save a lot of signaling in the paging message. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order to more clearly illustrate the embodiments of the present disclosure or related technologies, the following drawings will be briefly introduced in the embodiments. Obviously, the drawings are only some embodiments of the present disclosure, and ordinary technicians in this field can derive other drawings based on these drawings without inventive work.

[0012] FIG1 is a schematic diagram illustrating a wireless communication system architecture provided by the present disclosure.

[0013] FIG2 illustrates one of the flow charts of the paging method for an IoT device provided by the present disclosure.

[0014] FIG3 illustrates a second flowchart of the paging method for an IoT device provided by the present disclosure.

[0015] FIG4 illustrates one of the schematic diagrams of a resource allocation graph provided by the present disclosure.

[0016] FIG5 illustrates a second schematic diagram of a resource allocation diagram provided by the present disclosure.

[0017] FIG6 illustrates a third schematic diagram of a resource allocation diagram provided by the present disclosure.

[0018] FIG7 illustrates one of the signaling interaction schematic diagrams between an IoT device and a base station provided in the present disclosure.

[0019] FIG8 illustrates one of the signaling interaction diagrams of an IoT device, a base station, and a core network provided in the present disclosure.

[0020] FIG9 illustrates a second schematic diagram of signaling interaction among an IoT device, a base station, and a core network provided by the present disclosure.

[0021] FIG10 illustrates a third schematic diagram of signaling interaction among an IoT device, a base station, and a core network provided in the present disclosure.

[0022] FIG11 illustrates a second schematic diagram of signaling interaction between an IoT device and a base station provided in the present disclosure.

[0023] FIG12 illustrates a fourth schematic diagram of signaling interaction among an IoT device, a base station, and a core network provided in the present disclosure.

[0024] FIG13 illustrates a third schematic diagram of signaling interaction between an IoT device and a base station provided in the present disclosure.

[0025] FIG14 illustrates a fourth schematic diagram of signaling interaction between an IoT device and a base station provided in the present disclosure.

[0026] FIG15 illustrates the fifth schematic diagram of signaling interaction between an IoT device and a base station provided in the present disclosure.

[0027] FIG16 illustrates the sixth schematic diagram of signaling interaction between an IoT device and a base station provided in the present disclosure.

[0028] FIG17 illustrates an exemplary block diagram of a wireless communication system provided by the present disclosure. DETAILED DESCRIPTION

[0029] The embodiments of the present disclosure describe technical matters, structural features, objectives and effects in detail with reference to the accompanying drawings, as described below. Specifically, the terms in the embodiments of the present disclosure are only used to describe the purpose of specific embodiments, rather than to limit the present disclosure.

[0030] The relevant technical terms in this article are shown in Table 1:

[0031] Table 1

[0032] In this disclosure, "A or B" may mean "only A," "only B," or "both A and B."

[0033] In other words, in the present disclosure, "A or B" may be interpreted as "A and / or B." For example, in the present disclosure, "A, B or C" may mean "only A," "only B," "only C," or "any combination of A, B, and C."

[0034] As used in this disclosure, a slash ( / ) or a comma may mean "and / or". For example, "A / B" may mean "A and / or B". Thus, "A / B" may mean "only A", "only B", or "both A and B". For example, "A, B, C" may mean "A, B, or C".

[0035] In the present disclosure, “at least one of A and B” may mean “only A”, “only B”, or “both A and B”. In addition, in the present disclosure, the expression “at least one of A or B” or “at least one of A and / or B” may be interpreted as “at least one of A and B”.

[0036] In addition, in the present disclosure, “at least one of A, B, and C” may mean “only A,” “only B,” “only C,” or “any combination of A, B, and C.” In addition, “at least one of A, B, or C” or “at least one of A, B, and / or C” may mean “at least one of A, B, and C.”

[0037] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features being referred to. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the described features. Throughout the description of this application, "plurality" means two or more, unless otherwise specifically defined.

[0038] Those skilled in the art will recognize and appreciate that the details of the described examples are merely illustrative of some embodiments and that the teachings set forth herein are applicable to various alternative arrangements.

[0039] The technical solution disclosed herein can be applied to various wireless communication systems, such as: Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) system, 5G communication system or future wireless communication systems, etc.

[0040] Exemplarily, a wireless communication system 100 applied in the present disclosure is shown in FIG1 . The wireless communication system 100 may include a base station 110, which may be a device that communicates with a user equipment 120 (User Equipment, UE) (in the present disclosure, the user equipment 120 may be an Internet of Things device or an environmental Internet of Things device). The base station 110 may provide communication coverage for a specific geographical area and may communicate with user equipment located within the coverage area. Optionally, the base station 110 may be an evolved base station 110 (Evolutional Node B, eNB or eNodeB) in an LTE system, or the base station 110 may be a mobile switching center, a relay station, an access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, a network-side device in a 5G network, or a base station 110 in a future communication system, etc.

[0041] The wireless communication system 100 also includes at least one user equipment 120 located within the coverage area of ​​the base station 110. As used herein, "user equipment" includes, but is not limited to, a device configured to receive / send communication signals via a wired connection, such as a Public Switched Telephone Network (PSTN), a Digital Subscriber Line (DSL), a digital cable, a direct cable connection; and / or another data connection / network; and / or via a wireless interface, such as a cellular network, a Wireless Local Area Network (WLAN), a digital television network such as a DVB-H network, a satellite network, an AM-FM broadcast transmitter; and / or another user equipment; and / or an Internet of Things (IoT) device. A user equipment configured to communicate via a wireless interface may be referred to as a "wireless communication terminal," "wireless terminal," or "mobile terminal." Examples of mobile terminals include, but are not limited to, satellite or cellular telephones; Personal Communications System (PCS) terminals that can combine cellular radiotelephones with data processing, fax, and data communication capabilities; PDAs that can include radiotelephones, pagers, Internet / Intranet access, web browsers, notepads, calendars, and / or Global Positioning System (GPS) receivers; and conventional laptop and / or palmtop receivers or other electronic devices that include radiotelephone transceivers. User equipment can refer to access terminals, subscriber units, subscriber stations, mobile stations, mobile stations, remote stations, remote user equipment, mobile devices, wireless communication devices, or user agents. An access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a user device in a 5G network, or a user device in a future evolved PLMN, etc.

[0042] Optionally, the user equipments 120 may perform device-to-device (D2D) communication with each other.

[0043] Optionally, the 5G communication system or 5G network may also be referred to as a New Radio (NR) system or NR network.

[0044] The wireless communication system 100 also includes a core network 130. Core network 130 may be an IP mobile communication network operated by a mobile communication operator. For example, core network 130 may be a core network used by a mobile communication operator that operates and manages the wireless communication system 100, or may be a core network used by a virtual mobile communication operator such as an MVNO (Mobile Virtual Network Operator).

[0045] The core network 130 can be connected to the base station 110 and serve as a relay device for transmitting user data. The user equipment 120 transmits and receives user data via the core network 130. It should be noted that the communication of user data is not limited to IP communication and can also be non-IP communication.

[0046] FIG1 exemplarily shows a base station 110 , two user equipments 120 and a core network 130 . Optionally, the wireless communication system 100 may include multiple base stations 110 and each base station 110 may include other numbers of user equipments within its coverage area, which is not limited in the present disclosure.

[0047] Optionally, the wireless communication system 100 may further include other network entities such as a network controller, a mobility management entity, and a network element, which is not limited in this disclosure. For example, the core network 130 may include other network entities such as a network controller, a mobility management entity, and a network element, which is not limited in this disclosure.

[0048] It should be understood that in this disclosure, a device with wireless communication capabilities in a network / system may be referred to as a wireless communication device. Taking the wireless communication system 100 shown in Figure 1 as an example, the wireless communication device may include a base station 110 with communication capabilities, a user device 120, and a core network 130. The base station 110 and the user device 120 may be the specific devices described above and will not be described in detail here. The wireless communication device may also include other devices in the wireless communication system 100 (core network 130). For example, the core network 130 may include other network entities such as a network controller and a mobility management entity, but this disclosure does not limit this.

[0049] TR 22.840 is being developed by SA1 to capture the use cases, traffic scenarios, and device constraints of ambient energy-driven IoT, and to define new potential service requirements and new key performance indicators. SA1 is considering devices that are battery-free or have limited energy storage capabilities (i.e., using capacitors), and where energy is provided by harvesting radio waves, light, motion, heat, or any other suitable power source.

[0050] Considering the limited size and complexity of battery-free devices with no energy storage capabilities or devices with limited energy storage capabilities that do not require manual replacement or recharging required for practical applications, the output power of energy harvesters is typically 1 microwatt to hundreds of microwatts. Existing cellular devices may not be well suited for energy harvesting because their peak power consumption is higher than 10 milliwatts.

[0051] One example application in TR 22.840 is asset identification, which currently relies primarily on barcodes and radio frequency identification (RFID) in most industries. The primary advantages of these two technologies are their ultra-low tag complexity and miniaturization. However, their limited read range often requires handheld scanning, which results in labor-intensive and time-consuming operations, or RFID access control, leading to expensive deployment. Furthermore, the lack of interference management solutions can lead to significant interference and capacity issues between RFID readers, especially in dense deployments. This makes it difficult to support large-scale RFID networks with seamless coverage.

[0052] TSG RAN has completed the Rel-18 RAN-level SI on Ambient IoT (AIoT), providing a terminology and scope framework for future discussions on Ambient IoT. The framework defines representative use cases, deployment scenarios, connectivity topologies, Ambient IoT devices, design goals, and required capabilities; it also conducts a preliminary feasibility assessment and provides recommendations for future selection when setting the scope for further working group-level studies.

[0053] Since existing technologies cannot meet all the requirements of the target use cases, it is recommended to introduce a new IoT technology to open up new markets within the 3GPP system, with the number of connections and / or device density being several orders of magnitude higher than that of existing 3GPP IoT technologies. This new IoT technology should provide lower complexity and power consumption than existing 3GPP Low Power Wide Area (LPWA) technologies (such as Narrow Band IoT (NB-IoT) and Enhanced Machine-Type Communication (eMTC), and should address use cases and scenarios that cannot be met by existing 3GPP LPWA IoT technologies.

[0054] The information sending method provided by the embodiment of the present application is described in detail below through some embodiments and their application scenarios in combination with the accompanying drawings.

[0055] FIG2 illustrates a paging method for an IoT device provided by the present disclosure, which is executed on the IoT device 120. The paging method includes:

[0056] Step S100, receiving a paging message and / or configuration information, wherein the paging message includes a short IoT device identifier or an IoT device group local identifier; the configuration information includes an uplink scheduling authorization, the time-frequency resources allocated by the uplink scheduling authorization correspond one-to-one to the IoT device identifier or the time-frequency resources allocated by the uplink scheduling authorization correspond one-to-one to the IoT device group local identifier, the short IoT device identifier is used to page the IoT device 120 in paging, and the IoT device group local identifier is an identifier corresponding to several IoT devices 120 in an IoT device group.

[0057] FIG3 illustrates a paging method for an IoT device provided by the present disclosure, which is executed by a base station 110. The paging method includes:

[0058] Step H100, sending a paging message and / or configuration information of an uplink scheduling authorization, wherein the paging message includes a short IoT device identifier or an IoT device group local identifier; the time-frequency resources allocated by the uplink scheduling authorization in the configuration information correspond one-to-one to the IoT device identifier or the time-frequency resources allocated by the uplink scheduling authorization correspond one-to-one to the IoT device group local identifier, the short IoT device identifier is used to page the IoT device 120 in the paging, and the IoT device group local identifier is an identifier corresponding to several IoT devices 120 in an IoT device group.

[0059] Specifically, the base station 110 sends a paging message and / or configuration information of an uplink scheduling authorization to the IoT device 120. Since the short IoT device identifier in the paging message corresponds one-to-one to the time-frequency resources allocated by the uplink scheduling authorization in the configuration information, there is no need for dynamic DCI scheduling of the uplink scheduling authorization of the IoT device 120; since the IoT device group local identifier in the paging message corresponds one-to-one to the time-frequency resources allocated by the uplink scheduling authorization in the configuration information, and the IoT device group local identifier belongs to an IoT device group, the paging message can be processed for a group of IoT devices 120, which can save a lot of signaling in the paging message.

[0060] Example 1

[0061] In the prior art, the user equipment identifier (UE ID) is used in paging messages using the System Architecture Evolution Temporary Mobile Station Identifier (S-TMSI) or the Inactive Radio Network Temporary Identifier (I-RNTI). However, neither of these two IDs exists on AIOT UEs. Therefore, only the device ID can be used in paging messages to uniquely identify a UE, for example:

[0062] Device ID=PLMN ID+vendor ID+UE device ID

[0063] Wherein, the (Public Land Mobile Network, PLMN) ID is the public land mobile network identifier, the vendor ID is the manufacturer identifier, and the UE device ID is the user equipment identifier. In a scenario where a large number of ambient IoT devices 120 exist in a cell, a new identifier needs to be introduced, that is, a new identifier needs to be added to the paging message.

[0064] In some embodiments, the paging message includes at least one of the following: a short UE device ID (short UE device ID1, short UE device ID2, short UE device ID3, ...), a subcarrier ID, and a slot offset. In some embodiments, the short UE device ID includes a vendor ID and / or an UE device ID, and the time-frequency resources are allocated to the UE device 120 based on the order of the short UE device IDs.

[0065] Specifically, the short IoT device identifier is used to page the IoT device 120 in the paging message. The short IoT device identifier includes a device vendor identifier (vendor ID) and / or an IoT device identifier (AIOT UE device ID), and may be presented in the form of: Short UE device ID = vendor ID + UE device ID, or Short UE device ID = UE device ID. Using the above-mentioned paging message, the paging message will not be too long. The subcarrier identifiers are subcarrier 1, subcarrier 2, subcarrier 3, and subcarrier 4 in Figure 4. The effect of the time slot offset is that the base station 110 can start scheduling time-frequency resources after the time slot offset (for example, 3), and adopt the order of time domain first and then frequency domain.

[0066] Optionally, the base station 110 allocates the time-frequency resources to the IoT devices 120 based on the order of the short IoT device identifiers. The order may be from largest to smallest short IoT device identifiers, or from smallest to largest short IoT device identifiers. For example, as shown in FIG4 , the base station 110 may continuously schedule time-frequency resources according to the resource arrangement order of FIG4 . That is, the base station 110 allocates the first time-frequency resource to the IoT device 120 corresponding to the first short IoT device identifier, allocates the second time-frequency resource to the IoT device 120 corresponding to the second short IoT device identifier, and allocates the twelfth time-frequency resource to the IoT device 120 corresponding to the twelfth short IoT device identifier. For example, the first short IoT device identifier (short UE device ID) in the paging message occupies the resources corresponding to subcarrier 1 and time slot 1, and the second short IoT device identifier (short UE device ID) occupies the resources corresponding to subcarrier 2 and time slot 2.

[0067] It should be noted that the first embodiment can be implemented independently or in combination with other embodiments.

[0068] Example 2

[0069] In some embodiments, CG (configured grant) scheduling information is added to the paging message.

[0070] AIOt UE uses CG for two purposes:

[0071] 1: Some AIOT UEs need to periodically send data to indicate trigger conditions;

[0072] 2: If the scheduling cannot be completed in one time, multiple scheduling is required.

[0073] Background technology: In the existing CG, the Radio Resource Control (RRC) configures the CG, and then the physical downlink control channel PDCCH is activated (type 2), or directly activated after configuration (type 1).

[0074] In Figure 5, CG is scheduled for 3 cycles, time slots slot1-3 are the first cycle, time slots slot4-6 are the second cycle, and time slots slot7-9 are the third cycle.

[0075] This paging CG scheduling method differs from existing CGs, which require RRC configuration and are activated directly or through PDCCH. Once activated, they remain active until a deactivation instruction is received. However, the CG in this embodiment is directly configured with a set number of cycles, such as three cycles in the figure above, and then no more cycles. This is because the message size is fixed for a specific AIOT service.

[0076] It should be noted that the second embodiment can be implemented independently or in combination with other embodiments.

[0077] Example 3

[0078] In some embodiments, the paging message includes at least one of the following: a local identifier of an IoT device group, a subcarrier identifier, and a time slot offset, wherein the local identifier of the IoT device group is determined based on the IoT device grouping, and the time-frequency resources are allocated to the IoT device 120 based on the order of the local identifier of the IoT device group.

[0079] Specifically, because the IoT device 120 in the paging message is an IoT device group ID, time-frequency domain resources cannot be allocated sequentially according to the order of IoT devices 120 corresponding to each IoT device ID, as previously described. Therefore, the present disclosure utilizes a pre-assigned IoT device group local ID. The base station 110 then allocates time-frequency domain resources to the IoT devices 120 corresponding to the IoT device group local ID. It is worth noting that this group local device ID is only valid within the group.

[0080] For example, a device group contains 12 IoT devices 120. The core network device assigns each of these 12 IoT devices 120 a number, which serves as the IoT device group local device ID. Time-frequency resources for each IoT device 120 within the group are arranged sequentially according to their group local device ID, as shown in Figure 6. It's important to note that each IoT device 120 is assigned a group local device ID so that it can locate its location when allocating time-frequency domain resources.

[0081] In addition, if a UE has moved out of the cell, this is a rare scenario in the AIOT scenario. The main application scenario of AIOT is inventory, so the IoT device 120 (AIOT UE) usually does not move. If an AIOT UE moves outside the cell, the network side can use implementation methods to discover that the IoT device 120 has moved out of the cell. That is, after multiple inventories, the IoT device 120 has not reported, then the network believes that the AIOT UE has moved out of the cell. Then the group local device ID can be assigned to other IoT devices 120.

[0082] It is worth noting that the third embodiment can be implemented independently or in combination with other embodiments.

[0083] Example 4

[0084] Because a single cell can potentially host a vast number of ambient IoT devices 120 (AIOTs), AIOT UEs must be grouped. AIOT UEs share many commonalities, such as supermarket tags, which are numerous. If grouped, paging messages processed for all IoT devices 120 would contain a significant amount of signaling. Therefore, this disclosure proposes a method for grouping IoT devices 120.

[0085] The purpose of grouping is to enable group paging. Within a cell, there may be multiple types of environmental IoT devices 120. Therefore, the network may require one or more environmental IoT devices 120 of a specific type to report. Before paging messages are sent, the environmental IoT devices 120 need to be grouped.

[0086] However, the ambient IoT device 120 uses a lightweight RRC, which supports limited functionality and lacks an RRC connection. Therefore, the ambient IoT device 120 has no RRC state. Traditional UEs first access the network and then obtain configuration through dedicated RRC signaling. However, due to limited capabilities, AIOT UEs bypass this signaling and must directly access the network and obtain services. Therefore, they must obtain an IoT device group ID (group UE ID) during initial network access.

[0087] In some embodiments, the paging method further includes receiving a first message, the first message including at least one of the following: an IoT device group identifier, an IoT device group local identifier, and a service type identifier. The IoT device group identifier is used to identify an identifier corresponding to a set of multiple IoT devices 120 having common characteristics, and the service type identifier is used to identify a service type corresponding to the IoT device 120. In some embodiments, the IoT device group identifier is assigned by base station 110. In some embodiments, the first message is sent by base station 110, and the first message is MsgB or Msg4.

[0088] Specifically, as shown in FIG7 , the base station 110 allocates the IoT device group identifier. In order for the IoT device 120 to obtain the IoT device group identifier from the base station 110 during initial access, in a 2-step random access channel, after receiving message A (MSGA) sent by the IoT device 120, the base station 110 sends a first message (e.g., message B (MSGB)) to the IoT device 120. In a 4-step random access channel, the first message is MSG4, where message A includes a random number RN16. Since the first message includes at least one of the following: the IoT device group identifier, the IoT device group local identifier, and the service type identifier, the IoT device 120. In this way, the IoT device 120 can know the service type, group identifier, and IoT device group local identifier corresponding to the device. It is worth noting that the IoT device group local identifier is only valid within the IoT device group.

[0089] In some embodiments, the IoT device group identifier is allocated by a core network device, and the IoT device group identifier is determined based on the type of the 5G service quality identifier.

[0090] Specifically, the core network device assigns an IoT device group identifier, meaning that the core network device groups the IoT devices 120. Service types can be predefined in the core network device. When the IoT device 120 accesses the network, the core network establishes a Quality of Service (QoS) flow using one or more newly defined 5G Quality of Service (5QI) identifiers. IoT devices 120 are unlikely to have many service types; we assume eight 5QI types. The 5G radio access network (NG-RAN) node determines the 5QI type based on the protocol data unit (PDU) session initiated by the CN, thereby classifying the UE.

[0091] In some embodiments, the IoT device group identifier is allocated by a core network device, and the IoT device group identifier is determined based on a service type.

[0092] Specifically, if there are eight express delivery companies in a warehouse (STO, YTO, SF Express, China Post, Jitu, Yunda, ZTO Express, and JD.com), each company's IoT devices 120 are grouped together. When an IoT device 120 from a courier company connects to the core network, the core network assigns an IoT device group ID (UE group ID) to the base station 110 based on the UE's subscription information. The base station 110 then assigns an AIOT local group ID to the IoT device 120.

[0093] In one implementation, the IoT device 120's subscription information in the Home Subscriber Server (HSS) contains two levels of grouping. For example, the first level grouping is the service type, indicating that the UE is a courier, while the second level grouping is for courier companies such as SF Express. Once the AMF obtains the subscription information from the HSS, it can pass the UE's grouping information to the gNB when maintaining the UE context for the UE on the NG interface. Specifically, the UE first determines the service type (courier) and then the UE group ID (SF Express).

[0094] In some embodiments, the paging method further includes sending a second message, wherein the second message includes an IoT device identifier.

[0095] In some embodiments, the second message is Msg5.

[0096] In some embodiments, the first message is received and forwarded by the base station 110 , and the first message is a downlink non-access stratum (DL NAS).

[0097] Specifically, as shown in Figure 8, IoT device 120 first sends message 1 to base station 110, then receives confirmation information sent by base station 110, then sends messages 3 and 4 to base station 110, and finally sends a second message (e.g., message 5 (Msg5)) to base station 110, where the second message includes the identifier of IoT device 120. Base station 110 sends an initial IoT device message carrying the identifier of IoT device 120 to the access and mobility management function (AMF) in the core network via the non-access stratum (NAS). The AMF determines the service type, IoT device group identifier, and IoT device group local identifier based on the IoT device identifier, and then sends an initial context establishment request message containing at least one of the following: IoT device group identifier, IoT device group local identifier, and service type identifier included in the first message to base station 110. Base station 110 then forwards the message to IoT device 120. Finally, base station 110 sends an initial context establishment response message to the AMF. It is worth noting that the allocation of the IoT device group identifier (UE group ID) is not limited to the Initial context setup request message, but can also be other message names such as the IoT device context modification request (UE context modification request).

[0098] Unlike the Multimedia Broadcast Multicast Service (MBS), MBS paging packets are configured within the RRC reconfiguration message, which can be configured at any time. However, the IoT device 120 (AIOT UE) cannot maintain a continuous connection to the network. Therefore, the AIOT UE needs to obtain an AIOT group ID during the network access process.

[0099] The AIOT group ID = UE group ID is used by the IoT device 120 to determine whether it is in the paging category based on the AIOT group ID. If so, it prepares to send data based on the service type ID.

[0100] The service type ID contained in the paging message is the service type identifier. Assume that the UE has 8 services, for example, service type ID = 1 represents temperature, which requires 64 bits to report, and service type ID = 2 represents humidity, which requires 128 bits to report.

[0101] It should be noted that the fourth embodiment can be implemented independently or in combination with other embodiments.

[0102] Example 5

[0103] As shown in Figure 9, in the prior art, after the access network side receives the paging message sent by the core network side, it interprets the content therein, obtains the tracking area identity (TAI) list information of the UE, and broadcasts the paging message on the air interface of the cell belonging to the tracking area identity list. The core network domain (CN Domain, Core Network Domain) indication and access category (Access Type) indication information in the interface paging message will not be decoded by the access network side, but will be directly transmitted to the user equipment UE. The interface paging message may also carry discontinuous reception (DRX, Discontinuous Reception) parameter configuration information, which is used to notify the access network side of the specific DRX parameters of the paged UE. The configuration is notified to the core network side by the UE through a non-access stratum (NAS, Non Access Stratum) message before being sent to the access network side under the core network. Since the AIOT UE does not have mobility (cell selection / reselection), there is no need for a TAI list (TAI list). Therefore, it is necessary to consider paging the IoT device 120 when it is not mobile.

[0104] In some embodiments, when the IoT device 120 is a non-mobile IoT device, the paging message further includes an identifier of the cell where the IoT device 120 is located.

[0105] Specifically, as shown in Figure 10, in this application scenario, IoT device 120 (AIOT UE) inherently lacks mobility. This embodiment assumes that the AIOT UE never moves, meaning it always serves a single cell, effectively acting as a fixed-location user equipment (UE). In practice, paging is categorized into core network (CN) paging and radio access network (RAN) paging. CN paging requires specifying the TAI of IoT device 120. When the TAI of IoT device 120 changes, IoT device 120 initiates a TAI update process to update the CN's TAI. RAN paging manages the RRC state of IoT device 120. Because AIOT UEs lack RRC state, RAN paging is not required. Since AIOT UEs lack mobility (cell selection / reselection), a TAI list is not necessary. However, the CN still needs to notify base station 110 of the cell where the AIOT UE is located. Therefore, the cell where IoT device 120 resides must be included in the paging message on the RAN NG interface. Discontinuous Reception (DRX) is also not required because AIOT UEs receive data only after a network activation signal is received, not according to the DRX configuration. Therefore, in the present disclosure, the IoT device 120 removes the TAI list and DRX configuration from the paging message on the NG interface and adds the cell ID.

[0106] It is worth noting that the fifth embodiment can be implemented independently or in combination with other embodiments.

[0107] Example 6

[0108] In the prior art, CW (Carrier Wave) activation signal: CW is any signal used to activate an AIOT device in the environment. It can be a dedicated activation signal or it can be combined with an existing paging message.

[0109] Some AIOT UEs have mobility capabilities, such as couriers that require tracking. However, mobility is not the same as mobility management. Mobility management refers to handover / cell reselection (HO / Cell reselection), which AIOT UEs do not have. According to the Study Item Descriptoin (SID), if HO / Cell reselection is not supported, then tracking area update (TAU) is likely not supported either. If TAU is supported, then, like the existing process, TAU can be updated periodically and based on the TAI in the system information block (SIB). In addition, existing paging is divided into core network paging (CN paging) and network-side paging (RAN paging). CN paging uses the temporary mobile group identifier (TMGI) as the user equipment identifier (UE ID) for paging. The tracking area (TA) is used to maintain the UE's location. When the UE moves out of the TA, a TAU is triggered. RAN paging uses the radio network temporary identifier (RNTI) as the UE ID for paging. The RAN notification area (RNA) is used to maintain the UE's location. When the UE moves out of the RNA, an RNA update is triggered.

[0110] In some embodiments, when the IoT device 120 is a mobile IoT device, the paging message also includes at least one of the following: the IoT device group identifier, a tracking area list, and a radio access network notification area list. In some embodiments, the paging method further includes: the IoT device 120 receiving the paging message after receiving a carrier activation signal sent by the base station 110. This allows the base station 110 to communicate with IoT devices 120 of the same category via broadcast messages, saving signaling.

[0111] In some embodiments, the broadcast message also includes at least one of the following: the IoT device group identifier, a tracking area list, and a radio access network notification area list. In some embodiments, the paging method further includes: IoT device 120 receiving the broadcast message after receiving a carrier activation signal sent by base station 110. This allows base station 110 to page IoT devices 120 of the same category, saving signaling.

[0112] In some embodiments, the paging message is also used to obtain energy for the IoT device 120, or the broadcast message is also used to obtain energy for the IoT device 120. In this way, since the paging message or broadcast message carries energy, only the paging message or broadcast message needs to be sent without sending a carrier activation signal, which can save signaling overhead.

[0113] Specifically, since AIOT UEs do not monitor system information blocks (SIBs), they must first receive an activation signal after entering a new cell. After receiving the notification area (TA) and tracking area (RNA) list, the AIOT UE updates the notification area list (RNA) and tracking area list (TA) list. In legacy UEs, the RNA and TA lists are included after a TAU (including the TA list) or in an RRCRelease (including the RAN area list) message. Therefore, each UE has a different TA list and RAN area list. However, in AIOT UEs, such as express delivery, it is not necessary to distinguish each AIOT UE individually. Instead, a specific category of AIOT UEs can be distinguished and the TA list and RAN notification area list configured identically for that category. Furthermore, since there are no TAU and RRCRelease processes, AIOT UEs cannot obtain the TA list and RAN area list independently from the network and can only obtain them from system messages. This means that AIOT UEs neither need nor have the ability to obtain UE-specific TA lists and RAN area lists. In summary, when the IoT device 120 has a mobile function, the paging process can be completed using the signaling transmission method shown in FIG11 :

[0114] Method 1: The base station 110 sends a carrier activation signal to the IoT device 120 so that the IoT device 120 obtains energy. After sending the carrier activation signal to the IoT device 120, the base station 110 sends a broadcast message (that is, the broadcast configuration information in Figure 11). The broadcast message includes at least one of the following: the IoT device group identifier, the tracking area list, and the wireless access network notification area list.

[0115] Method 2: The base station 110 sends a carrier activation signal to the IoT device 120 so that the IoT device 120 obtains energy. After sending the carrier activation signal to the IoT device 120, the base station 110 sends a paging message. The paging message includes at least one of the following: the IoT device group identifier, the tracking area list, and the wireless access network notification area list.

[0116] Method 3: When the broadcast message is also used for the IoT device 120 to obtain energy, the base station 110 does not need to send a carrier activation signal. Instead, it can send only a broadcast message to achieve communication with the IoT device 120 of the same category, thereby saving signaling.

[0117] Method 4: When the paging message is also used for the IoT device 120 to obtain energy, the base station 110 does not need to send a carrier activation signal. Instead, it can send only a paging message to page the IoT devices 120 of the same category, thereby saving signaling.

[0118] FIG11 illustrates the steps of interaction between the base station 110 and the IoT device 120:

[0119] 1. Send a carrier (CW) activation signal to obtain energy. Some IoT devices 120 can directly use the subsequent paging message to obtain energy;

[0120] 2. The broadcast configuration information obtained from the network contains the TA list and RNA list corresponding to the IoT device group ID. The group ID may be the UE group ID or the service type ID.

[0121] Alternatively, the above step 2 can obtain this information (group ID, TA list, RNA list) from the paging message.

[0122] It is worth noting that step 1 above is optional.

[0123] In some embodiments, the paging method further includes receiving a third message, wherein the third message includes at least one of the following: the IoT device group identifier, the tracking area list, and a mapping relationship between the IoT device group identifier and the tracking area list.

[0124] Specifically, the TA list may be allocated by the core network device CN, and the base station 110 may obtain the group ID and the TA list, as well as the mapping relationship between the group ID and the TA list (e.g., a mapping table of the group ID and the TA list) from the CN in advance, as shown in FIG12 . The message name may be any NG interface protocol (NGAP) message.

[0125] It is worth noting that the sixth embodiment can be implemented independently or in combination with other embodiments.

[0126] Example 7

[0127] In some embodiments, the paging method further includes reporting a fourth message, the fourth message including a supported service type identifier, wherein the service type identifier corresponds one-to-one with the message size. In some embodiments, the paging method further includes receiving a service type query request, wherein the service type query request is used to query the service types supported by the IoT device 120. By querying whether the IoT device 120 has the supported service type, the base station 110 avoids wasting resources by sending paging messages to user devices that do not support the service type.

[0128] Specifically, as shown in Figure 13, if eight service types are predefined in the protocol, each service type corresponds to a message size. The user device sends a service type query request to inquire about supported service types from IoT device 120. IoT device 120 then sends a fourth message, which includes a service type identifier corresponding to the supported service type. In practice, the eight predefined service types correspond to eight message sizes to facilitate network scheduling.

[0129] In some embodiments, the paging method further comprises reporting a fourth message, the fourth message comprising a supported service type identifier, wherein the service type identifier corresponds to a message size in a one-to-one manner. In some embodiments, the paging method further comprises receiving a fifth message, the fifth message comprising at least one of the following: a plurality of service types and a plurality of message sizes corresponding to the plurality of service types.

[0130] Specifically, the base station 110 sends an ID corresponding to a service type in a system information block SIB or other configuration message (eg, an RRC message), such as a 96-bit corresponding service type ID (eg, 1), and only needs to report the 96-bit corresponding identifier (eg, 1).

[0131] In the prior art, message sizes are grouped. Therefore, each service type ID can be assigned a message size. The correspondence between these message sizes and service type IDs is shown in Table 2.

[0132] Table 2 Mapping relationship between message size and service type identifier

[0133] As shown in FIG14 , the base station 110 may use a system information block (SIB) or an RRC reconfiguration message to configure a mapping relationship between a service type ID and a message size, and then send the service type ID, message size, and the mapping relationship between the service type ID and the message size to the IoT device 120. The IoT device 120 then only needs to report the service type ID.

[0134] It should be noted that the seventh embodiment can be implemented independently or in combination with other embodiments.

[0135] The MIB and SIB1 of traditional networks are sent periodically, but AIOT UEs do not periodically monitor MIB and SIB1. Therefore, it is necessary to find a way to send MIB and SIB1 all at once after the AIOT UE is activated. Therefore, the existing technology needs to be improved. The specific solution is shown in Example 8.

[0136] Example 8

[0137] The current random access configuration (RACH-ConfigCommon) is placed in SIB1. However, for the AIOT UE 120, the AIOT UE 120 does not monitor the SIB. The network sends an activation signal to the AIOT UE 120 and then immediately sends a paging signal. Therefore, there are two ways for the AIOT UE to monitor the paging signal directly after receiving the activation signal:

[0138] Method 1:

[0139] In some embodiments, the configuration information further includes at least one of the following: partial information of a master information block and partial information of a system information block type 1. In some embodiments, the configuration information is a broadcast message. In some embodiments, the configuration information is also used by the IoT device 120 to acquire energy, and the paging method further includes the IoT device 120 receiving the configuration information only once each time it acquires energy. In some embodiments, the paging method further includes receiving the configuration information only once after receiving a carrier activation signal.

[0140] Specifically, after the network (eg, base station 110) sends a carrier activation signal, base station 110 sends another configuration message (a new broadcast message AIOT config message), and puts part of the information included in MIB and SIB1 into this configuration message.

[0141] It's worth noting that, compared to existing MIB and SIB1, configuration information (AIOT config messages) is not sent periodically but only once after the carrier activation signal. The interval between the carrier activation signal and configuration information (AIOT config messages) is predefined. All MIB and SIB1 parameters can be included as optional parameters in the configuration information.

[0142] As shown in FIG15 , as an example, the signaling interaction between the base station 110 and the IoT device 120 includes the following steps:

[0143] Step 1. The base station 110 sends a carrier wave (CW) activation signal to the IoT device 120. For some IoT devices 120, this CW activation signal is unnecessary because the IoT device 120 can obtain energy through configuration information.

[0144] Step 2. Base station 110 sends configuration information (a broadcast AIOT config message) to IoT device 120. This configuration message includes some MIB information and / or some SIB1 information. When base station 110 only sends configuration information to IoT device 120, the configuration information also enables IoT device 120 to harvest energy, thereby saving signaling.

[0145] Method 2:

[0146] In some embodiments, the paging message carries the configuration information. In some embodiments, the paging message is also used to enable the IoT device 120 to obtain energy, and the paging method further includes receiving the paging message only once. In some embodiments, the paging method further includes receiving the paging message only once after receiving the carrier activation signal.

[0147] Specifically, part of the MIB information and / or part of the SIB1 information are placed in the paging. As shown in FIG16 , as an example, the signaling interaction between the base station 110 and the IoT device 120 includes the following steps:

[0148] Step 1: The base station 110 sends a carrier wave (CW) activation signal to the IoT device 120. For some IoT devices 120, this CW signal is unnecessary because the IoT device 120 can obtain energy through the paging message.

[0149] Step 2: Base station 110 sends a paging message to IoT device 120. This message contains some MIB information and / or some SIB1 information. If base station 110 only sends configuration information to IoT device 120, the configuration information can also enable IoT device 120 to harvest energy, thereby saving signaling.

[0150] It should be noted that the eighth embodiment can be implemented independently or in combination with other embodiments.

[0151] Described herein is a paging method for an IoT device 120, applicable to communications between a UE (e.g., IoT device 120) and a base station 110, as well as communications between a core network and the base station 110. However, these inventive concepts, methods, apparatuses, devices, computer-readable storage media, chips, and computer program products are not limited to 5G communications, but can also be extended to other communication scenarios (e.g., 6G communications) to achieve the same technical benefits and effects.

[0152] In these scalable communication scenarios, the IoT device 120 or environmental IoT device 120 can be a user equipment (UE), a base station 110 (such as a gNB, eNodeB, transmission reception point (TRP), a next-generation communication NodeB or a Wi-Fi access point, etc.), or an entity such as a network element. User equipment (UE) refers to a device used for communication at the user end, such as a mobile phone, and can also be called a terminal, mobile station, or mobile terminal. UE can be a variety of devices, including but not limited to mobile phones, tablets, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals for industrial control, wireless terminals for autonomous driving, wireless terminals for remote medical surgery, wireless terminals for smart grids, wireless terminals for environmental monitoring, wireless terminals for smart cities, and wireless terminals for smart homes.

[0153] Furthermore, the UE and base station 110 may be deployed in different environments, including but not limited to indoors, outdoors, as handheld devices, in vehicles, or even on water, in the air, on airplanes, drones, or satellites.

[0154] Therefore, although this document describes a paging method and wireless communication device for IoT devices, the inventive concepts and technologies contained therein can be extended to other communication scenarios and are expected to achieve the same technical benefits and effects. It is easy to understand that these inventive concepts have broad applicability and scalability, whether in communications between different types of base stations 110 and user equipment, or in communications in different deployment environments.

[0155] It should be noted that the above steps are merely examples and do not limit the scope of the present invention. Various modifications and variations can be made to the steps without departing from the spirit and scope of the present invention.

[0156] The order of the described steps (signaling / boxes) is not intended to be construed as a limitation, and any number of the described steps (signaling / boxes) may be skipped or combined in any order to implement a method or an alternative method.

[0157] The present disclosure describes examples of communication between terminals and network element components in a network architecture in the above embodiments, which are mainly for illustrative purposes and not restrictive.

[0158] The order of the steps (signaling / boxes) described is not intended to be interpreted as limiting, and any number of the steps (signaling / boxes) described can be skipped or combined in any order to implement a method or alternative method. Typically, any of the components, modules, methods, and operations described herein can be implemented using software, firmware, hardware (e.g., fixed logic circuitry), manual processing, or any combination thereof. Some operations of the example methods can be described in the general context of executable instructions stored on a computer-readable memory locally and / or remotely on a computer processing system, and implementation methods can include software applications, programs, functions, and the like. Alternatively or in addition, any function described herein can be performed, at least in part, by one or more hardware logic components, such as, but not limited to, a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), an application specific standard product (ASSP), a system on a chip (SoC), a complex programmable logic device (CPLD), and the like.

[0159] In addition, the signaling described in the embodiments of the present disclosure can be implemented in any manner known in the art. For example, the signaling can be explicit and / or implicit. In addition, the steps (signaling / frames) shown are for illustrative purposes only and are not intended to limit the present application.

[0160] FIG17 is a schematic structural diagram of a wireless communication device 900 provided by the present disclosure. The wireless communication device includes: a processor and a memory, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, and perform the following operations:

[0161] Receive a paging message and / or configuration information, wherein the paging message includes a short IoT device identifier or an IoT device group local identifier; the configuration information includes an uplink scheduling authorization, the time-frequency resources allocated by the uplink scheduling authorization correspond one-to-one with the IoT device identifier or the time-frequency resources allocated by the uplink scheduling authorization correspond one-to-one with the IoT device group local identifier, the short IoT device identifier is used to page the IoT device in paging, and the IoT device group local identifier is an identifier corresponding to several IoT devices in an IoT device group.

[0162] or

[0163] Sending paging messages and / or configuration information of uplink scheduling authorization, wherein the paging message includes a short IoT device identifier or an IoT device group local identifier; the time-frequency resources allocated by the uplink scheduling authorization in the configuration information correspond one-to-one to the IoT device identifier or the time-frequency resources allocated by the uplink scheduling authorization correspond one-to-one to the IoT device group local identifier, the short IoT device identifier is used to page the IoT device in paging, and the IoT device group local identifier is the identifier corresponding to several IoT devices in an IoT device group.

[0164] The wireless communication device may be a user device, a base station 110, or a network element. The wireless communication device 900 shown in FIG17 includes a processor 910. The processor 910 may call and run a computer program from a memory to implement the method in an embodiment of the present application.

[0165] Optionally, as shown in FIG17 , the wireless communication device 900 may further include a memory 920. The processor 910 may call and execute a computer program from the memory 920 to implement the method in the embodiment of the present application. The memory 920 may be a separate device independent of the processor 910 or may be integrated into the processor 910.

[0166] Optionally, as shown in FIG17 , the wireless communication device 900 may further include a transceiver 930. The processor 910 may control the transceiver 930 to communicate with other devices. Specifically, the transceiver 930 may send information or data to other devices or receive information or data sent by other devices. The transceiver 930 may include a transmitter and a receiver. The transceiver 930 may further include one or more antennas.

[0167] Optionally, the wireless communication device 900 may specifically be the base station 110 of the embodiment of the present application, and the wireless communication device 900 may implement the corresponding processes implemented by the base station 110 in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0168] Optionally, the wireless communication device 900 may specifically be a mobile user device / user device in an embodiment of the present application, and the wireless communication device 900 may implement the corresponding processes implemented by the mobile user device / user device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0169] Optionally, the wireless communication device 900 may specifically be a network element in an embodiment of the present application, and the wireless communication device 900 may implement the corresponding processes implemented by the network element in each method in the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0170] According to an example embodiment, a chip is provided, comprising: a processor for calling and running a computer program from a memory, so that a device equipped with the chip executes a method according to any one of the above embodiments, examples, or exemplary embodiments.

[0171] According to an example embodiment, there is provided a computer-readable storage medium for storing a computer program, wherein the computer program causes a computer to execute a method according to any one of the above-mentioned embodiments, examples, or exemplary embodiments.

[0172] According to an example embodiment, a computer program product is provided, comprising a computer program / instruction, which, when executed by a processor (e.g., by the processor or an apparatus, device, computer or machine including the processor), implements a method according to any one of the above-mentioned embodiments, examples, or example embodiments.

[0173] The embodiments of the present disclosure are a combination of techniques / processes that may be employed in 3GPP specifications to create a final product.

[0174] While the present disclosure has been described in connection with what is considered to be the most practical and preferred embodiment, it is to be understood that the disclosure is not limited to the disclosed embodiment, but is intended to cover various arrangements embodied within the broadest interpretation of the appended claims.

Claims

1. A paging method for an Internet of Things device, executed on the Internet of Things device, the paging method comprising: Receive a paging message and / or configuration information, wherein the paging message includes a short IoT device identifier or an IoT device group local identifier; the configuration information includes an uplink scheduling authorization, the time-frequency resources allocated by the uplink scheduling authorization correspond one-to-one with the IoT device identifier or the time-frequency resources allocated by the uplink scheduling authorization correspond one-to-one with the IoT device group local identifier, the short IoT device identifier is used to page the IoT device in paging, and the IoT device group local identifier is an identifier corresponding to several IoT devices in an IoT device group.

2. The method according to claim 1, wherein The paging message includes at least one of the following: a short IoT device identifier, a subcarrier identifier, and a time slot offset.

3. The method according to claim 2, wherein: The short IoT device identifier includes a device vendor identifier and / or an IoT device identifier, and the time-frequency resources are allocated to the IoT devices according to the order of the short IoT device identifiers.

4. The method according to claim 1, wherein The paging message includes at least one of the following: a local identifier of an IoT device group, a subcarrier identifier, and a time slot offset. The local identifier of the IoT device group is determined based on the grouping of IoT devices, and the time-frequency resources are allocated to IoT devices based on the order of the local identifiers of the IoT device group.

5. The method according to claim 4, wherein The paging method also includes receiving a first message, which includes at least one of the following: an Internet of Things device group identifier, an Internet of Things device group local identifier, and a service type identifier. The Internet of Things device group identifier is used to identify the identifier corresponding to a set of several common Internet of Things devices, and the service type identifier is used to identify the service type corresponding to the Internet of Things device.

6. The method according to claim 5, wherein: The IoT device group identifier is allocated by a base station.

7. The method according to claim 6, wherein: The first message is sent by a base station, and the first message is MsgB or Msg4.

8. The method according to claim 5, wherein The IoT device group identifier is allocated by a core network device, and the IoT device group identifier is determined based on the type of the 5G service quality identifier.

9. The method according to claim 5, wherein: The IoT device group identifier is allocated by a core network device and is determined based on a service type.

10. The method according to claim 8 or 9, wherein: The first message is received and forwarded by the base station, and the first message is a downlink non-access stratum (DL NAS).

11. The method according to claim 10, wherein: The paging method further includes sending a second message, where the second message includes an IoT device identifier.

12. The method according to claim 11, wherein The second message is Msg5.

13. The method according to any one of claims 1 to 12, wherein: When the Internet of Things device is a non-mobile Internet of Things device, the paging message further includes an identifier of a cell where the Internet of Things device is located.

14. The method according to any one of claims 1 to 12, wherein: When the Internet of Things device is a mobile Internet of Things device, the paging message further includes at least one of the following: the Internet of Things device group identifier, a tracking area list, and a wireless access network notification area list.

15. The method according to claims 1-12, wherein: When the Internet of Things device is a mobile Internet of Things device, the broadcast message further includes at least one of the following: the Internet of Things device group identifier, a tracking area list, and a wireless access network notification area list.

16. The method according to claim 14 or 15, wherein: The paging method further includes: receiving the paging message or the broadcast message after receiving a carrier activation signal.

17. The method according to claim 14 or 15, wherein: The paging message is also used for the IoT device to obtain energy, or the broadcast message is also used for the IoT device to obtain energy.

18. The method according to any one of claims 14 to 17, wherein: The paging method further includes receiving a third message, where the third message includes at least one of the following: the IoT device group identifier, the tracking area list, and a mapping relationship between the IoT device group identifier and the tracking area list.

19. The method according to any one of claims 1 to 18, wherein: The paging method further includes reporting a fourth message, wherein the fourth message includes a supported service type identifier, wherein the service type identifier corresponds to the message size in a one-to-one manner.

20. The method according to claim 19, wherein The paging method further includes receiving a service type query request, wherein the service type query request is used to query the service types supported by the Internet of Things device.

21. The method according to claim 19, wherein The paging method further includes receiving a fifth message, where the fifth message includes at least one of the following: several service types and several message sizes corresponding to the several service types.

22. The method according to claim 1, wherein The configuration information further includes at least one of the following: partial information of a master information block and partial information of a system information block type 1.

23. The method according to claim 22, wherein The configuration information is a broadcast message.

24. The method according to claim 23, wherein The configuration information is also used by the Internet of Things device to obtain energy, and the paging method also includes the Internet of Things device receiving the configuration information only once each time it obtains energy.

25. The method according to claim 24, wherein The paging method further includes: receiving the configuration information only once after receiving the carrier activation signal.

26. The method according to claim 22, wherein The paging message carries the configuration information.

27. The method according to claim 26, wherein The paging message is also used by the IoT device to obtain energy, and the paging method further includes receiving the paging message only once.

28. The method according to claim 27, wherein The paging method further includes: receiving the paging message only once after receiving the carrier activation signal.

29. A wireless communication device, wherein: The wireless communication device includes: a processor and a memory, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the paging method according to any one of claims 1 to 28.

30. A paging method for an Internet of Things device, executed by a base station, the paging method comprising: Sending paging messages and / or configuration information of uplink scheduling authorization, wherein the paging message includes a short IoT device identifier or an IoT device group local identifier; the time-frequency resources allocated by the uplink scheduling authorization in the configuration information correspond one-to-one to the IoT device identifier or the time-frequency resources allocated by the uplink scheduling authorization correspond one-to-one to the IoT device group local identifier, the short IoT device identifier is used to page the IoT device in paging, and the IoT device group local identifier is the identifier corresponding to several IoT devices in an IoT device group.

31. The method according to claim 30, wherein The paging message includes at least one of the following: a short IoT device identifier, a subcarrier identifier, and a time slot offset.

32. The method according to claim 31, wherein The short IoT device identifier includes a device vendor identifier and / or an IoT device identifier, and the time-frequency resources are allocated to the IoT devices according to the order of the short IoT device identifiers.

33. The method according to claim 32, wherein The paging message includes at least one of the following: a local identifier of an IoT device group, a subcarrier identifier, and a time slot offset. The local identifier of the IoT device group is determined based on the grouping of IoT devices, and the time-frequency resources are allocated to IoT devices based on the order of the local identifiers of the IoT device group.

34. The method according to claim 33, wherein The paging method also includes sending a first message, which includes at least one of the following: an Internet of Things device group identifier, an Internet of Things device group local identifier, and a service type identifier. The Internet of Things device group identifier is used to identify the identifier corresponding to a set of several common Internet of Things devices, and the service type identifier is used to identify the service type corresponding to the Internet of Things device.

35. The method according to claim 34, wherein The IoT device group identifier is allocated by a base station.

36. The method according to claim 35, wherein The first message is MsgB or Msg4.

37. The method of claim 34, wherein: The IoT device group identifier is allocated by a core network device, and the IoT device group identifier is determined based on the type of the 5G service quality identifier.

38. The method of claim 34, wherein: The IoT device group identifier is allocated by the core network device and is determined based on a service type.

39. The method according to claim 37 or 38, wherein After receiving the message from the core network device, the base station sends a first message, where the first message is a downlink non-access stratum (DL NAS).

40. The method of claim 39, wherein The paging method further includes receiving a second message sent by the Internet of Things device, where the second message includes an Internet of Things device identifier.

41. The method according to claim 40, wherein The second message is Msg5.

42. The method according to any one of claims 30 to 41, wherein: When the IoT device is a non-mobile IoT device, the paging message further includes an identifier of a cell where the IoT device is located. The base station receives the paging message sent by the core network device and forwards it to the IoT device.

43. The method according to any one of claims 30 to 41, wherein: When the Internet of Things device is a mobile Internet of Things device, the paging message further includes at least one of the following: the Internet of Things device group identifier, a tracking area list, and a wireless access network notification area list.

44. The method according to claims 30-41, wherein When the Internet of Things device is a mobile Internet of Things device, the broadcast message further includes at least one of the following: the Internet of Things device group identifier, a tracking area list, and a wireless access network notification area list.

45. The method according to claim 43 or 44, wherein The paging method further includes: sending the paging message or the broadcast message after sending the carrier activation signal.

46. ​​The method according to claim 43 or 44, wherein The paging message is also used for the IoT device to obtain energy, or the broadcast message is also used for the IoT device to obtain energy.

47. The method according to any one of claims 43 to 46, wherein: The paging method further includes: Receive a third message sent by the core network device; wherein the third message includes at least one of the following: the Internet of Things device group The mapping relationship between the identifier, the tracking area list, and the IoT device group identifier and the tracking area list; Send the third message to the IoT device.

48. The method according to any one of claims 30 to 47, wherein: The paging method further includes receiving a fourth message, wherein the fourth message includes a supported service type identifier, wherein the service type identifier corresponds to the message size in a one-to-one manner.

49. The method according to claim 48, wherein The paging method further includes sending a service type query request, wherein the service type query request is used to query the service types supported by the Internet of Things device.

50. The method of claim 48, wherein The paging method further includes sending a fifth message, where the fifth message includes at least one of the following: several service types and several message sizes corresponding to the several service types.

51. The method of claim 30, wherein: The configuration information further includes at least one of the following: partial information of a master information block and partial information of a system information block type 1.

52. The method of claim 51, wherein The configuration information is a broadcast message.

53. The method of claim 52, wherein: The configuration information is also used for the Internet of Things device to obtain energy, and the paging method also includes sending the configuration information only once.

54. The method of claim 53, wherein: The paging method further includes: sending the configuration information only once after sending the carrier activation signal.

55. The method of claim 51, wherein The paging message carries the configuration information.

56. The method of claim 55, wherein: The paging message is also used by the Internet of Things device to obtain energy. The paging method also includes the Internet of Things device sending the paging message only once each time it obtains energy.

57. The method of claim 55, wherein: The paging method further includes: sending the paging message only once after sending the carrier activation signal.

58. A wireless communication device, wherein: The wireless communication device includes: a processor and a memory, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the paging method according to any one of claims 30 to 57.

Images