Communication method, communication device, and computer-readable storage medium

Abstract

The application provides a communication method, a communication device and a computer readable storage medium, so that a terminal device can be authorized as a reader, thereby facilitating the establishment efficiency of an environmental Internet of Things service. The terminal device can be authorized as a reader, for example, in a network registration scenario. The method can include: a first core network element receiving a first message from a first terminal device, the message including an identifier of the first terminal device and being used to request authorization of the first terminal device as a reader; the first core network element obtaining subscription information of the first terminal device from a second core network element, and determining whether to authorize the first terminal device as a reader based on at least the subscription information of the first terminal device; and the first core network element sending a second message to the first terminal device via a base station, the second message including the identifier of the first terminal device and authorization result indication information, the authorization result indication information being used to indicate that the first terminal device is authorized as a reader.

Description

Technical Field

[0001] This application relates to the field of communication technology, specifically to a communication method, a communication device, and a computer-readable storage medium. Background Technology

[0002] With the development of IoT technology, the Ambient Internet of Things (AIoT or AIoT) has emerged. AIoT includes AIoT devices, which primarily utilize environmental energy harvested from the environment for power. Environmental energy can include radio waves, light, motion, and heat. AIoT also includes readers, which can be base stations or user equipment (UE). Communication between AIoT devices and readers is possible, such as data transmission and signaling transmission.

[0003] When a UE is authorized to act as a UE reader, it can request the base station to allocate AIoT radio resources (or air interface resources), and can also establish Protocol Data Unit (PDU) sessions and AIoT UE reader control connections with core network elements. The AIoT radio resources are used for signaling and / or data interaction between the UE and AIoT devices, while the PDU session is used for AIoT services. How a UE is authorized to act as a UE reader is currently a hot research topic. Summary of the Invention

[0004] This application provides a communication method, a communication device, and a computer-readable storage medium, enabling terminal devices to be authorized as readers / writers, thereby improving the efficiency of establishing environmental Internet of Things (IoT) services.

[0005] In a first aspect, embodiments of this application provide a communication method applied to a first core network element. That is, the method can be executed by the first core network element or by a device matched with the first core network element, such as a processor or chip. The method may include: receiving a first message from a first terminal device; wherein the first message includes an identifier of the first terminal device, and the first message is used to request authorization for the first terminal device to act as a reader / writer; obtaining subscription information of the first terminal device from a second core network element, and determining, at least based on the subscription information of the first terminal device, whether to authorize the first terminal device to act as a reader / writer; wherein the second core network element is a unified data management network element and / or a unified data storage network element; and sending a second message to the first terminal device via a base station, the second message including an identifier of the first terminal device and authorization result indication information, the authorization result indication information being used to indicate that the first terminal device has been authorized to act as a reader / writer.

[0006] As can be seen, the first terminal device sends a first message to the first core network element to request authorization from the first core network element to act as a reader / writer. If the first core network element determines whether to authorize the first terminal device as a reader / writer, it sends an authorization result indication message to the first terminal device via a base station, indicating that the first terminal device has been authorized as a reader / writer. This allows the first terminal device to be authorized as a reader / writer, thereby improving the efficiency of establishing environmental IoT services.

[0007] Specifically, the first core network element receives a first message from the first terminal device, which can be achieved by the first core network element receiving the first message from the first terminal device via a base station. The first core network element then sends a second message to the first terminal device via the base station; that is, the first core network element sends a second message to the first terminal device via the base station.

[0008] Optionally, the first core network element can be an access and mobility management (AML) network element or an environmental IoT function network element. If the first core network element is an AML network element, it receives the first message from the first terminal device through a base station. If the first core network element is an environmental IoT function network element, it receives the first message from the first terminal device through both the AML network element and the base station. That is, the first terminal device sends the first message to the AML network element through the base station, and the AML network element sends the first message to the environmental IoT function network element.

[0009] In one possible implementation, the aforementioned authorization result indication information is further used to indicate one or more of the following: authorization time information, authorization location information, and the binding relationship between the first terminal device and the application function network element. Regarding the authorization result indication information further indicating authorization time and authorization location information, the first terminal device can know when and where it can act as a reader / writer. Regarding the authorization result indication information further indicating the binding relationship, the first terminal device can know in which application function network element triggers the environmental IoT service and in which it can act as a reader / writer.

[0010] In one possible implementation, the method further includes sending a subscription information update request message to a second core network element. This request message includes authorization result indication information, requesting the second core network element to update the subscription information of the first terminal device based on the authorization result indication information. Thus, the second core network element can record that the first terminal device has been authorized as a reader / writer. Optionally, it can also record one or more of the following: authorization time information, authorization location information, and the binding relationship between the first terminal device and the application function network element.

[0011] In one possible implementation, the method further includes sending a first identifier list to the base station, the first identifier list including identifiers of terminal devices authorized to act as readers. This allows the base station to determine which terminal devices are authorized to act as readers.

[0012] In one possible implementation, when determining whether to authorize the first terminal device as a reader / writer, the first core network element may base its decision on the first terminal device's subscription information and its environmental IoT capability information. The environmental IoT capability information includes one or more of the following:

[0013] The environmental IoT service type, the effective time information of the first terminal device as a reader, the effective area information of the first terminal device as a reader, the binding relationship between the first terminal device and the application function network element, and the reader information of the first terminal device as a reader.

[0014] In one possible implementation, the first message also includes environmental IoT capability information of the first terminal device, so that the first core network element can determine whether to authorize the first terminal device as a reader / writer based on the first terminal device's subscription information and environmental IoT capability information.

[0015] In one possible implementation, the first message also includes the location information of the first terminal device, so that the first core network element can determine whether to authorize the first terminal device as a reader / writer based on the subscription information and the location information of the first terminal device.

[0016] In one possible implementation, when the first core network element is an access and mobility management network element, the first message is a registration request message from the first terminal device. That is, during the process of registering with the network, the first terminal device requests authorization from the first core network element to act as a reader / writer, thereby improving the efficiency of establishing environmental IoT services.

[0017] Optionally, when the first core network element is an environmental IoT function network element, the access and mobility management network element, upon receiving the registration request message, sends an authorization request message to the environmental IoT function network element to request the environmental IoT function network element to authorize the first terminal device as a reader / writer. Upon receiving the authorization request message, the environmental IoT function network element determines whether to authorize the first terminal device as a reader / writer, at least based on the first terminal device's subscription information. The environmental IoT function network element sends the authorization result indication information to the first terminal device, or sends it to the first terminal device through the access and mobility management network element.

[0018] In one possible implementation, the first message is an environmental IoT reader / writer authorization request message from a first terminal device located in a preset environmental IoT service area. That is, when the first terminal device is located in the preset environmental IoT service area, it requests authorization from a first core network element to act as a reader / writer. This improves the efficiency of establishing environmental IoT services.

[0019] In one possible implementation, the first message is a PDU session request message from a first terminal device located in a preset environmental IoT service area. That is, when the first terminal device is located in the preset environmental IoT service area, it requests authorization to act as a reader / writer during the PDU session establishment process. This helps improve the efficiency of establishing environmental IoT services.

[0020] Secondly, embodiments of this application provide a communication method applied to a first terminal device. That is, the method can be executed by the first terminal device or by a device compatible with the first terminal device, such as a processor or chip. The method may include: sending a first message via a base station to a first core network element, the message including an identifier of the first terminal device for requesting authorization for the first terminal device to act as a reader / writer; and receiving a second message via the base station from the first core network element, the second message including an identifier of the first terminal device and authorization result indication information, the authorization result indication information indicating that the first terminal device has been authorized as a reader / writer.

[0021] As can be seen, the first terminal device learns that it has been authorized as a reader / writer by sending a first message to the first core network element and receiving authorization result indication information from the first core network element. This helps to improve the efficiency of establishing environmental IoT services.

[0022] Specifically, the first terminal device sends a first message to the first core network element via a base station, meaning the first terminal device sends a first message to the first core network element through the base station. The first terminal device also receives a second message from the first core network element via the base station, meaning the first terminal device receives a second message from the first core network element through the base station.

[0023] Optionally, the first core network element can be an access and mobility management (AMI) network element or an environmental IoT function network element. If the first core network element is an AMI network element, the first terminal device sends a first message to the AMI network element via a base station. If the first core network element is an environmental IoT function network element, the first terminal device sends a first message to the environmental IoT function network element via both the base station and the AMI network element. That is, the first terminal device sends a first message to the AMI network element via the base station, and the AMI network element sends a first message to the environmental IoT function network element.

[0024] In one possible implementation, the aforementioned authorization result indication information is further used to indicate one or more of the following: authorization time information, authorization location information, and the binding relationship between the first terminal device and the application function network element. Regarding the authorization result indication information further indicating authorization time and authorization location information, the first terminal device can know when and where it can act as a reader / writer. Regarding the authorization result indication information further indicating the binding relationship, the first terminal device can know in which application function network element triggers the environmental IoT service and in which it can act as a reader / writer.

[0025] In one possible implementation, the first message also includes environmental IoT capability information of the first terminal device, so that the first core network element can determine whether to authorize the first terminal device as a reader / writer based on the first terminal device's subscription information and environmental IoT capability information.

[0026] The environmental IoT capability information includes one or more of the following:

[0027] The environmental IoT service type, the effective time information of the first terminal device as a reader, the effective area information of the first terminal device as a reader, the binding relationship between the first terminal device and the application function network element, and the reader information of the first terminal device as a reader.

[0028] In one possible implementation, the first message also includes the location information of the first terminal device, so that the first core network element can determine whether to authorize the first terminal device as a reader / writer based on the subscription information and the location information of the first terminal device.

[0029] In one possible implementation, the first message is a registration request message. That is, during the process of requesting registration with the network, the first terminal device requests the first core network element to authorize the first terminal device as a reader / writer, thereby improving the efficiency of establishing environmental IoT services.

[0030] In one possible implementation, sending a first message to a first core network element via a base station includes: responding to the first terminal device being located in a preset IoT service area, sending a first message to the first core network element via the base station. That is, when the first terminal device is located in a preset IoT service area, the first terminal device sends a first message to the first core network element via the base station to request the first core network element to authorize the first terminal device as a reader / writer.

[0031] In one possible implementation, the first message is an environmental IoT reader / writer authorization request message. That is, when the first terminal device is located in a preset environmental IoT service area, the first terminal device sends an environmental IoT reader / writer authorization request message to the first core network element, requesting the first core network element to authorize the first terminal device as a reader / writer. This helps improve the efficiency of establishing environmental IoT services.

[0032] In one possible implementation, the first message is a PDU session request message. That is, when the first terminal device is located in a preset environmental IoT service area, the first terminal device sends a PDU session request message to the first core network element to request authorization as a reader / writer during the PDU session establishment process. This helps improve the efficiency of establishing environmental IoT services.

[0033] In one possible implementation, in response to the first terminal device being located in a preset environmental IoT service area, it sends an environmental IoT radio resource request message to the base station. This message requests the base station to authorize the first terminal device as a reader / writer. The device then receives an environmental IoT radio resource response message from the base station, indicating that the first terminal device has been authorized as a reader / writer. In other words, when the first terminal device is located in the preset environmental IoT service area, it requests authorization from the base station to act as a reader / writer via the environmental IoT radio resource request message. Therefore, requesting authorization for the first terminal device as a reader / writer during the environmental IoT radio resource request process improves the efficiency of establishing environmental IoT services.

[0034] In one possible implementation, the environmental IoT radio resource response message is also used to indicate the environmental IoT radio resources allocated to the first terminal device. That is, when the base station authorizes the first terminal device as a reader / writer, the allocated environmental IoT radio resources are also communicated to the first terminal device so that the first terminal device can use these radio resources to perform data and / or signaling interactions with the environmental IoT device.

[0035] Thirdly, embodiments of this application provide a communication method applied to a first core network element. That is, the method can be executed by the first core network element or by a device matching the first core network element, such as a processor or chip. The method may include: receiving a third message from an application function network element; wherein the third message includes an identifier of a first terminal device, and the third message is used to request authorization for the first terminal device to act as a reader / writer; obtaining subscription information of the first terminal device from a second core network element, and determining whether to authorize the first terminal device to act as a reader / writer based at least on the subscription information of the first terminal device; wherein the second core network element is a unified data management network element and / or a unified data storage network element; and sending a fourth message to the first terminal device via a base station, the fourth message including an identifier of the first terminal device and authorization result indication information, the authorization result indication information being used to indicate that the first terminal device has been authorized to act as a reader / writer.

[0036] As can be seen, the application function network element sends a third message to the first core network element to request the first core network element to authorize the first terminal device as a reader / writer. If the first core network element determines whether to authorize the first terminal device as a reader / writer, it sends an authorization result indication message to the first terminal device via the base station, indicating that the first terminal device has been authorized as a reader / writer. This allows the first terminal device to be authorized as a reader / writer, thereby improving the efficiency of establishing environmental IoT services.

[0037] Optionally, the first core network element can be an access and mobility management network element, or an environmental IoT function network element.

[0038] Optionally, the subscription information of the first terminal device may include the reader / writer subscription information of the first terminal device, used to indicate whether the first terminal device is allowed to act as a reader / writer. Optionally, the subscription information of the first terminal device may also include the network registration status of the first terminal device, used to indicate whether the first terminal device has registered with the network or not. For a terminal device that has registered with the network and is allowed to act as a reader / writer, the first core network element may authorize the terminal device as a reader / writer. For a terminal device that has not registered with the network but is allowed to act as a reader / writer, the first core network element will not authorize the terminal device as a reader / writer.

[0039] In one possible implementation, the aforementioned authorization result indication information is further used to indicate one or more of the following: authorization time information, authorization location information, and the binding relationship between the first terminal device and the application function network element. Regarding the authorization result indication information further indicating authorization time and authorization location information, the first terminal device can know when and where it can act as a reader / writer. Regarding the authorization result indication information further indicating the binding relationship, the first terminal device can know in which application function network element triggers the environmental IoT service and in which it can act as a reader / writer.

[0040] In one possible implementation, the method further includes sending a subscription information update request message to a second core network element. This request message includes authorization result indication information, requesting the second core network element to update the subscription information of the first terminal device based on the authorization result indication information. Thus, the second core network element can record that the first terminal device has been authorized as a reader / writer. Optionally, it can also record one or more of the following: authorization time information, authorization location information, and the binding relationship between the first terminal device and the application function network element.

[0041] In one possible implementation, when determining whether to authorize the first terminal device as a reader / writer, the first core network element may base its decision on the first terminal device's subscription information and its environmental IoT capability information. The environmental IoT capability information includes one or more of the following:

[0042] The environmental IoT service type, the effective time information of the first terminal device as a reader, the effective area information of the first terminal device as a reader, the binding relationship between the first terminal device and the application function network element, and the reader information of the first terminal device as a reader.

