Information transmission method, data processing method and related communication device

Abstract

The embodiment of the invention discloses an information transmission method, and in the method, a paging mechanism of an RAN (Radio Access Network) for a terminal serving as a reader is designed. In the method, even if a first terminal serving as a target reader is in a non-connection state, the first terminal serving as the target reader can still initiate a connection establishment request through a paging message for the first terminal serving as the target reader to establish connection with an RAN (Radio Access Network), so that a service instruction is received; and executing a service operation on the Internet of Things equipment. Thus, when performing service transmission, the Internet of Things functional entity does not need to interact with core network elements such as an AMF, so that the first terminal serving as the target reader can send the service request to the RAN only after being in the connected state, the service request can be directly sent to the RAN, and then the RAN enables the first terminal to receive the service request, so that the service transmission efficiency is improved. Signaling interaction between the Internet of Things function entity and the AMF and other core network elements is reduced or even avoided, so that the signaling overhead is reduced, and the information transmission efficiency is improved.

Description

Technical Field

[0001] This application relates to the field of Internet of Things (IoT) technology, specifically to information transmission methods, data processing methods, and related communication devices. Background Technology

[0002] In IoT technologies such as ambient IoT (A-IoT), business operators such as servers can send business requests through the core network to IoT functional entities such as the ambient IoT management function (AIoTMF) entity, instructing terminals acting as readers to perform business operations on IoT devices.

[0003] After receiving a service request, the IoT functional entity can send service instructions to core network elements such as the access and mobility management function (AMF) of the service terminal. The AMF then sends the service instructions to the terminal via non-access-stratum (NAS) messages. Alternatively, the IoT functional entity can query the AMF for the terminal's connection status and then send service instructions to the RAN (radio access network). The RAN then sends service instructions to the terminal to instruct the terminal to perform service operations on the IoT device as a reader.

[0004] It is evident that in the current interaction process where IoT functional entities send business instructions to terminals acting as readers, signaling interaction with core network elements such as AMF is often required, resulting in high signaling overhead and low information transmission efficiency. Summary of the Invention

[0005] To address the aforementioned technical problems, embodiments of this application provide an information transmission method that can reduce or even avoid interaction between IoT functional entities and core network elements during service transmission, thereby reducing signaling overhead and improving information transmission efficiency. This application also provides corresponding apparatus, devices, computer-readable storage media, and computer program products.

[0006] Firstly, an information transmission method is provided. In this method, the RAN receives first information from an Internet of Things (IoT) functional entity, the first information indicating the execution of a service operation on an IoT device; then, if the RAN determines that a first terminal, acting as a target reader, is in a disconnected state, the RAN sends a paging message, the paging message including identification information, the terminal indicated by the identification information including the first terminal.

[0007] In the first aspect, a paging mechanism for terminals acting as readers by the RAN is designed. In this method, even if the first terminal acting as the target reader is in a disconnected state, a paging message can still be sent to the first terminal acting as the target reader to initiate a connection establishment request, thereby establishing a connection with the RAN, receiving service instructions, and executing service operations on IoT devices.

[0008] In this way, when IoT functional entities transmit services, they do not need to interact with core network elements such as AMF to send service requests to RAN only after the first terminal, which is the target reader, is in a connected state. Instead, they can send service requests directly to RAN, and RAN will then enable the first terminal to receive the service requests. This reduces or even avoids signaling interactions between IoT functional entities and core network elements such as AMF, thereby reducing signaling overhead and improving information transmission efficiency.

[0009] Furthermore, the paging mechanism in the first aspect differs from existing paging mechanisms. Traditional paging mechanisms typically carry a temporary terminal identifier or other terminal identifier to page a specific terminal, but cannot page the first terminal (target reader) and initiate connection establishment with a single paging. However, in some embodiments of this application, the RAN can page the first terminal (target reader) and initiate connection establishment with a single paging that carries a first identifier or other special identifier, resulting in higher paging efficiency and improved information exchange efficiency.

