Method, apparatus, and system for allocating and using resource

Abstract

Embodiments of the present application provide a method, an apparatus, and a system for allocating and using a resource for signal reception and transmission. The method comprises: a network device receives first information from a first device or from a core network; and the network device transmits second information to the first device, the second information being used for configuring a resource for the first device, and the resource being used for communication by the first device on an A-IoT wireless interface or for communication between the first device and a second device.

Description

Methods, apparatus and systems for resource allocation and use Technical Field

[0001] The embodiments of this application relate to the field of communication technology. Background Technology

[0002] From the early days of 2G (second generation) systems to the early days of 4G (fourth generation) systems, cellular mobile communication systems primarily served mobile phones, i.e., mobile terminal devices held by people. With the rapid development of mobile internet and the Internet of Things (IoT), from the later stages of 4G systems to the present, the evolution of cellular mobile communication system technology has considered and supported increasingly diverse IoT application scenarios. Correspondingly, more types of IoT device terminals have been supported and implemented in actual network deployments and service applications, such as eMTC (enhanced Machine-Type Communication) terminal devices, NB-IoT (Narrow Band Internet of Things) terminal devices, and RedCap (Reduced Capability) terminal devices. With the increasing diversity of IoT terminal device types, cellular mobile systems have gained increasingly stronger capabilities in providing services and offering services to vertical industries.

[0003] However, among the massive number of IoT devices, the area of ​​large-scale and lower-cost IoT terminal devices remains a gap in cellular mobile communication systems. In order to provide more robust, reliable, and complete IoT application solutions, how to support lower-cost IoT terminal devices in 3GPP (3rd Generation Partnership Project) cellular mobile systems has become an urgent problem to be solved.

[0004] It should be noted that the above introduction to the technical background is only for the purpose of providing a clear and complete explanation of the technical solutions of this application and facilitating understanding by those skilled in the art. It should not be assumed that these technical solutions are known to those skilled in the art simply because they have been described in the background section of this application.

[0005] Summary of the Invention

[0006] The inventor discovered:

[0007] RFID (Radio Frequency Identification, commonly known as electronic tags) systems are solutions for the large-scale, lower-cost Internet of Things (IoT) terminal devices. RFID systems have wide applications. The advantages of RFID systems include low cost and affordability of RFID tags. The small size of RFID tags reduces restrictions on the size and material of the items they can be used with, making them easy to apply to various scenarios such as item management and tracking. One disadvantage of RFID systems is the limited information reading range (i.e., the communication range based on wireless signals) of RFID tags. If a manual handheld tag reader is used, labor costs may become the main expense. Using dedicated RFID ports or gateways to read and manage RFID tags requires higher deployment costs. Furthermore, the simple logical architecture of RFID systems makes it difficult to effectively coordinate with interference in radio wave transmission, resulting in generally lower system capacity and spectrum utilization efficiency.

[0008] Compared to RFID systems, 3GPP's 5G (fifth generation) system supports tag-based terminal devices, allowing for the reuse of existing base station deployments and leveraging existing cellular mobile communication networks to support industry applications based on this type of terminal, thereby effectively reducing deployment and usage costs. 3GPP's 5G system provides reliable authentication, network coordination, and accurate and stable terminal device management mechanisms, and can also optimize the network to improve system capacity and spectrum utilization efficiency.

[0009] For R2D (reader to device), the only physical channel is the PRDCH (Physical Reader to Device CHannel), which carries any / all higher-layer payloads (including system information, if defined) and L1R2D control information (if defined). One possible PRDCH is shown in Figure 1.

[0010] For D2R (device to reader), the Physical Device to Reader Channel (PDRCH) carries any / all higher-layer payloads, responses sent from the device (e.g., device / A-IoT device) to the reader during a contention-based access process, and L1D2R control information (if defined). One possible PDRCH is shown in Figure 2, where Figure 2(a) illustrates the generation of a single PDRCH on a device with linear coding, and Figure 2(b) illustrates the generation of a single PDRCH on a device without linear coding. Furthermore, Figures 2(a) and (b) both address the presence of Forward Error Correction (FEC) and repetition.

[0011] The scheduling information for PDRCH transmissions is provided by the corresponding PDRCH.

[0012] For D2R scheduling, the following information can be explicitly / implicitly indicated to the device via the corresponding PRDCH:

[0013] Time domain resources;

[0014] Frequency domain resources;

[0015] MCS-like information;

[0016] Chip duration;

[0017] The ID associated with the device;

[0018] Repetitions.

[0019] For each message, use higher-level signaling and / or L1R2D control information.

[0020] For D2R, it may support time-domain multiple access and frequency-domain multiple access using a small frequency shift in the baseband.

[0021] For A-IoT (Ambient IoT), the information carried by the A-IoT air interface (such as command and / or inventory) is considered high-level data. The protocol stack for the A-IoT air interface between the A-IoT device and the reader includes at least the physical layer and the MAC layer. A new AS layer may be added above the A-IoT MAC layer, as shown in Figure 3. Supported functions include A-IoT paging, A-IoT random access procedures, and A-IoT data transmission.

[0022] The AS signaling process is shown in Figure 4, including:

[0023] Step A: A-IoT Paging. Based on the service request, the reader sends an A-IoT paging message to indicate which device needs to respond;

[0024] Step B: D2R Data (device ID) Transmission. The triggered A-IoT device performs device ID transmission, with or without using the A-IoT random access procedure;

[0025] Step C1: Possible R2D data transmission (e.g., for sending commands);

[0026] Step C2: Possible D2R data transmission (such as command responses).

[0027] For the "inventory-only" use case, steps A and B of the above AS procedure are used as the baseline; for the "inventory and command" or "command-only" use case, steps A, B, C1, and C2 of the above AS procedure are used as the baseline.

[0028] In topology 2, the radio resources used for the A-IoT radio interface between the A-IoT device and the UE reader are controlled by the network. These radio resources are dedicated to a single UE reader and are configured only through dedicated signaling. The mechanism of resource pools shared among UE readers is not currently considered. The UE reader can only perform A-IoT procedures on the A-IoT radio interface between the reader and the device if the radio resource configuration is valid within the cell. How to configure the radio resources of the A-IoT radio interface dedicated to a single UE reader through dedicated signaling and the validity of these radio resources are problems that urgently need to be solved.

[0029] To address at least one of the above-mentioned problems or other similar issues, embodiments of this application provide a method, apparatus, and system for resource allocation and use.

[0030] According to one aspect of the embodiments of this application, a method for resource allocation and use is provided, including:

[0031] The network device receives first information from the first device or from the core network;

[0032] The network device sends second information to the first device. The second information is used to configure resources for the first device. The resources are used for communication of the first device on the A-IoT wireless interface, or for communication between the first device and the second device.

[0033] According to another aspect of the embodiments of this application, a method for resource allocation and use is provided, comprising:

[0034] The first device receives second information sent by the network device. The second information is used to configure resources for the first device. The resources are used for communication of the first device on the A-IoT wireless interface, or for communication between the first device and the second device (A-IoT device).

[0035] According to another aspect of the embodiments of this application, a method for resource allocation and use is provided, comprising:

[0036] The core network sends initial information related to A-IoT to network devices;

[0037] The first information relates to A-IoT wireless interface resources, and / or the first information is used to indicate at least one of the following:

[0038] The first device is a UE reader;

[0039] The first device is an A-IoT-enabled UE;

[0040] The first device supports A-IoT processes, functions, or capabilities;

[0041] The first device has A-IoT reading functionality or capability;

[0042] The first device has a public reader function;

[0043] The first device is capable of performing or supporting the A-IoT process;

[0044] A-IoT processes or services.

[0045] According to another aspect of the embodiments of this application, an apparatus for resource allocation and use is provided, configured in a network device, including:

[0046] A receiving unit that receives first information from a first device or from a core network;

[0047] The transmitting unit sends second information to the first device, the second information being used to configure resources for the first device, the resources being used for communication of the first device on the A-IoT wireless interface, or for communication between the first device and the second device.

[0048] According to another aspect of the embodiments of this application, a resource allocation and usage apparatus is provided, configured in a first device, comprising:

[0049] The receiving unit receives second information sent by the network device. The second information is used to configure resources for the first device. The resources are used for communication of the first device on the A-IoT wireless interface, or for communication between the first device and the second device (A-IoT device).

[0050] According to another aspect of the embodiments of this application, a resource allocation and usage apparatus is provided, configured in a core network, including:

[0051] The transmitting unit sends first information related to A-IoT to the network device;

[0052] The first information relates to A-IoT wireless interface resources, and / or the first information is used to indicate at least one of the following:

[0053] The first device is a UE reader;

[0054] The first device is an A-IoT-enabled UE;

[0055] The first device supports A-IoT processes, functions, or capabilities;

[0056] The first device has A-IoT reading functionality or capability;

[0057] The first device has a public reader function;

[0058] The first device is capable of performing or supporting the A-IoT process;

[0059] A-IoT processes or services.

[0060] According to another aspect of the embodiments of this application, a communication system is provided, including the aforementioned network device, the aforementioned core network, the aforementioned first device, and the aforementioned second device.

[0061] One of the beneficial effects of this application embodiment is that: the network device receives first information from a first device (e.g., UE) or the core network and sends second information to the first device to configure the (wireless) resources for transmission or communication (on the A-IoT radio / air interface) between the first device and the second device (A-IoT device). Therefore, it is possible to support the allocation of wireless resources for communication between the UE and A-IoT device on the A-IoT radio / air interface under different A-IoT upper layer information transmission mechanisms in Topology 2, thereby ensuring the A-IoT process or function in Topology 2.

[0062] Specific embodiments of this application are disclosed in detail with reference to the following description and accompanying drawings, indicating how the principles of this application can be adopted. It should be understood that the embodiments of this application are not limited in scope. Within the spirit and scope of the appended claims, embodiments of this application include many changes, modifications, and equivalents.

[0063] Features described and / or illustrated for one embodiment may be used in the same or similar manner in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments.

[0064] It should be emphasized that the term "including / comprises" as used herein refers to the presence of a feature, whole, step, or component, but does not exclude the presence or addition of one or more other features, wholes, steps, or components. Attached Figure Description

[0065] The elements and features described in one drawing or embodiment of this application may be combined with elements and features shown in one or more other drawings or embodiments. Furthermore, in the drawings, similar reference numerals denote corresponding parts in several drawings and can be used to indicate corresponding parts used in more than one embodiment.