[0043] In one possible implementation, the third message is an Environmental IoT Service Request message, used to request the establishment of an Environmental IoT service. If the first core network element is an access and mobility management network element, it sends the fourth message to the first terminal device via a non-access stratum message. If the first core network element is an Environmental IoT function network element, it sends the fourth message to the first terminal device via an access and mobility management network element, or via an AIOT UE reader control message.

[0044] In other words, when an application function network element requests environmental IoT services, it requests the first core network element to authorize the first terminal device as a reader / writer, which helps to improve the efficiency of establishing environmental IoT services.

[0045] In one possible implementation, for the third message being an environmental IoT service request message, the method further includes: sending a second identifier list to the base station, the second identifier list including identifiers of terminal devices authorized as readers / writers. Thus, the base station can determine which terminal devices are authorized as readers / writers.

[0046] In one possible implementation, for the third message being an environmental IoT service request message, the method further includes: receiving confirmation indication information from the first terminal device, used to instruct the first terminal device to confirm the authorization result indication information. That is, upon receiving the fourth message, the first terminal device sends confirmation indication information back to the first core network element, indicating that the first terminal device agrees to act as a reader / writer. Thus, during the establishment of the environmental IoT service, the first terminal device can act as a reader / writer to communicate with the environmental IoT device.

[0047] In one possible implementation, the third message is an authorization request message. This authorization request message includes a third identifier list, which includes identifiers of terminal devices that the application function network element expects to be authorized as readers / writers. The third identifier list also includes the identifier of the first terminal device. In other words, the authorization request message sent by the application function network element to the first core network element carries the identifiers of the terminal devices that the application function network element expects to be authorized as readers / writers, requesting the first core network element to authorize the terminal devices in the list to act as readers / writers.

[0048] Optionally, the authorization request message may also include environmental IoT capability information of each terminal device in the third identifier list, so that the first core network element can determine whether to authorize the terminal device as a reader / writer based on the subscription information and environmental IoT capability information.

[0049] The environmental IoT capability information includes one or more of the following:

[0050] The information includes the type of IoT service in the environment, the effective time information of the terminal device as a reader, the effective area information of the terminal device as a reader, the binding relationship between the terminal device and the application function network element, and the reader information of the terminal device as a reader.

[0051] In one possible implementation, for the third message being an authorization request message, the method further includes: sending a fourth identifier list to the base station. The fourth identifier list includes some or all of the identifiers in the third identifier list, and includes identifiers of terminal devices already authorized as readers. In other words, the first core network element informs the base station of the terminal devices already authorized as readers.

[0052] Fourthly, embodiments of this application provide a communication device comprising a module / unit for performing any of the methods described in the first aspect and its possible implementations, or for performing any of the methods described in the second aspect and its possible implementations, or for performing any of the methods described in the third aspect and its possible implementations.

[0053] Fifthly, embodiments of this application provide a communication device. This device can be a first terminal device, a chip, chip system, or processor supporting the first terminal device in implementing the above-described methods, or a logic node, logic module, or software capable of implementing all or part of the terminal functions. The communication device can also be a chip system. This communication device can execute the method described in the second aspect. The functions of the communication device can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above-described functions. These units can be software and / or hardware. The operations performed by the communication device and its beneficial effects can be found in the method described in the second aspect above, and the details will not be repeated.

[0054] Sixthly, embodiments of this application provide a communication device. This device can be a first core network element, a chip, chip system, or processor supporting the first core network element in implementing the above-described methods, or a logical node, logical module, or software capable of implementing all or part of the functions of the first core network element. The communication device can also be a chip system. This communication device can execute the methods described in the first or third aspect. The functions of the communication device can be implemented in hardware or by executing corresponding software. The hardware or software includes one or more units corresponding to the above-described functions. These units can be software and / or hardware. The operations performed by the communication device and its beneficial effects can be found in the methods described in the first or third aspect and their beneficial effects; repeated descriptions will not be repeated.

[0055] In a seventh aspect, embodiments of this application provide a communication device, the communication device including a processor coupled to a memory for storing programs or instructions, wherein when the program or instructions are executed by the processor, the communication device performs the method described in any one of the first to third aspects.

[0056] Eighthly, embodiments of this application provide a communication device, the communication device including a processor and an interface circuit, the interface circuit being configured to receive signals from other communication devices outside the communication device and transmit them to the processor, or to send signals from the processor to other communication devices outside the communication device, the processor being configured to implement the method as described in any one of the first to third aspects through logic circuits or execution code instructions.

[0057] Ninthly, embodiments of this application provide a computer-readable storage medium for storing computer-executable instructions, which, when executed, cause the method executed by the first core network element as described in the first aspect to be implemented; or cause the method executed by the first terminal device as described in the second aspect to be implemented; or cause the method executed by the first core network element as described in the third aspect to be implemented.

[0058] In a tenth aspect, embodiments of this application provide a computer program product including a computer program, which, when executed, causes the method executed by the first core network element as described in the first aspect to be implemented; or causes the method executed by the first terminal device as described in the second aspect to be implemented; or causes the method executed by the first core network element as described in the third aspect to be implemented.

[0059] Eleventhly, embodiments of this application provide a communication system, which includes a communication device (e.g., a first core network element) for performing the method described in the first aspect above and a communication device (e.g., a first terminal device) for performing the communication method described in the second aspect above.

[0060] Understandably, the beneficial effects that the communication methods, communication devices, computer-readable storage media, and computer program products provided above can be referenced to the beneficial effects in the first, second, or third aspects and any possible implementation thereof, and will not be repeated here. Attached Figure Description

[0061] Figure 1 This is a schematic diagram of the network architecture of a 5G system according to an embodiment of this application;

[0062] Figure 2A and Figure 2B This is a schematic diagram of the transmission topology architecture of an AIoT device according to an embodiment of this application;

[0063] Figure 3A and Figure 3B This is a schematic diagram of the control plane transmission scheme of an AIoT device in the core network according to an embodiment of this application;

[0064] Figure 4A and Figure 4B This is a schematic diagram of the protocol stack for transmission within the core network of an AIoT device according to an embodiment of this application;

[0065] Figure 5 This is a schematic diagram of the system architecture applied in the embodiments of this application;

[0066] Figure 6A , Figure 6B, Figure 7A , Figure 7B , Figure 8A , Figure 8B as well as Figure 9A This is a flowchart illustrating several communication methods provided in the embodiments of this application;

[0067] Figure 10 This is a flowchart illustrating another communication method provided in an embodiment of this application;

[0068] Figure 11 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0069] Figure 12 This is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0070] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0071] The terms "first," "second," "third," etc., used in the embodiments of this application are to distinguish different objects, rather than to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, it may include a series of steps or units, or optionally, steps or units not listed, or other steps or units inherent to these processes, methods, products, or devices. The terms "one embodiment" or "some embodiments," etc., mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of the embodiments of this application, do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized.

[0072] Furthermore, "at least one" refers to one or more, while "more than one" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, and c can mean: a, or b, or c, or a and b, or a and c, or b and c, or a, b, and c, where a, b, and c can be single or multiple.

[0073] The terminology used in the following embodiments of this application is for the purpose of describing particular embodiments only and is not intended to be a limitation of this application.

[0074] 1. Environmental Internet of Things

[0075] With the widespread application of IoT technology in wireless communication, reducing the size, complexity, and power consumption of IoT devices has become a major concern. Since most wireless communication devices require manual battery replacement or are powered by rechargeable batteries, this can lead to high maintenance costs and even safety hazards. As the demands of the digital age continue to grow and automation levels increase, there is an urgent need to introduce new IoT technologies to support devices without power storage capabilities or those requiring no manual battery replacement or recharging. Therefore, IoT technology supporting higher-density connectivity, lower complexity, and lower power consumption—Environmental IoT—has emerged.

[0076] The Environmental Internet of Things (IoT) includes environmental IoT devices, which are characterized by low power consumption, low complexity, small size, and long lifespan. They typically do not use traditional batteries and primarily utilize energy derived from environmental sources. Environmental energy sources can include radio waves, solar energy, kinetic energy, thermal energy, pressure energy, or any other form of energy. Radio waves may originate from base stations or user equipment (UEs). Environmental IoT devices can also be simply referred to as IoT devices, and may have other names as standards evolve.

[0077] Environmental IoT also includes readers, which can be devices with environmental IoT capabilities. These readers can power environmental IoT devices or provide carrier signals for backscattering to them. Readers can also be called readers, excitation sources, IoT-capable devices, IoT-functional devices, etc., and may have other names as standards evolve. Readers can be base stations or user-defined devices (UEs).

[0078] A base station can be a base station in a new radio (NR) system, such as a next-generation node B (gNB), an evolved node B (eNB), a radio network controller (RNC), a node B (NB), a base station controller (BSC), a base transceiver station (BTS), a home base station (e.g., a home evolved node B or home node B, HNB), a baseband unit (BBU), a transmission and reception point (TRP), a transmitting point (TP), a mobile switching center, etc. A base station can also be a base station in a future communication system, such as a sixth-generation (6G) base station. th Base stations are used in 6G (generation, 6G) communication systems. Base stations can also be access network devices in non-terrestrial network (NTN) communication systems, meaning they can be deployed on high-altitude platforms or satellites. Base stations can also function as base stations in device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, drone communication, and machine-to-machine (M2M) communication. Optionally, base stations can also be servers, wearable devices, vehicles, or in-vehicle equipment. For example, in vehicle-to-everything (V2X) technology, the base station can be a roadside unit (RSU).

[0079] A UE can also be referred to as a terminal, terminal equipment, mobile station (MS), mobile terminal (MT), access terminal equipment, vehicle-mounted terminal equipment, industrial control terminal equipment, UE unit, UE station, mobile station, remote station, remote terminal equipment, mobile device, wireless communication equipment, UE agent, or UE device, etc. A UE can be fixed or mobile. It should be noted that a UE can support at least one wireless communication technology, such as Wideband Code Division Multiple Access (WCDMA), Long Time Evolution (LTE), NR, 6G, or next-generation wireless communication technologies. For example, a UE can be a mobile phone, tablet, desktop computer, laptop computer, all-in-one computer, vehicle terminal, virtual reality (VR) terminal device, augmented reality (AR) terminal device, mixed reality (MR) terminal device, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical surgery, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, wearable device, UE in future mobile communication networks, or UE in future evolved public land mobile network (PLMN), etc.

[0080] The reader-to-AIOT device (R2D) transmission can be simply referred to as R2D transmission. R2D transmission is used by the reader to send R2D data and / or R2D signaling to the AIOT device. The AIOT device-to-reader (D2R) transmission can be simply referred to as D2R transmission. D2R transmission is used by the AIOT device to send D2R data and / or D2R signaling to the reader. For ease of description, the AIOT is simply referred to as AIOT.

[0081] Second, the fifth generation (5 th Core network in 5G (generation) system

[0082] The core network is a crucial component of a mobile communication network, connecting external networks and the access network to provide support for core services to users. Please see [link / reference]. Figure 1 This is a schematic diagram of the network architecture of a 5G system. This architecture includes the User Equipment (UE), radio access network (RAN) equipment, and core network elements. The RAN equipment is part of the access network and is responsible for connecting the UE to the network. Application functions (AFs) are network elements in the external network that are primarily responsible for providing various service functions.

[0083] Core network elements may include the following: User plane function (UPF), data network (DN), authentication server function (AUSF), access and mobility management function (AMF), session management function (SMF), network slice selection function (NSSF), network exposure function (NEF), network function repository function (NRF), policy control function (PCF), unified data management (UDM), unified data repository (UDR), and ambient internet of things function (AIOTF).

[0084] The Access Management Function (AMF) is primarily responsible for mobility management, access management, encryption and integrity protection of non-access stratum (NAS) messages, and registration. The Service Management Function (SMF) is primarily responsible for managing the creation and deletion of Protocol Data Unit (PDU) sessions, maintaining PDU session context, and user plane forwarding. The User Provider Function (UPF) is primarily responsible for packet routing and forwarding, as well as Quality of Service (QoS) flow mapping. The Computer Processing Function (PCF) is primarily responsible for generating and managing policies, such as network discovery and selection policies, and network handover selection policies. The User Authentication and Delegation Function (UDM) is primarily responsible for access authentication, registration, mobility management, and user subscription information management. User subscription information is authenticated and stored through the UDM, and managed overall by the User Controller Receiver (UDR), with standard interfaces provided by the specification for retrieval and querying. The Network Authentication and Delegation Function (NEF) is primarily used to provide a framework, authentication, and interfaces related to network capability exposure. The Network Authentication and Delegation Function (NRF) supports service discovery functions. The User USF supports both 3GPP and non-3GPP access authentication.

[0085] AIOTF is a new core network element added for AIoT services. AIOTF can also be described as an AIoT network function (AIOT NF), and may have other names as the standard evolves. AIOTF may have one or more of the following functions:

[0086] a. AIOTF can register its network function (NF) profile with NRF.

[0087] b, in topology 1 ( Figure 2A Under topology 2 (as shown), AIOTF can select a base station reader (i.e., the base station as the reader) and / or an AIOT RAN device. Figure 2B As shown, AIOTF can select UE readers (e.g., candidate UE readers or final UE readers) and provide the RAN equipment with a list of selected UE readers.

[0088] c. The AIOTF receives AIOT service requests from the AF and triggers the base station reader or UE reader to execute AIOT services with the AIOT device.

[0089] d. AIOTF summarizes the AIOOT service execution results (including the deletion of duplicate device records) from the base station reader and UE reader, and sends the summarized AIOOT service execution results to AF.

[0090] e. The AIOTF can provide auxiliary information to the base station reader or UE reader. This auxiliary information may include one or more of the following: AIoT service type (e.g., inventory or command), an estimate of the number of AIoT devices determined based on the AIoT service request from the AF, and an estimate of the D2R message size determined based on the AIoT service request from the AF. If multiple readers are selected for the AIoT service, the AIOTF can provide an estimate of the number of AIoT devices to each reader.

[0091] Inventory, or stocktaking, refers to requesting an inventory operation, such as requesting to count the number of AIoT devices. Commands can include one or more of the following: read, write, disable, and enable. Reading requests to retrieve information from an AIoT device. Writing requests to write information to an AIoT device. Disabling requests to permanently or temporarily disable the radio frequency (RF) transmission capabilities of an AIoT device. Enabling requests to enable a disabled AIoT device.

[0092] f. When the AIOTF sends an AIoT service execution request to the base station reader or UE reader, it can receive a response and one or more reports, including the AIoT service execution results. The AIOTF needs to associate these results with the given AIoT service execution request. When the AMF routes the AIoT service execution request, the AMF will also carry the AIOTF identifier in the AIoT service execution request. The response received by the AMF to the corresponding AIoT service execution request also carries the AIOTF identifier, so the AMF can forward the response to the AIOTF.

[0093] The functions a to f described above are for illustrative purposes only and do not constitute a limitation on the embodiments of this application. As the standard evolves, AIOTF may have more or fewer functions.

[0094] For UE subscription information stored in the UDM, this subscription information may include UE reader / writer subscription information, indicating whether the UE is allowed to act as a UE reader / writer. The UE reader / writer subscription information also indicates other information, such as the validity period (i.e., the valid period during which the UE is allowed to act as a UE reader / writer). The UE reader / writer subscription information is available to the AMF and AIOTF. If the AMF receives an indication that the UE is authorized to act as a UE reader / writer, the AMF can notify the NG-RAN that the UE has been authorized to act as a UE reader / writer.

[0095] Radio resource management when a UE is running as a UE reader / writer may include: if the gNB receives an indication message indicating that the UE is authorized as a UE reader / writer, then the gNB may allocate radio resources for the UE reader / writer to run; assuming the UE reader / writer requests radio resources for the reader / writer to run from the gNB, for example, the gNB receives copy information from AIOTF and requests radio resources for the reader / writer to run from the gNB.

[0096] III. Transmission Topology Architecture of AIoT Devices

[0097] From the perspective of the RAN working group, the third-generation partner program (3GPP) rd The 3GPP (3rd Generation Partnership Project) defines two transmission topology architectures for AIoT devices: Topology 1 and Topology 2. and topology 2 This indicates bidirectional communication. See Topology 1 for details. Figure 2A As shown, the base station acts as a reader / writer, performing D2R and R2D transmissions with AIoT devices. See Topology 2 for details. Figure 2BAs shown, the base station and the intermediate node communicate via Uu interface. The intermediate node, acting as a reader / writer, communicates with the AIoT device via D2R and R2D. In topology 2, the UE acts as the intermediate node. That is, the UE is a UE reader / writer.

[0098] 3GPP also defines two transmission schemes for AIoT devices within the core network: a control plane transmission scheme and a user plane transmission scheme. The control plane transmission scheme is used to transmit signaling and / or data for AIoT devices. For the control plane transmission scheme based on Topology 1, please refer to [link to Topology 1 documentation]. Figure 3A As shown, the control plane transmission scheme based on topology 2 can be found in [reference needed]. Figure 3B As shown. Figure 3A and Figure 3B In the diagram, AMF is indicated by a dashed box, signifying that AMF is an optional core network element. The protocol stack for the control plane transmission scheme based on Topology 2 can be found in [reference needed]. Figure 4A As shown. Figure 4A In this protocol stack, the AIOT reader control protocol is included between AIOTF and RAN to implement AIOT reader control connection between AIOTF and RAN.

[0099] The user plane transport scheme is used to transmit signaling and / or data for AIoT devices. The protocol stack for the user plane transport scheme based on Topology 2 can be found in [reference needed]. Figure 4B As shown. For the user plane transmission scheme based on topology 2, a dedicated PDU session for AIoT services can be established between the UE and the UPF, and an AIOT UE reader control connection can be established between the UE and the AIOTF. The AIOT UE reader control connection can also be described as an AIOT-AP connection. Figure 4B In this protocol stack, the AIOT UE reader control protocol is used to implement the AIOT UE reader control connection between the UE and the AIOTF.

[0100] Figure 4B In this context, the AIOT UE reader control protocol between the UE and AIOTF can implement some or all of the functions in the NG-AP protocol.

[0101] Figure 4A and Figure 4B In this context, the RAN has AIOT capabilities and can be either NG-RAN or a base station, etc.

[0102] Based on topology 2, when the UE is authorized as a UE reader / writer, it is possible to achieve Figure 4A The control plane transmission scheme shown, and Figure 4B The user plane transmission scheme is shown. In other words, when the UE is authorized as a UE reader / writer, the UE can perform the following procedures:

[0103] 1) The UE can request the base station to allocate AIoT radio resources (applicable to both control plane transmission scheme and user plane transmission scheme) to enable interaction between the UE and AIoT devices;

[0104] 2) The UE can establish a PDU session with the UPF for AIoT services so that the UE can transmit AIoT service data; the UE can also establish an AIoT UEreader control connection with the AIOTF.