[0010] Furthermore, in some scenarios, when the RAN acts as a reader, the IoT functional entity can send service instructions to the RAN, typically without needing to interact with core network elements such as the AMF (Agency Filtering Function). Therefore, in the first aspect, when the terminal acts as a reader, the service transmission method of the IoT functional entity is the same. That is to say, the first approach allows the IoT functional entity cabinet to use the same service transmission method (i.e., sending service instructions to the RAN) when facing both types of readers—terminals acting as readers and the RAN acting as readers—and ensures the reliability of service transmission while reducing information interaction with core network elements such as the AMF (i.e., through the RAN's paging mechanism for terminals acting as readers, the first terminal acting as the target reader, which is in a disconnected state, is found and a connection is established to receive service instructions, ensuring the execution of service operations). In addition, the first approach is essentially consistent with the service instruction distribution method when the RAN acts as a reader, thus maximizing compatibility with two different reader types through a single architecture.

[0011] Furthermore, in many scenarios of the first aspect, since signaling interaction between IoT functional entities and core network elements such as AMF can be avoided, it is possible to deploy only IoT functional entities in the campus without deploying core network elements such as AMF, which facilitates the reduction of IoT deployment costs.

[0012] In one possible implementation of the first aspect, the identification information includes one or more of the following: target reader identifier, target reader group identifier, first identifier, and target location information, wherein the first identifier indicates any terminal with reader capability.

[0013] In one possible implementation of the first aspect, after the RAN determines that the first terminal, which is the target reader, is in a disconnected state and sends a paging message, the RAN further includes: receiving a connection establishment request from the first terminal, the connection establishment request being used to request the establishment of a connection between the first terminal and the RAN; and, if the RAN establishes a connection with the first terminal, sending second information to the first terminal, the second information instructing the first terminal to perform a service operation.

[0014] The paging mechanism in this possible implementation differs from existing paging mechanisms. Traditional paging mechanisms typically carry terminal identifiers such as temporary identifiers to page a specific terminal, but cannot page the first terminal (target reader) and initiate connection establishment with a single paging call. In this possible implementation, however, the RAN can page the first terminal (target reader) and initiate connection establishment with a single paging call carrying special identifiers such as a first identifier, resulting in higher paging efficiency and improved information exchange efficiency.

[0015] In one possible implementation of the first aspect, the method further includes: the RAN receiving third information, the third information including one or more of the following: a reader identifier corresponding to the first terminal, a reader group identifier corresponding to the first terminal, a second identifier corresponding to the first terminal, and location information of the first terminal, wherein the second identifier indicates that the terminal has reader capability; the RAN determining the first terminal as the target reader based on the third information.

[0016] In this possible implementation, the source of the third information and the timing of the RAN receiving the third information can be varied. For example, the RAN may determine the first terminal as the target reader based on the third information after receiving the first information and before sending the paging message; alternatively, the RAN may receive the third information and determine the first terminal as the target reader based on the third information after the first terminal initiates a connection establishment request to the RAN based on the paging message.

[0017] In one possible implementation of the first aspect, the first information further includes reader information indicating the target reader performing the business operation. The reader information includes one or more of the following: target reader identifier, target reader group identifier, first identifier, and target location information. The first identifier in the reader information indicates any terminal with reader capability.

[0018] In this possible implementation, the service requester can send a service request carrying reader information to the IoT functional entity, enabling the IoT functional entity to determine the reader information of the target reader for performing the service operation. Based on this, the first information can carry reader information indicating the target reader for performing the service operation, so that the RAN can determine the reader indicated by the service requester for performing the service operation based on this reader information.

[0019] In one possible implementation of the first aspect, the RAN determines the first terminal as the target reader based on the third information, including: the RAN determines the first terminal as the target reader by matching the third information with reader information.

[0020] In this possible implementation, if the reader identifier corresponding to the first terminal in the third information matches the target reader identifier in the first information, the reader group identifier corresponding to the first terminal matches the target reader group identifier in the first information, both the third information and the first information carry the first identifier, and the location information of the first terminal is located in one or more of the target locations indicated by the target location information in the first information, then the third information can be considered to match the reader information, thereby determining the first terminal as the target reader.

[0021] A second aspect of this application provides an information transmission method. In this method, a first terminal receives a paging message, the paging message including identification information, the identification information including one or more of the following: target reader identifier, target reader group identifier, first identifier, and target location information, wherein the first identifier indicates any terminal with reader capability; the first terminal initiates a connection establishment request to the RAN according to the paging message, the connection establishment request being used to request the establishment of a connection between the first terminal and the RAN.

[0022] In one possible implementation of the second aspect, before the first terminal receives the paging message, the method further includes: the first terminal receiving fourth information, the fourth information including one or more of the following: a reader identifier corresponding to the first terminal, a reader group identifier corresponding to the first terminal, a second identifier corresponding to the first terminal, and location information of the first terminal, wherein the second identifier indicates that the terminal has reader capability; the first terminal initiating a connection establishment request to the RAN based on the paging message, including: the first terminal initiating a connection establishment request to the RAN based on the matching of the fourth information with the identifier information.

[0023] In one possible implementation of the second aspect, after establishing the connection between the first terminal and the RAN, the method further includes: the first terminal receiving fifth information from the RAN, the fifth information indicating the execution of business operations on the Internet of Things device.

[0024] A third aspect of this application provides a data processing method. In this method, a first network device determines a first terminal as a reader; the first network device manages the connection state of the first terminal so that the first terminal is in a connected state.

[0025] In the third aspect, after the first terminal is determined to be a reader, the first network device can manage the connection status of the first terminal to ensure that the first terminal is in a connected state.

[0026] In this way, when IoT functional entities transmit services, they can directly send service requests to the first terminal through the RAN, without having to send service requests to the first terminal through core network elements such as AMF. This reduces or even avoids signaling interaction between IoT functional entities and core network elements such as AMF, thereby reducing signaling overhead and improving information transmission efficiency. In many cases, only IoT functional entities need to be deployed in the campus without deploying core network elements such as AMF, which helps to reduce the deployment cost of IoT.

[0027] In one possible implementation of the third aspect, when the first network device is a RAN, the first network device determines the first terminal as a reader, including: the RAN receiving sixth information from the AMF, the sixth information indicating that the first terminal is a reader.

[0028] In some possible implementations, the AMF can authorize the first terminal as a reader based on one or more of the reader identifier, reader group identifier, second identifier, and location information received from the first terminal during the first terminal's registration process, and / or subscription data about the first terminal received from the unified data management (UDM). After authorizing the first terminal as a reader, the AMF can send a sixth message to the RANRAN to indicate that the first terminal is acting as a reader. In one possible implementation, the sixth message may include one or more of the following: the first terminal's identifier (e.g., the first terminal's GPSI or SUPI), the reader identifier, the reader group identifier, the second identifier, the location information, the time information for acting as a reader, and the location information for acting as a reader. The time information indicates that the terminal can act as a reader when the time falls within a specified time period. The location information indicates that the terminal acts as a reader when it is located in a specific location (e.g., within a specific location area).

[0029] In one possible implementation of the third aspect, when the first network device is a RAN, the first network device manages the connection state of the first terminal so that the first terminal is in a connected state, including: when the first terminal is disconnected from the RAN, the RAN initiates a paging of the first terminal so that the first terminal can establish a connection with the RAN.

[0030] In this possible implementation, when the first network device is a RAN, one way to manage the connection status of the first terminal is for the RAN to detect that the connection of the first terminal has been interrupted and then initiate a paging process so that the first terminal can establish a connection with the RAN.

[0031] In one possible implementation of the third aspect, when the first network device is a RAN, the first network device manages the connection state of the first terminal so that the first terminal is in a connected state, including: the RAN sets the connection state parameters of the first terminal to a target state so that the first terminal maintains the connection with the RAN.

[0032] In this possible implementation, when the first network device is a RAN, one way to manage the connection state of the first terminal is to set parameters of the non-connection state, such as the RRC Inactive timer, so that the first terminal does not enter the non-connection state such as the RRC Inactive state as much as possible, thereby ensuring that the first terminal does not enter the RRC idle state.

[0033] In one possible implementation of the third aspect, when the first network device is an AMF, the first network device determines the first terminal as a reader, including: the AMF determines the first terminal as a reader based on seventh information from the first terminal and / or subscription data from the UDM, wherein the seventh information indicates that the first terminal is a reader.

[0034] In one possible implementation of the third aspect, when the first network device is an AMF, the first network device manages the connection state of the first terminal so that the first terminal is in a connected state, including: when receiving a release request from the RAN serving the first terminal, the AMF rejects the release request, which is used to request the release of the connection between the first terminal and the AMF.

[0035] In this possible implementation, when the first network device is an AMF, one way to manage the connection state of the first terminal is for the AMF to refuse the first terminal from entering the CM idle state.

[0036] In one possible implementation of the third aspect, when the first network device is an AMF, the first network device manages the connection state of the first terminal so that the first terminal is in a connected state, including: after disconnecting the connection between the first terminal and the AMF, the AMF sends a paging message to the RAN, the paging message instructing the first terminal to be paged so that the first terminal can establish a connection with the AMF.

[0037] In this possible implementation, when the first network device is an AMF, one way to manage the connection status of the first terminal is to have the AMF trigger a paging process after the first terminal enters the CM idle state so that the first terminal can establish a connection with the AMF.

[0038] In one possible implementation of the third aspect, when the first network device is an Internet of Things (IoT) functional entity, the first network device determines the first terminal as a reader, including: the IoT functional entity sending a subscription request to the UDM or AMF, the subscription request indicating the subscription to the status information of the first terminal as a reader, the status information including one or more of the statuses such as registration status and connection status; the IoT functional entity receiving a first status notification from the UDM or AMF, the first status notification indicating that the first terminal as a reader is in a registered state and / or a connected state.

[0039] In this possible implementation, the subscription request can be directed only to the first terminal (i.e., only to the first terminal's status information) or to all terminals acting as readers, including the first terminal.

[0040] In one possible implementation of the third aspect, when the first network device is an Internet of Things (IoT) functional entity, the first network device manages the connection state of the first terminal to ensure that the first terminal is in a connected state, including: the IoT functional entity receiving a second status notification from a UDM or an AMF, the second status notification indicating that the first terminal is in an idle state; the IoT functional entity instructing the UDM or the AMF serving the first terminal to initiate a paging process to ensure that the first terminal enters a connected state.

[0041] In one possible implementation, the UDM can subscribe to the status information of the first terminal acting as a reader from the AMF, and then the IoT functional entity can subscribe to the status information of the first terminal acting as a reader from the UDM; in this case, the IoT functional entity can receive a second status notification from the UDM. Alternatively, in another example, if the IoT functional entity obtains the AMF information (e.g., AMF ID) of the first terminal acting as a reader, the IoT functional entity can also subscribe to the status information of the first terminal acting as a reader from the AMF; in this case, the IoT functional entity receives a second status notification from the AMF.

[0042] In this way, the terminal's status information can be subscribed to through AMF before the service arrives, thereby enabling the terminal's status management. This allows the first terminal, acting as the reader, to remain connected, reducing signaling overhead during service transmission and improving transmission efficiency.

[0043] In one possible implementation of the third aspect, when the first network device is a UDM, the first network device determines the first terminal as a reader by: the UDM determining the first terminal as a reader based on the first terminal's subscription data, the eighth information from the AMF, or the ninth information from the service requester, wherein the eighth information indicates that the first terminal is authorized to be a reader, and the ninth information indicates that the first terminal is a reader.

[0044] In one possible implementation of the third aspect, when the first network device is a UDM, the first network device manages the connection state of the first terminal so that the first terminal is in a connected state, including: the UDM receiving a third status notification from the AMF serving the first terminal, the third status notification indicating that the first terminal is in an idle state; the UDM sending paging indication information to the AMF, the paging indication information instructing the AMF to page the first terminal so that the first terminal enters the connected state.

[0045] In this possible implementation, the terminal's status information can be subscribed to via UDM before the service arrives to achieve terminal status management, thereby keeping the first terminal, which acts as the reader, connected, thus reducing signaling overhead during service transmission and improving transmission efficiency.

[0046] In one possible implementation of the third aspect, the first network device manages the connection state of the first terminal to ensure that the first terminal is in a connected state, including: the first network device managing the connection state of the first terminal to ensure that the first terminal is in a connected state when it determines that the first terminal is located at a first location, the current time is within a specified time period, and / or the first network device receives target mode information sent by the first terminal, wherein the target mode information indicates that the first terminal is in a mode that can be used as a reader.

[0047] In this possible implementation, after determining that the first terminal is a reader, the first network device may consider that the connection status of the first terminal needs to be managed if it determines that the first terminal is located at a first location, the current time is within a specified time period, and / or the first network device receives target mode information sent by the first terminal. In this way, the function of managing the connection status of the first terminal can be enabled, so that the function can be activated only when needed, thereby reducing unnecessary energy consumption.

[0048] A fourth aspect of this application provides a communication device. This device has the function of implementing the method of the first aspect or any possible implementation thereof, or the function of implementing the method of the second aspect or any possible implementation thereof, or the function of implementing the method of the third aspect or any possible implementation thereof. This function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions, such as a transmitting module, a processing module, or a receiving module.

[0049] The fifth aspect of this application provides a communication device, which includes a processor and an interface circuit. The interface circuit is used to receive signals from other communication devices and transmit them to the processor or to send signals from the processor to other communication devices. The processor is used to implement the function of the method of the first aspect or any possible implementation of the first aspect through logic circuits or execution code instructions, or to implement the function of the method of the second aspect or any possible implementation of the second aspect, or to implement the function of the method of the third aspect or any possible implementation of the third aspect.

[0050] The sixth aspect of this application provides a computer-readable storage medium storing one or more computer-executable instructions, wherein when the computer-executable instructions are executed by a processor, the processor executes a method as described in the first aspect or any possible implementation thereof, or a method as described in the second aspect or any possible implementation thereof, or a method as described in the third aspect or any possible implementation thereof.

[0051] The seventh aspect of this application provides a computer program product storing one or more computer-executable instructions, wherein when the computer-executable instructions are executed by a processor, the processor executes a method as described in the first aspect or any possible implementation thereof, or a method as described in the second aspect or any possible implementation thereof, or a method as described in the third aspect or any possible implementation thereof.

[0052] An eighth aspect of this application provides a chip system including a processor for supporting a communication device in implementing the functions involved in the first aspect or any possible implementation of the first aspect, or in implementing the functions involved in the second aspect or any possible implementation of the second aspect, or in implementing the methods of the third aspect or any possible implementation of the third aspect. In one possible design, the chip system may further include a memory for storing necessary program instructions and data. This chip system may be composed of chips or may include chips and other discrete devices.

[0053] The technical effects of aspects four through eight, or any of their possible implementations, can be found in the first aspect or the technical effects of its related possible implementations, and will not be repeated here. Attached Figure Description

[0054] Figure 1 This is an exemplary schematic diagram of the communication system provided in an embodiment of this application;

[0055] Figure 2 This is a schematic diagram of an embodiment of the information transmission method provided in this application;

[0056] Figure 3 This is an exemplary flowchart provided in an embodiment of this application;

[0057] Figure 4 This is a schematic diagram of an embodiment of the data processing method provided in this application;

[0058] Figure 5 This is an exemplary flowchart provided in an embodiment of this application;

[0059] Figure 6 This is an exemplary flowchart provided in an embodiment of this application;

[0060] Figure 7 This is a schematic diagram of an embodiment of the communication device provided in this application;

[0061] Figure 8 This is a schematic diagram of an embodiment of the communication device provided in this application;

[0062] Figure 9 This is a schematic diagram of an embodiment of the communication device provided in this application;

[0063] Figure 10 This is a schematic diagram of an embodiment of the communication device provided in this application. Detailed Implementation

[0064] The embodiments of this application are described below with reference to the accompanying drawings. The terminology used in the implementation section of this application is for explaining specific embodiments only and is not intended to limit the scope of this application.

[0065] As will be known to those skilled in the art, with the development of technology and the emergence of new scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0066] In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: 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. The terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate; this is merely a way of distinguishing objects with the same attributes in the embodiments of this application. Furthermore, the terms “comprising” and “having”, and any variations thereof, are intended to cover non-exclusive inclusion, such that a process, method, system, product, or apparatus that comprises a series of units is not necessarily limited to those units, but may include other units not expressly listed or inherent to those processes, methods, products, or apparatus.

[0067] First, the concepts involved in this application will be introduced.

[0068] 1. Ambient Internet of Things (A-IoT)

[0069] The Environmental Internet of Things (IoT), also known as ambient power-enabled IoT or passive IoT (P-IoT), includes nodes that can be passive. These passive nodes do not have their own power source (such as batteries) and instead obtain energy from the environment to support data sensing, transmission, and distributed computing. The method by which passive nodes obtain energy is not limited; for example, they can obtain energy from solar, radio frequency, wind, hydro, or tidal sources. Furthermore, passive nodes can store the obtained energy.

[0070] An environmental IoT architecture can include IoT devices, readers, IoT functional entities, and business requesters (such as application functions (AF)).

[0071] The IoT device can be in the form of a sensor, a tag, or any other terminal; there are no restrictions. The reader can be an access network device, such as a base station, pole station, micro base station, macro station, etc.; or, the reader can be a terminal device, such as a mobile phone, IoT device, handheld reader, etc.

[0072] It is evident that communication between IoT devices and readers is frequently involved in IoT architectures such as the Internet of Things (IoT) for the environment.

[0073] 2. Reader

[0074] The reader interacts with IoT devices (hereinafter, exemplified by tags) via radio frequency signals or wireless signals. It should be understood that this application does not limit the name of the reader; it can also be named a reader-writer or other names. The reader described here may possess the functions described in this application, such as the ability to perform business operations on IoT devices (which may be tags) (e.g., acquiring tag information, inventory operations, read operations, write operations, expiration operations, or message interaction with tags), acquire billing-related information and / or billing information, and send billing information to the converged charging function (CHF).

[0075] In one possible implementation, the reader can send business requests from a business operator, such as a server or application function, to the tag, or the reader can send messages from the tag to the business operator. In another possible implementation, the reader can retrieve information stored in a specified tag based on a business request from the business operator. For example, if the business request indicates an inventory operation (or stocktaking operation), the reader retrieves the tag's identification information, which can be a unique identifier or a temporary identifier. If the business request indicates a read operation, the reader reads data from the tag's storage space. Exemplarily, in application scenarios where information stored in the tag needs to be rewritten, the reader can also have a write function; for example, if the business request indicates a write operation, the reader writes data to the tag's storage space. In addition, the reader can also perform an invalidation operation on the tag. After an invalidation operation is performed, the tag becomes invalid and cannot be used for business operations such as retrieving tag information, inventory operations, read operations, message interaction with the tag, or write operations. In one possible implementation, "tag failure prevents the acquisition of tag information" can be understood as the reader being unable to obtain the tag information of the failed tag after it fails. In another possible implementation, "tag failure prevents the execution of tag message interaction operations" can be understood as the reader being unable to interact with the failed tag after it fails. The reader can take many forms; for example, it can be a terminal (e.g., user equipment (UE)), or a RAN, pole station, eNodeB, gNodeB, integrated access and backhaul (IAB) node, etc. This application does not limit the form of the reader.

[0076] The reader can operate in two ways: one is that when the tag enters the reader's effective identification range, it receives the radio frequency signal emitted by the reader and uses the energy obtained by the induced current to emit the information stored in the chip (corresponding to passive tags, or to passive communication / backscatter communication methods); the other is that the tag can store some electrical energy through solar energy or other means, enabling it to actively transmit a signal of a certain frequency (this type of tag can be called a semi-passive or semi-active tag). After the reader receives and decodes the information, it sends it to the central information system for relevant data processing.

[0077] Readers and IoT devices can be widely used in various application fields. For example, they can be used for the management of warehouses, transportation, and the collection and query of materials in logistics processes. They can also be used for the management of fixed assets in application scenarios with large assets or valuable items, such as libraries and museums. This application does not limit the specific application fields of readers and IoT devices.

[0078] 3. Terminal connection status

[0079] In this application, the connection status of the terminal is used to describe whether the terminal is connected to the network.

[0080] Taking 5G mobile communication systems as an example, there are two main connection states between terminals and networks: connection management states (CM states) corresponding to the core network and radio resource control states (RRC states) corresponding to the access network.

[0081] The CM state includes the CM-CONNECTED state and the CM-IDLE state, and the RRC state includes the RRC-CONNECTED state, the RRC-Inactive state, and the RRC-IDLE state.

[0082] The following section describes the transitions of the terminal's CM state.

[0083] After the terminal establishes an RRC connection with the RAN, the terminal enters the RRC connected state (RRC_CONNECTED). At this time, the terminal maintains an AN signaling connection with the RAN. When the terminal sends an initial NAS message to the AMF of the core network through the RAN (i.e., sends the NAS message through the RRCSetupComplete message), the terminal enters the RRC_CONNECTED CM-CONNECTED state.

[0084] When the terminal releases the AN signal connection with the RAN and disconnects the RRC connection, it enters the RRC-IDLE state. At this time, the terminal will also enter the CM-IDLE state.

[0085] Correspondingly, AMF will also perform CM state management on the terminal.

[0086] Specifically, when the RAN of the serving terminal establishes an N2 context with the AMF (for example, when the terminal initiates a registration request, the AMF establishes an N2 context with the RAN through a security authentication process), the AMF considers the terminal to have entered the CM connection state.

[0087] When the RAN and AMF release the N2 context of the terminal under certain circumstances (such as when the terminal releases the AN connection with the RAN), the AMF considers the terminal to have entered the CM idle state.

[0088] RRC Inactive is a new RRC state added in 5G, designed to allow terminals to quickly return to RRC Connected state without needing to reconnect. Similar to RRC Idle, RRC Inactive terminals can only receive content from the common search space (e.g., paging, broadcasts, 5G core network paging), and can perform cell reselection, with the same principles as RRC Idle.

[0089] However, unlike the RRC idle state, when the terminal is in the RRC Inactive state, the terminal's CM state is still the CM connected state (CM-CONNECTED).

[0090] It is understandable that when the terminal's CM state is CM connected, the terminal's RRC state may be RRC connected or RRC inactive. That is, the terminal's RRC state entering the RRC inactive state will not cause the CM state to enter the CM idle state. On the other hand, when the terminal's CM state is CM idle, the terminal's RRC state is also RRC idle. In other words, the terminal's RRC state entering the RRC idle state will cause the terminal's CM state to enter the CM idle state.

[0091] It is evident that keeping the terminal's CM state in the CM connected state prevents the terminal's RRC state from entering the RRC idle state, but it can enter the RRC inactive state.

[0092] In this application, the connection state of the terminal includes a connected state and a disconnected state. In a 5G mobile communication system, the terminal being in a disconnected state can be one or more of the following: RRC idle state, RRC inactive state, and CM idle state, while the terminal being in a connected state can be the terminal being in an RRC connected state and / or a CM connected state. In other types of communication systems (e.g., future communication systems), the connection state and disconnected state of the terminal can also be described by other states, and no limitation is made here.

[0093] The communication system involved in the embodiments of this application will be described below.

[0094] The specific type of this communication system can vary and is not limited here. For example, this communication system can be applied to 5G mobile communication systems, as well as 4G mobile communication systems, 6G mobile communication systems, or other types of communication systems.

[0095] The communication system may include IoT functional entities, RAN and terminals, and may also include one or more core network elements such as AMF (access and mobility management function) and UDM (unified data management). Figure 1 Only one exemplary communication system is shown; other possible communication systems in various scenarios may include those with... Figure 1 The communication system shown has different devices, and may include more than Figure 1 The communication system shown may have more or fewer devices.

[0096] The following sections will introduce each of the devices that may be involved in the communication system.

[0097] 1. RAN

[0098] RAN is an access device that enables terminals to wirelessly access a communication system. RAN can be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next-generation NodeB (gNB) in a 5G mobile communication system, a next-generation base station in a 6G mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system; it can also be a module or unit that performs some of the functions of a base station, for example, it can be a central unit (CU) or a distributed unit (DU). The CU here performs the functions of the radio resource control protocol and packet data convergence protocol (PDCP) of the base station, and can also perform the functions of the service data adaptation protocol (SDAP). The DU performs the functions of the radio link control layer and medium access control (MAC) layer of the base station, and can also perform some or all of the physical layer functions. For specific descriptions of the above-mentioned protocol layers, please refer to the relevant technical specifications of the 3rd Generation Partnership Project (3GPP). The RAN can be a macro base station, a micro base station, an indoor station, a relay node, or a donor node, etc. The embodiments of this application do not limit the specific technology and equipment form used in the RAN. For ease of description, the base station is used as an example of the RAN in the following description.

[0099] 2. Terminal

[0100] A terminal is a device with wireless transceiver capabilities, capable of sending signals to or receiving signals from a base station. Terminals can also be called terminal equipment, user equipment (UE), mobile station, mobile terminal, etc. Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, etc. Terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, airplanes, ships, robots, robotic arms, smart home devices, etc. The embodiments of this application do not limit the specific technology or device form used in the terminal.

[0101] In this embodiment, the terminal can function as a reader and perform business operations on IoT devices.

[0102] 3. Internet of Things (IoT) functional entities

[0103] An IoT functional entity can be considered an entity responsible for IoT management functions or environmental IoT management functions. For example, an IoT functional entity may have one or more of the following capabilities: transmission of business data from IoT devices, management of IoT devices, security procedures for IoT devices, business operations as instructed by a business requester, and instructing a reader to perform IoT business operations, etc.

[0104] The names of IoT functional entities can take many forms. For example, IoT functional entities can be Ambient IoT Function (AIoTF), Ambient IoT Management Function (AIoTMF), IoT Device Management Function (IDMF), IoT Management Function (IMF), Tag Management Function (TMF), etc. This application does not limit the naming of IoT functional entities; other names are allowed.

[0105] 4. Requesting Party

[0106] The party requesting the service can also be called the party requesting the operation or a third party.

[0107] In this embodiment, the service requester can be understood as a device that sends a service request to request the execution of a service operation. For example, the service requester can be a server, a passive IoT server (P-IoT server), an application function, or a device requesting a service. The service requester can correspond to a designated user. For example, the designated user can include an enterprise, tenant, third party, or company, without limitation. The fact that the service requester corresponds to a designated user can be understood as the service requester belonging to and being managed by that designated user.

[0108] 5. Access and Mobility Management Function (AMF)

[0109] Access and Mobility Management (AMF), also known as AMF device, AMF entity, AMF network element, mobility management device, mobility management network element, or mobility management entity, is a type of core network equipment. AMF is used to control terminal access and manage mobility. In practical applications, AMF can include the AMF within the Mobility Management Entity (MME) in the Long Term Evolution (LTE) network framework, and also incorporates access management functions. Specifically, it can be responsible for terminal registration, mobility management, tracking area update procedures, reachability detection, selection of session management network elements, and mobility state transition management. For example, in 5G networks, the AMF network element can be an AMF network element, which can provide Namf services. Namf services can include transmitting N1 and / or N2 information through the AMF, and subscribing to AMF state change notifications. In future communications, such as 6G, the AMF network element may still be an AMF network element, or it may have other names. In this application, for ease of description, the Access and Mobility Management Function is referred to as AMF. In other communication systems, the Access and Mobility Management Function may also have other names, and this application does not limit it.

[0110] 6. Unified Data Management (UDM)

[0111] Unified data management can also be referred to as UDM, UDM device, UDM network element, data management device, UDM entity, etc. Unified data management is used to handle one or more functions such as terminal identification, access authentication, registration, and mobility management. In 5G communication systems, unified data management can be either unified data management (UDM) or a UDM device. In future communication systems, UDM may have other names. For ease of description in this embodiment, unified data management is referred to as UDM. In other communication systems, unified data management may have other names, and this embodiment does not limit this. UDM can be a core network device. UDM can be a control plane device.

[0112] In addition, in some examples, the communication system may also include one or more existing or future network elements such as user plane function (UPF) network elements (also known as user plane equipment), session management function (SMF) (also known as session management equipment), user data repository (UDR) (also known as user database equipment, user database entity, user database network element), and policy control equipment (such as policy control function, PCF), which will not be listed in this application.

[0113] The following is based on Figure 1 Taking the exemplary communication system shown as an example, the interaction process that may be involved in the communication system will be introduced in an exemplary manner.

[0114] like Figure 1 In the example shown, in this exemplary communication system, the IoT functional entity can receive business requests from the business requester.

[0115] There are several ways for the business requester to send business requests to the IoT functional entity, which are not limited here.

[0116] In some examples, the requester can send the request directly to the IoT functional entity.

[0117] In other examples, the requesting party can send service requests to IoT functional entities through a control plane device. Exemplarily, this control plane device can be a network exposure function (NEF), session management function (SMF), policy control function (PCF), unified data management (UDM), or a network slice-specific and SNPN authentication and authorization function (NSSAAF). Figure 1 In the example shown, the requester can send a service request to the IoT functional entity through NEF.

[0118] Furthermore, in some other examples, the requesting party can also send service requests to the IoT function entity through the user plane channel. For example, the requesting party can send service requests to the IoT function entity through the user plane function (UPF) or SMF.

[0119] After receiving a service request, an IoT functional entity can send the request to the reader. Depending on the different forms of readers in real-world applications, the way the IoT functional entity sends the service request can vary; that is, different forms of readers correspond to different communication system architectures.

[0120] like Figure 1 The examples shown illustrate the different communication system architectures corresponding to different types of readers.

[0121] The following examples, using the reader as the RAN and the reader as the terminal, illustrate how IoT functional entities send service requests to the reader.

[0122] exist Figure 1 In the example shown, when such as RAN acts as a reader, IoT functional entities (e.g., AIoTMF) can have a direct communication interface with RAN (e.g., an interface called the AIoT NG Interface Protocol (NGAP)).

[0123] In this way, after an IoT functional entity obtains a service request (such as an inventory request) from a service requester through NEF, it can select the RAN corresponding to the service request based on the interaction with the UDM, and then send a service instruction to the RAN as a reader to instruct the RAN to perform the service operation as a reader.

[0124] When the reader is a terminal, the terminal itself can access the network as a 3GPP UE, so there will be an AMF serving the terminal.

[0125] The IoT functional entity has the ability to process service requests from the service requester and to execute service request authorization. In order to be compatible with scenarios where the reader is the terminal and the reader is the RAN, the IoT functional entity can send service requests to the terminal acting as the reader in two possible ways: one is that the IoT functional entity sends the service instruction corresponding to the service request through the AMF of the service terminal. For example, the IoT functional entity sends the service instruction to the AMF of the service terminal, and the AMF sends the service instruction to the terminal through the NAS message of the terminal; the other is that the IoT functional entity directly sends the service instruction through the RAN of the service terminal.

[0126] Of these two possible approaches, the first requires the IoT functional entity to communicate with the AMF (Access Controller Function) of the service terminal each time, and the IoT functional entity needs to pre-select specific terminals as readers, so that the AMF can determine which terminals should be sent as readers. In the second approach, when sending service instructions, the IoT functional entity only needs to send the service instructions to the RAN (Radio Range), and the RAN can determine which terminals should be sent as readers to receive the service instructions. However, the latter approach requires the terminal's connection status to be either RRC Inactive or RRC Connected and CM Connected before the IoT functional entity can directly send service instructions to the RAN. If the terminal is in CM Idle, the IoT functional entity, without being aware of the terminal's connection status, may send service instructions directly to the RAN, potentially failing to deliver the instructions to the terminals acting as readers. Therefore, to avoid this situation, the IoT functional entity needs to query the AMF for the terminal's connection status before sending the service instruction to the RAN each time. In other words, IoT functional entities cannot interact in the latter possible way mentioned above. That is to say, IoT functional entities cannot send service instructions directly to the RAN without interacting with the core network equipment. Instead, they need to increase the signaling overhead (increase the signaling for the interaction between the IoT functional entity and the AMF) before sending service instructions to the RAN.

[0127] It is evident that in many scenarios, the interaction process in which IoT functional entities send business instructions to terminals acting as readers often requires signaling interaction with core network elements such as AMF, resulting in high signaling overhead and low information transmission efficiency.

[0128] Based on this, the embodiments of this application propose a management scheme for the connection status of the terminal, which reduces or even avoids the interaction between IoT functional entities and core network elements such as AMF during service transmission, thereby reducing signaling overhead and improving information transmission efficiency.

[0129] Specifically, the embodiments of this application may include two management schemes for the connection status of the terminal, which will be described by way of example through two embodiments below.

[0130] Example 1:

[0131] In this embodiment, a paging mechanism is designed for the RAN to target terminals acting as readers. In this scheme, even if the first terminal acting as the target reader is in a non-connected state such as RRC Inactive or RRC Idle, a paging message can still be sent to the first terminal acting as the target reader to initiate a connection establishment request, thereby establishing a connection with the RAN, receiving service instructions, and executing service operations on IoT devices.

[0132] like Figure 2 As shown, based on the above communication system, the information transmission method of this application embodiment includes steps 201-202, and in some examples, steps 203-206 are also included.

[0133] Step 201: The RAN receives the first information from the IoT functional entity.

[0134] The first information indicates the execution of business operations for IoT devices.

[0135] In this embodiment, the IoT functional entity can send first information to the RAN based on a service request from a service requester. The method by which the service requester sends the service request to the IoT functional entity can be referred to... Figure 1 The details of how the business requester sends business requests to the IoT functional entity in the example shown will not be repeated here.

[0136] The first message indicates the execution of business operations on the IoT device. The number of IoT devices can be one or more, and there is no limit to this.

[0137] The specific type and content of this business operation can vary and are not limited here. For example, this business operation may include one or more of the following operations:

[0138] (1) Inventory Operation: Also known as inventory check. When an inventory operation is instructed to be performed, the reader obtains the identification information of the IoT devices; this identification information can be a unique identifier of the IoT device or a temporary identifier of the IoT device. Furthermore, in some examples, the inventory operation may also include an inventory operation for all IoT devices, i.e., obtaining the identifiers of IoT devices within the reader's coverage area. It is understood that specific naming can be used to distinguish the above-mentioned inventory operation, such as calling it an inventory operation for all IoT devices or an unrestricted inventory operation; or, when the scope of IoT device identifiers in the above-mentioned inventory operation is not limited, it can be understood that the inventory operation is to obtain the identifiers of IoT devices within the reader's coverage area.

[0139] (2) Read operation: Reading data from IoT devices. IoT devices can have storage capabilities, and their storage space can store data. If a service requester requests to perform a read operation on an IoT device, it can send a service request to the network instructing the IoT device to perform a read operation. The network sends a read command to the reader, and the reader sends a read operation to the IoT device, reading the data from the IoT device's storage space and sending the data back to the service requester through the network.

[0140] (3) Write operation: This involves writing data to the IoT device. The requesting party can send a write command to the reader, which then performs the write operation on the IoT device, writing data into the device's storage space. Alternatively, if the requesting party requests a write operation on the IoT device, it can send a request to the network instructing the network to perform the write operation. The network then sends a write command to the reader, which in turn sends a write command to the IoT device, reads data from the device's storage space, and sends the data back to the requesting party via the network.

[0141] (4) Disabling or deactivation (e.g., disable or kill): This disables the IoT device. The requesting party can send a service request to the network instructing the IoT device to be disabled. The network sends a disable command to the reader, which may include the identification information of the IoT device (i.e., the identifier of the IoT device to be disabled). The reader performs the disable operation on the IoT device according to the disable command. After the disable operation is completed, the IoT device will be disabled and cannot be inventoried or subjected to other operations.

[0142] (5) Obtaining IoT device information. In one possible implementation, the reader obtains or receives IoT device information sent by the IoT device. The reader then sends the IoT device information to the service requester or the core network device. In another possible implementation, before obtaining the IoT device information sent by the IoT device, the reader may receive a service instruction and send the service instruction to the IoT device; the service instruction may come from the service requester or from the core network device, and this application does not impose any restrictions. For example, the IoT device information may include IoT device identification information and / or information stored by the IoT device.

[0143] (6) Message interaction with IoT devices. In one possible implementation, the reader sends a message from the service requester to the IoT device. In another possible implementation, the reader receives a message from the IoT device and sends a message from the IoT device to the service requester. In yet another possible implementation, the reader can interact with the IoT device by exchanging messages, such as exchanging random numbers, before receiving a message from the IoT device.

[0144] (7) Sending payload to the IoT device. In one possible implementation, the service requester can send the payload to the IoT device through a reader. After receiving the payload from the service requester, the reader sends the payload to the IoT device. In another possible implementation, the core network device can send the payload to the IoT device through a reader. After receiving the payload from the core network device, the reader sends the payload to the IoT device. For example, the payload can be instructions sent by the core network device or the service requester to the IoT device, data written by the core network device or the service requester to the IoT device, application layer information sent by the core network device or the service requester to the IoT device, etc., or the payload can be other information related to the IoT device, which is not limited in this application.

[0145] (8) Location Operation: Locating or acquiring the location information of IoT devices. In one possible implementation, the acquired location information may include one or more of the following: coordinates, latitude and longitude, cell identifier, tracking area identifier, network identifier, etc. In another possible implementation, the location operation may include the IoT device sending a signal for performing location, the reader receiving the signal to perform location, or receiving the signal and sending it to a device that performs location calculation (e.g., a location management function, LMF) to perform location calculation.

[0146] It is understood that the business operation indicated by the first information may include a combination of one or more of the aforementioned business operations, or other existing or subsequently developed operations, without limitation. For example, in one example, the business operation indicated by the first information may include an inventory operation; while in another example, the business operation indicated by the first information may include multiple operations executed sequentially, such as an inventory operation, and subsequent operations on the IoT devices obtained from the inventory operation (e.g., one or more of read operations, write operations, etc.).

[0147] Furthermore, in this embodiment, when the first information indicates the execution of a business operation on an IoT device, the first information may or may not carry information about the IoT device. For example, if the business operation is an inventory operation, indicating an inventory of IoT devices within the RAN's coverage area (i.e., indicating the acquisition of the identifiers of IoT devices within the RAN's coverage area), then the first information may not carry information about the IoT device. Alternatively, if the business operation follows the inventory operation, then the first information may carry IoT device information such as the identifier of the IoT device to point to a specific IoT device. For example, after the inventory operation, the business operation may be performing a write operation or a read operation on the specified IoT device.

[0148] Step 202: If the RAN determines that the first terminal, which is the target reader, is in a disconnected state, it sends a paging message.

[0149] The paging message includes identification information, and the terminal indicated by the identification information includes the first terminal.

[0150] In this embodiment of the application, the target reader is used to perform business operations on the Internet of Things (IoT) device. At this time, the IoT device can be considered as a tag, and the target reader can be considered as the reader corresponding to the IoT device.

[0151] The target reader and the first terminal that serves as the target reader can be of various types.

[0152] In some examples, the target reader can be a terminal with reader capabilities. In this example, the target reader may not need to be represented by a target reader identifier; or, the target reader may be represented by a first identifier, which indicates any terminal with reader capabilities as the target reader. For example, if the service request sent by the application requesting party to the AMF does not carry target reader information, then any terminal with reader capabilities is indicated as the target reader. Based on this, the first information sent by the AMF to the RAN may carry a first terminal to indicate any terminal with reader capabilities as the target reader; or, the first information sent by the AMF to the RAN may not carry target reader information, then any terminal with reader capabilities is indicated as the target reader. In this example, the first terminal as the target reader can be a terminal with reader capabilities. In the embodiments of this application, having reader capabilities can mean being able to implement the functions of a reader; in addition, having reader capabilities can also mean being able to act as a reader role. For example, if a terminal is in a mode that can act as a reader, it indicates that the terminal can act as a reader role and can implement the functions of a reader. In this example, the first identifier can be pre-configured in the RAN.

[0153] In other examples, the target reader can be described by identifiers of the target reader, such as the target reader identifier and / or the target reader group identifier.

[0154] For example, a reader identifier can be called a reader ID, used to uniquely identify a reader. That is, different readers have different reader IDs, and different terminals acting as readers have different reader IDs. For instance, the reader ID corresponding to terminal A as a reader is different from the reader ID corresponding to terminal B as a reader; that is, terminal A and terminal B act as different readers. In this embodiment, the target reader identifier corresponding to the target reader is the target reader ID, and the terminal corresponding to the target reader ID is the first terminal acting as the target reader. It should be noted that a target reader may correspond to one or more target reader identifiers (i.e., one or more target reader IDs), and the terminals corresponding to these one or more target reader identifiers are the one or more first terminals acting as the target reader.

[0155] Furthermore, for example, a reader group identifier can be called a target ID. A reader group identifier (i.e., a target ID) uniquely identifies a reader group, and a reader group contains one or more readers. The target reader can correspond to one or more target reader group identifiers (i.e., one or more target IDs). Then, the readers contained in the one or more target reader group identifiers are the target readers, and the one or more groups of terminals corresponding to the one or more target reader group identifiers that serve as readers are the terminals that serve as target readers.

[0156] The target reader identifier and / or target reader group identifier can be assigned by AMF or UDM, or pre-configured in UDM, or provided by the service requester.

[0157] In other examples, the target reader can be described by target location information, which indicates that the terminal located at the target location described by the target location information is the target reader.

[0158] In this embodiment of the application, there may be one or more first terminals. When there are multiple first terminals, the different first terminals may be of the same type or different types.

[0159] After receiving the first information, the RAN can determine whether the connection state of the first terminal, which is the target reader, is connected or disconnected.

[0160] For RAN, a terminal being in a disconnected state can mean that the terminal is in an RRC idle state or an RRC inactive state.

[0161] There are several situations in which the first terminal of the target reader can be in a disconnected state.

[0162] For example, when there are multiple first terminals, the first terminal acting as the target reader being in a disconnected state can mean that among the multiple first terminals acting as the target reader, there is one in a disconnected state. Alternatively, when the RAN requires the number of terminals acting as the target reader to be greater than a specified number based on first information, the first terminal acting as the target reader being in a disconnected state can mean that the number of first terminals in a connected state is not greater than that specified number. Alternatively, the first terminal acting as the target reader being in a disconnected state can mean that one or more of the first terminals acting as the target reader are all in a disconnected state.

[0163] It can be seen that the RAN determines that the first terminal serving as the target reader is in a non-connected state by either determining that there are no first terminals serving as the target reader that are in a connected state, or determining that there are not a sufficient number of first terminals serving as the target reader that are in a connected state.

[0164] It is understood that in the embodiments of this application, in step 202, RAN can be which terminal or terminals have been determined as the first terminal of the target reader, or it can be which terminal or terminals have not yet been determined as the first terminal of the target reader, and there is no limitation here.

[0165] For example, in one instance, the RAN can determine that the terminal in the connected state is not the first terminal that is the target reader (e.g., none of the terminals in the connected state have the capability to act as readers), thus determining that the first terminal that is the target reader is in the disconnected state. In this example, the RAN has not yet determined which terminal or terminals are specifically the first terminal that is the target reader.

[0166] Alternatively, the RAN can determine that among the connected terminals, the number of terminals acting as target readers does not meet a specified condition (e.g., not exceeding a specified number). In other words, the RAN can determine that there are not enough connected first terminals acting as target readers, thus determining that the first terminals acting as target readers are in a disconnected state. In this example, the RAN can identify some of the first terminals acting as target readers that are already in a connected state, but has not yet identified the other part of the first terminals that are not in a connected state.

[0167] Alternatively, prior to step 202, the method may further include the following steps: the RAN receives third information, which includes one or more of the following: a reader identifier corresponding to the first terminal, a reader group identifier corresponding to the first terminal, a second identifier corresponding to the first terminal, and location information of the first terminal, wherein the second identifier indicates that the terminal has reader capability; the RAN determines the first terminal as the target reader based on the third information.

[0168] In this example, the third information can come from core network equipment such as the AMF. For example, the AMF can authorize the first terminal as a reader based on one or more of the reader identifier, reader group identifier, second identifier, and location information of the first terminal received from the first terminal during the first terminal's registration process, and / or the subscription data about the first terminal received from the UDM; then, the AMF can send the third information to the RAN. In this example, when the third information includes the second identifier corresponding to the first terminal, the second identifier corresponding to the first terminal can indicate that the first terminal has reader capability; that is, the second identifier corresponding to the first terminal can be considered as the reader capability information of the first terminal. This second identifier can be the same as the first identifier mentioned above, for example, it can be a specific value in a specified field, or it can be different. In this example, the first identifier and the second identifier can be considered to match. For example, the third information received by the RAN includes a second identifier corresponding to the first terminal, indicating that the first terminal has reader capability. The first information may carry a first identifier, indicating that the target reader is a terminal with reader capability. Therefore, it can be assumed that the second identifier in the third information matches the first identifier in the first information, thereby determining the first terminal as the target reader.

[0169] In this example, when the RAN receives the third information, the first terminal is in a connected state. Then, after the first terminal transitions from a connected state to a disconnected state (e.g., RRC Inactive or RRC Idle), the RAN receives the first information. Next, the RAN can determine the first terminal as the target reader based on the third information and determine that the first terminal is in a disconnected state.

[0170] For example, the first information also includes reader information indicating the target reader to perform the business operation. The reader information includes one or more of the following: target reader identifier, target reader group identifier, first identifier, and target location information. The first identifier in the reader information indicates any terminal with reader capability.

[0171] In this example, the service requester can send a service request carrying reader information to the IoT functional entity, enabling the IoT functional entity to determine the reader information of the target reader for performing the service operation. Based on this, the first information can carry reader information indicating the target reader for performing the service operation, so that the RAN can determine the reader indicated by the service requester to perform the service operation based on this reader information.

[0172] In this way, the RAN determines the first terminal as the target reader based on the matching of the third information and the reader information. For example, if one or more of the following conditions are met: the reader identifier corresponding to the first terminal in the third information matches the target reader identifier in the first information; the reader group identifier corresponding to the first terminal matches the target reader group identifier in the first information; both the third and first information carry the first identifier; and the location information of the first terminal is located in the target location indicated by the target location information in the first information, then the third information can be considered to match the reader information, thereby determining the first terminal as the target reader.

[0173] After determining that the first terminal, which is the target reader, is in a disconnected state, the RAN can send a paging message. In one example, the paging message may include identification information carrying a reader message describing the target reader. This allows the terminal receiving the paging message to identify itself as the first terminal of the target reader by matching the reader message, thereby responding to the paging message and subsequently receiving service instructions and executing service operations. Alternatively, in another example, the identification information included in the paging message indicates that terminals within the RAN's coverage area are being paged. This allows terminals within the RAN's coverage area to respond to the paging message and establish a connection with the RAN, after which the RAN identifies the first terminal of the target reader from among the terminals connected to the RAN.

[0174] Step 203: The first terminal receives the paging message.

[0175] In some examples, the paging message includes identification information, which includes one or more of the following: target reader identifier, target reader group identifier, first identifier, and target location information, wherein the first identifier indicates any terminal with reader capability.

[0176] In this way, the first terminal can identify itself as the target reader based on the identification information carried in the paging message.

[0177] For example, before performing step 203, the method further includes: before the first terminal receives the paging message, the method further includes:

[0178] The first terminal receives fourth information, which includes one or more of the following: the reader identifier corresponding to the first terminal, the reader group identifier corresponding to the first terminal, the second identifier corresponding to the first terminal, and the location information of the first terminal.

[0179] After step 203, the first terminal can match the fourth information with the identification information. If the fourth information matches the identification information (for example, the reader identifier corresponding to the first terminal matches the target reader identifier, the reader group identifier corresponding to the first terminal matches the target reader group identifier, etc.), then the first terminal can determine that it needs to respond to the paging message, or it can determine that the first terminal is the target reader.

[0180] In other examples, the paging message includes identification information to instruct terminals within the RAN's coverage area to be paged. This allows terminals within the RAN's coverage area to establish a connection with the RAN in response to the paging message. The RAN then selects the first terminal from those connected to the RAN as the target reader. Therefore, upon receiving the paging message, the first terminal can initiate a connection establishment request to the RAN in response to the paging message without needing to determine which terminal is the target reader.

[0181] In other examples, the paging message includes identification information to instruct a terminal matching the identification information to be paged, so that a terminal within the RAN's coverage area matching the identification information responds to the paging message and establishes a connection with the RAN. For example, when the identification information includes a first identifier, a terminal with reader capability can respond to the paging message; or, for example, when the identification information includes a reader identifier or a reader group identifier, the terminal indicated by the reader identifier or a terminal belonging to the reader group can respond to the paging message.

[0182] Step 204: The first terminal initiates a connection establishment request to the RAN based on the paging message.

[0183] The connection establishment request is used to request the establishment of a connection between the first terminal and the RAN.

[0184] In some examples, the first terminal can determine itself as the target reader based on the paging message, and thus initiate a connection establishment request to the RAN. For example, the first terminal initiates a connection establishment request to the RAN based on the matching of the fourth information with the identification information, according to the paging message.

[0185] In other examples, the paging message includes identification information to instruct terminals within the RAN's coverage area to be paged, so that after a terminal within the RAN's coverage area responds to the paging message and establishes a connection with the RAN, the RAN then determines the first terminal from among the terminals that have established a connection with the RAN as the target reader.

[0186] In some examples, after step 204, the RAN can determine the first terminal as the target reader.

[0187] In some embodiments, after step 204, the method further includes:

[0188] The RAN receives third information, which includes one or more of the following: the reader identifier corresponding to the first terminal, the reader group identifier corresponding to the first terminal, the second identifier corresponding to the first terminal, and the location information of the first terminal. The second identifier indicates that the terminal has reader capability.

[0189] Based on the third information, the RAN determines the first terminal as the target reader.

[0190] In this embodiment of the application, there can be various sources of the third information and the timing of the RAN receiving the third information, which are not limited here.

[0191] In this example, after receiving a paging message, the first terminal can register in response to the paging message. During the registration process of the first terminal, the RAN can receive a third message from the first terminal, AMF, or UDM, and thus determine the first terminal as the target reader based on the third information.

[0192] As can be seen from the above example, the RAN can determine the first terminal as the target reader after step 201 and before step 202, or it can determine the first terminal as the target reader after step 204.

[0193] In addition, after establishing the connection between the first terminal and the RAN, the method further includes step 205: the first terminal receives fifth information from the RAN, the fifth information indicating the execution of business operations on the IoT device.

[0194] In this way, the first terminal can perform step 206: perform business operations on the IoT device when an IoT device is present.

[0195] The following is a specific example illustrating an exemplary implementation of an embodiment of this application. It should be understood that this specific example is merely an illustrative description of the embodiment of this application and is not intended to limit it.

[0196] like Figure 3 As shown in the specific example, the business request from the business requester can be an inventory request, and the business requester can be AF.

[0197] A specific example may include steps 31-319.

[0198] Step 31. AF can indicate to UDM via NEF as the first terminal of the target reader.

[0199] In one possible implementation, the AF sends the terminal's identifier, such as the generic public subscription identifier (GPSI) or subscription permanent identifier (SUPI), and may also send reader information indicating the target reader. This reader information may include one or more of the following: target reader group identifier (target ID(s)), a first identifier, time information, and target location information. The first identifier in the reader information indicates any terminal with reader capability. The target ID(s) may be used to indicate the target reader group corresponding to the first terminal acting as the target reader. A target reader group may contain one or more readers. The target reader group identifier sent in this step may include one or more reader groups. The time information may indicate the time the first terminal acts as a reader (e.g., start time, duration, end time, one or more of these); the target location information indicates the location range of the first terminal acting as a reader (e.g., geographic location, coordinate values, cell identifier, tracking area identifier, one or more of these).

[0200] In one possible implementation, the AF sends information indicating the first terminal as the target reader to the NEF via Nnef_ParameterProvision Create / UpdateRequest. If the AF provides a GPSI, the NEF can obtain the corresponding SUPI based on the GPSI and send the first terminal's SUPI, first identifier, and / or target ID(s) to the UDM via Nudm_ParameterProvision Create / Update Request. If the AF is a trusted AF, it can directly send information indicating the first terminal as the target reader to the UDM; for example, the AF can send the first terminal's SUPI / GPSI, first identifier, and / or target ID(s) to the UDM via Nudm_ParameterProvision Create / Update Request.

[0201] Step 32. The first terminal sends a registration request message to the RAN. This registration request message may carry the registration type and the identification information of the first terminal (subscription concealed identifier (SUCI), 5G globally unique temporary identifier (5G-GUTI), or permanent equipment identifier (PEI)).

[0202] The registration types are as follows:

[0203] Initial registration: The registration process initiated when the terminal is in a deregistering state;

[0204] Mobility registration update: A registration process that needs to be initiated when a terminal needs to move.

[0205] Periodic registration update: A registration process initiated when a terminal is in a registration state and the periodic registration update timer expires.

[0206] Emergency registration: A registration process initiated when a terminal is in a business-restricted state.

[0207] In the scenarios described in this application, the registration type is typically initial registration, mobility registration update, or periodic registration. Regarding the identification information of the first terminal, if the first terminal has a valid 5G-GUTI (a temporary identity identifier assigned by the AMF serving it), the 5G-GUTI is carried in the registration request; if the first terminal does not have a valid 5G-GUTI, then a SUCI is carried; in emergency registration, if the first terminal has neither a valid 5G-GUTI nor a SUPI (i.e., no SUCI, where SUCI is an encrypted SUPI), then a PEI is carried.

[0208] Optionally, the first terminal may include first indication information (which can be understood as reader capability information) in the registration request message to indicate that the terminal device has the capability to act as a reader. In one possible implementation, the first terminal may include a first identifier (e.g., reader capable indication) in the registration request message, or it may add a new information element (e.g., adding a preferred network behavior to the information element of Preferred Network Behaviour) as the first identifier to indicate that the terminal device has the capability to act as a reader. This new information element may be used to indicate whether it supports acting as a reader (e.g., whether support reader capability) or whether to activate a target mode that enables reader operation (e.g., whether activate reader mode). The RAN selects a suitable AMF; the RAN forwards the registration request message sent by the UE to the AMF.

[0209] Step 33. The first terminal executes a security process with AMF, AUSF, and UDM to complete the two-way authentication between the first terminal and the network.

[0210] Step 34. The AMF registers with the UDM as the serving AMF for the first terminal. In one possible implementation, the AMF sends a Nudm_UECM Registration message to the UDM, which contains the AMF's identifier (AMF ID).

[0211] Step 35. The AMF interacts with the UDM to obtain the subscription data of the first terminal. The subscription data sent by the UDM to the AMF may include a first identifier (indicating the capability to act as a reader) and / or, target ID(s).

[0212] Step 36. The AMF may authorize the first terminal as a reader based on reader capability information from the first terminal and / or, the UDM's subscription data. The reader capability information may include a first identifier.

[0213] One possible implementation is that the AMF, through interaction with the UDM, assigns a reader ID to the first terminal authorized as a reader. In another possible implementation, this reader ID can be assigned by the AMF or the UDM; it can also be pre-configured in the UDM or provided by the AF.

[0214] In one possible implementation, in step 37a, after obtaining the reader ID, the AMF sends the SUPI of the first terminal and the reader ID of the first terminal (as the reader identifier corresponding to the first terminal) to the IoT Functional Entity to indicate that the first terminal is acting as a reader. In another possible implementation, in step 37b, the AMF also sends information indicating that the first terminal is acting as a reader to the RAN, optionally including the reader ID and / or target ID(s). For example, the AMF can send context information of the first terminal to the RAN, which includes information indicating that the UE is acting as a reader, such as the reader ID and / or target ID(s) of the first terminal. Through the above methods, both the IoT Functional Entity and the RAN obtain the reader ID corresponding to the first terminal. In subsequent applications, the reader ID information corresponding to the terminal can be used to inform the RAN which terminals need to be selected as readers to receive service instructions.

[0215] Step 38. The AMF sends a registration acceptance message to the first terminal via the RAN. Optionally, the AMF can send the target ID(s) or reader ID corresponding to the first terminal to the first terminal. Subsequently, when the IoT functional entity wants the terminal corresponding to a specific target ID to receive service instructions, the RAN can send a paging message through that target ID(s).

[0216] Steps 39a-39d. Optionally, the first terminal disconnects from the RAN and enters the RRC idle state, and the RAN triggers the context release procedure. The RAN sends an N2 UE context release request to the AMF, the AMF sends an N2 UE context release command to the RAN, and the RAN sends an N2 UE context release complete message to the AMF.

[0217] Step 310. AF sends an inventory request to the IoT functional entity, instructing it to perform an inventory operation.

[0218] For example, the AF sends an inventory request to the NEF, which may include the AF's identifier. Optionally, the AF may also send the identifier information of the first terminal acting as the target reader (e.g., the GPSI of the first terminal), the target location information for which the inventory operation needs to be performed, or the target ID(s) of the target reader. The NEF selects an IoT functional entity according to its configuration, for example, based on one or more of the AF identifier, GPSI (or SUPI), target location information, and target ID(s); or when the AF provides GPSI information, the NEF obtains the corresponding SUPI information based on the GPSI and selects an IoT functional entity based on the SUPI (e.g., based on the SUPI number range); the NEF sends a service request message to the IoT functional entity, which includes the AF identifier; if the AF provides the GPSI or SUPI information of the first terminal in step 310, the NEF also sends the SUPI of the first terminal to the IoT functional entity. If the AF sends the target location information to the NEF, the NEF sends the target location information to the IoT functional entity; if the AF provides the target ID(s) of the target reader, the NEF sends the target ID(s) of the target reader to the IoT functional entity.

[0219] In one possible implementation, if the IoT functional entity receives a SUPI in step 310, the IoT functional entity interacts with the UDM to obtain the Reader ID information corresponding to the SUPI, or in step 37a, the IoT functional entity obtains the reader ID information corresponding to the SUPI through the AMF. In another possible implementation, if the IoT functional entity receives a target ID(s) or target location information in step 310, the IoT functional entity selects a RAN based on the target ID(s) or target location information. The IoT functional entity sends one or more of the reader ID, target ID(s), or target location information to the RAN. For example, the IoT functional entity sends an inventory request (e.g., via an AIoT NGAP message) to the selected RAN, which includes reader information indicating the target reader, such as one or more of the reader ID, target ID(s), or target location information.

[0220] The RAN determines the first terminal to be the target reader based on the inventory request sent by the IoT functional entity.

[0221] In one possible implementation, if an IoT functional entity sends a reader ID (i.e., a target reader identifier), the RAN determines the first terminal as the target reader based on the reader ID. For example, it retrieves the context of each terminal. If the reader identifier contained in the context of a terminal is the same as the target reader identifier of the IoT functional entity, then the terminal is determined to be the first terminal as the target reader.

[0222] In another possible implementation, if the IoT functional entity sends a target ID (i.e., the target reader group identifier), the RAN determines the first terminal as the target reader based on the target ID. For example, it retrieves the context of each terminal. If the target ID contained in the context of a terminal is the same as the target ID from the IoT functional entity, then the terminal is determined to be the first terminal as the target reader.

[0223] In another possible implementation, if an IoT functional entity sends target location information, the RAN determines, based on the target location information, a terminal with reader capability located at the target location indicated by the target location information as the first terminal.

[0224] In one possible implementation, during steps 39a-39d, some terminals acting as readers enter an idle state, resulting in the RAN not storing the context information. When the RAN determines that there is no suitable first terminal as a target reader, or that there are not enough first terminals as target readers, then in step 311a, the RAN determines that the first terminal acting as a target reader is in a disconnected state based on the inventory request sent by the IoT functional entity.

[0225] In step 311b, the RAN can trigger paging of the first terminal acting as the target reader. The RAN sends a paging message, which may contain reader information indicating the target reader, such as one or more of a first identifier, reader ID, target ID(s), or target location information. The reader ID in the paging message can be used to instruct the terminal identified by that reader ID to initiate connection establishment. The target ID in the paging message can be used to instruct terminals belonging to the reader group indicated by that target ID to initiate connection establishment. The first identifier in the paging message can instruct authorized terminals acting as readers to initiate connection establishment. If the IoT functional entity sends target location information, the paging message may contain the target location information, instructing terminals located at the target location indicated by that target location information to initiate connection establishment. If the paging message contains one or more of the first identifier, reader ID, target ID, and target location information, terminals matching one or more of these parameters will initiate connection establishment. In one example, the inventory request sent by the application to the AMF does not carry target reader information, but can designate any terminal with reader capability as the target reader. The inventory request sent by the AMF to the RAN can carry a first identifier to designate any terminal with reader capability as the target reader. Alternatively, the inventory request sent by the AMF to the RAN can also not carry target reader information, in which case it designates any terminal with reader capability as the target reader. In this example, the paging message broadcast by the RAN can carry a first identifier to instruct a terminal with reader capability to respond to the paging message and initiate connection establishment.

[0226] Step 312. The terminal that received the paging message in step 311b initiates connection establishment and sends a service request to the AMF through the RAN. The AMF and RAN then establish an N2 UE context.

[0227] Step 313. The RAN learns that the terminal belongs to the first terminal indicated in step 310 as the target reader. For example, the RAN can determine this through the target location information, reader ID, or target ID in the reader information.

[0228] Step 314. The RAN sends an inventory request to the first terminal (e.g., via an RRC message).

[0229] Step 315. The first terminal interacts with the IoT device to complete the random access process of the IoT device.

[0230] Step 316. The IoT device sends an IoT device identifier (Device ID) to the first terminal. For example, the IoT device sends a Device to Reader message (D2R message) to the first terminal, which includes the IoT device identifier.

[0231] Step 317. The first terminal sends (e.g., via RRC message) information from the IoT device to the RAN, such as the IoT device identifier.

[0232] Step 318. The RAN sends information from the IoT device, such as the IoT device identifier, to the IoT functional entity (e.g., via an AIoT NGAP message).

[0233] Step 319. The IoT functional entity sends a response message to the AF via NEF, including information about the IoT device, such as the IoT device identifier.

[0234] As can be seen, in this embodiment of the application, a paging mechanism for the RAN targeting the terminal acting as a reader is designed. In this scheme, even if the first terminal acting as the target reader is in a disconnected state, it can still initiate a connection establishment request through a paging message targeting the first terminal acting as the target reader, thereby establishing a connection with the RAN, receiving service instructions, and executing service operations on the IoT device.

[0235] In this way, when IoT functional entities transmit services, they do not need to interact with core network elements such as AMF to send service requests to RAN only after the first terminal, which is the target reader, is in a connected state. Instead, they can send service requests directly to RAN, and RAN will then enable the first terminal to receive the service requests. This reduces or even avoids signaling interactions between IoT functional entities and core network elements such as AMF, thereby reducing signaling overhead and improving information transmission efficiency.

[0236] Furthermore, the paging mechanism in this application differs from existing paging mechanisms. Traditional paging mechanisms typically carry temporary identifiers such as the terminal's TMSI to page a specific terminal, but cannot page the first terminal (target reader) and initiate connection establishment with a single paging. However, in some embodiments of this application, the RAN can page the first terminal (target reader) and initiate connection establishment with a single paging that carries special identifiers such as a first identifier, resulting in higher paging efficiency and improved information exchange efficiency.

[0237] Furthermore, in some scenarios, when the RAN acts as a reader, the IoT functional entity can send service instructions to the RAN, typically without needing to interact with core network elements such as the AMF (Agency Filtering Function). Therefore, in this embodiment, when the terminal acts as a reader, the service transmission method of the IoT functional entity is the same. That is to say, the solution in this embodiment allows the IoT functional entity cabinet to use the same service transmission method (i.e., sending service instructions to the RAN) when facing both types of readers—terminals as readers and RAN as readers—and ensures the reliability of service transmission while reducing information interaction with core network elements such as the AMF (i.e., through the RAN's paging mechanism for terminals acting as readers, the first terminal acting as the target reader, which is in a disconnected state, is found and a connection is established to receive service instructions, ensuring the execution of service operations). In addition, the solution in this embodiment is basically consistent with the service instruction issuance method when the RAN acts as a reader, thus maximizing compatibility with two different reader types through a single architecture.

[0238] Furthermore, in many scenarios of the embodiments of this application, since signaling interaction between IoT functional entities and core network elements such as AMF can be avoided, it is possible to deploy only IoT functional entities in the park without deploying core network elements such as AMF, which facilitates the reduction of IoT deployment costs.

[0239] Example 2:

[0240] In this embodiment, the connection status of the first terminal, which acts as a reader, can be managed by a first network device to ensure that the first terminal is in a connected state. Thus, during service transmission, since the first terminal, which is the target reader corresponding to the IoT device, is in a connected state, the IoT functional entity can directly send service instructions to the RAN to instruct the first terminal to perform service operations. This reduces or even avoids signaling interaction between the IoT functional entity and core network elements such as the AMF, thereby reducing signaling overhead and improving information transmission efficiency.

[0241] like Figure 4 As shown, the data processing method in this application embodiment includes steps 401-402.

[0242] Step 401: The first network device determines the first terminal as a reader.

[0243] In this embodiment of the application, the specific type of the first network device is not limited. For example, the first network device can be a RAN, a core network element such as an AMF or UDM, or a network element such as an Internet of Things functional entity.

[0244] The following provides exemplary descriptions of how the first network device determines the first terminal as a reader when the first network device is of different types.

[0245] 1. The first network device is RAN.

[0246] Specifically, in some embodiments, when the first network device is a RAN, step 401 includes:

[0247] The RAN receives the sixth message from the AMF, which instructs the first terminal to act as a reader.

[0248] In some examples, the sixth information may come from the AMF. For instance, the AMF may authorize the first terminal as a reader based on one or more of the reader identifier corresponding to the first terminal, the reader group identifier corresponding to the first terminal, the second identifier corresponding to the first terminal, and the location information of the first terminal received from the first terminal during the registration process, and / or, the subscription data about the first terminal received from the UDM. After authorizing the first terminal as a reader, the AMF may send the sixth information to the RAN to indicate that the first terminal is acting as a reader. In one possible implementation, the sixth information may include one or more of the following: the identifier of the first terminal (e.g., the GPSI or SUPI of the first terminal), the reader identifier corresponding to the first terminal, the reader group identifier corresponding to the first terminal, the second identifier corresponding to the first terminal, the location information of the first terminal, the time information of acting as a reader, and the location information of acting as a reader. The time information of acting as a reader indicates that the terminal can act as a reader when the time is within a specified time period indicated by the time information. The location information of acting as a reader indicates that the terminal acts as a reader when it is located in a specific location (e.g., within a specific location area).

[0249] 2. The first network device is AMF.

[0250] Specifically, in some embodiments, when the first network device is an AMF, step 401 includes:

[0251] AMF determines the first terminal as a reader based on the seventh information from the first terminal and / or the subscription data from the UDM, with the seventh information indicating that the first terminal is a reader.

[0252] For example, the AMF can receive the seventh information from the first terminal during the registration process of the first terminal, or it can receive subscription data about the first terminal from the UDM as the seventh information. In one possible implementation, the seventh information may include one or more of the following: the identifier of the first terminal, the reader identifier corresponding to the first terminal, the reader group identifier corresponding to the first terminal, the second identifier corresponding to the first terminal, the location information of the first terminal, the time information as a reader, and the location information as a reader.

[0253] 3. The first network device is an Internet of Things (IoT) functional entity.

[0254] Specifically, in some embodiments, when the first network device is an Internet of Things (IoT) functional entity, step 401 includes:

[0255] The IoT functional entity sends a subscription request to the UDM or AMF. The subscription request indicates that the status information of the first terminal as the reader is subscribed. The status information includes one or more of the status information such as registration status and connection status.

[0256] The IoT functional entity receives a first status notification from UDM or AMF, which indicates that the first terminal acting as a reader is in a registered state and / or a connected state.

[0257] In this embodiment of the application, the IoT functional entity can subscribe to the status information of the first terminal as a reader from UDM or AMF.

[0258] For example, in one scenario, the UDM can subscribe to the status information of the first terminal acting as a reader from the AMF, and then the IoT functional entity can subscribe to the status information of the first terminal acting as a reader from the UDM. Alternatively, in another scenario, if the IoT functional entity obtains the AMF information (e.g., AMF ID) of the first terminal acting as a reader, the IoT functional entity can also subscribe to the status information of the first terminal acting as a reader from the AMF.

[0259] The subscription request may carry information about the first terminal acting as a reader, such as one or more of the following: a reader identifier corresponding to the first terminal, a reader group identifier corresponding to the first terminal, a second identifier corresponding to the first terminal, and the location information of the first terminal. Alternatively, the subscription request may not carry information about the first terminal acting as a reader. Instead, after the first terminal completes registration and / or establishes a connection, the IoT functional entity determines the first terminal acting as a reader based on the received first status information, and determines that the first terminal acting as a reader is in a registered state and / or a connected state.

[0260] It is understood that the subscription request can be directed only to the first terminal (that is, only to the status information of the first terminal), or it can be directed to all terminals acting as readers, including the first terminal.

[0261] 4. The first network device is UDM.

[0262] Specifically, in some embodiments, when the first network device is a UDM, step 401 includes:

[0263] UDM determines the first terminal as a reader based on the first terminal's subscription data, the eighth information from AMF, or the ninth information from the service requester. The eighth information indicates that the first terminal is authorized to act as a reader, and the ninth information indicates that the first terminal is acting as a reader.

[0264] In this embodiment, the UDM can obtain the subscription data of the first terminal through the registration process of the first terminal; or, it can receive the eighth information from the AMF after the AMF authorizes the first terminal as a reader; or, the first terminal can be instructed to act as a reader in the service request sent by the service requester, so that the UDM can receive the ninth information such as the service request from the service requester to determine that the first terminal is the reader.

[0265] The contract data, the eighth information, or the ninth information may include one or more of the following: the identifier of the first terminal, the reader identifier corresponding to the first terminal, the reader group identifier corresponding to the first terminal, the second identifier corresponding to the first terminal, the location information of the first terminal, the time information as a reader, and the location information as a reader.

[0266] In this embodiment of the application, when the first terminal is determined to be a reader, the reader can be a reader in a broad sense, indicating that the first terminal has the ability to be a reader, or it can be determined that the first terminal is a specific reader, such as a target reader of an Internet of Things device, and the target reader is described by a target reader identifier, a target reader group identifier, target location information, etc.

[0267] Step 402: The first network device manages the connection status of the first terminal so that the first terminal is in a connected state.

[0268] In this embodiment of the application, there are several possible times when the first network device manages the connection status of the first terminal.

[0269] In some embodiments, the first network device may enable the function of managing the connection status of the first terminal based on pre-configured devices, etc., in order to manage the connection status of the first terminal.

[0270] In other embodiments, the first network device manages the connection state of the first terminal to keep the first terminal in a connected state, including:

[0271] When the first network device determines that the first terminal is located at a first location, the current time is within a specified time period, and / or the first network device receives target mode information sent by the first terminal, it manages the connection state of the first terminal so that the first terminal is in a connected state, and the target mode information indicates that the first terminal is in a mode that can be used as a reader.

[0272] In one possible implementation, the aforementioned sixth information, seventh information, subscription data from UDM regarding the first terminal, eighth information, ninth information, etc., may include information on the first location and / or a specified time period. The first location may be included in the first location information of the reader, and the specified time period may be included in the time information of the reader.

[0273] In this way, after the first network device determines that the first terminal is a reader, it can determine that the connection status of the first terminal needs to be managed if it determines that the first terminal is located at a first location and / or the current time is within a specified time period, thereby enabling the function of managing the connection status of the first terminal.

[0274] In one possible implementation, the first network device can receive target mode information from the first terminal to instruct the first terminal to enter reader mode and be able to act as a reader.

[0275] It is understandable that the above implementation methods can be combined. That is to say, the timing when the first network device manages the connection status of the first terminal can meet one or more of the following conditions: the first terminal is located at a first position, the current time is within a specified time period, and the first network device receives the target mode information sent by the first terminal.

[0276] The specific method by which the first network device manages the connection status of the first terminal so that the first terminal is in a connected state can be referred to in subsequent related embodiments, and will not be repeated here.

[0277] In this embodiment, the connection status of the first terminal can be managed by the first network device so that the first terminal is in a connected state. This ensures that during service transmission, when the first terminal is in a connected state, the IoT functional entity sends information such as service instructions to the first terminal, which acts as a reader, through the RAN to instruct the first terminal to perform the service operation on the IoT device as indicated by the service instructions.

[0278] In one possible implementation, the first terminal can be put into a connected state through steps 401-402 before the business request from the business requester is transmitted.

[0279] Then, after step 402, one or more of the following steps may be performed:

[0280] The RAN receives a first service instruction from the IoT functional entity. The first service instruction instructs the execution of a specified service operation on the IoT device. The specified service operation may include one or more of the following operations: inventory operation, read operation, write operation, failure operation, message interaction operation with the IoT device, sending load to the IoT device, and location operation.

[0281] The RAN sends a second service instruction to the first terminal, which acts as a reader, and the second service instruction instructs the first terminal to perform a specified service operation.

[0282] The first terminal receives the second service instruction;

[0283] The first terminal executes the specified business operation on the IoT device according to the second business instruction.

[0284] As can be seen, in this embodiment of the application, since the first terminal is made to be in a connected state through steps 401-402 before the service request of the service requester is transmitted, the IoT functional entity can directly send service instructions to the RAN during the service transmission process, and then the RAN can directly send service instructions to the first terminal to instruct the first terminal to perform the specified service operation, without the need for the IoT functional entity to interact with core network elements such as AMF during the service transmission process, which makes the service transmission efficiency higher.

[0285] The following is an exemplary description of a specific method by which the first network device manages the connection status of the first terminal so that the first terminal is in a connected state.

[0286] In this embodiment of the application, the specific method by which the first network device manages the connection status of the first terminal may include one or more of the following methods:

[0287] Method 1: RAN and / or AMF can maintain and preserve the connection state of the first terminal through process mechanisms to manage the connection state of the first terminal.

[0288] Method 2: IoT functional entities and / or UDMs can manage the connection status of the first terminal by subscribing to the status information of the first terminal.

[0289] The above methods will be described in detail below.

[0290] Method 1: RAN or AMF can maintain and preserve the connection state of the first terminal through process mechanisms to manage the connection state of the first terminal.

[0291] Since the connection status of the first terminal can include the RRC status with the access network and the CM status with the core network, the RAN and / or AMF can maintain and preserve the connection status of the first terminal through process mechanisms to manage the connection status of the first terminal.

[0292] When the first network device is either RAN or AMF, the process mechanisms used differ, and will be described separately below.

[0293] 1) The first network device is RAN.

[0294] When the first network device is a RAN, managing the connection status of the first terminal can include any of the following methods:

[0295] A. If the RAN detects a connection interruption, it will initiate a paging process.

[0296] Specifically, in some embodiments, when the first network device is a RAN, step 402 includes:

[0297] When the first terminal disconnects from the RAN, the RAN initiates a paging process for the first terminal to re-establish a connection with the RAN.

[0298] As can be seen, in this embodiment of the application, after the first terminal disconnects from the RAN and enters the RRC idle state, the RAN can trigger paging to trigger the first terminal to establish a connection with the RAN, thereby restoring to the RRC connected state, so that the first terminal can maintain the connected state.

[0299] B. To ensure that the first terminal does not enter the RRC Inactive state as much as possible, thereby ensuring that the first terminal does not enter the RRC Idle state.

[0300] Specifically, in some embodiments, when the first network device is a RAN, step 402 includes:

[0301] The RAN sets the connection status parameters of the first terminal to the target state so that the first terminal maintains its connection with the RAN.

[0302] For example, the connection state parameter can be a parameter of the non-connection state, such as an RRC Inactive timer, to maximize the duration for which the first terminal enters the non-connection state, thereby reducing the time for the first terminal to enter the RRC Inactive state, or even preventing the first terminal from entering the RRC Inactive state, so that the first terminal remains in the connection state. In this example, setting the connection state parameter of the first terminal to the target state can be done by setting the value of the RRC Inactive timer to the maximum settable value.

[0303] 2) The first network device is AMF.