[0066] Figure 1 is a schematic diagram of PRDCH;

[0067] Figure 2 is a schematic diagram of PDRCH;

[0068] Figure 3 is a schematic diagram of the protocol stack of the A-IoT air interface between the A-IoT device and the reader;

[0069] Figure 4 is a schematic diagram of the AS signaling process;

[0070] Figure 5 is a schematic diagram of a communication system according to an embodiment of this application;

[0071] Figure 6 is another schematic diagram of the communication system according to an embodiment of this application;

[0072] Figure 7 is another schematic diagram of the communication system according to an embodiment of this application;

[0073] Figure 8 is a schematic diagram of the logical system structure of Topology 2;

[0074] Figure 9 is a schematic diagram of a resource allocation and usage method according to an embodiment of this application;

[0075] Figure 10 is a schematic diagram of the resource allocation method on the A-IoT radio interface;

[0076] Figure 11 is another schematic diagram of the resource allocation method on the A-IoT radio interface;

[0077] Figure 12 is another schematic diagram of the resource allocation method on the A-IoT radio interface;

[0078] Figure 13 is another schematic diagram of the resource allocation method on the A-IoT radio interface;

[0079] Figure 14 is another schematic diagram of the resource allocation and usage method according to an embodiment of this application;

[0080] Figure 15 is another schematic diagram of the resource allocation and usage method according to an embodiment of this application;

[0081] Figure 16 is a schematic diagram of a resource allocation and usage apparatus according to an embodiment of this application;

[0082] Figure 17 is another schematic diagram of a resource allocation and usage apparatus according to an embodiment of this application;

[0083] Figure 18 is another schematic diagram of a resource allocation and usage apparatus according to an embodiment of this application;

[0084] Figure 19 is a schematic diagram of a network device according to an embodiment of this application;

[0085] Figure 20 is a schematic diagram of a terminal device according to an embodiment of this application;

[0086] Figure 21 is a schematic diagram of a core network device according to an embodiment of this application. Detailed Implementation

[0087] Referring to the accompanying drawings, the foregoing and other features of this application will become apparent from the following description. Specific embodiments of this application are specifically disclosed in the description and drawings, illustrating partial implementations in which the principles of this application may be employed. It should be understood that this application is not limited to the described embodiments; rather, it includes all modifications, variations, and equivalents falling within the scope of the appended claims.

[0088] In the embodiments of this application, the terms "first," "second," etc., are used to distinguish different elements by name, but do not indicate the spatial arrangement or chronological order of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one or more of the terms listed in association and all combinations thereof. The terms "comprising," "including," "having," etc., refer to the presence of the stated features, elements, components, or assemblies, but do not exclude the presence or addition of one or more other features, elements, components, or assemblies.

[0089] In the embodiments of this application, the singular forms "a," "the," etc., including the plural forms, should be broadly understood as "a kind" or "a class" rather than limited to the meaning of "an." Furthermore, the term "the" should be understood to include both the singular and plural forms, unless the context explicitly indicates otherwise. Additionally, the term "according to" should be understood as "at least partially based on…," and the term "based on" should be understood as "at least partially based on…," unless the context explicitly indicates otherwise.

[0090] In the embodiments of this application, the term "communication network" or "wireless communication network" may refer to a network that conforms to any of the following communication standards, such as Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), Ambient IoT, etc.

[0091] Furthermore, communication between devices in a communication system can be carried out according to communication protocols at any stage, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G, New Radio (NR), future 6G, etc., and / or other currently known or future communication protocols.

[0092] In the embodiments of this application, the term "network device" refers, for example, to a device in a communication system that connects a terminal device to a communication network and provides services to that terminal device. Network devices may include, but are not limited to, the following devices: base station (BS), access point (AP), transmission reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), etc. Furthermore, network devices may also include readers or interrogators for A-IoT, but this application is not limited to these devices.

[0093] Base stations can include, but are not limited to: NodeBs (or NBs), evolved NodeBs (eNodeBs or eNBs), 5G base stations (gNBs), IAB (Integrated Access and Backhaul) hosts, etc. They can also include Remote Radio Heads (RRHs), Remote Radio Units (RRUs), relays or low-power nodes (e.g., femeto, pico, etc.), reders, or interrogators. The term "base station" can encompass some or all of their functions, and each base station can provide communication coverage to a specific geographic area. The term "cell" can refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0094] In the embodiments of this application, the terms "User Equipment" (UE) or "Terminal Equipment" (TE) refer, for example, to a device that accesses a communication network and receives network services through a network device. A terminal device can be fixed or mobile, and may also be referred to as a mobile station (MS), terminal, subscriber station (SS), access terminal (AT), tag, etc.

[0095] The terminal device may include, but is not limited to, the following devices: cellular phone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, machine communication device, laptop computer, cordless phone, smartphone, smartwatch, digital camera, tag, device attached to or related to an item (e.g., for item management), etc.

[0096] For example, in scenarios such as the Internet of Things (IoT), terminal devices can also be machines or devices for monitoring or measurement, including but not limited to: machine-type communication (MTC) terminals, vehicle communication terminals, device-to-device (D2D) terminals, machine-to-machine (M2M) terminals, ambient IoT devices (A-IoT), etc.

[0097] Furthermore, the terms "network side" or "network equipment side" refer to one side of the network, which can be a base station or include one or more network devices as described above. The terms "user side," "terminal side," or "terminal equipment side" refer to the side of the user or terminal, which can be a UE or include one or more terminal devices as described above. Unless otherwise specified, "equipment" can refer to either network equipment or terminal equipment.

[0098] The following examples illustrate the scenarios of embodiments of this application, but this application is not limited thereto.

[0099] Figure 5 is a schematic diagram of a communication system, Figure 6 is another schematic diagram of a communication system, and Figure 7 is yet another schematic diagram of a communication system. Figures 5 to 7 illustrate the situation using terminal equipment and network equipment as examples.

[0100] As shown in Figure 5, network devices can communicate directly with A-IoT devices, sending signals directly to or receiving signals directly from A-IoT devices. As shown in Figure 6, network devices can also send signals to or receive signals from A-IoT devices through intermediate nodes. As shown in Figure 7, network devices can also send signals to or receive signals from A-IoT devices with the assistance of assisting nodes.

[0101] Intermediate nodes can be terminal devices, UEs, or network nodes, such as relays, IAB nodes, repeaters, etc., and this application is not limited to these. Intermediate nodes have the function of communicating with the network devices in Figure 6, and at least have the ability to send signals to and / or receive signals from A-IoT devices. Auxiliary nodes can be terminal devices, UEs, or network nodes, such as relays, IAB nodes, repeaters, etc., and this application is not limited to these. Auxiliary nodes have the function of communicating with the network devices in Figure 7, and at least have the ability to send signals to and / or receive signals from A-IoT devices. The signals sent to and received from A-IoT devices as described herein conform to the specifications and descriptions of A-IoT devices in communication standard protocols.

[0102] In the examples in Figures 5 to 7, the network device sends signals / information / configurations to the A-IoT device, or the A-IoT device receives signals / information / configurations from the network device. This can be done by the network device sending the signals directly to the A-IoT device and receiving them, by the network device sending the signals to the A-IoT device via an intermediate node and receiving them, by the network device sending the signals to the A-IoT device with the help of an auxiliary node and receiving them, or by the network device sending the signals to the A-IoT device through other methods and receiving them.

[0103] In the examples in Figures 5 to 7, the A-IoT device sends signals / information to the network device or the network device receives signals / information from the A-IoT device. This can be done by the A-IoT device sending the signal and the network device receiving it directly, by the A-IoT device sending the signal and the network device receiving it through an intermediate node, by the A-IoT device sending the signal and the network device receiving it with the help of an auxiliary node, or by the A-IoT device sending the signal and the network device receiving it through other methods.

[0104] This application embodiment applies to the scenario of Topology 2 shown in Figure 6. In Topology 2, as shown in Figure 6, A-IoT devices communicate bidirectionally with an intermediate node. In this topology, the intermediate node can be a relay, IAB node, user equipment (UE), repeater, etc., with A-IoT capabilities. The intermediate node transmits A-IoT data and / or signaling between the A-IoT device and the network device. Currently, UEs are supported as intermediate nodes, and scenarios where the UE acts as a reader within the coverage area of ​​the network device are also supported.

[0105] Figure 8 is a schematic diagram of the logical system structure of Topology 2. As shown in Figure 8, the "common reader function" is located in the "A-IoT-enabled UE", the "A-IoT RAN node function" is located in the "A-IoT-enabled gNB", and the "A-IoT CN" may include AMF (Authentication Management Function) and A-IoT related functions.

[0106] In the structure shown in Figure 8, the "A-IoT-enabled UE" is a UE that supports the common reader function and can communicate with A-IoT devices via the A-IoT radio interface; the "A-IoT-enabled gNB" is a gNB that supports the A-IoT RAN node function and can communicate with the A-IoT-enabled UE via the NR Uu interface. The A-IoT-enabled gNB can perform radio resource management of A-IoT related radio resources.

[0107] Currently, the following solutions exist for transmitting A-IoT upper layer information:

[0108] The solution is based on RRC (Radio Resource Control). Using this solution, the A-IoT CN explicitly transmits A-IoT upper layer information via XXAP (XX Application Protocol) signaling, and then forwards the A-IoT upper layer information to or from the A-IoT-enabled UE via NR Uu RRC.

[0109] A NAS (Non-Access Stratum) based solution: With this solution, there is no explicit termination of A-IoT upper layer information at the A-IoT-enabled gNB; the A-IoT upper layer information is sent via the NAS of the A-IoT-enabled UE.

[0110] The solution is based on the UP (User Plane). With this solution, there is no explicit termination of A-IoT upper layer information at the A-IoT-enabled gNB; the A-IoT upper layer information is transmitted as user plane data of the A-IoT-enabled UE.

[0111] The specific implementation of the embodiments of this application will be described below with reference to the accompanying drawings. In the following description, without causing confusion, "if...", "in the case of...", and "when..." have the same meaning and can be used interchangeably; "RRC signaling" and "RRC message" have the same meaning and can be used interchangeably.

[0112] First aspect of the embodiments

[0113] This application provides a method for resource allocation and use, described from the perspective of a network device.