[0105] Currently, based on topology 2, there is no clear solution regarding when and how a UE is authorized to act as a UE reader / writer. Therefore, how a UE is authorized to act as a UE reader / writer is a current research hotspot.

[0106] In view of this, embodiments of this application provide a communication method, a communication device, and a computer-readable storage medium, which clarifies the timing when a terminal device can be authorized as a reader / writer, thereby enabling the terminal device to be authorized as a reader / writer and thus improving the efficiency of establishing AIoT services.

[0107] To better understand the embodiments of this application, the system architecture involved in the embodiments of this application will be described first below:

[0108] This application's embodiments can be applied to communication systems evolving after 5G, such as Long Term Evolution (LTE) systems, 5G systems, and 6G systems, as well as satellite communications and short-range wireless communication systems. The wireless communication systems mentioned in this application's embodiments include, but are not limited to: the three major application scenarios of 5G / 6G mobile communication systems: enhanced mobile broadband (eMBB), ultra-reliable low latency communication (URLLC), and massive machine-type communication (mMTC); long-range (LoRa) IoT systems; environmental IoT systems; or vehicle-to-everything (V2X) systems. A wireless communication system may include one or more base stations and one or more terminal devices.

[0109] The embodiments of this application can be applied to Figure 5 In the system architecture shown. Figure 5The system architecture shown may include, but is not limited to: terminal device 501, base station 502, first core network element 503, second core network element 504, and application function network element 505. Figure 5 The number of devices mentioned is for illustrative purposes only and does not constitute a limitation on the embodiments of this application. For example, in actual applications, multiple terminal devices may be included.

[0110] A terminal device, also known as a UE, can be registered with the core network via a base station 502 in this embodiment. During the registration process, a first core network element 503 can authorize the terminal device 501 as a UE reader, for example, authorizing it as such. The terminal device 501 can also receive authorization result indication information from the first core network element 503 via the base station 502, indicating whether it has been authorized as a reader, i.e., whether it has been authorized as a UE reader. Furthermore, if the terminal device 501 is located within a preset AIoT service area, it can request the base station 502 or request the first core network element 503 via the base station 502 to authorize it as a reader.

[0111] This application does not limit the form of the terminal device. The device used to implement the function of the terminal device can be the terminal device itself, or it can be a device that supports the terminal device in implementing the function, such as a chip system. The device can be installed in the terminal device or used in conjunction with the terminal device. In this application, the chip system can be composed of chips or can include chips and other discrete components.

[0112] Multiple base stations collaborate to assist terminal devices in achieving wireless access, with each base station performing a specific function. For example, a base station can be a central unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). CUs and DUs can be separate entities or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs). It is understood that a base station can be a CU node, a DU node, or a combination of both. Furthermore, a CU can be classified as equipment in the access network (RAN) or the core network (CN); there are no restrictions on this classification.

[0113] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software modules and hardware modules.

[0114] The embodiments of this application do not limit the form of the base station. The device used to implement the function of the base station can be a base station; it can also be a device that supports the base station in implementing the function, such as a chip system. The device can be installed in the base station or used in conjunction with the base station. In the embodiments of this application, the chip system can be composed of chips, or it can include chips and other discrete components.

[0115] The first core network element 503 can be... Figure 1 AMF in the text can also be Figure 1In the AIOTF within the system. In this embodiment, the first core network element 503 can obtain the subscription information of the terminal device 501 from the second core network element 504, and determine whether to authorize the terminal device 501 as a reader / writer based at least on the subscription information. The second core network element 504 can be... Figure 1 The second core network element 504 stores the subscription information of the terminal device 501, including UE reader / writer subscription information, indicating whether the terminal device 501 is allowed to act as a UE reader / writer. For example, if the subscription information indicates that the terminal device 501 is allowed to act as a UE reader / writer, then the first core network element 503 can authorize the terminal device 501 as a reader / writer; conversely, if the subscription information indicates that the terminal device 501 is not allowed to act as a UE reader / writer, then the first core network element 503 can refuse to authorize the terminal device 501 as a reader / writer. Optionally, the subscription information may also include the network registration status of the terminal device 501, indicating whether the terminal device 501 has registered to the network or not.

[0116] The embodiments of this application do not limit the form of the core network element. The device used to implement the function of the core network element can be the core network element itself; it can also be a device that supports the core network element in implementing the function, such as a chip system. The device can be installed in the core network element or used in conjunction with the core network element. In the embodiments of this application, the chip system can be composed of chips or can include chips and other discrete devices.

[0117] Application function network element 505 is a network element in the external network. In this embodiment, application function network element 505 can send an AIoT service request to the core network to request the core network to establish a control plane transmission channel and a user plane transmission channel to carry AIoT services. Application function network element 505 can also send a UE reader authorization request to the core network. This request carries a list of terminal device identifiers that application function network element 505 expects to be authorized as UE readers, so as to request the core network to determine whether to authorize each terminal device in the list as a UE reader.

[0118] The embodiments of this application do not limit the form of the application function network element. The device used to implement the function of the application function network element can be the application function network element itself; it can also be a device that supports the application function network element in implementing the function, such as a chip system. The device can be installed in the application function network element or used in conjunction with the application function network element. In the embodiments of this application, the chip system can be composed of chips or can include chips and other discrete devices.

[0119] For ease of description, the embodiments in this application are described using UE1, gNB, AMF, AIOTF, AUSF, UDM, and AF as examples.

[0120] The following is based on Figure 5 The system architecture shown here provides a detailed explanation of the communication method provided in the embodiments of this application.

[0121] Please see Figure 6A This is a flowchart illustrating a communication method provided in an embodiment of this application. Figure 6A The embodiment shown illustrates that during the registration process of UE1 with the network, AIOF determines whether to authorize UE1 as a reader / writer.

[0122] Figure 6A The illustrated embodiments may include, but are not limited to, the following steps:

[0123] 601a, UE1 sends a registration request message to gNB. Correspondingly, gNB receives the registration request message from UE1.

[0124] UE1 can be any UE that initiates registration. UE1 sends a registration request message to the gNB. The registration request message may include UE1's AIOT capability information. The AIOT capability information may include one or more of the following: AIOT service type, valid time information of UE1 as a UE reader, valid area information of UE1 as a UE reader, binding relationship between UE1 and AF, and reader information of UE1 as a UE reader.

[0125] AIoT service types can be one or more of the following: inventory, command (read, write, disable, enable, etc.), or registration. Inventory refers to a request to perform an inventory operation, such as requesting to count the number of AIoT devices. Read refers to a request to read information from an AIoT device. Write refers to a request to write information to an AIoT device. Disable refers to a request to permanently or temporarily disable the RF transmission capability of an AIoT device. Enable refers to a request to enable a temporarily disabled AIoT device. Registration refers to a request to register an AIoT device.

[0126] The effective time information of UE1 as a UE reader / writer indicates which time period(s) UE1 can operate as a UE reader / writer. For example, UE1 can operate as a UE reader / writer during time period 1 (or time period 1 and time period 2). The rules and granularity of time period division are not limited in this embodiment.

[0127] The valid area information for UE1 as a UE reader / writer indicates which areas or regions UE1 can operate as a UE reader / writer. For example, UE1 can operate as a UE reader / writer in area 1. The area can be a geographical area, a cell, or a tracking area (TA).

[0128] The binding relationship between UE1 and AF indicates whether UE1 can act as a UE reader / writer when facing an AIoT service request from a specific AF. A specific AF must be bound to UE1. For example, if UE1 is bound to AF1 but not to AF2, then UE1 can act as a UE reader / writer when facing an AIoT service request from AF1, but cannot act as a UE reader / writer when facing an AIoT service request from AF2.

[0129] Reader information, such as reader type, is included. The reader information for UE1 as a UE reader can indicate the reader type of UE1. Reader types can be categorized as fixed or mobile. Fixed type indicates that the UE reader is located in a fixed geographical location; mobile type indicates that the UE reader is mobile and its geographical location is not fixed. The term "reader type" is used as an example and does not constitute a limitation on the embodiments of this application.

[0130] The information included in the above AIoT capability information is for illustrative purposes only and does not constitute a limitation on the embodiments of this application. As the standard evolves, the AIoT capability information may include more or less information.

[0131] Optionally, the registration request message may include a field whose value indicates whether UE1 supports AIoT capabilities, i.e., whether UE1 can operate as a UE reader / writer. If the value of this field indicates that UE1 supports AIoT capabilities, the registration request message may carry AIoT capability information. Alternatively, if the registration request message carries AIoT capability information, it implicitly indicates that UE1 supports AIoT capabilities. Conversely, if the registration request message does not carry AIoT capability information, it implicitly indicates that UE1 does not support AIoT capabilities.

[0132] The registration request message may also include the UE1 identifier (ID) and / or UE1's location information. The UEID can be a subscription permanent identifier (SUPI), a subscription concealed identifier (SUCI), a generic public subscription identifier (GPSI), a permanent equipment identifier (PEI), etc. The UE ID can also be described as the UEread ID. The UE's location information can be the UE's geographic location information (e.g., latitude and longitude), the UE's TA information, or one or more of the cell information to which the UE belongs.

[0133] 602a, the gNB sends a registration request message to the AMF. Correspondingly, the AMF receives the registration request message from the gNB.

[0134] Upon receiving a registration request message from UE1, the gNB selects an AMF and forwards the registration request message to the selected AMF.

[0135] 603a, the AMF sends an authorization request message to the AIOTF. Correspondingly, the AIOTF receives the authorization request message from the AMF.

[0136] Upon receiving a registration request message, the AMF sends an authorization request message to the AIOTF. This authorization request message includes UE1's AIoT capability information, as well as UE1's ID and / or UE1's location information.

[0137] 604a, authentication process.

[0138] Upon receiving the registration request message, the AMF selects both the AFS and the UDM. Then, the AMF, AFS, and UDM execute the authentication process for UE1. This process is not described in detail in this embodiment; however, it can be found in the authentication process during UE registration, such as the description of the UE registration process in 3GPP TS23.501, which includes an authentication process.

[0139] Steps 603a and 604a can be executed simultaneously, meaning that the authentication process and the sending of the authorization request message to AIOTF can be performed at the same time.

[0140] 605a, AIOTF obtains UE1's contract information from UDM.

[0141] Upon receiving an authorization request message, AIOTF retrieves UE1's subscription information from UDM based on UE1's ID. UE1's subscription information may include UE reader / writer subscription information, indicating whether UE1 is permitted to act as a UE reader / writer.

[0142] 606a, AIOTF determines whether to authorize UE1 as a UE reader / writer based on UE1's subscription information.

[0143] In one implementation, AIOTF determines whether to authorize UE1 as a UE reader / writer based on UE1's subscription information. For example, if UE1's subscription information indicates that UE1 is allowed to act as a UE reader / writer, then AIOTF may authorize UE1 as a UE reader / writer. Conversely, if UE1's subscription information indicates that UE1 is not allowed to act as a UE reader / writer, then AIOTF will refuse to authorize UE1 as a UE reader / writer.