[0304] When the first network device is an AMF, managing the connection status of the first terminal can include any of the following methods:

[0305] A. AMF refuses to allow the first terminal to enter the CM idle state.

[0306] Specifically, in some embodiments, when the first network device is an AMF, step 402 includes:

[0307] When the RAN receives a release request from the first terminal, the AMF rejects the release request, which is used to request the release of the connection between the first terminal and the AMF.

[0308] In this embodiment, after the first terminal enters the RRC idle state, the RAN sends an N2 UE context release request to the AMF to request the release of the connection between the first terminal and the AMF. At this time, the AMF refuses to release the N2 context to prevent the first terminal from entering the CM idle state, and instructs the RAN to page the first terminal so that the first terminal enters the RRC connected state and maintains the CM connected state.

[0309] B. After the first terminal enters the CM idle state, paging is triggered by the AMF.

[0310] Specifically, in some embodiments, when the first network device is an AMF, step 402 includes:

[0311] After disconnecting the first terminal from the AMF, the AMF sends a paging message to the RAN, instructing the first terminal to be paged so that the first terminal can establish a connection with the AMF.

[0312] In this embodiment, after the first terminal enters the RRC idle state, the RAN sends an N2 UE Context Release Request to the AMF to request the release of the connection between the first terminal and the AMF. At this time, the AMF can send an N2 UE Context Release Command to the RAN, and the RAN sends an N2 UE Context Release Complete Command to the AMF, and then initiates a paging message to the RAN. This paging message carries the identifier of the first terminal (e.g., a Temporary Mobile Subscriber Identity (TMSI)) to enable the first terminal to establish a connection with the AMF and enter the connected state through paging.