[0114] Figure 9 is a schematic diagram of a resource allocation and usage method according to an embodiment of this application. As shown in Figure 9, the method includes:

[0115] 910: The network device receives the first information from the first device or from the core network;

[0116] 920: The network device sends second information to the first device, the second information being used to configure resources for the first device, the resources being used for communication of the first device on the A-IoT wireless interface, or for communication between the first device and the second device.

[0117] It is worth noting that Figure 9 above is only an illustrative description of the embodiments of this application, but this application is not limited thereto. For example, the execution order between various operations can be appropriately adjusted, and other operations can be added or some operations can be removed. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description in Figure 9 above.

[0118] In the above embodiments, taking the scenario shown in Figure 6 as an example, the network device is the network device in the scenario shown in Figure 6, which has A-IoT RAN node function or an A-IoT enabled gNB, etc.; the first device is the intermediate node in the scenario shown in Figure 6, which can be a UE reader or an A-IoT enabled UE, etc.; the second device is the A-IoT device in the scenario shown in Figure 6. Furthermore, in the above embodiments, the core network (CN) includes at least AMF and A-IoT related functions.

[0119] According to the above embodiments, the network device receives first information from a first device (e.g., UE) or the core network (CN) and sends second information to the first device to configure resources for transmission or communication between the first device and the second device (A-IoT device), such as wireless resources for transmission or communication on the A-IoT radio interface (A-IoT radio / air interface, e.g., A-IoT radio interface or A-IoT Uu interface). This enables the allocation of wireless resources for communication between the UE and A-IoT device on the A-IoT radio interface under different A-IoT upper layer information transmission mechanisms in Topology 2, thereby ensuring the A-IoT process or function in Topology 2.

[0120] In this application embodiment, the first information is used to request or instruct a network device to configure resources for a first device. In some embodiments, the first information is used to instruct at least one of the following:

[0121] The first device is a UE reader (or UE reader).

[0122] The first device is an A-IoT-enabled UE;

[0123] The first device supports A-IoT processes, functions, or capabilities;

[0124] The first device has A-IoT reading function or capability;

[0125] The first device has a common reader function;

[0126] The first device is capable of performing or supporting the A-IoT process.

[0127] According to the above embodiments, by receiving the first information, the network device can confirm the function, type, or capabilities of the first device, and then pre-allocate appropriate resources to the first device. This simplifies the implementation of the network device, avoids implementation complexities, and thus reduces deployment costs.

[0128] In the above embodiments, the first information may come from the first device, that is, the first device makes the above instruction through the first information; or, the first information may also come from the core network, that is, the core network makes the above instruction through the first information.

[0129] If the first information originates from the first device, it can be carried by an RRC message, such as a UE capability message, an RRC establishment completion message, an RRC reconstruction completion message, an RRC reconfiguration completion message, etc. Furthermore, the first information can be carried by one or more of the aforementioned messages; this application does not limit the specific carrying method.

[0130] If the first information comes from the core network, it can be carried by the application protocol (AP) signaling of the interface between the core network and the network device, that is, by xxAP, where xx represents the interface between the core network (such as the existing functional module AMF or A-IoT related functional module in the core network) and the network device. For example, the first information can be carried by the interface between the AMF and the network device, such as the NG-C interface.

[0131] In other embodiments, the first information is used to indicate an A-IoT process or service, or the first information is related to A-IoT wireless interface (A-IoT radio / air interface) resources.

[0132] According to the above embodiments, by receiving the first information, the network device can identify which processes or services are requesting resources, and then pre-allocate appropriate resources to the first device. This results in high resource utilization, thereby ensuring system throughput.

[0133] In the above embodiments, the first information may be the estimated or expected size of the A-IoT wireless interface (A-IoT radio / air interface) resources, which may be represented, for example, by at least one of the following methods:

[0134] The size of the resource corresponds to the buffer size.

[0135] The scale of the resources, such as large, medium, small, etc.;

[0136] The number of messages or the size of messages corresponding to the resource;

[0137] The duration or length of time corresponding to the resource;

[0138] The number of second devices (A-IoT devices) that need to communicate.

[0139] The above are just examples; this application is not limited to these. The first information can also be represented in other ways, depending on the scenario and needs.

[0140] In the above embodiments, the first information may come from the first device, that is, the first device makes the above instruction through the first information, or the first device sends the first information related to A-IoT wireless interface resources to the network device; the first information may also come from the core network, that is, the core network makes the above instruction through the first information, or the core network sends the first information related to A-IoT wireless interface resources to the network device.

[0141] If the first information comes from the first device, the first information can be transmitted after the service request from the second device, or after the service response from the second device.

[0142] This first information can be carried by RRC signaling, such as by UAI (UE Assistance Information) messages, or by RRC reconfiguration completion messages, etc.

[0143] This first information can also be carried by MAC CE signaling, such as through BSR (Buffer Status Report) MAC CE, pre-emptive BSR MAC CE, or a MAC CE different from existing MAC CEs, etc. Whether the MAC CE is used for the A-IoT wireless interface can be identified by the logical channel identifier or enhanced logical channel identifier of the MAC CE, or by a field in the subheader of the MAC CE, or by a logical channel group configured by the network device; this application is not limited to these methods.

[0144] This first information can also be carried by UCI (Uplink Control Information) signaling, for example, by a resource request, or by a scheduling request (SR), or by a request dedicated to A-IoT wireless interface resources, and so on.

[0145] The above are just examples. The first information can also be carried by any combination of the above signaling. This application does not limit the specific carrying method.

[0146] If the first information comes from the core network, it can be transmitted together with the service request from the second device, or it can be transmitted after the service request from the second device.

[0147] The first information can be carried by the application protocol signaling of the interface between the core network and the network device, that is, by xxAP, where xx represents the interface between the core network (such as the existing functional module AMF or A-IoT related functional module in the core network) and the network device. For example, the first information can be carried by NGAP of the interface between the AMF and the network device, such as the NG-C interface.

[0148] In this example, the first information and the service request of the second device are transmitted together. This applies to both RRC and NAS architectures. In other words, under either an RRC or NAS architecture, the first information can be transmitted together with the service request of the second device.

[0149] In this example, the first information is transmitted after the service request from the second device. This applies to RRC architecture, NAS architecture, and UP-based architecture. That is, under RRC architecture, NAS architecture, or UP-based architecture, the first information can be transmitted after the service request from the second device.

[0150] In the above embodiments, under the RRC architecture, the "service request of the second device" is transmitted from the core network to the network device and then to the second device (A-IoT device); the "service response of the second device" is sent from the second device (A-IoT device) to the first device (UE reader) and then to the core network. Under the NAS or UP-based architecture, the "service request of the second device" is transmitted from the core network to the second device (A-IoT device) via the network device (invisible); the "service response of the second device" is transmitted from the second device (A-IoT device) to the core network via the first device (UE reader) (invisible).

[0151] For information on the "service request of the second device" and the "service response of the second device", please refer to the relevant technologies; they will not be elaborated here.

[0152] In this embodiment, the second information is used to configure resources for the first device. In some embodiments, the second information includes at least one of the following:

[0153] The index or ID of a resource;

[0154] Time domain resources;

[0155] Frequency domain resources;

[0156] Chip duration;

[0157] Starting point or offset;

[0158] cycle;

[0159] Duration.

[0160] For example, a network device configures resources for a first device by sending time-domain resources (e.g., at least one of start point, offset, period, and duration) and / or frequency-domain resources to the first device. Optionally, the network device may also send slice durations, etc. Furthermore, in some possible implementations, the network device may also send an index or identifier of a resource to the first device to associate the corresponding resource, so that the first device can process the resource using the associated index or identifier, such as releasing (e.g., using a release list in RRC signaling) or activating / deactivating (e.g., using MAC CE or DCI).

[0161] In the above embodiments, the resources configured by the network device for the first device may be resources configured for the first device, and / or resources configured for A-IoT services or processes, and / or resources configured for paging messages, and / or resources configured for each access round of paging messages, and / or resources configured for each R2D transmission, and / or resources configured for each D2R transmission, and / or resources configured for R2D and D2R transmission pairs, and / or resources configured for each time slot, and / or resources configured for each R2D trigger.

[0162] For example, the network device pre-configures resources for the first device. When the first information indicates that "the first device is a UE reader / the first device is an A-IoT enabled UE / the first device supports A-IoT procedures or functions or capabilities / the first device has A-IoT reader functions or capabilities / the first device has common reader functions / the first device has performed or supports A-IoT procedures", the network device may configure resources for the first device for one or each first device.

[0163] For example, in cases where the first information is used to indicate an A-IoT process or service, or where the first information is related to A-IoT wireless interface resources:

[0164] Network devices can configure resources for the first device for one or each A-IoT service or process;

[0165] If an A-IoT service or process involves, includes, or is associated with one or more paging messages, the network device may configure resources for the first device for one or each paging message (of the A-IoT service or process);

[0166] If a paging message involves, includes, or is associated with one or more access rounds, the network device may configure resources for the first device for one or each access round (of the paging message);

[0167] If an A-IoT service, process, or paging message involves, includes, or is associated with one or more R2D triggers, the network device can configure resources for the first device for one or each R2D trigger (of the A-IoT service, process, or paging message);

[0168] If an A-IoT service or process involves, includes, or is associated with one or more transmissions, the network device may configure resources for the first device for one or each R2D transmission (of the A-IoT service or process), and / or the network device may configure resources for the first device for one or each D2R transmission (of the A-IoT service or process), and / or the network device may configure resources for the first device for one or each R2D and D2R transmission pair (of the A-IoT service or process);

[0169] If an A-IoT service, process, or access round involves, includes, or is associated with one or more time slots, the network device may configure resources for the first device for one or each time slot (of the A-IoT service, process, or access round);

[0170] etc.

[0171] The above are just examples; the resources configured by the network device for the first device can be any combination of the above.

[0172] In the above embodiments, the second information may be included in an RRC message or signaling, and / or in a MAC CE, and / or in a DCI, and this application is not limited thereto. For example, the second information may be at least one of the following:

[0173] Information carried by RRC signaling or messages;

[0174] Information elements (IEs), fields, or information contained in RRC signaling or messages;

[0175] Information indicated or carried by MAC CE;

[0176] Information contained in MAC CE;

[0177] Information indicated or carried by downlink control information (DCI);

[0178] Information included in the DCI.