[0144] Optionally, UE1's subscription information also indicates a validity period, which can be understood as the validity period of the subscription. AIOTF can determine whether to authorize UE1 as a UE reader based on the indication of whether UE1 is allowed to act as a UE reader and the validity period. For example, if UE1's subscription information indicates that UE1 is allowed to act as a UE reader during time period 1, and if AIOTF receives the authorization request message earlier than the start time of time period 1 or within time period 1, AIOTF can authorize UE1 to act as a UE reader during time period 1; if AIOTF receives the authorization request message later than the end time of time period 1, then AIOTF can refuse to authorize UE1 to act as a UE reader during time period 1.

[0145] In another implementation, AIOTF determines whether to authorize UE1 as a UE reader / writer based on UE1's subscription information and UE1's AIOT capability information. For example, UE1's subscription information indicates that UE1 is allowed to act as a UE reader / writer during time period 1. If UE1's AIOT capability information specifies time period 2 as the effective time for UE1 to act as a UE reader / writer, and the start time of time period 2 is later than the end time of time period 1, then AIOTF may refuse to authorize UE1 to act as a UE reader / writer during time period 1. If time period 2 falls within time period 1, then AIOTF may authorize UE1 to act as a UE reader / writer during time period 2. As another example, UE1's subscription information indicates that UE1 is allowed to act as a UE reader / writer in cells 1 to 3. If UE1's AIOT capability information specifies cell 2 as the effective area for UE1 to act as a UE reader / writer, then AIOTF may authorize UE1 to act as a UE reader / writer in cell 2. If UE1's AIOT capability information specifies cell 4 as the effective area for UE1 to act as a UE reader / writer, then AIOTF may refuse to authorize UE1 to act as a UE reader / writer. For example, if UE1's subscription information indicates that UE1 is allowed to act as a UE reader within time period 1 and within cells 1 to 3, and if the effective time information for UE1 to act as a UE reader in UE1's AIoT capability information is time period 2 (assuming time period 2 is within time period 1), and the effective area information for UE1 to act as a UE reader in UE1's AIoT capability information is cell 2, then AIOTF can authorize UE1 to act as a UE reader within time period 2 and within cell 2.

[0146] 607a, AIOTF sends an authorization response message to AMF. Correspondingly, AMF receives the authorization response message from AIOTF.

[0147] The authorization response message may include authorization result indication information, which indicates whether UE1 has been authorized as a UE reader / writer. The authorization result indication information also includes the UE1 ID, indicating either the UE1 ID that has been authorized as a UE reader / writer or the UE1 ID that has not been authorized as a UE reader / writer.

[0148] For the authorization result indication information indicating that UE1 is authorized as a UE reader, the authorization result indication information may also include one or more of the following: authorization time information, authorization location information, and the binding relationship between UE1 and AF. The authorization time information indicates the time period for which UE1 is authorized to operate as a UE reader. The authorization location information indicates the area where UE1 is authorized to operate as a UE reader. The binding relationship between UE1 and AF indicates that when UE1 is authorized to operate as a UE reader, it can handle AIoT services initiated by the bound AF.

[0149] For authorization result indication information indicating that UE1 was not authorized as a UE reader / writer, the authorization result indication information may also include authorization failure reason information. The authorization failure reason information may include, for example, an authorization failure reason value. The authorization failure reason may include one or more of the following: not allowed to act as a UE reader / writer in the subscription information, a mismatch between the valid time information in the AIOT capability information and the valid time in the subscription information, a mismatch between the valid area information in the AIOT capability information and the valid area in the subscription information, etc. A mismatch between the valid time information in the AIOT capability information and the valid time in the subscription information means that the valid time information in the AIOT capability information and the valid time in the subscription information do not overlap. For example, if the valid time information in the AIOT capability information is time period 2, and the valid time in the subscription information is time period 1, then time period 2 and time period 2 do not overlap. A mismatch between the valid area information in the AIOT capability information and the valid area in the subscription information means that the valid area information in the AIOT capability information and the valid area in the subscription information do not overlap. For example, the valid area information in the AIoT capability information is cell 2, while the valid area in the contract information is cells 1 to 3, so the two match; as another example, the valid area information in the AIoT capability information is cell 4, while the valid area in the contract information is cells 1 to 3, so the two do not match.

[0150] Optionally, 608a, AIOTF sends a Subscription Information Update Request message to UDM. Correspondingly, UDM receives the Subscription Information Update Request message from AIOTF.

[0151] The subscription information update request message includes authorization result indication information, used to request the UDM to update UE1's subscription information based on the authorization result indication information. The UDM can update UE1's subscription information by adding authorization indication information to the subscription information. If the authorization result indication information indicates authorization as a UE reader / writer, the UDM can add authorization indication information to the subscription information to indicate that UE1 has been authorized as a UE reader / writer. If the authorization result indication information indicates not authorized as a UE reader / writer, the UDM can add authorization indication information to the subscription information to indicate that UE1 has not been authorized as a UE reader / writer. Optionally, for messages indicating that UE1 has been authorized as a UE reader / writer, the UDM can also add one or more of the following to the subscription information: authorization time information, authorization area information, and the binding relationship between UE1 and AF.

[0152] For example, the subscription information of UE1 stored in the UDM indicates that UE1 is allowed to act as a UE reader in cells 1 to 3; the authorization result indication information indicates that UE1 is authorized to act as a UE reader in cell 2. When the UDM receives a subscription information update request message, it adds authorization indication information and authorized area information to the subscription information. The authorization indication information indicates that UE1 has been authorized to act as a UE reader; the authorized area information indicates that the authorized cell is cell 2.

[0153] Optionally, after updating UE1's subscription information, UDM may send a subscription information update confirmation message to AIOTF to indicate that UDM has updated UE1's subscription information.

[0154] Optionally, AIOTF can send authorization result indication information to gNB so that gNB knows whether UE1 has been authorized as a UE reader / writer.

[0155] 609a, the AMF sends a contract information update request message to the UDM. Correspondingly, the UDM receives the contract information update request message from the AMF.

[0156] Upon successful registration, the AMF sends a subscription information update request message to the UDM. Either step 608a or step 609a needs to be executed. If the AIOTF does not execute step 608a, the AMF can execute step 609a to update UE1's subscription data upon successful registration. If the AIOTF executes step 608a, the AMF does not need to execute step 609a and can complete the registration process. The process by which the UDM updates UE1's subscription information is detailed in step 608a and will not be repeated here.

[0157] Optionally, after updating UE1's subscription information, UDM may send a subscription information update confirmation message to AMF to indicate that UDM has updated UE1's subscription information.

[0158] 610a, the AMF sends a registration response message to UE1 via the gNB. Correspondingly, UE1 receives the registration response message from the AMF via the gNB.

[0159] If UE1 successfully registers with the network, the AMF sends a registration response message to UE1 via a NAS message. This registration response message can be a successful registration response message, indicating that UE1 has registered with the network. The registration response message also includes authorization result indication information so that UE1 knows whether it has been authorized as a UE reader / writer. The AMF sending the registration response message to UE1 via a NAS message can be either the AMF sending a registration response message to the gNB, or the gNB sending a registration response message to UE1.

[0160] In the event that UE1 fails to register with the network, the AMF sends a registration failure response message to UE1 via a NAS message to indicate that UE1's network registration has failed. Optionally, the registration failure response message may also include registration failure reason information so that UE1 can know the reason for the registration failure. Optionally, the registration failure response message may also include authorization result indication information so that UE1 can know whether it has been authorized as a UE reader / writer.

[0161] Optionally, 611a, the AMF sends a first identifier list to the gNB. Correspondingly, the gNB receives the first identifier list from the AMF.

[0162] The first identifier list includes UE IDs authorized as UE readers, enabling the gNB to identify authorized UEs and request AIoT radio resources for them. The first identifier list may include one or more UE IDs, the specific number of which is not limited in this embodiment. For example, the first identifier list may include three UE IDs: UE2 ID, UE3 ID, and UE4 ID. The first identifier list can be plaintext information, such as plaintext information configured to the gNB by Operation Administration and Maintenance (OAM). Optionally, OAM can configure the list of authorized UE identifiers to the gNB. OAM can obtain the authorized UE IDs from the core network and configure the list of authorized UE identifiers to the gNB.

[0163] exist Figure 6AIn the illustrated embodiment, during the UE1 registration process with the network, the AIOTF determines whether to authorize UE1 as a UE reader / writer based on UE1's subscription information, thus giving UE1 the opportunity to be authorized as a UE reader / writer during network registration. In this way, when subsequent AIoT services are needed, UE1 has already prepared the resources for AIoT services, thereby improving the efficiency of AIoT service establishment.

[0164] Please see Figure 6B This is a flowchart illustrating another communication method provided in an embodiment of this application. Figure 6B The embodiment shown illustrates that during the registration process of UE1 with the network, the AMF determines whether to authorize UE1 as a reader / writer. Figure 6A and Figure 6B The difference is that, Figure 6A The AIOTF determines whether UE1 is authorized as a UE reader / writer. Figure 6B The AMF determines whether to authorize UE1 as a UE reader / writer. Figure 6A and Figure 6B The illustrated embodiment can be applied to both the control plane transmission scheme based on topology 2 and the user plane transmission scheme based on topology 2.

[0165] Figure 6B The illustrated embodiments may include, but are not limited to, the following steps:

[0166] 601b, UE1 sends a registration request message to the gNB. Correspondingly, the gNB receives the registration request message from UE1.

[0167] In step 602b, the gNB sends a registration request message to the AMF. Correspondingly, the AMF receives the registration request message from the gNB.

[0168] The implementation process of steps 601b and 602b can be found in [reference needed]. Figure 6A The specific descriptions of steps 601a and 602a in the illustrated embodiment will not be repeated here.

[0169] 603b, AMF obtains UE1's contract information from UDM.

[0170] Upon receiving a registration request message, the AMF selects an AFS and a UDM, and performs an authentication process for UE1 with the selected AFS and UDM. During or after the authentication process, the AMF obtains UE1's subscription information from the UDM based on UE1's ID. UE1's subscription information may include UE reader / writer subscription information, indicating whether UE1 is allowed to act as a UE reader / writer.

[0171] 604b, AMF determines whether to authorize UE1 as a UE reader / writer based on UE1's subscription information.

[0172] In one implementation, the AMF directly determines whether to authorize UE1 as a UE reader / writer based on UE1's subscription information. For example, if UE1's subscription information indicates that UE1 is allowed to act as a UE reader / writer, then the AMF can authorize UE1 as a UE reader / writer. Conversely, if UE1's subscription information indicates that UE1 is not allowed to act as a UE reader / writer, then the AMF will refuse to authorize UE1 as a UE reader / writer.

[0173] Optionally, UE1's subscription information also indicates a validity period, which can be understood as the validity period of the subscription. The AMF can determine whether to authorize UE1 as a UE reader based on the indication of whether UE1 is allowed to act as a UE reader and the validity period. For example, if UE1's subscription information indicates that UE1 is allowed to act as a UE reader during time period 1, and the AMF receives the registration request message earlier than the start time of time period 1 or within time period 1, the AMF can authorize UE1 to act as a UE reader during time period 1; if the AMF receives the registration request message later than the end time of time period 1, then the AMF can refuse to authorize UE1 to act as a UE reader during time period 1.

[0174] In another implementation, the AMF determines whether to authorize UE1 as a UE reader / writer based on UE1's subscription information and UE1's AIOT capability information. For example, UE1's subscription information indicates that UE1 is allowed to act as a UE reader / writer during time period 1. If UE1's AIOT capability information specifies time period 2 as the effective time for UE1 to act as a UE reader / writer, and the start time of time period 2 is later than the end time of time period 1, then the AMF can refuse to authorize UE1 to act as a UE reader / writer during time period 1; if time period 2 is within time period 1, then the AMF can authorize UE1 to act as a UE reader / writer during time period 2. As another example, UE1's subscription information indicates that UE1 is allowed to act as a UE reader / writer in cells 1 to 3. If UE1's AIOT capability information specifies cell 2 as the effective area for UE1 to act as a UE reader / writer, then the AMF can authorize UE1 to act as a UE reader / writer in cell 2; if UE1's AIOT capability information specifies cell 4 as the effective area for UE1 to act as a UE reader / writer, then the AMF can refuse to authorize UE1 to act as a UE reader / writer. For example, if UE1's subscription information indicates that UE1 is allowed to act as a UE reader within time period 1 and within cells 1 to 3, and if the effective time information for UE1 to act as a UE reader in UE1's AIOT capability information is time period 2 (assuming time period 2 is within time period 1), and the effective area information for UE1 to act as a UE reader in UE1's AIOT capability information is cell 2, then AMF can authorize UE1 to act as a UE reader within time period 2 and within cell 2.

[0175] 605b, the AMF sends an authorization result indication message to the AIOTF. Correspondingly, the AIOTF receives the authorization result indication message from the AMF.

[0176] The authorization result indication information can be found in the detailed description of the authorization result indication information in step 607a, and will not be repeated here.

[0177] Optionally, upon receiving authorization result indication information from the AMF, the AIOTF may send authorization result indication information to the gNB so that the gNB can know whether UE1 has been authorized as a UE reader / writer.

[0178] Optionally, according to 606b, AIOTF sends a Subscription Information Update Request message to UDM. Correspondingly, UDM receives the Subscription Information Update Request message from AIOTF.

[0179] The implementation process of step 606b can be found in the detailed description of step 608a, and will not be repeated here.

[0180] Optionally, after updating UE1's subscription information, UDM may send a subscription information update confirmation message to AIOTF to indicate that UDM has updated UE1's subscription information.

[0181] 607b, the AMF sends a Subscription Information Update Request message to the UDM. Correspondingly, the UDM receives the Subscription Information Update Request message from the AMF.

[0182] Once registration is complete, the AMF sends a subscription information update request message to the UDM. Either step 606b or step 607b needs to be performed. The process of the UDM updating UE1's subscription information is described in detail in step 608a and will not be repeated here.

[0183] Optionally, after updating UE1's subscription information, UDM may send a subscription information update confirmation message to AMF to indicate that UDM has updated UE1's subscription information.

[0184] 608b, the AMF sends a registration response message to UE1 via the gNB. Correspondingly, UE1 receives the registration response message from the AMF via the gNB.

[0185] Optionally, in 609b, the AMF sends a first identifier list to the gNB. Correspondingly, the gNB receives the first identifier list from the AMF.

[0186] For the implementation process of steps 608b and 609b, please refer to [link / reference]. Figure 6A The specific descriptions of steps 610a and 611a in the illustrated embodiments will not be repeated here.

[0187] exist Figure 6B In the illustrated embodiment, during the UE1 registration process with the network, the AMF determines whether to authorize UE1 as a UE reader / writer based on UE1's subscription information, thus giving UE1 the opportunity to be authorized as a UE reader / writer during network registration. In this way, when AIoT services are subsequently needed, UE1 has already prepared the resources for AIoT services, thereby improving the efficiency of AIoT service establishment.