[0313] The following is a specific example illustrating one particular implementation of this example. It should be understood that this specific example is merely an illustrative description of the embodiments of this application and is not intended to limit the scope of the invention.

[0314] like Figure 5 As shown in the specific example, the business request from the business requester can be an inventory request, and the business requester can be AF.

[0315] A specific example may include steps 51-520.

[0316] Step 51. AF can indicate to UDM via NEF as the first terminal of the target reader.

[0317] In one possible implementation, the AF sends the identifier of the first terminal, such as its GPSI or SUPI, and may also send reader information. This reader information may include one or more of the following: a first identifier, time information as a reader, and location information as a reader. Specifically, the time information indicates that the terminal can act as a reader when the time falls within a specified time period indicated by the time information. The location information indicates that the terminal acts as a reader when it is located in a specific location (e.g., within a specific location area).

[0318] In one possible implementation, the AF sends information indicating the first terminal as the target reader to the NEF via Nnef_ParameterProvision Create / UpdateRequest. If the AF provides a GPSI, the NEF can obtain the corresponding SUPI based on the GPSI and send the first terminal's SUPI, first identifier, and / or target ID(s) to the UDM via Nudm_ParameterProvision Create / Update Request. If the AF is a trusted AF, it can directly send information indicating the first terminal as the target reader to the UDM. For example, the AF can send the first terminal's SUPI / GPSI, first identifier, time information, or location information as one or more of these to the UDM via Nudm_ParameterProvision Create / Update Request.