[0179] In this embodiment of the application, the resources configured by the network device for the first device may take effect when / after the network device sends the second information, or when / after the first device receives the second information.

[0180] In the above embodiments, once the resource is active or valid, the first device can use the resource to communicate with the second device.

[0181] In this application implementation, the resources configured by the network device for the first device may become invalid when / after at least one of the following events occurs:

[0182] The network device indicates whether to release, deactivate, or disable the resource;

[0183] The first device is not located within the area related to this resource; for example, the first device is not located in one or more cells or areas configured in the current cell or network device, etc.

[0184] The effective time corresponding to the resource has been reached or exceeded. This effective time can be configured by the network device or it can be predefined.

[0185] In the above embodiments, when or after the resource fails, the first device may perform at least one of the following operations:

[0186] Pause, stop, or suspend communication with the second device;

[0187] Discard any information or data received from the second device;

[0188] Discard relevant information about the second device, such as the AS ID (Access Stratum ID);

[0189] Release the resource;

[0190] Release the resource and its associated configuration; and

[0191] Discard A-IoT upper layer information from the core network.

[0192] The embodiments of this application will be described below with reference to specific examples. In the following examples, option 1 corresponds to the case where "the first information indicates that the first device is a UE reader / the first device is an A-IoT enabled UE / the first device supports A-IoT procedures or functions or capabilities / the first device has A-IoT reader functions or capabilities / the first device has common reader functions / the first device has performed or supports A-IoT procedures", and option 2 corresponds to the case where "the first information indicates an A-IoT procedure or service or the first information is related to A-IoT wireless interface resources".

[0193] Figure 10 is a schematic diagram of the resource allocation method on the A-IoT radio interface. In this example, the first device is a UE reader, the second device is an A-IoT device, and the network device is a base station (BS).

[0194] As shown in Figure 10, according to the method of this application embodiment, in options 1 and 2, the BS receives a UE indication (first information) sent by the UE. Based on the UE indication, the BS sends resource configuration (second information) to the UE, providing the UE with radio resources for communication between the UE and the A-IoT device. Specifically, as shown in Figure 10, in option 2, the BS first transmits the A-IoT upper layer information (e.g., inventory / command) received from the CN to the UE via RRC signaling, and then sends resource allocation; in option 1, the BS first sends resource allocation to the UE, and then transmits the A-IoT upper layer information (e.g., inventory / command) received from the CN to the UE via RRC signaling. Furthermore, as shown in Figure 10, the BS transmits the A-IoT upper layer information (e.g., reports / responses corresponding to inventory / command) received from the UE via RRC signaling to the CN.

[0195] Figure 11 is another schematic diagram of the resource allocation method on the A-IoT radio interface. In this example, the first device is a UE reader, the second device is an A-IoT device, and the network device is a base station (BS).

[0196] As shown in Figure 11, according to the method of this application embodiment, in options 1 and 2, the BS receives a UE instruction (first information) sent by the UE. Based on the instruction, the BS sends resource configuration (second information) to the UE, providing the UE with radio resources for communication between the UE and the A-IoT device. As shown in Figure 11, the CN also sends A-IoT upper layer information (e.g., inventory / command) to the UE via NAS signaling or data. For option 1, this process can be performed after the BS sends the resource configuration to the UE; for option 2, this process can be performed before the BS sends the resource configuration to the UE. Furthermore, as shown in Figure 11, the UE transmits A-IoT upper layer information (e.g., reports / responses corresponding to inventory / command) to the CN via NAS signaling or UP.

[0197] Figure 12 is another schematic diagram of the resource allocation method on the A-IoT radio interface. In this example, the first device is the UE reader, the second device is the A-IoT device, and the network device is the base station (BS).

[0198] As shown in Figure 12, according to the method of this application embodiment, in option 1, the BS receives xxAP signaling (first information) from the CN, which includes, for example, a UE reader notification. Based on this, the BS sends resource configuration (second information) to the UE, providing the UE with radio resources for communication between the UE and the A-IoT device. In option 2, the BS receives xxAP signaling (first information) from the CN, which includes, for example, A-IoT upper layer information (e.g., inventory / command) and a UE reader notification. Based on this, the BS sends resource configuration (second information) to the UE via RRC signaling, providing the UE with radio resources for communication between the UE and the A-IoT device. Optionally, as shown in Figure 12, the BS can also send the A-IoT upper layer information (e.g., inventory / command) from the CN to the UE. Furthermore, as shown in Figure 12, the BS can also transmit to the CN the A-IoT upper layer information (e.g., reports / responses corresponding to inventory / command) received from the UE via RRC signaling.

[0199] Figure 13 is another schematic diagram of the resource allocation method on the A-IoT radio interface. In this example, the first device is the UE reader, the second device is the A-IoT device, and the network device is the base station (BS).

[0200] As shown in Figure 13, according to the method of this application embodiment, in option 1, the BS receives xxAP signaling (first information) from the CN. This xxAP signaling includes, for example, a UE reader notification. Based on this, the BS sends resource configuration to the UE.

[0201] (Second Information) provides the UE with radio resources for communication between the UE and the A-IoT device; in Option 2, the BS receives xxAP signaling (first information) from the CN, which includes, for example, information related to services or A-IoT devices. Based on this, the BS sends resource configuration (second information) to the UE, providing the UE with radio resources for communication between the UE and the A-IoT device. Furthermore, as shown in Figure 13, the CN also sends A-IoT upper layer information to the UE.

[0202] (e.g., inventory / command) For option 1, this process can be performed after the BS sends the resource configuration to the UE; for option 2, this process can be performed after the BS receives the xxAP signaling from the CN. In addition, as shown in Figure 13, the UE transmits A-IoT upper layer information (e.g., reports / responses corresponding to inventory / command) to the core network (CN) via NAS signaling or UP.

[0203] The implementation methods for the first and second information have already been explained above, and will not be repeated here.

[0204] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0205] As can be seen from the above embodiments, the network device receives first information from a first device (e.g., UE) or the core network (CN) and sends second information to the first device to configure the resources for transmission or communication between the first device and the second device (A-IoT device), such as the wireless resources for transmission or communication on the A-IoT radio / air interface. Therefore, it is possible to support the allocation of wireless resources for communication between the UE and A-IoT device on the A-IoT radio interface under different A-IoT upper layer information transmission mechanisms in Topology 2, thereby ensuring the A-IoT process or function in Topology 2.

[0206] Second aspect of the embodiments

[0207] This application provides a method for resource allocation and use, described from the perspective of a terminal device. This terminal device is, for example, an intermediate node in the topology 2 scenario shown in Figure 6, and can be a UE reader, an A-IoT-enabled UE, etc. The embodiments of the second aspect can be implemented in conjunction with the embodiments of the first aspect, or they can be implemented independently. Content identical to that in the embodiments of the first aspect will not be repeated.

[0208] Figure 14 is a schematic diagram of a resource allocation and usage method according to an embodiment of this application. As shown in Figure 14, the method includes:

[0209] 1410: The first device receives second information sent by the network device. The second information is used to configure resources for the first device. These resources are used for communication of the first device on the A-IoT wireless interface, or for communication between the first device and the second device (A-IoT device).

[0210] According to the above embodiments, the network device can configure resources for transmission or communication between the first device and the second device (A-IoT device), such as wireless resources for transmission or communication on the A-IoT wireless interface (A-IoT radio / air interface). This enables the allocation of wireless resources for communication between the UE and the A-IoT device on the A-IoT wireless interface under different A-IoT upper layer information transmission mechanisms in Topology 2, thereby ensuring the A-IoT process or function in Topology 2.

[0211] In some embodiments, the second information includes at least one of the following:

[0212] The index or ID of a resource;

[0213] Time-domain resources;

[0214] Frequency domain resources;

[0215] Chip duration;

[0216] Starting point or offset;

[0217] cycle;

[0218] Duration.

[0219] In some embodiments, the second information is at least one of the following:

[0220] Information carried by RRC signaling or messages;

[0221] Information elements (IEs), fields, or information contained in RRC signaling or messages;

[0222] Information indicated or carried by MAC CE;

[0223] Information contained in MAC CE;

[0224] Information indicated or carried by downlink control information (DCI);

[0225] Information included in the DCI.

[0226] In some embodiments, the resources configured by the network device for the first device are at least one of the following:

[0227] Resources configured for the first device;

[0228] Resources configured for A-IoT services or processes;

[0229] Resources configured for paging messages;

[0230] Resources configured for each access round of paging messages;

[0231] Resources configured for each R2D (repeater to device) transmission;

[0232] Resources configured for each D2R (device to repeater) transmission;

[0233] Configure the resources for each R2D and D2R transport pair;

[0234] Resources configured for each slot;

[0235] Resources configured for each R2D trigger message.

[0236] The relevant content regarding the second information and the resources configured by the network device for the first device have been described in the embodiments of the first aspect, and their content is incorporated herein by reference and will not be repeated here.

[0237] In some embodiments, as shown in FIG14, the method further includes:

[0238] 1420: The first device sends the first message to the network device.

[0239] According to the above embodiments, the first device sends first information to the network device, requesting the network device to configure resources for it through the first information.

[0240] In some embodiments, the first information is used to indicate at least one of the following:

[0241] The first device is the UE reader;

[0242] The first device is an A-IoT enabled UE;

[0243] The first device supports A-IoT processes, functions, or capabilities;

[0244] The first device has A-IoT reader functionality or capability;

[0245] The first device has a common reader function;

[0246] The first device is capable of performing or supporting the A-IoT process.

[0247] In the above embodiments, the first information can be carried by an RRC message / signaling, for example, it can be carried by at least one of the following:

[0248] UE capability messages;

[0249] RRC establishment complete message;

[0250] RRC reconstruction complete message;

[0251] RRC reconfiguration complete message.

[0252] In other embodiments, the first information is used to indicate an A-IoT process or service, or the first information is related to A-IoT wireless interface resources.

[0253] In the above embodiments, the first information may be the estimated or expected size of the A-IoT wireless interface resources, expressed as at least one of the following:

[0254] The size of the resource corresponds to the buffer size.

[0255] The scale indication corresponding to the resource;

[0256] The number of messages or the size of messages corresponding to the resource;

[0257] The duration or length of time corresponding to the resource;

[0258] The number of A-IoT devices that need to communicate.

[0259] In the above embodiments, the first information can be transmitted after the service request or response from the second device.