[0188] Please see Figure 7A This is a flowchart illustrating another communication method provided in the embodiments of this application. Figure 7A The embodiment shown illustrates that when AF initiates an AIoT service, AIOTF determines whether to authorize UE1 as a UE reader / writer.

[0189] Figure 7A The illustrated embodiments may include, but are not limited to, the following steps:

[0190] 701a, the AF sends an AIoT service request message to the AIOTF. Correspondingly, the AIOTF receives the AIoT service request message from the AF.

[0191] The AF can send an AIoT service request message to the AIOTF via the NEF. This message is used to request the establishment of an AIoT service. The AIoT service request message may include a UE ID (e.g., UE1 ID) to request the identified UE to participate in the AIoT service. Alternatively, the AIOTF may not include a UE ID, and the AIOTF may select a UE to participate in the AIoT service based on the message, for example, selecting UE1.

[0192] Optional, 702a, AIOTF selects UE.

[0193] If the AIOTF includes a UE ID, the AIOTF can determine whether to authorize the identified UE as a UE reader, or inform the AMF of the UE ID, which will then determine whether to authorize the identified UE as a UE reader. The AIOTF may include one or more UE IDs; this embodiment uses UE1 ID as an example.

[0194] If the AIOTF service request message does not include a UE ID, then the AIOTF can select one or more UEs that have already been authorized as UE readers for the AIOOT service. In the case where the AIOTF selects UEs that have already been authorized as UE readers, the AIOTF does not need to execute steps 703a and 704a. Optionally, the AIOTF can select one or more UEs for the AIOOT service and determine whether to authorize these UEs as UE readers. Optionally, the AIOTF can select one or more UEs for the AIOOT service and inform the AMF of the IDs of these UEs, and the AMF will determine whether to authorize these UEs as UE readers. This embodiment takes the selection of UE1 by the AIOTF as an example.

[0195] 703a, AIOTF obtains UE1's contract information from UDM.

[0196] AIOTF obtains UE1's subscription information from UDM based on UE1 ID. UE1's subscription information may include UE reader / writer subscription information, indicating whether UE1 is allowed to act as a UE reader / writer. Optionally, UE1's subscription information may also include UE1's network registration status, indicating whether UE1 has registered with the network or not.

[0197] Optionally, AIOTF obtains UE1's AIOT capability information from UDM. AIOT capability information can be found in [link to relevant documentation]. Figure 6A The specific description of the embodiments shown will not be repeated here. AIOTF obtains the AIOT capability information of UE1 so that AIOTF can determine whether to authorize UE1 as a UE reader / writer based on UE1's subscription information and UE1's AIOT capability information. UE1 can report its AIOT capability information to the core network via a registration request message, and UDM can store UE1's AIOT capability information. Optionally, UDM can store UE1's AIOT capability information in UE1's subscription information, or UDM can store UE1's AIOT capability information in other information besides UE1's subscription information.

[0198] 704a, AIOTF determines whether to authorize UE1 as a UE reader / writer based on UE1's subscription information.

[0199] In one implementation, AIOTF determines whether to authorize UE1 as a UE reader / writer based on UE1's subscription information. For example, if UE1's subscription information indicates that UE1 is allowed to act as a UE reader / writer, then AIOTF can authorize UE1 as a UE reader / writer. As another example, if UE1's subscription information indicates that UE1 is allowed to act as a UE reader / writer but UE1's network registration status is not registered with a network, then AIOTF can refuse to authorize UE1 as a UE reader / writer.

[0200] In another implementation, AIOTF determines whether to authorize UE1 as a UE reader / writer based on UE1's subscription information and UE1's AIoT capability information. Regarding UE1's subscription information, including UE reader / writer subscription information, this implementation is detailed in step 606a and will not be repeated here. Regarding UE1's subscription information, including UE reader / writer subscription information and network registration status, if UE1 is already registered with the network, the detailed description is in step 606a; if UE1 is not registered with the network, AIOTF may refuse to authorize UE1 as a UE reader / writer.

[0201] 705a, AIOTF sends authorization result indication information to AMF. Correspondingly, AMF receives the authorization result indication information from AIOTF.

[0202] The authorization result indication information can be found in the detailed description of the authorization result indication information in step 607a, and will not be repeated here.

[0203] Optionally, AIOTF can send authorization result indication information to AMF via, for example, the Namf_UE_reader_authentication_request message.

[0204] 706a. The AMF sends authorization result indication information to UE1 via a NAS message. Correspondingly, UE1 receives the authorization result indication information from the AMF via a NAS message. This NAS message can be an Uplink / Downlink Transport NAS message or a new NAS message.

[0205] The AMF sends the authorization result indication information to UE1 via NAS messages. Alternatively, the AMF can send the authorization result indication information to the gNB, and the gNB can send the authorization result indication information to UE1.

[0206] For the user plane transmission scheme based on Topology 2, UE1 will not establish an AIOT-AP connection or a PDU session for AIoT services until it is authorized as a UE reader / writer. The core network then informs UE1 of the authorization result indication information via NAS messages. For example, the AIOTF can send the authorization result indication information to UE1 via an AIOT-AP establishment request message. The AIOT-AP establishment request message is used to request the establishment of an AIOT UEreader control layer connection between the AIOTF and the UE.

[0207] 707a, UE1 sends an acknowledgment message to AMF via a NAS message. Correspondingly, AMF receives the acknowledgment message from UE1 via a NAS message. This NAS message can be an Uplink / Downlink Transport NAS message or a new NAS message.

[0208] The confirmation indication information is used to indicate to UE1 that it agrees to the authorization result indication information, that is, UE1 agrees to be authorized as a UE reader or agrees not to be authorized as a UE reader. UE1 sends the confirmation indication information to AMF via NAS message, which can be UE1 sending the confirmation indication information to gNB, and gNB sending the confirmation indication information to AMF.

[0209] Optionally, upon receiving the authorization result indication information, UE1 may send a confirmation indication information to the AMF based on its AIOT capability information. For example, if the authorization result indication information indicates that UE1 is authorized as a UE reader / writer during time period 1, and the AIOT capability information indicates that UE1 is allowed as a UE reader / writer during time period 2, where time period 2 includes time period 1, then UE1 may send a confirmation indication information to the AMF.

[0210] Optionally, upon receiving an authorization result indication, UE1 may prompt the user that UE1 will be used as a UE reader / writer. This could be done, for example, by displaying a pop-up dialog box, or via SMS or voice message. Upon receiving a confirmation input from the user, UE1 will send a confirmation indication to the AMF in response.

[0211] 708a, the AMF sends an acknowledgment instruction to the AIOTF. Correspondingly, the AIOTF receives the acknowledgment instruction from the AMF.

[0212] Optionally, the AMF can send authorization result indication information to the AIOTF via, for example, the Namf_UE_reader_authentication_response message.

[0213] Optionally, upon receiving the confirmation indication information, the AIOTF sends a subscription information update request message to the UDM. Correspondingly, the UDM receives the subscription information update request message from the AIOTF. Optionally, after updating UE1's subscription information, the UDM may send a subscription information update confirmation message to the AIOTF to indicate that the UDM has updated UE1's subscription information. The AIOTF sending the subscription information update request message to the UDM and step 709a can be performed simultaneously; either one is sufficient.

[0214] 709a, the AMF sends a contract information update request message to the UDM. Correspondingly, the UDM receives the contract information update request message from the AMF.

[0215] Upon receiving the confirmation instruction and if the UE is authorized as a UE reader / writer, the AMF sends a subscription information update request message to the UDM. Optionally, after updating UE1's subscription information, the UDM may send a subscription information update confirmation message to the AMF to indicate that the UDM has updated UE1's subscription information.

[0216] Optionally, in 710a, the AMF sends a second identifier list to the gNB. Correspondingly, the gNB receives the second identifier list from the AMF.

[0217] The second identifier list includes UE IDs authorized as UE readers, enabling the gNB to identify authorized UE readers and request AIoT radio resources for these UEs. The second identifier list may include one or more UE IDs, the specific number of which is not limited in this embodiment. For example, the second identifier list may include three UE IDs: UE2 ID, UE3 ID, and UE4 ID. The AMF can send the second identifier list to the gNB via, for example, an N2 message.

[0218] Optionally, in 711a, the AIOTF sends a second identifier list to the gNB. Correspondingly, the gNB receives the second identifier list from the AIOTF.

[0219] The second identifier list includes UE IDs that have been authorized as UE readers, so that the gNB can identify UEs authorized as UE readers and request AIOOT radio resources for these UEs. The AIOTF can send the second identifier list to the gNB, for example, via an AIOTF readercontrol message.

[0220] 712a, AIOTF sends an AIoT service request message to gNB. Correspondingly, gNB receives the service request message from AIOTF.

[0221] AIOTF can send AIOT service request messages to gNB via, for example, AIOT reader control messages. Alternatively, AIOTF can send AIOT service request messages to gNB via AMF.

[0222] 713a, the gNB sends an AIOT service request message to UE1. Correspondingly, the gNB receives a service request message from the AIOTF.

[0223] The gNB can send AIOT service request messages to UE1 via radio resource control (RRC) messages, medium access control-control element (MAC-CE) messages, or downlink control information (DCI) messages. Figure 7A In the illustrated embodiment, UE1 and gNB have established an RRC connection, meaning UE1 can be in an RRC connected state. Therefore, gNB can send an AIoT service request message to UE1 via RRC messages to request UE1 to participate in AIoT services.

[0224] The AIOT service request message sent by AIOTF to gNB is different from the AIOT service request message sent by gNB to UE1. The AIOT service request message sent by gNB to UE1 can be carried in air interface messages such as RRC messages, MAC-CE or DCI, while the AIOT service request message sent by AIOTF to gNB can be carried in AIOT reader control messages.

[0225] exist Figure 7A In the illustrated embodiment, when the AF initiates an AIoT service request, the AIOTF determines whether to authorize UE1 as a UE reader / writer, thereby improving the efficiency of AIoT service establishment.

[0226] Please see Figure 7B This is a flowchart illustrating another communication method provided in the embodiments of this application. Figure 7B The embodiment shown illustrates that when the AF initiates an AIoT service request, the AMF determines whether to authorize UE1 as a UE reader / writer. Figure 7A and Figure 7B The difference is that, Figure 7A The AIOTF determines whether UE1 is authorized as a UE reader / writer. Figure 7B The AMF determines whether to authorize UE1 as a UE reader / writer. Figure 7A and Figure 7B The illustrated embodiment can be applied to both the control plane transmission scheme based on topology 2 and the user plane transmission scheme based on topology 2.

[0227] Figure 7B The illustrated embodiments may include, but are not limited to, the following steps:

[0228] 701b, the AF sends an AIoT service request message to the AIOTF. Correspondingly, the AIOTF receives the AIoT service request message from the AF. The implementation process of step 701b can be found in the detailed description of step 701a, and will not be repeated here.

[0229] Optional, 702b, AIOTF selects UE.

[0230] The implementation process of steps 701b and 702b can be found in the detailed description of steps 701a and 702a, and will not be repeated here.

[0231] 703b, AIOTF sends the UE1 ID to AMF. Correspondingly, AMF receives the UE1 ID from AIOTF.

[0232] In other words, AIOTF informs AMF of the UE ID carried in the AIoT service request message. Alternatively, AIOTF informs AMF of the selected UE ID.

[0233] 704b, AMF obtains UE1's contract information from UDM.

[0234] The AMF obtains UE1's subscription information from the UDM based on UE1's ID. UE1's subscription information may include UE reader / writer subscription information, indicating whether UE1 is allowed to act as a UE reader / writer. Optionally, UE1's subscription information may also include UE1's network registration status, indicating whether UE1 has registered with the network or not.

[0235] Optionally, the AMF obtains UE1's AIOT capability information from the UDM. The AIOT capability information can be found in [link to relevant documentation]. Figure 6A The specific description of the embodiments shown will not be repeated here. The AMF obtains the AIOT capability information of UE1 so that the AMFF can determine whether to authorize UE1 as a UE reader / writer based on UE1's subscription information and AIOT capability information. UE1 can report its AIOT capability information to the core network via a registration request message, and the UDM can store UE1's AIOT capability information. Optionally, the UDM can store UE1's AIOT capability information in UE1's subscription information, or the UDM can store UE1's AIOT capability information in other information besides UE1's subscription information.

[0236] AIOTF obtains UE1's subscription information from UDM based on UE1 ID. UE1's subscription information may include UE reader / writer subscription information, indicating whether UE1 is allowed to act as a UE reader / writer.

[0237] 705b, AMF determines whether to authorize UE1 as a UE reader / writer based on UE1's subscription information.

[0238] In one implementation, the AMF determines whether to authorize UE1 as a UE reader / writer based on UE1's subscription information. For example, if UE1's subscription information indicates that UE1 is allowed to act as a UE reader / writer, then the AMF can authorize UE1 as a UE reader / writer. As another example, if UE1's subscription information indicates that UE1 is allowed to act as a UE reader / writer but UE1's network registration status is not registered with the network, then the AMF can refuse to authorize UE1 as a UE reader / writer.

[0239] In another implementation, the AMF determines whether to authorize UE1 as a UE reader / writer based on UE1's subscription information and UE1's AIoT capability information. Regarding UE1's subscription information, including UE reader / writer subscription information, this implementation is detailed in step 604b and will not be repeated here. Regarding UE1's subscription information, including UE reader / writer subscription information and network registration status, if UE1 is already registered with the network, the detailed description is in step 604b; if UE1 is not registered with the network, the AMF may refuse to authorize UE1 as a UE reader / writer.

[0240] Optionally, in 706b, the AMF sends an authorization result indication message to the AIOTF. Correspondingly, the AIOTF receives the authorization result indication message from the AMF.

[0241] The authorization result indication information can be found in the detailed description of the authorization result indication information in step 607a, and will not be repeated here.

[0242] Optionally, upon receiving the authorization result indication information, the AIOTF sends a subscription information update request message to the UDM. Correspondingly, the UDM receives the subscription information update request message from the AIOTF. Optionally, after updating UE1's subscription information, the UDM may send a subscription information update confirmation message to the AIOTF to indicate that the UDM has updated UE1's subscription information.

[0243] 707b, the AMF sends authorization result indication information to UE1 via a NAS message. Correspondingly, UE1 receives the authorization result indication information from the AMF via a NAS message. This NAS message can be an Uplink / Downlink Transport NAS message or a new NAS message.

[0244] 708b, UE1 sends an acknowledgment message to the AMF via a NAS message. Correspondingly, the AMF receives the acknowledgment message from UE1 via a NAS message. This NAS message can be an Uplink / Downlink Transport NAS message or a new NAS message.

[0245] The confirmation indication information is used to indicate to UE1 the authorization result indication information, that is, UE1 agrees to be authorized as a UE reader or agrees not to be authorized as a UE reader. The implementation process of step 708b can be found in the detailed description of step 707a, and will not be repeated here.