[0319] Step 52. The first terminal sends a registration request message to the RAN. This registration request message may carry the registration type and the identification information of the first terminal (SUCI, 5G-GUTI, or PEI).

[0320] The registration types are as follows:

[0321] Initial registration: The registration process initiated when the terminal is in a deregistering state;

[0322] Mobility registration update: A registration process that needs to be initiated when a terminal needs to move.

[0323] Periodic registration update: A registration process initiated when a terminal is in a registration state and the periodic registration update timer expires.

[0324] Emergency registration: A registration process initiated when a terminal is in a business-restricted state.

[0325] In the scenarios described in this application, the registration type is typically initial registration, mobility registration update, or periodic registration. Regarding the identification information of the first terminal, if the first terminal has a valid 5G-GUTI (a temporary identity identifier assigned by the AMF serving it), the 5G-GUTI is carried in the registration request; if the first terminal does not have a valid 5G-GUTI, then a SUCI is carried; in emergency registration, if the first terminal has neither a valid 5G-GUTI nor a SUPI (i.e., no SUCI, where SUCI is an encrypted SUPI), then a PEI is carried.

[0326] Optionally, the first terminal may include first indication information (which can be understood as reader capability information) in the registration request message to indicate that the terminal device has the capability to act as a reader. In one possible implementation, the first terminal may include a first identifier (e.g., reader capable indication) in the registration request message, or it may add a new information element (e.g., adding a preferred network behavior to the information element of Preferred Network Behaviour) as the first identifier to indicate that the terminal device has the capability to act as a reader. This new information element may be used to indicate whether it supports acting as a reader (e.g., whether support reader capability) or whether to activate a target mode that enables reader operation (e.g., whether activate reader mode). The RAN selects a suitable AMF; the RAN forwards the registration request message sent by the UE to the AMF.