[0260] In the above embodiments, the first information may be carried by at least one of RRC signaling, MAC CE signaling, and UCI signaling.

[0261] The relevant content regarding the first information has been described in the embodiments of the first aspect, and its content is incorporated herein, and will not be repeated here.

[0262] The method of the embodiments of this application will be described below with reference to the examples in Figures 10 to 13.

[0263] As shown in Figure 10, according to the method of this application embodiment, in options 1 and 2, the UE sends a UE instruction (first information) to the BS and receives resource configuration (second information) from the BS. This resource configuration includes the radio resources provided by the BS for communication between the UE and A-IoT devices. Specifically, as shown in Figure 10, in option 2, the UE first receives A-IoT upper layer information (e.g., inventory / command) received from the CN via RRC signaling from the BS, and then receives resource allocation; in option 1, the UE first receives resource allocation from the BS, and then receives A-IoT upper layer information (e.g., inventory / command) received from the CN via RRC signaling from the BS. Furthermore, as shown in Figure 10, the UE also sends A-IoT upper layer information (e.g., reports / responses corresponding to inventory / commands) to the BS via RRC signaling so that the BS can transmit it to the CN.

[0264] As shown in Figure 11, according to the method of this application embodiment, in options 1 and 2, the UE sends a UE instruction (first information) to the BS and receives resource configuration (second information) from the BS. This resource configuration includes the radio resources provided by the BS for communication between the UE and A-IoT devices. As shown in Figure 11, the UE also receives A-IoT upper layer information (e.g., inventory / command) from the CN. For option 1, this process can be performed after the UE receives the resource configuration from the BS; for option 2, this process can be performed before the UE receives the resource configuration from the BS. Furthermore, as shown in Figure 11, the UE can also transmit A-IoT upper layer information (e.g., reports / responses corresponding to inventory / commands) to the CN via NAS signaling or UP.

[0265] As shown in Figure 12, according to the method of this application embodiment, in option 1, the UE receives resource configuration (second information) sent by the BS via RRC signaling. This resource configuration is sent by the BS after receiving xxAP signaling (first information) from the CN. The xxAP signaling includes, for example, a UE reader notification. Based on this, the BS sends resource configuration (second information) to the UE to provide the UE with radio resources for communication between the UE and A-IoT devices. In option 2, the UE receives resource configuration (second information) sent by the BS via RRC signaling. This resource configuration is sent by the BS after receiving xxAP signaling (first information) from the CN. The xxAP signaling includes, for example, A-IoT upper layer information (e.g., inventory / command) and a UE reader notification. Based on this, the BS sends resource configuration (second information) to the UE via RRC signaling to provide the UE with radio resources for communication between the UE and A-IoT devices. Optionally, as shown in Figure 12, the UE can also receive A-IoT upper layer information (e.g., inventory / command) obtained from the CN and sent by the BS via RRC signaling. As shown in Figure 12, the UE can also send A-IoT upper layer information (such as inventory / command reports / responses) to the BS via RRC signaling so that the BS can transmit it to the CN.

[0266] As shown in Figure 13, according to the method of this application embodiment, in option 1, the UE receives resource configuration from the BS.

[0267] (Second Information) This resource configuration is sent by the BS after receiving the xxAP signaling (first information) from the CN. This xxAP signaling may include, for example, a UE reader notification. Based on this, the BS sends the resource configuration (second information) to the UE, providing the UE with radio resources for communication between the UE and A-IoT devices. In Option 2, the UE receives the resource configuration (second information) from the BS, which is sent by the BS after receiving the xxAP signaling (first information) from the CN. This xxAP signaling may include, for example, information related to services or A-IoT devices. Based on this, the BS sends the resource configuration (second information) to the UE, providing the UE with radio resources for communication between the UE and A-IoT devices. Furthermore, as shown in Figure 13, the UE can also receive A-IoT upper layer information (e.g., inventory / command) from the CN. For Option 1, this process can be performed after the UE receives the resource configuration from the BS; for Option 2, this process can be performed before the UE receives the resource configuration from the BS. In addition, as shown in Figure 13, the UE can also transmit A-IoT upper layer information (such as inventory / command reports / responses) to the core network (CN) via NAS signaling or UP.

[0268] It is worth noting that Figure 14 above is only an illustrative description of the embodiments of this application, but this application is not limited thereto. For example, the execution order between various operations can be appropriately adjusted, and other operations can be added or some operations can be removed. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description in Figure 14 above.

[0269] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0270] As can be seen from the above embodiments, the network device can configure resources for transmission or communication between the first device and the second device (A-IoT device), such as wireless resources for transmission or communication on the A-IoT wireless interface (A-IoT radio / air interface). Therefore, it is possible to support the allocation of wireless resources for communication between the UE and the A-IoT device on the A-IoT wireless interface under different A-IoT upper layer information transmission mechanisms in Topology 2, thereby ensuring the A-IoT process or function in Topology 2.

[0271] Third aspect of the embodiments

[0272] This application provides a method for resource allocation and use, described from the perspective of the core network. The core network includes existing functions (e.g., AMF) and A-IoT related functions. The description of the core network's behavior below could also refer to the behavior of the existing functional modules and / or the A-IoT related functional modules, etc. The embodiments of the third aspect can be implemented in combination with the embodiments of the first and second aspects, or they can be implemented independently. Content identical to the embodiments of the first and second aspects will not be repeated.

[0273] Figure 15 is a schematic diagram of a resource allocation and usage method according to an embodiment of this application. As shown in Figure 15, the method includes:

[0274] 1510: The core network sends first information related to A-IoT to network devices, the first information relating to A-IoT radio interface resources, and / or, the first information is used to indicate at least one of the following:

[0275] The first device is the UE reader;

[0276] The first device is an A-IoT enabled UE;

[0277] The first device supports A-IoT processes, functions, or capabilities;

[0278] The first device has A-IoT reader functionality or capability;

[0279] The first device has a common reader function;

[0280] The first device is capable of performing or supporting the A-IoT process.

[0281] According to the above embodiments, the core network sends first information to the network device to request or instruct the network device to allocate resources for the first device. Thus, the network device can configure resources for transmission or communication between the first device and the second device (A-IoT device), such as wireless resources for transmission or communication on the A-IoT radio / air interface. This enables the allocation of wireless resources for communication between the UE and A-IoT devices on the A-IoT radio interface under different A-IoT upper layer information transmission mechanisms in Topology 2, thereby ensuring the A-IoT processes or functions in Topology 2.

[0282] In some embodiments, the first information is used by the network device to send second information to the first device. This second information is used to configure resources for the first device for communication on the A-IoT wireless interface or for communication between the first and second devices. The details of this second information have already been described in the embodiments of the first aspect and will not be repeated here.

[0283] In some embodiments, the first information is carried by application protocol signaling at the interface between the core network and network devices. The specific carrying method has already been described in the embodiments of the first aspect and will not be repeated here.

[0284] In some embodiments, the first information is the estimated or expected size of the A-IoT wireless interface resources, expressed as at least one of the following:

[0285] The size of the resource corresponds to the buffer size.

[0286] The scale indication corresponding to the resource;

[0287] The number of messages or the size of messages corresponding to the resource;

[0288] The duration or length of time corresponding to the resource;

[0289] The number of A-IoT devices that need to communicate.

[0290] In some embodiments, the first information is transmitted together with the service request of the second device or after the service request of the second device.

[0291] The method of the embodiments of this application will be described below with reference to the examples in Figures 10 to 13.

[0292] As shown in Figure 10, according to the method of this application embodiment, the CN can transmit A-IoT upper layer information (e.g., inventory / command) to the BS. Furthermore, as shown in Figure 10, the CN can also receive A-IoT upper layer information (e.g., reports / responses corresponding to inventory / command) from the UE sent by the BS via xxAP signaling.

[0293] As shown in Figure 11, according to the method of this application embodiment, the CN can send A-IoT upper layer information (e.g., inventory / command) to the UE via NAS signaling or data. Furthermore, as shown in Figure 11, the CN can also receive A-IoT upper layer information (e.g., reports / responses corresponding to inventory / command) sent by the UE via NAS signaling or UP.

[0294] As shown in Figure 12, according to the method of this application embodiment, in option 1, the CN can send xxAP signaling (first information) to the BS, which includes, for example, a UE reader notification. Based on this, the BS sends resource configuration (second information) to the UE, providing the UE with radio resources for communication between the UE and A-IoT devices. In option 2, the CN can send xxAP signaling (first information) to the BS, which includes, for example, A-IoT upper layer information (e.g., inventory / command) and a UE reader notification. Based on this, the BS sends resource configuration (second information) to the UE via RRC signaling, providing the UE with radio resources for communication between the UE and A-IoT devices. Optionally, as shown in Figure 12, the RRC signaling may also include A-IoT upper layer information (e.g., inventory / command) obtained by the BS from the CN. As shown in Figure 12, the CN can also receive A-IoT upper layer information (e.g., reports / responses corresponding to inventory / command) sent by the BS from the UE.

[0295] As shown in Figure 13, according to the method of this application embodiment, in option 1, the CN can send xxAP signaling (first information) to the BS. This xxAP signaling may include, for example, a UE reader notification. Based on this, the BS sends resource configuration to the UE.

[0296] (Second Information) provides the UE with radio resources for communication between the UE and A-IoT devices; in Option 2, the CN can send xxAP signaling to the BS, which includes, for example, information related to services or A-IoT devices. Based on this, the BS sends resource configuration (second information) to the UE, providing the UE with radio resources for communication between the UE and A-IoT devices. Furthermore, as shown in Figure 13, the CN can also send A-IoT upper layer information (e.g., inventory / command) to the UE. For Option 1, this process can be performed after the UE receives the resource configuration from the BS; for Option 2, this process can be performed before the UE receives the resource configuration from the BS. Additionally, as shown in Figure 13, the CN can also receive A-IoT upper layer information (e.g., reports / responses corresponding to inventory / command) sent by the UE via NAS signaling or UP.

[0297] It is worth noting that Figure 15 above is only an illustrative description of the embodiments of this application, but this application is not limited thereto. For example, the execution order between various operations can be appropriately adjusted, and other operations can be added or some operations can be removed. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description in Figure 15 above.