[0246] Optionally, in step 709b, the AMF sends an acknowledgment instruction to the AIOTF. Correspondingly, the AIOTF receives the acknowledgment instruction from the AMF. Either step 706b or step 709b needs to be performed.

[0247] Optionally, upon receiving the confirmation indication information, the AIOTF sends a subscription information update request message to the UDM. Correspondingly, the UDM receives the subscription information update request message from the AIOTF. Optionally, after updating UE1's subscription information, the UDM may send a subscription information update confirmation message to the AIOTF to indicate that the UDM has updated UE1's subscription information. The AIOTF sending the subscription information update request message to the UDM and step 710b can be performed simultaneously; either one is sufficient.

[0248] 710b, the AMF sends a contract information update request message to the UDM. Correspondingly, the UDM receives the contract information update request message from the AMF.

[0249] Upon receiving the confirmation instruction and if the UE is authorized as a UE reader / writer, the AMF sends a subscription information update request message to the UDM. Optionally, after updating UE1's subscription information, the UDM may send a subscription information update confirmation message to the AMF to indicate that the UDM has updated UE1's subscription information.

[0250] Optionally, in 711b, the AMF sends a second identifier list to the gNB. Correspondingly, the gNB receives the second identifier list from the AMF.

[0251] The second identifier list includes UE IDs authorized as UE readers, enabling the gNB to identify authorized UE readers and request AIoT radio resources for these UEs. The second identifier list may include one or more UE IDs, the specific number of which is not limited in this embodiment. For example, the second identifier list may include three UE IDs: UE2 ID, UE3 ID, and UE4 ID. The AMF can send the second identifier list to the gNB via, for example, an N2 message.

[0252] Optionally, in 712b, the AIOTF sends a second identifier list to the gNB. Correspondingly, the gNB receives the second identifier list from the AIOTF.

[0253] The second identifier list includes UE IDs that have been authorized as UE readers, so that the gNB can identify UEs authorized as UE readers and request AIOOT radio resources for these UEs. The AIOTF can send the second identifier list to the gNB, for example, via an AIOTF readercontrol message.

[0254] 713b, AIOTF sends an AIoT service request message to gNB. Correspondingly, gNB receives the service request message from AIOTF.

[0255] AIOTF can send AIoT service request messages to gNB via, for example, AIOT reader control messages.

[0256] 714b, the gNB sends an AIOTF service request message to UE1. Correspondingly, the gNB receives a service request message from the AIOTF.

[0257] gNB can send AIOT service request messages to UE1 via RRC messages. Figure 7B In the illustrated embodiment, UE1 and gNB have established an RRC connection, meaning UE1 can be in an RRC connected state. Therefore, gNB can send an AIoT service request message to UE1 via RRC messages to request UE1 to participate in AIoT services.

[0258] exist Figure 7B In the illustrated embodiment, when the AF initiates an AIoT service request, the AMF determines whether to authorize UE1 as a UE reader / writer, which helps to improve the efficiency of AIoT service establishment.

[0259] Please see Figure 8A This is a flowchart illustrating another communication method provided in the embodiments of this application. Figure 8A The embodiment shown is that the AF carries a list of UE IDs that it expects to be authorized as UE readers in the authorization request, and requests the AIOTF to determine whether to authorize each UE in the list as a UE reader. Figure 8A The illustrated embodiment uses the example of the list including UE1 ID, and AIOTF determining whether to authorize UE1 as a UE reader / writer.

[0260] Figure 8A The illustrated embodiments may include, but are not limited to, the following steps:

[0261] 801a, the AF sends an authorization request message to the AIOTF. Correspondingly, the AIOTF receives the authorization request message from the AF.

[0262] The authorization request message can be a UEreader authentication request message. This message includes a third identifier list, which contains the UE IDs that the AF (Automatic Authentication Center) expects to authorize as UE readers. In other words, the third identifier list is a list of UE IDs, and the UEs in this list are those that the AF expects to authorize as UE readers. Figure 8A The illustrated embodiment uses the example of a third identifier list including UE1 ID, and AIOTF determining whether to authorize UE1 as a UE reader / writer.

[0263] Optionally, the authorization request message may also include AIOT capability information for each UE in the third identifier list. The AIOT capability information can be found in the detailed description in step 601a, and will not be repeated here.

[0264] Optionally, the authorization request message may include an AF ID, which identifies the AF that sent the authorization request message.

[0265] Optionally, the AF may send an authorization request message to the AIOTF before sending the AIOTF service request message. Alternatively, the AF may send an authorization request message to the AIOTF after UE1 has registered with the network.

[0266] 802a, AIOTF obtains UE1's contract information from UDM.

[0267] Upon receiving an authorization request message, AIOTF retrieves UE1's subscription information from the UDM based on UE1's ID. UE1's subscription information may include UE reader / writer subscription information, indicating whether UE1 is permitted to act as a UE reader / writer. Optionally, UE1's subscription information may also include UE1's network registration status, indicating whether UE1 has registered with the network or not.

[0268] Optionally, if the authorization request message does not include the AIOT capability information of each UE in the third identifier list, AIOTF may obtain the AIOT capability information of each UE in the third identifier list from UDM.

[0269] 803a, AIOTF determines whether to authorize UE1 as a UE reader / writer based on UE1's subscription information.

[0270] In one implementation, AIOTF determines whether to authorize UE1 as a UE reader / writer based on UE1's subscription information. For example, if UE1's subscription information indicates that UE1 is allowed to act as a UE reader / writer but UE1's network registration status is not registered with the network, then AIOTF may refuse to authorize UE1 as a UE reader / writer.

[0271] In another implementation, AIOTF determines whether to authorize UE1 as a UE reader / writer based on UE1's subscription information and UE1's AIoT capability information. Regarding UE1's subscription information, including UE reader / writer subscription information, this implementation is detailed in step 606a and will not be repeated here. Regarding UE1's subscription information, including UE reader / writer subscription information and network registration status, if UE1 is already registered with the network, the detailed description is in step 606a; if UE1 is not registered with the network, AIOTF may refuse to authorize UE1 as a UE reader / writer.

[0272] AIOTF performs steps 802a and 803a for each UE in the third identifier list, that is, AIOTF authorizes each UE reader / writer in the third identifier list. Alternatively, AIOTF obtains the subscription information of the UEs in the third identifier list in batches and determines whether to authorize the UEs in the list as UE readers / writers.

[0273] 804a, AIOTF sends a fourth identifier list to AMF. Correspondingly, AMF receives the fourth identifier list from AIOTF.

[0274] The fourth identifier list includes some or all of the identifiers in the third identifier list, and includes UE IDs that have been authorized as UE readers. In other words, AIOTF informs AMF of the UEs that have been authorized as UE readers in the third identifier list.

[0275] Optionally, the AIOTF may send a fourth identifier list to the AMF via, for example, the Namf_UE_reader_authentication_request message. Optionally, this message may also include authorization result indication information for UEs authorized as UE readers. The authorization result indication information can be found in the detailed description of authorization result indication information in step 607a, and will not be repeated here.

[0276] Optionally, AIOTF may send a fourth identifier list to the gNB. Optionally, AIOTF may also send authorization result indication information for UEs authorized as UE readers to the gNB. AIOTF may send the fourth identifier list to the gNB via, for example, an AIOTF reader control message.

[0277] Optionally, AIOTF also sends a subscription information update request message to UDM to request UDM to update the subscription information of the UE in the third identifier list.

[0278] Optionally, the AMF may also send a subscription information update request message to the UDM to request the UDM to update the subscription information of the UE in the third identifier list. Either the AMF sending the subscription information update request message to the UDM or the AIOTF sending the subscription information update request message to the UDM can be performed.

[0279] Optionally, in 805a, the AMF sends a fourth identifier list to the gNB. Correspondingly, the gNB receives the fourth identifier list from the AMF. Optionally, the AMF also sends authorization result indication information for UEs authorized as UE readers to the gNB. The AMF can send the fourth identifier list to the gNB via, for example, an N2 message.

[0280] Optionally, in 806a, the AMF sends a paging message to UE1 via the gNB. Correspondingly, UE1 receives the paging message from the AMF via the gNB.

[0281] When UE1 is in the RRC idle state, AMF sends a paging message to UE1 via NAS message based on UE1 ID.

[0282] When UE1 is in the RRC inactive state, AMF sends a paging message to UE1 via gNB based on UE1 ID.

[0283] Optionally, 807a, UE1 establishes a NAS connection.

[0284] If step 806a is executed, step 807a is executed, causing UE1 to switch from RRC idle state to RRC connected state, or from RRC inactive state to RRC connected state.

[0285] Optionally, 808a, the AMF sends authorization result indication information to UE1 via the gNB. Correspondingly, UE1 receives the authorization result indication information from the AMF via the gNB.

[0286] When UE1 is in RRC connected state, the AMF sends authorization result indication information to UE1 via the gNB based on UE1 ID. Optionally, the AMF can send authorization result indication information to UE1 via a NAS message. Optionally, the AMF can send a fourth identifier list and authorization result indication information for each UE in the list to the gNB, and the gNB can send UE1's authorization result indication information to UE1 via an RRC message.

[0287] exist Figure 8A In the illustrated embodiment, the AF initiates an authorization request, which carries a list of UE IDs that the AF expects to authorize as UE readers. The AIOTF then determines whether to authorize each UE in the list as a UE reader, thereby improving the efficiency of AIoT service establishment.

[0288] Please see Figure 8B This is a flowchart illustrating another communication method provided in the embodiments of this application. Figure 8B The embodiment shown is that the AF carries a list of UE IDs that it expects to authorize as UE readers in the authorization request, and requests the AMF to determine whether to authorize each UE in the list as a UE reader. Figure 8B The illustrated embodiment uses the example of the list including UE1 ID, and the AMF determining whether to authorize UE1 as a UE reader / writer. Figure 8A and Figure 8B The difference is that, Figure 8A The AIOTF determines whether UE1 is authorized as a UE reader / writer. Figure 8B The AMF determines whether to authorize UE1 as a UE reader / writer. Figure 8A and Figure 8B The illustrated embodiment can be applied to both the control plane transmission scheme based on topology 2 and the user plane transmission scheme based on topology 2.

[0289] Figure 8B The illustrated embodiments may include, but are not limited to, the following steps:

[0290] 801b, the AF sends an authorization request message to the AIOTF. Correspondingly, the AIOTF receives the authorization request message from the AF.

[0291] The implementation process of step 801b can be found in the detailed description of step 801a, and will not be repeated here.

[0292] 802b, AIOTF sends a third identifier list to AMF. Correspondingly, AMF receives the third identifier list from AIOTF.

[0293] AIOTF sends a third identifier list to AMF, which then authorizes UE readers for the UEs in that list.

[0294] 803b, AMF obtains UE1's contract information from UDM.

[0295] Upon receiving the third identifier list, the AMF retrieves UE1's subscription information from the UDM based on UE1's ID. UE1's subscription information may include UE reader / writer subscription information, indicating whether UE1 is permitted to act as a UE reader / writer. Optionally, UE1's subscription information may also include UE1's network registration status, indicating whether UE1 has registered with the network or not.

[0296] Optionally, if the authorization request message does not include the AIOT capability information of each UE in the third identifier list, the AMF may obtain the AIOT capability information of each UE in the third identifier list from the UDM.

[0297] 804b, AMF determines whether to authorize UE1 as a UE reader / writer based on UE1's subscription information.

[0298] In one implementation, the AIOTF determines whether to authorize UE1 as a UE reader based on UE1's subscription information. For example, if UE1's subscription information indicates that UE1 is allowed to act as a UE reader but UE1's network registration status is not registered with the network, then the AIOTF can refuse to authorize UE1 as a UE reader.

[0299] In another implementation, the AMF determines whether to authorize UE1 as a UE reader / writer based on UE1's subscription information and UE1's AIoT capability information. Regarding UE1's subscription information, including UE reader / writer subscription information, this implementation is detailed in step 604b and will not be repeated here. Regarding UE1's subscription information, including UE reader / writer subscription information and network registration status, if UE1 is already registered with the network, the detailed description is in step 604b; if UE1 is not registered with the network, the AMF may refuse to authorize UE1 as a UE reader / writer.

[0300] For each UE in the third identifier list, the AMF performs steps 803b and 804b, that is, the AMF authorizes each UE in the third identifier list as a UE reader / writer. Alternatively, the AMF obtains the subscription information of the UEs in the third identifier list in batches and determines whether to authorize the UEs in the list as UE readers / writers.

[0301] Optionally, the AMF may send the authorization result indication information of each UE in the third identifier list to the AIOTF. Optionally, the AIOTF may also send a subscription information update request message to the UDM to request the UDM to update the subscription information of the UEs in the third identifier list. Optionally, the AIOTF may also send a fourth identifier list to the gNB. Optionally, the AIOTF may also send the authorization result indication information of UEs authorized as UE readers to the gNB. The AIOTF may send the fourth identifier list to the gNB via, for example, an AIOTF readercontrol message.

[0302] The fourth identifier list includes some or all of the identifiers in the third identifier list, and the fourth identifier list includes UE IDs that have been authorized as UE readers.

[0303] 805b, the AMF sends a fourth identifier list to the gNB. Correspondingly, the gNB receives the fourth identifier list from the AMF.

[0304] In other words, the AMF informs the gNB of the UEs that have been authorized as UE readers in the third identifier list. The AMF can send the fourth identifier list to the gNB via, for example, the N2 message.

[0305] Optionally, the AMF also sends authorization result indication information of the UE that has been authorized as a UE reader to the gNB.

[0306] Optionally, the AMF may also send a subscription information update request message to the UDM to request the UDM to update the subscription information of the UE in the third identifier list. Either the AMF sending the subscription information update request message to the UDM or the AIOTF sending the subscription information update request message to the UDM can be performed.

[0307] Optionally, in 806b, the AMF sends a paging message to UE1 via the gNB. Correspondingly, UE1 receives the paging message from the AMF via the gNB.

[0308] When UE1 is in the RRC idle state, AMF sends a paging message to UE1 via NAS message based on UE1 ID.

[0309] When UE1 is in the RRC inactive state, AMF sends a paging message to UE1 via gNB based on UE1 ID.

[0310] Optionally, 807b, UE1 establishes a NAS connection.

[0311] If step 806b is executed, step 807b is executed, causing UE1 to switch from RRC idle state to RRC connected state, or from RRC inactive state to RRC connected state.

[0312] Optionally, in 808b, the AMF sends authorization result indication information to UE1 via the gNB. Correspondingly, UE1 receives the authorization result indication information from the AMF via the gNB.

[0313] When UE1 is in RRC connected state, the AMF sends authorization result indication information to UE1 via the gNB based on UE1 ID. Optionally, the AMF can send authorization result indication information to UE1 via a NAS message. Optionally, the AMF can send a fourth identifier list and authorization result indication information for each UE in the list to the gNB, and the gNB can send UE1's authorization result indication information to UE1 via an RRC message.