[0327] Step 53. The first terminal executes a security process with AMF, AUSF, and UDM to complete the two-way authentication between the first terminal and the network.

[0328] Step 54. The AMF registers with the UDM as the serving AMF for the first terminal. In one possible implementation, the AMF sends a Nudm_UECM Registration message to the UDM, which contains the AMF's identifier (AMF ID).

[0329] Step 55. The AMF interacts with the UDM to obtain the subscription data of the first terminal. The subscription data sent by the UDM to the AMF may include one or more of the following: a first identifier (indicating the capability to act as a reader), time information as a reader, and location information as a reader.

[0330] Step 56. The AMF may authorize the first terminal as a reader based on reader capability information from the first terminal and / or, the UDM's subscription data. The reader capability information may include a first identifier.

[0331] One possible implementation is that the AMF, through interaction with the UDM, assigns a reader ID to the first terminal authorized as a reader. In another possible implementation, this reader ID can be assigned by the AMF or the UDM; it can also be pre-configured in the UDM or provided by the AF.

[0332] In one possible implementation, in step 57a, after obtaining the reader ID, the AMF sends the SUPI of the first terminal and the reader ID of the first terminal (as the reader identifier corresponding to the first terminal) to the IoT functional entity to indicate that the first terminal is acting as a reader. In another possible implementation, in step 57b, the AMF also sends information indicating that the first terminal is acting as a reader to the RAN, optionally including one or more of the reader ID, time information as a reader, and location information as a reader. For example, the AMF can send context information of the first terminal to the RAN, which includes information indicating that the UE is acting as a reader, such as one or more of the reader ID of the first terminal, time information as a reader, and location information as a reader. Through the above methods, both the IoT functional entity and the RAN obtain the reader ID corresponding to the first terminal. In subsequent applications, the reader ID information corresponding to the terminal can be used to inform the RAN which terminals need to be selected as readers to receive service instructions.

[0333] Step 58. The AMF sends a registration acceptance message to the first terminal via the RAN. Optionally, the AMF may send one or more of the following to the first terminal: authorization information for the first terminal to act as a reader, time information for acting as a reader, and location information for acting as a reader.

[0334] Steps 59a-59b. Optionally, when the first terminal learns, based on its internal implementation or through the information in step 58, that it needs to act as a reader during a specified time period and / or at a first location, the first terminal can send information to the RAN or AMF to activate the reader mode (i.e., target mode information). The RAN or AMF can then determine, based on the target mode information from the first terminal, that the first terminal is in a mode capable of acting as a reader. Alternatively, the RAN or AMF can, based on the information in steps 56 or 57a, 57b, determine that the first terminal is acting as a reader, thereby ensuring, through the process mechanism of steps 510a-510c or 511a-511e, 512, that the first terminal acting as a reader remains in a connected state.

[0335] Step 510a. In one possible implementation, if the RAN keeps the first terminal in a connected state, the RAN can set the RRC Inactive timer corresponding to the first terminal to be as long as possible, thereby reducing the time the first terminal enters the RRC_Inactive state. For example, the RRC Inactive timer corresponding to the first terminal can be set to be as long as possible only when the first terminal is acting as a reader. For instance, the RAN determines whether the first terminal is acting as a reader when it receives target mode information from the first terminal, or based on one or more of the indication information, time information, or location information sent by the AMF indicating that the first terminal is acting as a reader.

[0336] In one possible implementation, in steps 510b-510c, if the first terminal acting as the reader disconnects from the RAN and enters the RRC idle state, the RAN triggers a paging message to trigger the first terminal to establish a connection with the RAN and return to the RRC connected state.

[0337] In one possible implementation, the AMF can ensure that the first terminal is in a connected state. Steps 511a-511b: When the first terminal disconnects from the RAN and enters the RRC idle state, the RAN triggers a context release procedure. For example, the RAN sends an N2 UE Context Release Request to the AMF. In one example, step 511c can be executed: The AMF can determine that the first terminal is a reader based on the indication information from the first terminal activating reader mode, or based on one or more of the reader authorization result, the time information as a reader, and the location information as a reader, and refuse to release the N2 context of the first terminal. In this possible implementation, the AMF, by refusing to release the N2 context, refuses to allow the UE to enter the idle state, indicating to the RAN that paging of the UE is necessary. Alternatively, steps 511d-511e can be executed: When the first terminal enters the CM idle state, the AMF can determine the first terminal as the reader based on the indication information from the first terminal to activate the reader mode, or based on one or more of the reader authorization results, the time information of the reader, and the location information of the reader, and then initiate a paging process to trigger the first terminal to initiate connection establishment.

[0338] Step 512.RAN can trigger a paging of the first terminal acting as the reader.

[0339] Step 513. The first terminal, acting as the reader, initiates connection establishment by sending a service request to the AMF through the RAN. The AMF and RAN establish an N2 UE context so that the first terminal is in the connected state.

[0340] Step 514. AF sends an inventory request to the IoT functional entity, instructing it to perform an inventory operation.

[0341] For example, the AF sends an inventory request to the NEF, which may include the AF's identifier. Optionally, the AF may also send the identifier information of the first terminal acting as the target reader (e.g., the GPSI of the first terminal), the target location information for which the inventory operation needs to be performed, or the target ID(s) of the target reader. The NEF selects an IoT functional entity according to its configuration, for example, based on one or more of the AF identifier, GPSI (or SUPI), target location information, and target ID(s); or when the AF provides GPSI information, the NEF obtains the corresponding SUPI information based on the GPSI and selects an IoT functional entity based on the SUPI (e.g., based on the SUPI number range); the NEF sends a service request message to the IoT functional entity, which includes the AF identifier; if the AF provides the GPSI or SUPI information of the first terminal in step 310, the NEF also sends the SUPI of the first terminal to the IoT functional entity. If the AF sends the target location information to the NEF, the NEF sends the target location information to the IoT functional entity; if the AF provides the target ID(s) of the target reader, the NEF sends the target ID(s) of the target reader to the IoT functional entity.