[0298] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0299] As can be seen from the above embodiments, the core network sends first information to the network device to request or instruct the network device to allocate resources for the first device. Thus, the network device can configure resources for transmission or communication between the first device and the second device (A-IoT device), such as wireless resources for transmission or communication on the A-IoT radio / air interface. Therefore, it is possible to support the allocation of wireless resources for communication between the UE and A-IoT devices on the A-IoT radio interface under different A-IoT upper layer information transmission mechanisms in Topology 2, thereby ensuring the A-IoT process or function in Topology 2.

[0300] Fourth aspect of the embodiment

[0301] This application provides an apparatus for resource allocation and use. This apparatus may be, for example, a network device, or one or more components or parts configured within a network device; details identical to those in the embodiments of the first to third aspects will not be repeated.

[0302] Figure 16 is another schematic diagram of a resource allocation and usage apparatus according to an embodiment of this application. As shown in Figure 16, the resource allocation and usage apparatus 1600 includes a receiving unit 1610 and a transmitting unit 1620, wherein:

[0303] The receiving unit 1610 receives first information from the first device or from the core network;

[0304] The sending unit 1620 sends second information to the first device. The second information is used to configure resources for the first device. These resources are used for communication of the first device on the A-IoT wireless interface, or for communication between the first device and the second device.

[0305] In some embodiments, the first information is used to indicate at least one of the following:

[0306] The first device is a UE reader;

[0307] The first device is an A-IoT-enabled UE;

[0308] The first device supports A-IoT processes, functions, or capabilities;

[0309] The first device has A-IoT reading function or capability;

[0310] The first device has a public reader function;

[0311] The first device is capable of performing or supporting A-IoT processes.

[0312] In the above embodiments, in some possible implementations, the first information comes from the first device, and this first information is carried by a Radio Resource Control (RRC) message. This RRC message may include, for example, at least one of the following:

[0313] UE capability messages;

[0314] RRC establishment complete message;

[0315] RRC reconstruction complete message;

[0316] RRC reconfiguration complete message.

[0317] In the above embodiments, in some other possible implementations, the first information comes from the core network, and the first information is carried by the application protocol signaling of the interface between the core network and the network devices.

[0318] In other embodiments, the first information is used to indicate an A-IoT process or service, or the first information is related to A-IoT wireless interface resources.

[0319] In the above embodiments, the first information can be the estimated or expected size of the A-IoT wireless interface resources, and can be expressed as at least one of the following:

[0320] The cache size corresponds to the size of the resource;

[0321] The scale indication corresponding to the resource;

[0322] The number of messages or the size of messages corresponding to the resource;

[0323] The duration or length of time corresponding to the resource;

[0324] The number of second devices (A-IoT devices) that need to communicate.

[0325] In the above embodiments, in some possible implementations, the first information comes from the first device, and the first information is transmitted after the service request or response of the second device.

[0326] In the above implementation, the first information can be carried by at least one of the following signaling methods:

[0327] RRC signaling;

[0328] Media Access Control Element (MAC CE) signaling;

[0329] Uplink Control Information (UCI) signaling.

[0330] In the above embodiments, in some other possible implementations, the first information comes from the core network, and the first information is transmitted together with the service request of the second device or after the service request of the second device.

[0331] In the above implementation, the first information can be carried by the application protocol (AP) signaling of the interface between the core network and the network equipment.

[0332] In some other embodiments, the second information includes at least one of the following:

[0333] The index or identifier of a resource;

[0334] Time-domain resources;

[0335] Frequency domain resources;

[0336] Slice duration;

[0337] Starting point or offset;

[0338] cycle;

[0339] Duration.

[0340] In the above embodiments, the resources configured by the network device for the first device can be at least one of the following:

[0341] Resources configured for the first device;

[0342] Resources configured for A-IoT services or processes;

[0343] Resources configured for paging messages;

[0344] Resources configured for each access round of paging messages;

[0345] Resources configured for each R2D transport;

[0346] Resources configured for each D2R transport;

[0347] Configure the resources for each R2D and D2R transport pair;

[0348] Resources configured for each time slot;

[0349] Resources configured for each R2D trigger.

[0350] In some other embodiments, the second information is at least one of the following:

[0351] Information carried by RRC signaling or messages;

[0352] Information elements, fields, or information contained in RRC signaling or messages;

[0353] Information indicated or carried by MAC CE;

[0354] Information contained in MAC CE;

[0355] Information indicated or carried by downlink control information (DCI);

[0356] Information included in the DCI.

[0357] In some other embodiments, the aforementioned resource becomes active when the sending unit 1620 sends the second information. Thus, the first device can utilize this resource to communicate with the second device.

[0358] In some other embodiments, the aforementioned resource becomes invalid when at least one of the following events occurs:

[0359] The network device indicates that the resource should be released, deactivated, or disabled.

[0360] The first device is not located within the area related to this resource; and

[0361] The effective time corresponding to the resource has been reached or exceeded.

[0362] Therefore, the first device can perform at least one of the following operations:

[0363] Pause, stop, or suspend communication with the second device;

[0364] Discard any information or data received from the second device;

[0365] Discard information related to the second device;

[0366] Release the aforementioned resources;

[0367] Release the aforementioned resources and their associated configurations; and

[0368] Discard A-IoT upper-layer information from the core network.

[0369] In some embodiments, as shown in FIG16, the device 1600 further includes a processing unit 1630, which is used to generate relevant information and / or perform corresponding processing, for example, it can generate the aforementioned second information.

[0370] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0371] It is worth noting that the above description only covers the components or modules relevant to this application, but this application is not limited thereto. The resource allocation and use apparatus 1600 may also include other components or modules, and for details regarding these components or modules, please refer to related technologies.

[0372] Furthermore, for simplicity, Figure 16 only illustrates the connection relationships or signal flow between the various components or modules, but those skilled in the art should understand that various related technologies such as bus connections can be used. The aforementioned components or modules can be implemented using hardware facilities such as processors, memory, transmitters, and receivers; this application does not limit this implementation.

[0373] As can be seen from the above embodiments, the network device receives first information from a first device (e.g., UE) or the core network (CN) and sends second information to the first device to configure the resources for transmission or communication between the first device and the second device (A-IoT device), such as the wireless resources for transmission or communication on the A-IoT radio / air interface. Therefore, it is possible to support the allocation of wireless resources for communication between the UE and A-IoT device on the A-IoT radio interface under different A-IoT upper layer information transmission mechanisms in Topology 2, thereby ensuring the A-IoT process or function in Topology 2.

[0374] Fifth aspect of the embodiment

[0375] This application provides an apparatus for resource allocation and use. This apparatus may be, for example, a terminal device, or one or more components or parts configured on a terminal device. The terminal device is the first device described in the embodiments of the first to fourth aspects, and the same content as in the embodiments of the first to fourth aspects will not be repeated.

[0376] Figure 17 is a schematic diagram of a resource allocation and usage apparatus according to an embodiment of this application. As shown in Figure 17, the resource allocation and usage apparatus 1700 according to an embodiment of this application includes a receiving unit 1710, which receives second information sent by a network device. The second information is used to configure resources for a first device. The resources are used for communication of the first device on the A-IoT wireless interface, or for communication between the first device and the second device (A-IoT device).

[0377] In some embodiments, the second information includes at least one of the following:

[0378] The index or identifier of a resource;

[0379] Time-domain resources;

[0380] Frequency domain resources;

[0381] Slice duration;

[0382] Starting point or offset;

[0383] cycle;

[0384] Duration.

[0385] In the above embodiments, the resources (i.e., the resources configured for the first device) are at least one of the following:

[0386] Resources configured for the first device;

[0387] Resources configured for A-IoT services or processes;

[0388] Resources configured for paging messages;

[0389] Resources configured for each access round of paging messages;

[0390] Resources configured for each R2D transport;

[0391] Resources configured for each D2R transport;

[0392] Configure the resources for each R2D and D2R transport pair;

[0393] Resources configured for each time slot;

[0394] Resources configured for each R2D trigger.

[0395] In some embodiments, the second information is at least one of the following:

[0396] Information carried by RRC signaling or messages;

[0397] Information elements, fields, or information contained in RRC signaling or messages;

[0398] Information indicated or carried by MAC CE;

[0399] Information contained in MAC CE;

[0400] Information indicated or carried by downlink control information;

[0401] Information included in the DCI.

[0402] In some embodiments, as shown in FIG17, the device 1700 further includes:

[0403] The sending unit 1720 sends first information to the network device, the first information being used to request the aforementioned resources.

[0404] In some embodiments, the first information is used to indicate at least one of the following:

[0405] The first device is a UE reader;

[0406] The first device is an A-IoT-enabled UE;

[0407] The first device supports A-IoT processes, functions, or capabilities;

[0408] The first device has A-IoT reading functionality or capability;

[0409] The first device has a public reader function;

[0410] The first device is capable of performing or supporting the A-IoT process.

[0411] In the above embodiments, the first information may be carried by an RRC message / signaling. This RRC message / signaling may include, for example, at least one of the following:

[0412] UE capability messages;

[0413] RRC establishment complete message;

[0414] RRC reconstruction complete message;

[0415] RRC reconfiguration complete message.

[0416] In other embodiments, the first information is used to indicate an A-IoT process or service, or the first information is related to A-IoT wireless interface resources.

[0417] In the above embodiments, the first information is the estimated or expected size of the A-IoT wireless interface resources, which can be expressed as at least one of the following:

[0418] The cache size corresponds to the size of the resource;

[0419] The scale indication corresponding to the resource;

[0420] The number of messages or the size of messages corresponding to the resource;

[0421] The duration or length of time corresponding to the resource;

[0422] The number of A-IoT devices that need to communicate.

[0423] In the above embodiments, the first information can be transmitted after the service request or response from the second device.

[0424] In the above embodiments, the first information may be carried by at least one of the following signaling methods:

[0425] RRC signaling;

[0426] MAC CE signaling;

[0427] UCI signaling.

[0428] In some embodiments, as shown in FIG17, the device 1700 further includes a processing unit 1730.

[0429] In some embodiments, when the receiving unit 1710 receives the second information, the aforementioned resource becomes effective, and the processing unit 1730 uses the resource to communicate with the second device.

[0430] In some embodiments, the above-mentioned resources become invalid when at least one of the following events occurs:

[0431] The network device indicates that the resource should be released, deactivated, or disabled.

[0432] The first device is not located within the area related to this resource; and