[0314] exist Figure 8BIn the illustrated embodiment, the AF initiates an authorization request, which carries a list of UE IDs that the AF expects to authorize as UE readers. The AMF then authorizes each UE in the list as a UE reader, thereby improving the efficiency of AIoT service establishment.

[0315] Please see Figure 9A This is a flowchart illustrating another communication method provided in the embodiments of this application. Figure 9A The embodiment shown is that when UE1 is located in a preset AIoT service area, it initiates an AIoT reader authorization request, and AIOTF determines whether to authorize UE1 as a UE reader.

[0316] Figure 9A The illustrated embodiments may include, but are not limited to, the following steps:

[0317] 901a, UE1 sends an AIOT reader authorization request message to AMF via gNB. Correspondingly, AMF receives the AIOT reader authorization request message from AMF via gNB.

[0318] The AIOT reader authorization request message includes the UE1 ID. Optionally, the AIOT reader authorization request message may also include the location information of UE1.

[0319] Optionally, the AIOT reader authorization request message may also include UE1's AIOT capability information, which can be found in [link to relevant documentation]. Figure 6A The specific description of it in the illustrated embodiment will not be repeated here.

[0320] In one implementation, UE1 sends an AIOT reader / writer authorization request message to the AMF via a NAS message to request the AMF to determine whether to authorize UE1 as a UE reader / writer. Alternatively, upon receiving the AIOT reader / writer authorization request message, the AMF sends an AIOT reader / writer authorization request message to the AIOTF to request the AIOTF to determine whether to authorize UE1 as a UE reader / writer. This method is applicable to both user plane and control plane transmission schemes based on Topology 2. UE1 sending the AIOT reader / writer authorization request message to the AMF via a NAS message may include UE1 sending an AIOT reader / writer authorization request message to the gNB, and the gNB sending an AIOT reader / writer authorization request message to the AMF.

[0321] In another implementation, UE1 sends an AIOT reader authorization request message to the gNB via an RRC message. The gNB then forwards the AIOT reader authorization request message to the AMF or AIOTF. Alternatively, the gNB sends the AIOT reader authorization request message to the AMF, and the AMF forwards the AIOT reader authorization request message to the AIOTF. This method is applicable to both user plane and control plane transmission schemes based on Topology 2.

[0322] When UE1 is located within a preset AIoT service area, it sends an authorization request message to the AMF. The preset AIoT service area can be information pre-configured in UE1, or information configured for UE1 by the AF, gNB, or core network elements (such as AMF, AIOTF, SMF, PCF). The preset AIoT service area is the area where AIoT services can be carried out, and its granularity can be land mobile network (LAND), geographical region, TA, or cell, etc.

[0323] 902a, the AMF sends an AIOT reader authorization request message to the AIOTF. Correspondingly, the AIOTF receives the AIOT reader authorization request message from the AMF.

[0324] 903a, AIOTF obtains UE1's contract information from UDM.

[0325] For the implementation process of step 903a, please refer to [link / reference]. Figure 6A The specific description of step 605a in the illustrated embodiment will not be repeated here.

[0326] Optionally, if the authorization request message does not include UE1's AIOT capability information, AIOTF may obtain UE1's AIOT capability information from UDM.

[0327] 904a, AIOTF determines whether to authorize UE1 as a UE reader / writer based on UE1's subscription information.

[0328] In one implementation, AIOTF determines whether to authorize UE1 as a UE reader / writer based on UE1's subscription information.

[0329] In another implementation, AIOTF determines whether to authorize UE1 as a UE reader / writer based on UE1's subscription information and UE's location information. The UE's location information can be carried in the authorization request message, the location information of UEs subscribed to by AIOTF, or the location information measured by the gNB. The location information of UEs subscribed to by AIOTF or the location information measured by the gNB may be the same as or different from the location information carried in the authorization request message, and the location information carried in the authorization request message may be inaccurate.

[0330] In another implementation, AIOTF determines whether to authorize UE1 as a UE reader / writer based on UE1's subscription information, the location information of the subscribed UEs, and UE1's AIOT capability information. For example, if UE1's subscription information indicates that UE1 is allowed to act as a UE reader / writer in cells 1 to 3, and if the effective area information for UE1 as a UE reader / writer in UE1's AIOT capability information is cell 2, and the location information of the subscribed UEs is cell 2, then AIOTF can authorize UE1 to act as a UE reader / writer in cell 2; if the effective area information for UE1 as a UE reader / writer in UE1's AIOT capability information is cell 4, or the location information of the subscribed UEs is cell 4, then AIOTF can refuse to authorize UE1 as a UE reader / writer.

[0331] In another implementation, AIOTF determines whether to authorize UE1 as a UE reader / writer based on UE1's subscription information and the location information of the subscribed UEs. For example, if UE1's subscription information indicates that UE1 is allowed to act as a UE reader / writer in cells 1 to 3, and the location information of the subscribed UE is cell 2, then AIOTF can authorize UE1 to act as a UE reader / writer in cell 2; if the location information of the subscribed UE is cell 4, then AIOTF can refuse to authorize UE1 to act as a UE reader / writer in cell 2.

[0332] Optionally, AIOTF also sends a subscription information update request message to UDM to request UDM to update UE1's subscription information based on UE1's authorization result indication information.

[0333] 905a, AIOTF sends an AIOT reader authorization response message to AMF. Correspondingly, AMF receives the AIOT reader authorization response message from AIOTF.

[0334] The AIOT reader authorization response message includes authorization result indication information for UE1.

[0335] Optionally, the AMF may also send a subscription information update request message to the UDM to request the UDM to update the subscription information of UE1 based on the authorization result indication information of UE1.

[0336] 906a, the AMF sends an AIOT reader authorization response message to UE1 via the gNB. Correspondingly, UE1 receives the AIOT reader authorization response message from the AMF via the gNB.

[0337] The AIOT reader authorization response message includes authorization result indication information for UE1.

[0338] exist Figure 9A In the illustrated embodiment, when UE1 is located in a preset AIoT service area, it initiates an AIoT reader authorization request. AIOTF determines whether to authorize UE1 as a UE reader based on UE1's subscription information, thereby improving the efficiency of AIoT service establishment.

[0339] As an optional embodiment 1, after step 901a, the AMF can obtain the subscription information of UE1 from the UDM, and based on the subscription information of UE1, determine whether to authorize UE1 as a UE reader / writer. The AMF can inform the AIOTF of the authorization result indication information of UE1.

[0340] As an optional embodiment 2, UE1 sends an AIOT radio resource request message to the gNB to request the gNB to allocate radio resources, such as A-interface resources, for AIOT services. The AIOT radio resource request message may carry the UE1 ID. Upon receiving the AIOT radio resource request message, the gNB determines whether to authorize UE1 as a UE reader / writer based on a pre-configured UE reader / writer list. The pre-configured UE reader / writer list includes UE IDs already authorized as UE readers / writers. This list is configured by the core network for the gNB. If the gNB determines whether to authorize UE1 as a UE reader / writer, it sends an AIOT radio resource response message to UE1. The AIOT radio resource response message may include authorization result indication information. If the authorization result indication information indicates that UE1 is authorized as a UE reader / writer, then the response message may also include radio resources allocated for the AIOT service; if the authorization result indication information indicates that UE1 is not authorized as a UE reader / writer, then the response message does not carry radio resources.

[0341] As an optional embodiment 3, UE1 sends an AIOT radio resource request message to the gNB to request the gNB to allocate radio resources, such as A-interface resources, for AIOT services. The AIOT radio resource request message may carry the UE1 ID, and optionally may also carry the UE1's AIOT capability information. Upon receiving the AIOT radio resource request message, the gNB sends an authorization request message to the AIOTF via an AIOT readercontrol layer message or via the AMF, carrying the UE1 ID. The AIOTF then determines whether to authorize UE1 as a UE reader (e.g., based on UE1's subscription information, a pre-configured UE reader list, or both UE1's subscription information and AIOT capability information). If the AIOTF determines whether to authorize UE1 as a UE reader, it sends an authorization response message to the gNB, and the gNB sends an AIOT radio resource response message to UE1. The AIoT radio resource response message may include authorization result indication information. If the authorization result indication information indicates that UE1 is authorized as a UE reader, then the response message may also include radio resources allocated for AIoT services. If the authorization result indication information indicates that UE1 is not authorized as a UE reader, then the response message does not carry radio resources.

[0342] Alternatively, upon receiving an AIoT radio resource request message, the gNB sends an authorization request message to the AMF. The AMF then determines whether to authorize UE1 as a UE reader based on UE1's subscription information or a pre-configured list of UE readers. If the AMF determines whether to authorize UE1 as a UE reader, it sends an authorization response message to the gNB, which in turn sends an AIOT radio resource response message to UE1. The AIOT radio resource response message may include authorization result indication information. If the authorization result indication information indicates that UE1 has been authorized as a UE reader, the response message may also include radio resources allocated for the AIoT service; if the authorization result indication information indicates that UE1 has not been authorized as a UE reader, the response message does not carry radio resources.

[0343] The pre-configured list of UE readers includes UE IDs that have been authorized as UE readers.

[0344] In Embodiments 2 and 3 above, UE1 sends an AIOT radio resource request message to gNB when it is located in a preset AIOT service area.

[0345] Optionally, for Embodiment 3 above, AIOTF or AMF may send a subscription information update request message to UDM to request UDM to update UE1's subscription information based on UE1's authorization result indication information.

[0346] As an optional embodiment 4, when UE1 is located in a preset AIoT service area, it sends a PDU session establishment request message to the UPF via the gNB to request the establishment of a PDU session for the AIoT service. This PDU session establishment request message also includes the UE1 ID and UE1's AIoT capability information, requesting a determination of whether to authorize UE1 as a UE reader during the PDU session establishment process. Upon receiving this PDU session establishment request message, the UPF sends a PDU session establishment request message to the specific DN (i.e., the DN corresponding to the AIoT service). During the PDU session establishment process, the AMF or AIOTF determines whether to authorize UE1 as a UE reader. If the AMF or AIOTF determines that UE1 is authorized as a UE reader, the PDU session is allowed to be established; if the AMF or AIOTF determines that UE1 is not authorized as a UE reader, the PDU session is not allowed to be established. The determination of whether the AMF or AIOTF authorizes UE1 as a UE reader can be found in the detailed description in the foregoing embodiments, and will not be repeated here.

[0347] Please see Figure 10 This is a flowchart illustrating another communication method provided in an embodiment of this application. The method may include, but is not limited to, the following steps:

[0348] 1001, UE1 sends the first message to the first core network element via gNB. Correspondingly, the first core network element receives the first message from UE1 via gNB.

[0349] The first message is used to request authorization for UE1 to act as a UE reader / writer. The first core network element can be an AMF or an AIOTF.

[0350] UE1 can send the first message to the AMF via the gNB. UE1 can also send the first message to the AIOTF via both the gNB and the AMF.

[0351] 1002, the first core network element obtains UE1's subscription information from the second core network element.

[0352] The second core network element can be a UDM and / or a UDR. UE1's subscription information can be found here. Figure 6A The specific description of it in the illustrated embodiment will not be repeated here.

[0353] In one implementation, the first message includes the AIOT capability information of UE1. In another implementation, the first message does not include the AIOT capability information of UE1, and the first core network element can obtain the AIOT capability information of UE1 from the second core network element.

[0354] 1003. The first core network element determines whether to authorize UE1 as a UE reader or writer based at least on UE1's subscription information.

[0355] In one implementation, the first core network element determines whether to authorize UE1 as a UE reader / writer based on UE1's subscription information. For example, if UE1's subscription information indicates that UE1 is allowed to act as a UE reader / writer, then AIOTF can authorize UE1 as a UE reader / writer. UE1's subscription information may include UE1's network registration status. For example, if UE1's subscription information indicates that UE1 is allowed to act as a UE reader / writer but UE1's network registration status is not registered with the network, then the first core network element can refuse to authorize UE1 as a UE reader / writer.

[0356] In another implementation, the first core network element determines whether to authorize UE1 as a UE reader / writer based on UE1's subscription information and UE1's AIoT capability information. For example, see the specific description of this method in step 606a, which will not be repeated here.

[0357] In another implementation, the first core network element determines whether to authorize UE1 as a UE reader / writer based on UE1's subscription information, the location information of the subscribed UEs, and UE1's AIoT capability information. For example, see the specific description of this method in step 904a, which will not be repeated here.

[0358] 1004, the first core network element sends a second message to UE1 via the gNB. Correspondingly, UE1 receives the second message from the first core network element via the gNB.

[0359] The second message includes the UE1 ID and authorization result indication information. The authorization result indication information can be found here. Figure 6A The specific description of the embodiments shown will not be repeated here. The AMF sending the second message to UE1 via the gNB can be that the AMF can send the second message to UE1 via the gNB. The AIOTF sending the second message to UE1 via the gNB can be that the AIOTF can send the second message to UE1 via both the AMF and the gNB.

[0360] For the first core network element to be AIOTF:

[0361] In one implementation, the first message sent by UE1 to AIOTF may include a registration request message sent by UE1 to AMF via gNB and an authorization request message sent by AMF to AIOTF; the second message sent by AIOTF to UE1 may include an authorization response message sent by AIOTF to AMF and a registration response message sent by AMF to UE1, i.e., steps 607a and 610a.

[0362] In another implementation, the first message sent by UE1 to AIOTF may include an AIOT reader authorization request message sent by UE1 to AMF via gNB, and an authorization request message sent by AMF to AIOTF; the second message sent by AIOTF to UE1 may include steps 905a and 906a.

[0363] For the first core network element being AMF:

[0364] In one implementation, UE1 sending the first message to AMF can be UE1 sending a registration request message to AMF via gNB, i.e., steps 601b and 602b; AMF sending the second message to UE1 can be AMF sending a registration response message to UE1 via gNB, i.e., step 608b.

[0365] In another implementation, the first message sent by UE1 to AMF may include an AIOT reader authorization request message sent by UE1 to AMF via gNB; the second message sent by AMF to UE1 may be an AIOT reader authorization response message sent by AMF to UE1.

[0366] exist Figure 10 In the embodiment shown, the first core network element determines whether to authorize UE1 as a UE reader / writer based on UE1's subscription information, which helps to improve the efficiency of AIoT service establishment.

[0367] This application provides a communication device that can be used to implement the functions of the first terminal device (i.e., UE1) or the first core network element (i.e., AMF or AIOTF). The communication device can be the first terminal device or the first core network element. The communication device includes units corresponding one-to-one with the methods / operations / steps / actions performed by the first terminal device or the first core network element in the above method embodiments. These units can be hardware circuits, software, or a combination of hardware circuits and software implementation. Please refer to... Figure 11 , Figure 11 A schematic diagram of a communication device 1100 according to an embodiment of this application is shown. The communication device 1100 may include an interface unit 1101 and a processing unit 1102. Specifically, the processing unit 1102 is used to process signaling and / or data, which may be data received by the interface unit 1101, and the processed signaling and / or data may also be sent by the interface unit 1101.