[0342] In one possible implementation, if the IoT functional entity receives a SUPI in step 514, the IoT functional entity interacts with the UDM to obtain the Reader ID information corresponding to the SUPI, or in step 57a, the IoT functional entity obtains the reader ID information corresponding to the SUPI through the AMF. In another possible implementation, if the IoT functional entity receives a target ID(s) or target location information in step 514, the IoT functional entity selects a RAN based on the target ID(s) or target location information.

[0343] The IoT functional entity sends one or more of the reader ID, target ID(s), or target location information to the RAN. For example, the IoT functional entity sends an inventory request (e.g., via an AIoT NGAP message) to the selected RAN, which includes reader information indicating the target reader, such as one or more of the reader ID, target ID(s), or target location information.

[0344] The RAN determines the first terminal to be the target reader based on the inventory request sent by the IoT functional entity.

[0345] In one possible implementation, if an IoT functional entity sends a reader ID (i.e., a target reader identifier), the RAN determines the first terminal as the target reader based on the reader ID. For example, it retrieves the context of each terminal. If the reader identifier contained in the context of a terminal is the same as the target reader identifier of the IoT functional entity, then the terminal is determined to be the first terminal as the target reader.

[0346] In another possible implementation, if the IoT functional entity sends a target ID (i.e., the target reader group identifier), the RAN determines the first terminal as the target reader based on the target ID. For example, it retrieves the context of each terminal. If the target ID contained in the context of a terminal is the same as the target ID from the IoT functional entity, then the terminal is determined to be the first terminal as the target reader.

[0347] In another possible implementation, if an IoT functional entity sends target location information, the RAN determines, based on the target location information, a terminal with reader capability located at the target location indicated by the target location information as the first terminal.

[0348] Step 515. The RAN sends an inventory request to the first terminal (e.g., via an RRC message).

[0349] Step 516. The first terminal interacts with the IoT device to complete the random access process of the IoT device.

[0350] Step 517. The IoT device sends an IoT device identifier (Device ID) to the first terminal. For example, the IoT device sends a Device to Reader message (D2R message) to the first terminal, which includes the IoT device identifier.

[0351] Step 518. The first terminal sends (e.g., via RRC message) information from the IoT device to the RAN, such as the IoT device identifier.

[0352] Step 519. The RAN sends information from the IoT device, such as the IoT device identifier, to the IoT functional entity (e.g., via an AIoT NGAP message).

[0353] Step 520. The IoT functional entity sends a response message to the AF via NEF, including information about the IoT device, such as the IoT device identifier.

[0354] It is evident that the RAN or AMF can maintain and preserve the connection state of the first terminal through process mechanisms to manage the connection status of the first terminal. This ensures that the first terminal is in a connected state, thereby guaranteeing that when the IoT functional entity sends a service instruction to the first terminal through the RAN, the service instruction can be sent directly to the first terminal through the RAN. This eliminates the need for the IoT functional entity to interact with the AMF before sending the instruction to the IoT functional entity through the AMF, reducing the involvement of core network elements such as the AMF in the service process.

[0355] Method 2: IoT functional entities and / or UDMs can manage the connection status of the first terminal by subscribing to the status information of the first terminal.

[0356] Since IoT functional entities and / or UDMs can subscribe to the status information of the first terminal to know whether the first terminal has entered the idle state, IoT functional entities and / or UDMs can promptly trigger AMFs, etc. to paging when the first terminal enters the idle state, so that the first terminal can enter the connected state.

[0357] The following section describes the subscription methods when the first network device is either an IoT functional entity or a UDM.

[0358] 1) The first network device is an Internet of Things (IoT) functional entity.

[0359] In some embodiments, when the first network device is an Internet of Things (IoT) functional entity, step 402 includes:

[0360] The IoT functional entity receives a second status notification from UDM or AMF, which indicates that the first terminal is in an idle state.

[0361] The IoT functional entity instructs the UDM or the AMF serving the first terminal to initiate a paging process so that the first terminal enters the connected state.

[0362] In this embodiment, the AMF can provide a subscription service, enabling IoT functional entities or network elements such as UDMs to subscribe to the connection status of terminals from the AMF. In one example, the UDM can subscribe to the status information of the first terminal acting as a reader from the AMF, and then the IoT functional entity can subscribe to the status information of the first terminal acting as a reader from the UDM; in this case, the IoT functional entity can receive a second status notification from the UDM. Alternatively, in another example, if the IoT functional entity obtains the AMF information (e.g., AMF ID) of the first terminal acting as a reader, the IoT functional entity can also subscribe to the status information of the first terminal acting as a reader from the AMF; in this case, the IoT functional entity receives a second status notification from the AMF.

[0363] When the IoT functional entity determines that the first terminal is in an idle state such as the CM idle state based on the second state notification, the IoT functional entity can directly send paging indication information to the AMF of the first terminal that serves as the reader, or it can send paging indication information to the AMF through other network devices, thereby instructing the AMF to page the first terminal so that the first terminal can enter the connected state.

[0364] 2) The first network device is UDM.

[0365] In some embodiments, when the first network device is a UDM, step 402 includes:

[0366] The UDM receives the third status notification of the AMF from the first terminal, which indicates that the first terminal is in an idle state.

[0367] The UDM sends a paging instruction message to the AMF, which instructs the AMF to page the first terminal so that the first terminal enters the connected state.

[0368] In this embodiment, the UDM can subscribe to the status information of the first terminal acting as a reader from the AMF. In response to the subscription, the AMF sends a third status notification to the UDM to indicate that the first terminal is in an idle state. Thus, the UDM can respond to the third status notification by sending paging indication information to the AMF, thereby instructing the AMF to page the first terminal so that the first terminal enters a connected state.

[0369] The following is a specific example illustrating one particular implementation of this example. It should be understood that this specific example is merely an illustrative description of the embodiments of this application and is not intended to limit the scope of the invention.

[0370] like Figure 6 As shown in the specific example, the business request from the business requester can be an inventory request, and the business requester can be AF.

[0371] A specific example may include steps 61-621.

[0372] Step 61. AF can be directed to UDM via NEF as the first terminal of the target reader.

[0373] In one possible implementation, the AF sends the identifier of the first terminal, such as its GPSI or SUPI, and may also send reader information. This reader information may include one or more of the following: a first identifier, time information as a reader, and location information as a reader. Specifically, the time information indicates that the terminal can act as a reader when the time falls within a specified time period indicated by the time information. The location information indicates that the terminal acts as a reader when it is located in a specific location (e.g., within a specific location area).

[0374] In one possible implementation, the AF sends information indicating the first terminal as the target reader to the NEF via Nnef_ParameterProvision Create / UpdateRequest. If the AF provides a GPSI, the NEF can obtain the corresponding SUPI based on the GPSI and send the first terminal's SUPI, first identifier, and / or target ID(s) to the UDM via Nudm_ParameterProvision Create / Update Request. If the AF is a trusted AF, it can directly send information indicating the first terminal as the target reader to the UDM. For example, the AF can send the first terminal's SUPI / GPSI, first identifier, time information, or location information as one or more of these to the UDM via Nudm_ParameterProvision Create / Update Request.

[0375] The IoT functional entity can subscribe to reachability notifications from the UDM, which acts as the primary terminal for reading. Optionally, the IoT functional entity can also instruct the UDM to maintain the connectivity of the IoT device acting as the reader.

[0376] Step 62. The first terminal sends a registration request message to the RAN. This registration request message may carry the registration type and the identification information of the first terminal (SUCI, 5G-GUTI, or PEI).

[0377] The registration types are as follows:

[0378] Initial registration: The registration process initiated when the terminal is in a deregistering state;

[0379] Mobility registration update: A registration process that needs to be initiated when a terminal needs to move.

[0380] Periodic registration update: A registration process initiated when a terminal is in a registration state and the periodic registration update timer expires.

[0381] Emergency registration: A registration process initiated when a terminal is in a business-restricted state.

[0382] In the scenarios described in this application, the registration type is typically initial registration, mobility registration update, or periodic registration. Regarding the identification information of the first terminal, if the first terminal has a valid 5G-GUTI (a temporary identity identifier assigned by the AMF serving it), the 5G-GUTI is carried in the registration request; if the first terminal does not have a valid 5G-GUTI, then a SUCI is carried; in emergency registration, if the first terminal has neither a valid 5G-GUTI nor a SUPI (i.e., no SUCI, where SUCI is an encrypted SUPI), then a PEI is carried.

[0383] Optionally, the first terminal may include first indication information (which can be understood as reader capability information) in the registration request message to indicate that the terminal device has the capability to act as a reader. In one possible implementation, the first terminal may include a first identifier (e.g., reader capable indication) in the registration request message, or it may add a new information element (e.g., adding a preferred network behavior to the information element of Preferred Network Behaviour) as the first identifier to indicate that the terminal device has the capability to act as a reader. This new information element may be used to indicate whether it supports acting as a reader (e.g., whether support reader capability) or whether to activate a target mode that enables reader operation (e.g., whether activate reader mode). The RAN selects a suitable AMF; the RAN forwards the registration request message sent by the UE to the AMF.

[0384] Step 63. The first terminal executes a security process with AMF, AUSF, and UDM to complete the two-way authentication between the first terminal and the network.

[0385] Step 64. The AMF registers with the UDM as the serving AMF for the first terminal. In one possible implementation, the AMF sends a Nudm_UECM Registration message to the UDM, which contains the AMF's identifier (AMF ID).

[0386] Step 65. The AMF interacts with the UDM to obtain the subscription data of the first terminal. The subscription data sent by the UDM to the AMF may include one or more of the following: a first identifier (indicating the capability to act as a reader), time information as a reader, and location information as a reader.

[0387] Step 66. The AMF may authorize the first terminal as a reader based on reader capability information from the first terminal and / or, the UDM's subscription data. The reader capability information may include a first identifier.

[0388] One possible implementation is that the AMF, through interaction with the UDM, assigns a reader ID to the first terminal authorized as a reader. In another possible implementation, this reader ID can be assigned by the AMF or the UDM; it can also be pre-configured in the UDM or provided by the AF.

[0389] In one possible implementation, in step 67a, after obtaining the reader ID, the AMF sends the SUPI of the first terminal and the reader ID of the first terminal (as the reader identifier corresponding to the first terminal) to the IoT functional entity to indicate that the first terminal is acting as a reader. In another possible implementation, in step 67b, the AMF also sends information indicating that the first terminal is acting as a reader to the RAN, optionally including one or more of the reader ID, time information as a reader, and location information as a reader. For example, the AMF can send context information of the first terminal to the RAN, which includes information indicating that the UE is acting as a reader, such as one or more of the reader ID of the first terminal, time information as a reader, and location information as a reader.

[0390] Alternatively, in step 67c, the UDM may send one or more of the following to the IoT functional entity: the reader ID of the first terminal, the connection status of the first terminal, the time information as a reader, the location information as a reader, and the AMF information (AMF ID) serving the first terminal. In this way, both the IoT functional entity and the RAN obtain the reader ID corresponding to the first terminal. In subsequent applications, the reader ID information corresponding to the terminal can be used to inform the RAN which terminals need to be selected as readers to receive service instructions.

[0391] Step 68. The AMF sends a registration acceptance message to the first terminal via the RAN. Optionally, the AMF may send one or more of the following to the first terminal: authorization information for the first terminal to act as a reader, time information for acting as a reader, and location information for acting as a reader.

[0392] In steps 69a-69d, when the first terminal disconnects from the RAN and enters the RRC idle state, the RAN triggers the context release procedure. For example, the RAN sends an N2 UE Context Release Request to the AMF. The AMF sends an N2 UE Context Release Command to the RAN, and the RAN sends an N2 UE Context Release Complete message to the AMF. The first terminal then enters the CM idle state.

[0393] Steps 610a-610b. The AMF sends a notification to the UDM that the first terminal has entered the CM idle state. If, in step 61, the IoT functional entity subscribed to the status information of the first terminal acting as a reader from the UDM or AMF, then the UDM or AMF can send a notification to the IoT functional entity that the first terminal has entered the CM idle state.

[0394] In one possible implementation, as in step 611a, if the IoT functional entity triggers paging of the first terminal acting as a reader, the IoT functional entity can instruct the UDM to request the first terminal to enter the CM connected state. Furthermore, the UDM can instruct the AMF to trigger paging of the first terminal, or trigger the UDM to request the AMF serving the first terminal to enable the first terminal to enter the CM connected state. In another possible implementation, as in step 611b, if the IoT functional entity obtains the AMF information (e.g., AMF ID) serving the first terminal, the IoT functional entity can also send information to the AMF instructing to paging the first terminal, or request the AMF to enable the first terminal to enter the connected state.

[0395] If the IoT functional entity obtains the time information and / or location information of the first terminal as a reader, the IoT functional entity can further determine whether the time is within the specified time period indicated by the time information, or whether the first terminal is within the area indicated by the location information. Paging is triggered only when the time is within the specified time period indicated by the time information and / or the location of the first terminal is within the area indicated by the location information.

[0396] In another possible implementation, the UDM can determine, based on the subscription data, that a connected state needs to be maintained for the first terminal. Upon receiving an reachability notification from the AMF (the first terminal enters an idle state), it can trigger a paging process to bring the first terminal into a connected state. Similarly, if the UDM obtains the time and / or location information of the first terminal as a reader, it can further determine whether the time falls within the specified time period indicated by the time information, or whether the first terminal is located within the area indicated by the location information. Paging is only triggered when the time falls within the specified time period indicated by the time information and / or the first terminal's location is within the area indicated by the location information.

[0397] Step 612. The AMF initiates a paging process to trigger the first terminal to initiate connection establishment.

[0398] Step 613.RAN can trigger a paging of the first terminal acting as the reader.

[0399] Step 614. The first terminal, acting as the reader, initiates connection establishment by sending a service request to the AMF through the RAN. The AMF and RAN establish an N2 UE context so that the first terminal is in the connected state.

[0400] Step 615. AF sends an inventory request to the IoT functional entity, instructing it to perform an inventory operation.

[0401] For example, the AF sends an inventory request to the NEF, which may include the AF's identifier. Optionally, the AF may also send the identifier information of the first terminal acting as the target reader (e.g., the GPSI of the first terminal), the target location information for which the inventory operation needs to be performed, or the target ID(s) of the target reader. The NEF selects an IoT functional entity according to its configuration, for example, based on one or more of the AF identifier, GPSI (or SUPI), target location information, and target ID(s); or when the AF provides GPSI information, the NEF obtains the corresponding SUPI information based on the GPSI and selects an IoT functional entity based on the SUPI (e.g., based on the SUPI number range); the NEF sends a service request message to the IoT functional entity, which includes the AF identifier; if the AF provides the GPSI or SUPI information of the first terminal, the NEF also sends the SUPI of the first terminal to the IoT functional entity. If the AF sends target location information to the NEF, the NEF sends the target location information to the IoT functional entity; if the AF provides the target ID(s) of the target reader, the NEF sends the target ID(s) of the target reader to the IoT functional entity.

[0402] In one possible implementation, if the IoT functional entity receives a SUPI in step 615, the IoT functional entity interacts with the UDM to obtain the Reader ID information corresponding to the SUPI, or in step 67a, the IoT functional entity obtains the reader ID information corresponding to the SUPI through the AMF. In another possible implementation, if the IoT functional entity receives a target ID(s) or target location information in step 615, the IoT functional entity selects a RAN based on the target ID(s) or target location information.