[0433] The effective time corresponding to the resource has been reached or exceeded.

[0434] In the above embodiments, the processing unit 1730 may perform at least one of the following operations:

[0435] Pause, stop, or suspend communication with the second device;

[0436] Discard any information or data received from the second device;

[0437] Discard information related to the second device;

[0438] Release the aforementioned resources;

[0439] Release the aforementioned resources and their associated configurations; and

[0440] Discard A-IoT upper-layer information from the core network.

[0441] In the above embodiments, the processing unit 1730 may also perform other processing, such as generating the first information mentioned above, etc.

[0442] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0443] It is worth noting that the above description only covers the components or modules relevant to this application, but this application is not limited thereto. The resource allocation and use apparatus 1700 may also include other components or modules, and for details regarding these components or modules, please refer to related technologies.

[0444] Furthermore, for simplicity, Figure 17 only illustrates the connection relationships or signal flow between the various components or modules, but those skilled in the art should understand that various related technologies such as bus connections can be used. The aforementioned components or modules can be implemented using hardware facilities such as processors, memory, transmitters, and receivers; this application does not limit this implementation.

[0445] As can be seen from the above embodiments, the network device can configure resources for transmission or communication between the first device and the second device (A-IoT device), such as wireless resources for transmission or communication on the A-IoT wireless interface (A-IoT radio / air interface). Therefore, it is possible to support the allocation of wireless resources for communication between the UE and the A-IoT device on the A-IoT wireless interface under different A-IoT upper layer information transmission mechanisms in Topology 2, thereby ensuring the A-IoT process or function in Topology 2.

[0446] Implementation of the sixth aspect

[0447] This application provides a resource allocation and usage apparatus. The apparatus may be, for example, a core network, or one or more components or parts configured in the core network, such as the AMF module and / or A-IoT related functional modules configured in the core network. The contents that are the same as those in the embodiments of the first to fifth aspects will not be repeated.

[0448] Figure 18 is a schematic diagram of a resource allocation and usage apparatus according to an embodiment of this application. As shown in Figure 18, the resource allocation and usage apparatus 1800 according to an embodiment of this application includes a transmitting unit 1810, which transmits first information related to A-IoT to a network device. The first information is related to A-IoT wireless interface resources, and / or the first information is used to indicate at least one of the following:

[0449] The first device is the UE reader;

[0450] The first device is an A-IoT enabled UE;

[0451] The first device supports A-IoT processes, functions, or capabilities;

[0452] The first device has A-IoT reader functionality or capability;

[0453] The first device has a common reader function;

[0454] The first device is capable of performing or supporting the A-IoT process.

[0455] In some embodiments, the first information is used by the network device to send second information to the first device. This second information is used to configure resources for the first device for communication on the A-IoT wireless interface or for communication between the first and second devices. The details of this second information have already been described in the embodiments of the first aspect and will not be repeated here.

[0456] In some embodiments, the first information is carried by application protocol signaling at the interface between the core network and network devices. The specific carrying method has already been described in the embodiments of the first aspect and will not be repeated here.

[0457] In some embodiments, the first information is the estimated or expected size of the A-IoT wireless interface resources, expressed as at least one of the following:

[0458] The cache size corresponds to the size of the resource;

[0459] The scale indication corresponding to the resource;

[0460] The number of messages or the size of messages corresponding to the resource;

[0461] The duration or length of time corresponding to the resource;

[0462] The number of A-IoT devices that need to communicate.

[0463] In some embodiments, the first information is transmitted together with the service request of the second device or after the service request of the second device.

[0464] In some embodiments, as shown in FIG18, the device 1800 further includes a receiving unit 1820, which receives information from a network device, as detailed in related technologies.

[0465] In some embodiments, as shown in FIG18, the device 1800 further includes a processing unit 1830, which performs corresponding processing or generates corresponding information, such as generating the aforementioned first information, etc. For details, please refer to related technologies.

[0466] It is worth noting that Figure 18 above is only an illustrative description of the embodiments of this application, but this application is not limited thereto. For example, the execution order between various operations can be appropriately adjusted, and other operations can be added or some operations can be removed. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description in Figure 18 above.

[0467] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0468] It is worth noting that the above description only covers the components or modules relevant to this application, but this application is not limited thereto. The resource allocation and use apparatus 1800 may also include other components or modules, and for details regarding these components or modules, please refer to related technologies.

[0469] Furthermore, for simplicity, Figure 18 only illustrates the connection relationships or signal flow between the various components or modules, but those skilled in the art should understand that various related technologies such as bus connections can be used. The aforementioned components or modules can be implemented using hardware facilities such as processors, memory, transmitters, and receivers; this application does not limit this implementation.

[0470] As can be seen from the above embodiments, the core network sends first information to the network device to request or instruct the network device to allocate resources for the first device. Thus, the network device can configure resources for transmission or communication between the first device and the second device (A-IoT device), such as wireless resources for transmission or communication on the A-IoT radio / air interface. Therefore, it is possible to support the allocation of wireless resources for communication between the UE and A-IoT devices on the A-IoT radio interface under different A-IoT upper layer information transmission mechanisms in Topology 2, thereby ensuring the A-IoT process or function in Topology 2.

[0471] Seventh aspect of the embodiment

[0472] This application also provides a communication system, which can be referred to in Figures 1 to 3. The contents that are the same as those in the embodiments of the first to sixth aspects will not be repeated.

[0473] In some embodiments, the communication system includes: a network device, a first device (e.g., a UE reader), a second device (e.g., an A-IoT device), and a core network (CN).

[0474] Network devices can be configured, for example, as follows:

[0475] Receive first information from the first device or from the core network;

[0476] Send second information to the first device. The second information is used to configure resources for the first device. These resources are used for communication of the first device on the A-IoT wireless interface, or for communication between the first device and the second device.

[0477] The first device can be configured, for example, as follows:

[0478] The device receives second information sent by a network device. The second information is used to configure resources for the first device. These resources are used for communication of the first device on the A-IoT wireless interface, or for communication between the first device and the second device (A-IoT device).

[0479] The core network can be configured, for example, as follows:

[0480] Send initial information related to A-IoT to network devices;

[0481] The first information relates to A-IoT wireless interface resources, and / or the first information is used to indicate at least one of the following:

[0482] The first device is a UE reader;

[0483] The first device is an A-IoT-enabled UE;

[0484] The first device supports A-IoT processes, functions, or capabilities;

[0485] The first device has A-IoT reading functionality or capability;

[0486] The first device has a public reader function;

[0487] The first device is capable of performing or supporting the A-IoT process;

[0488] A-IoT processes or services.

[0489] The relevant content regarding network equipment, the first device, and the core network has been described in the embodiments of the first to sixth aspects, and its content has been incorporated here and will not be repeated here.

[0490] This application also provides a network device, such as a base station, but this application is not limited to this and may also include other network devices.

[0491] Figure 19 is a schematic diagram of the network device according to an embodiment of this application. As shown in Figure 19, the network device 1900 may include: a processor 1910 (e.g., a central processing unit CPU) and a memory 1920; the memory 1920 is coupled to the processor 1910. The memory 1920 can store various data; in addition, it also stores an information processing program 1930, and executes the program 1930 under the control of the processor 3010.

[0492] For example, processor 1910 can be configured to execute a program to implement the method described in the embodiment of the first aspect. For example, processor 1910 can be configured to perform the following control:

[0493] Receive first information from the first device or from the core network;

[0494] Send second information to the first device. The second information is used to configure resources for the first device. These resources are used for communication of the first device on the A-IoT wireless interface, or for communication between the first device and the second device.

[0495] In addition, as shown in Figure 19, network device 1900 may also include: transceiver 1940 and antenna 1950, etc.; the functions of the above components are similar to those in the prior art, and will not be described in detail here. It is worth noting that network device 1900 does not necessarily have to include all the components shown in Figure 19; in addition, network device 1900 may also include components not shown in Figure 19, which can be referred to in the prior art.

[0496] This application also provides a terminal device, but the application is not limited thereto and may also include other devices.

[0497] Figure 20 is a schematic diagram of a terminal device according to an embodiment of this application. As shown in Figure 20, the terminal device 2000 may include a processor 2010 and a memory 2020; for example, the memory 2020 stores data and programs and is coupled to the processor 2010. It is worth noting that this figure is exemplary; other types of structures may also be used to supplement or replace this structure to implement telecommunications functions or other functions.

[0498] For example, processor 2010 may be configured to execute a program to implement the method described in the embodiments of the second aspect. For example, processor 2010 may be configured to perform the following control:

[0499] The device receives second information sent by a network device. The second information is used to configure resources for the first device (terminal device). These resources are used for communication of the first device (terminal device) on the A-IoT wireless interface, or for communication between the first device (terminal device) and the second device (A-IoT device).

[0500] As shown in Figure 20, the terminal device 2000 may further include a communication module 2030; it may or may not have a power supply. It is worth noting that the terminal device 2000 is not necessarily required to include all the components shown in Figure 20; these components are not essential. Furthermore, the terminal device 2000 may also include components not shown in Figure 20, which can be referred to in the prior art.

[0501] This application also provides a core network device, such as an AMF module or an A-IoT related functional module, but this application is not limited to this and may also be other core network devices.

[0502] Figure 21 is a schematic diagram of the core network device according to an embodiment of this application. As shown in Figure 21, the core network device 2100 may include: a processor 2110 (e.g., a central processing unit CPU) and a memory 2120; the memory 2120 is coupled to the processor 2110. The memory 2120 can store various data; in addition, it also stores an information processing program 2130, and executes the program 2130 under the control of the processor 2110.

[0503] For example, processor 2110 may be configured to execute a program to implement the method described in the embodiments of the third aspect. For example, processor 2110 may be configured to perform the following control:

[0504] Send initial information related to A-IoT to network devices;

[0505] The first information relates to A-IoT wireless interface resources, and / or the first information is used to indicate at least one of the following:

[0506] The first device is a UE reader;

[0507] The first device is an A-IoT-enabled UE;

[0508] The first device supports A-IoT processes, functions, or capabilities;

[0509] The first device has A-IoT reading functionality or capability;

[0510] The first device has a public reader function;

[0511] The first device is capable of performing or supporting the A-IoT process;

[0512] A-IoT processes or services.