[0368] In one embodiment, when the communication device 1100 is a first core network element, wherein:

[0369] Interface unit 1101 is used to receive a first message from a first terminal device; wherein the first message includes the identifier of the first terminal device and is used to request authorization for the first terminal device to act as a reader / writer; and to obtain the subscription information of the first terminal device from the second core network element;

[0370] Processing unit 1102 is used to determine whether to authorize the first terminal device as a reader / writer based at least on the subscription information of the first terminal device; wherein the second core network element is a unified data management network element and / or a unified data storage network element;

[0371] The interface unit 1101 is also used to send a second message to the first terminal device via the base station; wherein the second message includes the identifier of the first terminal device and authorization result indication information, and the authorization result indication information is used to indicate that the first terminal device is authorized as a reader / writer.

[0372] Optionally, the authorization result indication information may also be used to indicate one or more of the following: authorization time information, authorization location information, and the binding relationship between the first terminal device and the application function network element.

[0373] Optionally, interface unit 1101 is further configured to send a subscription information update request message to the second core network element. The subscription information update request message includes authorization result indication information and is used to request the second core network element to update the subscription information of the first terminal device based on the authorization result indication information.

[0374] Optionally, the interface unit 1101 is also configured to send a first identifier list to the base station, the first identifier list including identifiers of terminal devices authorized as readers.

[0375] Optionally, the processing unit 1102 determines whether to authorize the first terminal device as a reader / writer based on the contract information of the first terminal device and the environmental IoT capability information of the first terminal device.

[0376] The environmental IoT capability information includes one or more of the following:

[0377] The environmental IoT service type, the effective time information of the first terminal device as a reader, the effective area information of the first terminal device as a reader, the binding relationship between the first terminal device and the application function network element, and the reader information of the first terminal device as a reader.

[0378] Optionally, the first message may also include information about the environmental IoT capabilities of the first terminal device.

[0379] Optionally, the first message may also include the location information of the first terminal device.

[0380] Optionally, the first core network element is the access and mobility management network element; the first message is the registration request message.

[0381] Optionally, the first message is an environmental IoT reader / writer authorization request message, and the first terminal device is located in a preset environmental IoT business area.

[0382] Optionally, the first message is a Protocol Data Unit (PDU) session request message, and the first terminal device is located in a preset IoT business area.

[0383] In this embodiment, the specific implementation of the interface unit 1101 and the processing unit 1102 can be found in the specific implementation steps of AMF or AIOTF in the foregoing embodiments, and will not be repeated here.

[0384] In another implementation, the Figure 11 When the communication device shown is the first terminal device, wherein:

[0385] Interface unit 1101 is used to send a first message to a first core network element via a base station; wherein the first message includes the identifier of a first terminal device and is used to request authorization for the first terminal device to be a reader / writer; and to receive a second message from the first core network element via the base station, the second message including the identifier of the first terminal device and authorization result indication information, the authorization result indication information being used to indicate that the first terminal device has been authorized to be a reader / writer.

[0386] Optionally, the authorization result indication information may also be used to indicate one or more of the following: authorization time information, authorization location information, and the binding relationship between the first terminal device and the application function network element.

[0387] Optionally, the first message may also include environmental IoT capability information of the first terminal device;

[0388] The environmental IoT capability information includes one or more of the following:

[0389] The environmental IoT service type, the effective time information of the first terminal device as a reader, the effective area information of the first terminal device as a reader, the binding relationship between the first terminal device and the application function network element, and the reader information of the first terminal device as a reader.

[0390] Optionally, the first message may also include the location information of the first terminal device.

[0391] Optionally, the first message is a registration request message.

[0392] Optionally, the interface unit 1101 is specifically used to send a first message to the first core network element via a base station in response to the first terminal device being located in a preset IoT service area.

[0393] Optionally, the first message is an environmental IoT reader / writer authorization request message.

[0394] Optionally, the first message is a Protocol Data Unit (PDU) session request message.

[0395] Optionally, the interface unit 1101 is further configured to respond to the first terminal device being located in a preset environmental IoT service area by sending an environmental IoT wireless resource request message to the base station via the base station, the environmental IoT wireless resource request message being used to request the base station to authorize the first terminal device as a reader / writer; and to receive an environmental IoT wireless resource response message from the base station, the environmental IoT wireless resource response message being used to indicate that the first terminal device has been authorized as a reader / writer.

[0396] Optionally, the environmental IoT radio resource response message is also used to indicate the environmental IoT radio resources allocated to the first terminal device.

[0397] In this embodiment, the specific implementation of the interface unit 1101 and the processing unit 1102 can be found in the specific implementation steps of UE1 in the foregoing embodiments, and will not be repeated here.

[0398] like Figure 12 The illustration shows a communication device 1200 provided in an embodiment of this application, used to implement the functions of the aforementioned first terminal device or first core network element. This device can be a communication device or a device used within a communication device. The communication device can be the first terminal device or the first core network element. The device used within the communication device can be a chip system or a chip within the communication device. The chip system can be composed of chips or can include chips and other discrete components.

[0399] The communication device 1200 includes at least one processor 1210 for implementing the processing functions of the device (e.g., a first terminal device or a first core network element) in the method provided in this application embodiment. The communication device 1200 may also include a communication interface 1220 for implementing the transmit and receive operations of the device (e.g., a first terminal device or a first core network element) in the method provided in this application embodiment. In this application embodiment, the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface for communicating with other devices via a transmission medium. For example, the communication interface 1220 enables the device in the communication device 1200 to communicate with other devices. The processor 1210 uses the communication interface 1220 to transmit and receive data and is used to implement the methods described in the above method embodiments.

[0400] The communication device 1200 may further include at least one memory 1230 for storing program instructions and / or data. The memory 1230 is coupled to the processor 1210. The coupling in this embodiment is an indirect coupling or communication connection between devices, units, or modules, and may be electrical, mechanical, or other forms, for information exchange between devices, units, or modules. The processor 1210 may operate in conjunction with the memory 1230. The processor 1210 may execute program instructions stored in the memory 1230. One or more memories may be included in the processor.

[0401] This application embodiment does not limit the specific connection medium between the communication interface 1220, processor 1210, and memory 1230. This application embodiment... Figure 12 The memory 1230, processor 1210, and communication interface 1220 are connected via a bus, and the bus is in... Figure 12 The connections between other components are shown in bold and are for illustrative purposes only, not as limiting information. The bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, Figure 12 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0402] When the communication device 1200 is specifically a device used for equipment (e.g., a first terminal device or a first core network element), for example, when the communication device 1200 is specifically a chip or chip system, the communication interface 1220 can output or receive baseband signals. When the communication device 1200 is specifically a device (e.g., a first terminal device or a first core network element), the communication interface 1220 can output or receive radio frequency signals. In the embodiments of this application, the processor can be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, which can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or being executed by a combination of hardware and software modules in the processor.

[0403] When the aforementioned communication device 1200 is a module applied to a base station, the base station module implements the functions of the base station in the above method embodiments. The base station module receives information from other modules (such as radio frequency modules or antennas) in the base station, which is information sent by the terminal to the base station; or, the base station module sends information to other modules (such as radio frequency modules or antennas) in the base station, which is information sent by the base station to the terminal. Here, the base station module can be a baseband chip of the base station, or a central unit (CU), distributed unit (DU), or other modules, or a device under an open RAN (O-RAN or ORAN) architecture, such as an open CU, open DU, etc.

[0404] It should be noted that the aforementioned communication interface 1220 can be used to execute the functions of the aforementioned interface unit 1101, and the aforementioned processor 1210 can be used to execute the functions of the aforementioned processing unit 1102, which will not be elaborated further here.

[0405] When the aforementioned communication device is a chip applied to the first terminal device, the chip implements the functions of the first terminal device in the above method embodiment, and the chip receives information from other devices; or, the chip sends information to other devices.

[0406] When the aforementioned communication device is a chip applied to a first core network element, the chip implements the functions of the first core network element in the above method embodiments. The chip receives information from other devices; or, the chip sends information to other devices.

[0407] It is understood that the processor in the embodiments of this application may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor may be a microprocessor or any conventional processor.

[0408] The method steps in the embodiments of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disks, portable hard disks, compact disc-ROMs (CD-ROMs), or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Furthermore, the ASIC can reside in a core network element or a terminal device. Alternatively, the processor and storage medium can exist as discrete components in a terminal or access network device.

[0409] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer program or instructions can be stored in a computer-readable storage medium or transmitted through the computer-readable storage medium. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video disk (DVD); or it can be a semiconductor medium, such as a solid-state drive (SSD).

[0410] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0411] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers described above does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

[0412] This application also provides a computer-readable storage medium storing computer-executable instructions. When the computer-executable instructions are executed, the method executed by the first terminal device or the first core network element in the above method embodiments is implemented.

[0413] This application also provides a computer program product, which includes a computer program that, when executed, enables the method executed by the first terminal device or the first core network element in the above method embodiments to be implemented.

[0414] This application also provides a communication system, which includes a first terminal device or a first core network element. Optionally, it further includes a second core network element and a base station. Each device is used to execute the methods executed by the devices in the above method embodiments.

[0415] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0416] The descriptions of the various embodiments provided in this application can be referenced mutually. Each embodiment has its own emphasis, and parts not described in detail in a certain embodiment can be referred to the relevant descriptions of other embodiments. For the sake of convenience and brevity, for example, the functions and execution steps of the various devices and equipment provided in the embodiments of this application can be referred to the relevant descriptions of the method embodiments of this application. The method embodiments and the device embodiments can also be referenced, combined or cited from each other.

[0417] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A communication method, characterized in that, The method is applied to a first core network element, and the method includes: Receive a first message from a first terminal device; wherein the first message includes the identifier of the first terminal device, and the first message is used to request authorization for the first terminal device to be a reader / writer; The system obtains the subscription information of the first terminal device from the second core network element, and determines whether to authorize the first terminal device as a reader or writer based at least on the subscription information of the first terminal device; wherein, the second core network element is a unified data management network element and / or a unified data storage network element; A second message is sent to the first terminal device via a base station; wherein the second message includes the identifier of the first terminal device and authorization result indication information, the authorization result indication information being used to indicate that the first terminal device is authorized as a reader / writer.

2. The method as described in claim 1, characterized in that, The authorization result indication information is also used to indicate one or more of the following: authorization time information, authorization location information, and the binding relationship between the first terminal device and the application function network element.

3. The method as described in claim 2, characterized in that, The method further includes: A subscription information update request message is sent to the second core network element. The subscription information update request message includes the authorization result indication information. The subscription information update request message is used to request the second core network element to update the subscription information of the first terminal device based on the authorization result indication information.

4. The method as described in claim 1, characterized in that, The method further includes: A first identifier list is sent to the base station, the first identifier list including identifiers of terminal devices authorized as readers.

5. The method according to any one of claims 1-4, characterized in that, The step of determining whether to authorize the first terminal device as a reader / writer, based at least on the subscription information of the first terminal device, includes: Based on the contract information of the first terminal device and the environmental IoT capability information of the first terminal device, determine whether to authorize the first terminal device as a reader / writer. The environmental IoT capability information includes one or more of the following: The environmental IoT service type, the effective time information of the first terminal device as a reader, the effective area information of the first terminal device as a reader, the binding relationship between the first terminal device and the application function network element, and the reader information of the first terminal device as a reader.

6. The method as described in claim 5, characterized in that, The first message also includes environmental IoT capability information of the first terminal device.

7. The method as described in claim 6, characterized in that, The first message also includes the location information of the first terminal device.

8. The method as described in claim 6, characterized in that, The first core network element is an access and mobility management network element; the first message is a registration request message.

9. The method as described in claim 6, characterized in that, The first message is an authorization request message for an environmental IoT reader / writer, and the first terminal device is located in a preset environmental IoT service area.

10. The method as described in claim 6, characterized in that, The first message is a Protocol Data Unit (PDU) session request message, and the first terminal device is located in a preset IoT service area.

11. A communication method, characterized in that, The method is applied to a first terminal device, and the method includes: A first message is sent to a first core network element via a base station; wherein, the first message includes the identifier of the first terminal device, and the first message is used to request authorization for the first terminal device to be a reader / writer; The base station receives a second message from the first core network element. The second message includes the identifier of the first terminal device and authorization result indication information. The authorization result indication information is used to indicate that the first terminal device is authorized as a reader / writer.

12. The method as described in claim 11, characterized in that, The authorization result indication information is also used to indicate one or more of the following: authorization time information, authorization location information, and the binding relationship between the first terminal device and the application function network element.

13. The method as described in claim 11, characterized in that, The first message also includes environmental IoT capability information of the first terminal device; The environmental IoT capability information includes one or more of the following: The environmental IoT service type, the effective time information of the first terminal device as a reader, the effective area information of the first terminal device as a reader, the binding relationship between the first terminal device and the application function network element, and the reader information of the first terminal device as a reader.

14. The method as described in claim 13, characterized in that, The first message also includes the location information of the first terminal device.

15. The method according to any one of claims 11-14, characterized in that, The first message is a registration request message.

16. The method according to any one of claims 11-14, characterized in that, The sending of the first message to the first core network element via the base station includes: In response to the first terminal device being located in a preset IoT service area, the first message is sent to the first core network element via a base station.

17. The method as described in claim 16, characterized in that, The first message is an authorization request message for an environmental IoT reader / writer.

18. The method as described in claim 16, characterized in that, The first message is a Protocol Data Unit (PDU) session request message.

19. The method as described in claim 11, characterized in that, The method further includes: In response to the first terminal device being located in a preset environmental IoT service area, an environmental IoT wireless resource request message is sent to the base station. The environmental IoT wireless resource request message is used to request the base station to authorize the first terminal device as a reader / writer. The first terminal device receives an Environmental IoT Radio Resource Response (IOR) message from the base station, the IOR message indicating that the first terminal device is authorized as a reader / writer.

20. The method as described in claim 19, characterized in that, The environmental IoT wireless resource response message is also used to indicate the environmental IoT wireless resources allocated to the first terminal device.

21. A communication system, characterized in that, The communication system includes a first core network element and a first terminal device, wherein the first core network element is used to implement the method as described in any one of claims 1-10, and the first terminal device is used to implement the method as described in any one of claims 11-20.

22. A communication device, characterized in that, The device includes a processor and an interface circuit. The interface circuit is used to receive signals from other communication devices besides the communication device and transmit them to the processor, or to send signals from the processor to other communication devices besides the communication device. The processor is used to implement the method as described in any one of claims 1-10, or the method as described in any one of claims 11-20, through logic circuits or execution code instructions.

23. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions, which, when executed by a communication device, implement the method as described in any one of claims 1-10; or the method as described in any one of claims 11-20.

Images