[0403] The IoT functional entity sends one or more of the reader ID, target ID(s), or target location information to the RAN. For example, the IoT functional entity sends an inventory request (e.g., via an AIoT NGAP message) to the selected RAN, which includes reader information indicating the target reader, such as one or more of the reader ID, target ID(s), or target location information.

[0404] The RAN determines the first terminal to be the target reader based on the inventory request sent by the IoT functional entity.

[0405] In one possible implementation, if an IoT functional entity sends a reader ID (i.e., a target reader identifier), the RAN determines the first terminal as the target reader based on the reader ID. For example, it retrieves the context of each terminal. If the reader identifier contained in the context of a terminal is the same as the target reader identifier of the IoT functional entity, then the terminal is determined to be the first terminal as the target reader.

[0406] In another possible implementation, if the IoT functional entity sends a target ID (i.e., the target reader group identifier), the RAN determines the first terminal as the target reader based on the target ID. For example, it retrieves the context of each terminal. If the target ID contained in the context of a terminal is the same as the target ID from the IoT functional entity, then the terminal is determined to be the first terminal as the target reader.

[0407] In another possible implementation, if an IoT functional entity sends target location information, the RAN determines, based on the target location information, a terminal with reader capability located at the target location indicated by the target location information as the first terminal.

[0408] Step 616. The RAN sends an inventory request to the first terminal (e.g., via an RRC message).

[0409] Step 617. The first terminal interacts with the IoT device to complete the random access process of the IoT device.

[0410] Step 618. The IoT device sends an IoT device identifier (Device ID) to the first terminal. For example, the IoT device sends a Device to Reader message (D2R message) to the first terminal, which includes the IoT device identifier.

[0411] Step 619. The first terminal sends (e.g., via RRC message) information from the IoT device to the RAN, such as the IoT device identifier.

[0412] Step 620. The RAN sends information from the IoT device, such as the IoT device identifier, to the IoT functional entity (e.g., via an AIoT NGAP message).

[0413] Step 621. The IoT functional entity sends a response message to the AF via NEF, including information about the IoT device, such as the IoT device identifier.

[0414] In traditional technologies, core network equipment only triggers paging of terminals via AMF when downlink services arrive. However, in this embodiment, the first terminal acting as a reader can maintain a connected state before the service arrives by using the RAN or AMF process mechanism or by subscribing to the terminal status notification of the first network device.

[0415] In this way, when IoT functional entities transmit services, they can directly send service requests to the first terminal through the RAN, without having to send service requests to the first terminal through core network elements such as AMF. This reduces or even avoids signaling interaction between IoT functional entities and core network elements such as AMF, thereby reducing signaling overhead and improving information transmission efficiency.

[0416] Furthermore, in some scenarios, when the RAN acts as a reader, the IoT functional entity can send service instructions to the RAN, typically without needing to interact with core network elements such as the AMF (Agency Filtering Function). Therefore, in this embodiment, when the terminal acts as a reader, the service transmission method of the IoT functional entity is the same. That is to say, the solution in this embodiment allows the IoT functional entity cabinet to use the same service transmission method (i.e., sending service instructions to the RAN) when facing both types of readers—terminals as readers and RAN as readers—and ensures the reliability of service transmission while reducing information interaction with core network elements such as the AMF (i.e., through the RAN's paging mechanism for terminals acting as readers, the first terminal acting as the target reader, which is in a disconnected state, is found and a connection is established to receive service instructions, ensuring the execution of service operations). In addition, the solution in this embodiment is basically consistent with the service instruction issuance method when the RAN acts as a reader, thus maximizing compatibility with two different reader types through a single architecture.

[0417] Furthermore, in many scenarios of the embodiments of this application, since signaling interaction between IoT functional entities and core network elements such as AMF can be avoided, it is possible to deploy only IoT functional entities in the park without deploying core network elements such as AMF, which facilitates the reduction of IoT deployment costs.

[0418] The above describes the information transmission method and data processing method provided by the embodiments of this application from multiple aspects. The communication device provided by the embodiments of this application will be described below with reference to the accompanying drawings.

[0419] like Figure 7 As shown, this application embodiment provides a communication device 70, which includes:

[0420] The receiving module 701 is configured to: receive first information from an IoT functional entity, wherein the first information indicates the execution of a business operation on an IoT device;

[0421] The sending module 702 is configured to: send a paging message when it is determined that the first terminal, which is the target reader, is in a disconnected state. The paging message includes identification information, and the terminal indicated by the identification information includes the first terminal.

[0422] Optionally, the identification information includes one or more of the following: target reader identifier, target reader group identifier, first identifier, and target location information, wherein the first identifier indicates any terminal with reader capability.

[0423] Optionally, the receiving module 701 is configured to: receive a connection establishment request from the first terminal, the connection establishment request being used to request the establishment of a connection between the first terminal and the RAN;

[0424] The sending module 702 is used to: send second information to the first terminal when a connection is established with the first terminal, wherein the second information instructs the first terminal to perform a business operation.

[0425] Optionally, the communication device 70 further includes a processing module 703;

[0426] The receiving module 701 is used to: receive third information, the third information including one or more of the following: reader identifier corresponding to the first terminal, reader group identifier corresponding to the first terminal, second identifier corresponding to the first terminal, and location information of the first terminal, wherein the second identifier indicates that the terminal has reader capability;

[0427] The processing module 703 is used to: determine the first terminal as the target reader based on the third information.

[0428] Optionally, the first information may also include reader information indicating the target reader to perform the business operation. The reader information includes one or more of the following: target reader identifier, target reader group identifier, first identifier, and target location information. The first identifier in the reader information indicates any terminal with reader capability.

[0429] Optionally, the processing module 703 is used for:

[0430] The RAN determines the first terminal as the target reader by matching the third information with the reader information.

[0431] like Figure 8 As shown, this application embodiment provides a communication device 80, which includes:

[0432] The receiving module 801 is used to receive a paging message. The paging message includes identification information, which includes one or more of the following: target reader identifier, target reader group identifier, first identifier, and target location information. The first identifier indicates any terminal with reader capability.

[0433] The sending module 802 is used to initiate a connection establishment request to the RAN based on the paging message. The connection establishment request is used to request the establishment of a connection between the first terminal and the RAN.

[0434] Optionally, the receiving module 801 is configured to: receive fourth information, the fourth information including one or more of the following: reader identifier corresponding to the first terminal, reader group identifier corresponding to the first terminal, second identifier corresponding to the first terminal, and location information of the first terminal, wherein the second identifier indicates that the terminal has reader capability;

[0435] The sending module 802 is used to: based on the matching of the fourth information and the identification information, initiate a connection establishment request to the RAN according to the paging message.

[0436] Optionally, the receiving module 801 is configured to: receive fifth information from the RAN, the fifth information indicating the execution of a business operation on the IoT device.

[0437] like Figure 9 As shown, this application embodiment provides a communication device 90, which includes:

[0438] Processing module 901 is used for:

[0439] The first terminal is identified as the reader;

[0440] Manage the connection status of the first terminal to ensure that the first terminal is in a connected state.

[0441] Optionally, the communication device 90 further includes a receiving module 902;

[0442] The receiving module 902 is used to: receive sixth information from the AMF, the sixth information indicating that the first terminal is a reader.

[0443] Optionally, the communication device 90 further includes a transmitting module 903;

[0444] The sending module 903 is used to: when the first terminal is disconnected from the communication device 90, the communication device initiates a paging of the first terminal so that the first terminal can establish a connection with the communication device 90.

[0445] Optionally, the processing module 901 is used for:

[0446] Set the connection status parameter of the first terminal to the target status so that the first terminal maintains the connection with the communication device 90.

[0447] Optionally, the processing module 901 is used for:

[0448] Based on the seventh information from the first terminal and / or the subscription data from the UDM, the first terminal is determined to be a reader, and the seventh information indicates that the first terminal is a reader.

[0449] Optionally, the processing module 901 is used for:

[0450] When a release request is received from the RAN serving the first terminal, the release request is rejected. The release request is used to request the release of the connection between the first terminal and the communication device 90.

[0451] Optionally, the sending module 903 is configured to: after disconnecting the connection between the first terminal and the communication device 90, send a paging message to the RAN, the paging message instructing the first terminal to be paged so that the first terminal can establish a connection with the communication device 90.

[0452] Optionally, the sending module 903 is used to send a subscription request to the UDM or AMF. The subscription request indicates the status information of the first terminal of the reader, including one or more status information such as registration status and connection status.

[0453] The receiving module 902 is used to receive a first status notification from UDM or AMF, the first status notification indicating that the first terminal acting as the reader is in a registered state and / or a connected state.

[0454] Optionally, the receiving module 902 is used to receive a second status notification from UDM or AMF, the second status notification indicating that the first terminal is in an idle state;

[0455] The sending module 903 is used to instruct the UDM or the AMF serving the first terminal to initiate a paging process so that the first terminal enters the connected state.

[0456] Optionally, the processing module 901 is used for:

[0457] Based on the contract data of the first terminal, the eighth information from the AMF, or the ninth information from the service requester, the first terminal is determined to be a reader. The eighth information indicates that the first terminal is authorized to be a reader, and the ninth information indicates that the first terminal is a reader.

[0458] Optionally, the receiving module 902 is used to receive a third status notification from the AMF of the first terminal, the third status notification indicating that the first terminal is in an idle state;

[0459] The sending module 903 is used to send paging indication information to the AMF, which instructs the AMF to page the first terminal so that the first terminal enters the connected state.

[0460] Optionally, the processing module 901 is used for:

[0461] When it is determined that the first terminal is located at a first location, the current time is within a specified time period, and / or the first network device receives the target mode information sent by the first terminal, the connection state of the first terminal is managed so that the first terminal is in a connected state, and the target mode information indicates that the first terminal is in a mode that can be used as a reader.

[0462] like Figure 10 As shown, the communication device 100 includes a processor 1001 and an interface circuit 1002. The processor 1001 and the interface circuit 1002 are coupled to each other. It is understood that the interface circuit 1002 can be a transceiver or an input / output interface. Optionally, the communication device 100 may also include a memory 1003 for storing instructions executed by the processor 1001, or storing input data required by the processor 1001 to execute instructions, or storing data generated after the processor 1001 executes instructions.

[0463] When the communication device 100 is used to implement any of the above method embodiments, the processor 1001 is used to implement the functions of one or more modules of the communication device 70, communication device 80 or communication device 90, and the interface circuit 1002 is used to implement the functions of one or more modules of the receiving module, sending module and processing module.

[0464] This communication device is used to implement the functions of the terminal or network device (e.g., RAN, IoT functional entity, AMF, or UDM) in the above method embodiments. For example, the communication device can be a terminal or a terminal chip, or it can be a network device, a network device module, or a network device chip.

[0465] When the aforementioned communication device is a chip applied to a terminal, the terminal chip implements the functions of the terminal in the above method embodiments. The terminal chip receives information from other modules (such as radio frequency modules or antennas) in the terminal, which is sent to the terminal by network devices such as RAN or Internet of Things devices; or, the terminal chip sends information to other modules (such as radio frequency modules or antennas) in the terminal, which is sent by the terminal to network devices such as RAN or Internet of Things devices.

[0466] When the aforementioned communication device is a module or chip applied to a network device, the module or chip of the network device implements the functions of the network device in the above method embodiments. The module or chip of the network device receives information from other modules (such as radio frequency modules or antennas) in the network device; or, the module or chip of the network device sends information to other modules (such as radio frequency modules or antennas) in the network device, and this information is sent by the network device to a terminal or other network devices.

[0467] 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.

[0468] The method steps in the embodiments of this application can be implemented in hardware or in software instructions executable by a processor. The software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, 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. The storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Alternatively, the ASIC can reside in a base station or terminal. The processor and storage medium can also exist as discrete components in a base station or terminal.

[0469] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer programs or instructions. When a computer program or instruction is loaded and executed on a computer, all or part of the processes or functions of the embodiments of this application are performed. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, a computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center 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 optical disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both types of storage media.

[0470] 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.

Claims

1. An information transmission method, characterized in that, The method includes: The wireless access network device receives first information from the Internet of Things (IoT) functional entity, the first information indicating the execution of a service operation on the IoT device; When the wireless access network device determines that the first terminal, which is the target reader, is in a disconnected state, it sends a paging message. The paging message includes identification information, and the terminal indicated by the identification information includes the first terminal.

2. The method according to claim 1, characterized in that, The identification information includes one or more of the following: target reader identifier, target reader group identifier, first identifier, and target location information, wherein the first identifier indicates any terminal with reader capability.

3. The method according to claim 2, characterized in that, After determining that the first terminal, which is the target reader, is in a disconnected state, the wireless access network device, after sending a paging message, further includes: The wireless access network device receives a connection establishment request from the first terminal, the connection establishment request being used to request the establishment of a connection between the first terminal and the wireless access network device; When the wireless access network device establishes a connection with the first terminal, it sends a second message to the first terminal, the second message instructing the first terminal to perform the service operation.

4. The method according to any one of claims 1-3, characterized in that, The method further includes: The wireless access network device receives third information, which includes one or more of the following: a reader identifier corresponding to the first terminal, a reader group identifier corresponding to the first terminal, a second identifier corresponding to the first terminal, and location information of the first terminal. The second identifier indicates that the terminal has reader capability. The wireless access network device determines the first terminal as the target reader based on the third information.

5. The method according to claim 4, characterized in that, The first information also includes reader information indicating the target reader to perform the service operation. The reader information includes one or more of the following: target reader identifier, target reader group identifier, first identifier, and target location information. The first identifier in the reader information indicates any terminal with reader capability.

6. The method according to claim 5, characterized in that, The wireless access network device determines the first terminal as the target reader based on the third information, including: The wireless access network device determines the first terminal as the target reader based on the matching of the third information with the reader information.

7. An information transmission method, characterized in that, The method includes: The first terminal receives a paging message, the paging message including identification information, the identification information including one or more of the following: target reader identifier, target reader group identifier, first identifier, target location information, the first identifier indicating any terminal with reader capability; The first terminal initiates a connection establishment request to the wireless access network device based on the paging message. The connection establishment request is used to request the establishment of a connection between the first terminal and the wireless access network device.

8. The method according to claim 7, characterized in that, Before the first terminal receives the paging message, the method further includes: The first terminal receives fourth information, which includes one or more of the following: reader identifier corresponding to the first terminal, reader group identifier corresponding to the first terminal, second identifier corresponding to the first terminal, and location information of the first terminal. The second identifier indicates that the terminal has reader capability. The first terminal initiates a connection establishment request to the radio access network device based on the paging message, including: The first terminal, based on the matching of the fourth information with the identification information, initiates a connection establishment request to the wireless access network device according to the paging message.

9. The method according to claim 7 or 8, characterized in that, After establishing the connection between the first terminal and the wireless access network device, the method further includes: The first terminal receives fifth information from the wireless access network device, the fifth information indicating the execution of a service operation on the Internet of Things device.

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

11. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1 to 6, or the method as described in any one of claims 7 to 9.

12. A computer program product containing instructions, characterized in that, When the instructions are executed by the processor, they implement the method as described in any one of claims 1 to 6, or the method as described in any one of claims 7 to 9.

Images