[0513] In addition, as shown in Figure 21, the core network device 2100 may also include a transceiver 2140 and an antenna 2150, etc.; the functions of the above components are similar to those in the prior art, and will not be described in detail here. It is worth noting that the core network device 2100 does not necessarily have to include all the components shown in Figure 21; in addition, the core network device 2100 may also include components not shown in Figure 21, which can be referred to in the prior art.

[0514] This application also provides a computer program, wherein when the program is executed in a network device, the program causes the network device to perform the method described in the first aspect of the embodiment.

[0515] This application also provides a storage medium storing a computer program, wherein the computer program causes a network device to perform the method described in the first aspect of the embodiment.

[0516] This application also provides a computer program, wherein when the program is executed in a terminal device, the program causes the terminal device to perform the method described in the second aspect of the embodiment.

[0517] This application also provides a storage medium storing a computer program, wherein the computer program causes a terminal device to perform the method described in the second aspect of the embodiment.

[0518] This application also provides a computer program, wherein when the program is executed in a core network device, the program causes the core network device to perform the method described in the third aspect of the embodiment.

[0519] This application also provides a storage medium storing a computer program, wherein the computer program causes a core network device to perform the method described in the third aspect of the embodiments.

[0520] The apparatus and methods described above in this application can be implemented in hardware or in combination with software. This application relates to a computer-readable program that, when executed by a logic component, enables the logic component to implement the apparatus or components described above, or to implement the various methods or steps described above. This application also relates to storage media for storing the above programs, such as hard disks, magnetic disks, optical disks, DVDs, flash memory, etc.

[0521] The methods / apparatus described in conjunction with the embodiments of this application can be directly embodied in hardware, software modules executed by a processor, or a combination of both. For example, one or more and / or combinations of one or more functional block diagrams shown in the figures can correspond to various software modules in a computer program flow, or to various hardware modules. These software modules can correspond to the various steps shown in the figures, respectively. These hardware modules can be implemented, for example, using a field-programmable gate array (FPGA) to embed these software modules.

[0522] The software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. A storage medium can be coupled to the processor, enabling the processor to read information from and write information to the storage medium; or the storage medium can be an integral part of the processor. The processor and storage medium can reside in an ASIC. The software module can be stored in the memory of a mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a high-capacity MEGA-SIM card or a high-capacity flash memory device, the software module can be stored in the MEGA-SIM card or the high-capacity flash memory device.

[0523] One or more and / or one or more combinations of functional blocks described in the accompanying drawings can be implemented as a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or any suitable combination thereof for performing the functions described herein. One or more and / or one or more combinations of functional blocks described in the accompanying drawings can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

[0524] The present application has been described above with reference to specific embodiments. However, those skilled in the art should understand that these descriptions are exemplary and not intended to limit the scope of protection of the present application. Those skilled in the art can make various modifications and variations to the present application based on its spirit and principles, and these modifications and variations are also within the scope of the present application.

[0525] Regarding the implementation methods including the above embodiments, the following notes are also disclosed:

[0526] 1. A method for resource allocation and use, the method comprising:

[0527] The network device receives first information from the first device or from the core network;

[0528] The network device sends second information to the first device. The second information is used to configure resources for the first device. The resources are used for communication of the first device on the A-IoT wireless interface, or for communication between the first device and the second device.

[0529] 2. A method for resource allocation and use, the method comprising:

[0530] The first device receives second information sent by the network device. The second information is used to configure resources for the first device. The resources are used for communication of the first device on the A-IoT wireless interface, or for communication between the first device and the second device (A-IoT device).

[0531] 3. A method for resource allocation and use, the method comprising:

[0532] The core network sends initial information related to A-IoT to network devices;

[0533] The first information relates to A-IoT wireless interface resources, and / or the first information is used to indicate at least one of the following:

[0534] The first device is a UE reader;

[0535] The first device is an A-IoT-enabled UE;

[0536] The first device supports A-IoT processes, functions, or capabilities;

[0537] The first device has A-IoT reading functionality or capability;

[0538] The first device has a public reader function;

[0539] The first device is capable of performing or supporting the A-IoT process;

[0540] A-IoT processes or services.

[0541] 4. A network device comprising a memory and a processor, the memory storing a computer program and the processor being configured to execute the computer program to implement the method as described in Appendix 1.

[0542] 5. A terminal device comprising a memory and a processor, the memory storing a computer program and the processor being configured to execute the computer program to implement the method as described in Appendix 2.

[0543] 6. A core network device, comprising a memory and a processor, the memory storing a computer program and the processor being configured to execute the computer program to implement the method as described in Appendix 3.

[0544] 7. A computer program product comprising at least a computer program that, when executed by a processor, causes a network device to perform the method as described in Appendix 1.

[0545] 8. A computer program product comprising at least a computer program that, when executed by a processor, causes a terminal device to perform the method as described in Appendix 2.

[0546] 9. A computer program product comprising at least a computer program that, when executed by a processor, causes a core network device to perform the method described in Appendix 3.

[0547] 10. A communication system, the communication system comprising network equipment, terminal equipment, core network equipment, and A-IoT devices, wherein,

[0548] The network device is configured to perform the method described in Appendix 1; and / or,

[0549] The terminal device is configured to perform the method described in Appendix 2; and / or,

[0550] The core network equipment is configured to perform the method described in Appendix 3.

Claims

1. A resource allocation and utilization apparatus, configured in a network device, the apparatus comprising: A receiving unit that receives first information from a first device or from a core network; The transmitting unit sends second information to the first device, the second information being used to configure resources for the first device, the resources being used for communication of the first device on the Ambient Internet of Things (A-IoT) wireless interface, or for communication between the first device and the second device.

2. The apparatus according to claim 1, wherein, The first information is used to indicate at least one of the following: The first device is a user equipment (UE) reader; The first device is an A-IoT-enabled UE; The first device supports A-IoT processes, functions, or capabilities; The first device has A-IoT reading function or capability; The first device has a public reader function; The first device is capable of performing or supporting A-IoT processes.

3. The apparatus according to claim 2, wherein, The first information comes from the first device and is carried by a Radio Resource Control (RRC) message.

4. The apparatus according to claim 3, wherein, The RRC message includes at least one of the following: UE capability messages; RRC establishment complete message; RRC reconstruction complete message; RRC reconfiguration complete message.

5. The apparatus according to claim 2, wherein, The first information comes from the core network and is carried by the application protocol signaling of the interface between the core network and the network device.

6. The apparatus according to claim 1, wherein, The first information is used to indicate an A-IoT process or service, or the first information is related to A-IoT wireless interface resources.

7. The apparatus according to claim 6, wherein, The first information is the estimated or expected size of the A-IoT wireless interface resources, expressed as at least one of the following: The cache size corresponds to the size of the resource; The scale indication corresponding to the resource; The number of messages or the size of messages corresponding to the resource; The duration or length of time corresponding to the resource; The number of second devices that need to communicate.

8. The apparatus according to claim 6, wherein, The first information comes from the first device, and the first information is transmitted after a service request or response from the second device.

9. The apparatus according to claim 8, wherein, The first information is carried by at least one of the following signaling: RRC signaling; Media Access Control Element (MAC CE) signaling; Uplink Control Information (UCI) signaling.

10. The apparatus according to claim 6, wherein, The first information comes from the core network, and the first information is transmitted together with the service request of the second device or after the service request of the second device.

11. The apparatus according to claim 10, wherein, The first information is carried by the application protocol (AP) signaling of the interface between the core network and the network device.

12. The apparatus according to claim 1, wherein, The second information includes at least one of the following: The index or identifier of a resource; Time-domain resources; Frequency domain resources; Slice duration; Starting point or offset; cycle; Duration.

13. The apparatus according to claim 1, wherein, The resource is at least one of the following: Resources configured for the first device; Resources configured for A-IoT services or processes; Resources configured for paging messages; Resources configured for each access round of paging messages; Resources configured for each Reader-to-Device (R2D) transfer; Resources configured for each device-to-reader (D2R) transfer; Configure the resources for each R2D and D2R transport pair; Resources configured for each time slot; Resources configured for each R2D trigger.

14. The apparatus according to claim 1, wherein, When the sending unit sends the second information, the resource becomes active, and the first device uses the resource to communicate with the second device; and / or The first device performs at least one of the following operations when the resource fails: The operation includes: Pause, stop, or suspend communication with the second device; Discard the received information or data from the second device; Discard the relevant information of the second device; Release the resources; Release the resource and the configuration associated with the resource; and Discard the A-IoT upper-layer information from the core network; The events include: The network device indicates that the resource should be released, deactivated, or disabled. The first device is not located within the area related to the resource; and The effective time corresponding to the resource has been reached or exceeded.

15. The apparatus according to claim 1, wherein, The second information is at least one of the following: Information carried by RRC signaling or messages; Information elements, fields, or information contained in RRC signaling or messages; Information indicated or carried by MAC CE; Information contained in MAC CE; Information indicated or carried by downlink control information (DCI); Information included in the DCI.

16. A resource allocation and use apparatus, configured in a first device, the apparatus comprising: The receiving unit receives second information sent by the network device. The second information is used to configure resources for the first device. The resources are used for communication of the first device on the A-IoT wireless interface, or for communication between the first device and the second device.

17. The apparatus according to claim 16, wherein, The device further includes: The sending unit sends first information to the network device, the first information being used to request the resource.

18. The apparatus according to claim 17, wherein, The first information relates to A-IoT wireless interface resources, and / or the first information is used to indicate at least one of the following: The first device is a UE reader; The first device is an A-IoT-enabled UE; The first device supports A-IoT processes, functions, or capabilities; The first device has A-IoT reading function or capability; The first device has a public reader function; The first device is capable of performing or supporting A-IoT processes; A-IoT processes or services.

19. A resource allocation and utilization apparatus, configured in a core network, the apparatus comprising: The transmitting unit sends first information related to A-IoT to the network device; The first information relates to A-IoT wireless interface resources, and / or the first information is used to indicate at least one of the following: The first device is a UE reader; The first device is an A-IoT-enabled UE; The first device supports A-IoT processes, functions, or capabilities; The first device has A-IoT reading functionality or capability; The first device has a public reader function; The first device is capable of performing or supporting the A-IoT process; A-IoT processes or services.

20. The apparatus according to claim 19, wherein, The first information is used by the network device to send second information to the first device, and the second information is used to configure resources for the first device for communication on the A-IoT wireless interface or for communication between the first device and the second device.

Images