Communication method and apparatus, and chip, chip module, storage medium and program product

Abstract

A communication method and apparatus, and a chip, a chip module, a storage medium and a program product. An Internet of Things function network element acquires a reader identifier and carries the reader identifier in first information sent to an access network device, and the access network device acquires a reader identifier from a core network device, so that on the basis of the reader identifiers acquired from the Internet of Things function network element and the core network device, the access network device can determine to send a service request message to a terminal device serving as a target, and thus the terminal device can execute a service operation on an Internet of Things device, thereby improving an Internet of Things operation process in which the terminal device functions as a reader.

Description

Communication method, device, chip, chip module, storage medium and program product

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on April 2, 2024, with application number 202410398156.3 and invention name “Communication method, device, chip, chip module, storage medium and program product”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technology, and in particular to a communication method, device, chip, chip module, storage medium and program product. Background Art

[0003] In a communication system, both base stations and terminal devices can act as readers for IoT devices. When the base station acts as a reader, the IoT functional network element can directly send instructions to the IoT device through the base station. However, when the terminal device acts as a reader, if the IoT functional network element needs to issue instructions through the access and mobility function (AMF) network element serving the terminal device, it is also necessary to introduce an AMF network element, which is costly. Therefore, there is an urgent need for a communication solution that can reduce the network functions involved in the process of sending IoT service instructions when the terminal device acts as a reader, thereby reducing deployment costs. Summary of the Invention

[0004] The present application provides a communication method, device, chip, chip module, storage medium and program product, so that when the terminal device acts as a reader / writer, the process of sending IoT business instructions can reduce the network functions involved, thereby reducing deployment costs.

[0005] In a first aspect, a communication method is provided, the method comprising: an Internet of Things functional network element receiving a service request message, the service request message including an identifier of a terminal device serving as a reader / writer; and the Internet of Things functional network element sending first information to an access network device, the first information instructing the terminal device to perform a service operation on the Internet of Things device, the first information including a reader / writer identifier, the reader / writer identifier being determined based on the identifier of the terminal device.

[0006] In this aspect, the IoT functional network element obtains the reader / writer identifier and carries the reader / writer identifier in the first information sent to the access network device, and the access network device obtains the reader / writer identifier from the core network device. Therefore, the access network device can determine to send a service request message to the target terminal device serving as a reader / writer based on the reader / writer identifier obtained from the IoT functional network element and the core network device, so that the target terminal device can perform service operations on the IoT device, thereby improving the IoT operation process of the terminal device as a reader / writer, and there is no need to deploy a new AMF, reducing the network functions involved and reducing deployment costs.

[0007] In combination with the first aspect, in a possible implementation, the method also includes: the Internet of Things functional network element sends second information to the unified data management function UDM, the second information includes the identification of the terminal device; and the Internet of Things functional network element receives third information from the UDM, the third information includes the reader identification.

[0008] In combination with the first aspect, in another possible implementation, the method also includes: the access and mobility management function AMF sends fourth information to the UDM, the fourth information indicating that the terminal device supports reader / writer capabilities; and the UDM allocates the reader / writer identifier to the terminal device based on the fourth information.

[0009] In combination with the first aspect, in another possible implementation, the method also includes: the UDM sends fifth information to the AMF, the fifth information includes the reader / writer identifier; and the AMF sends sixth information to the access network device, the sixth information includes the reader / writer identifier.

[0010] In combination with the first aspect, in another possible implementation, the method also includes: the AMF receives seventh information sent by the access network device, and the seventh information indicates that the terminal device supports reader / writer capabilities; the AMF allocates the reader / writer identifier to the terminal device based on the seventh information; and the AMF sends eighth information to the access network device, and the eighth information includes the reader / writer identifier.

[0011] In combination with the first aspect, in another possible implementation, the method also includes: the UDM receives the ninth information sent by the AMF, the ninth information includes the reader / writer identifier; and the UDM saves the correspondence between the identifier of the terminal device and the reader / writer identifier.

[0012] In combination with the first aspect, in another possible implementation, the method also includes: the Internet of Things functional network element sends a subscription request to the UDM, and the subscription request is used to subscribe to the status notification of the terminal device that supports reader / writer capabilities; the UDM sends a first notification to the Internet of Things functional network element, and the first notification includes the identifier of the terminal device, and the first notification indicates that the terminal device accesses the network; and the Internet of Things functional network element allocates the reader / writer identifier to the terminal device.

[0013] In combination with the first aspect, in another possible implementation, the method also includes: the Internet of Things functional network element sends a tenth message to the UDM, the tenth message includes the reader / writer identifier; and the UDM saves the correspondence between the identifier of the terminal device and the reader / writer identifier.

[0014] In combination with the first aspect, in another possible implementation, the method also includes: the UDM sends a second notification to the AMF, the second notification including the reader / writer identifier; and the AMF sends an eleventh message to the access network device, the eleventh message including the reader / writer identifier.

[0015] In combination with the first aspect, in another possible implementation, before the Internet of Things functional network element sends the first information to the access network device, the method also includes: the Internet of Things functional network element sends twelfth information to the UDM, and the twelfth information includes the identification of the terminal device; the UDM sends thirteenth information to the Internet of Things functional network element, and the thirteenth information includes the tracking area information TAI corresponding to the terminal device; and the Internet of Things functional network element determines the access network device based on the TAI of the terminal device.

[0016] In combination with the first aspect, in another possible implementation, the method further includes: the access network device determines the terminal device based on the reader / writer identifier; and the access network device instructs the terminal device to perform business operations on the Internet of Things device.

[0017] In a second aspect, a communication method is provided, which includes: AMF obtaining a reader / writer identifier of a terminal device, where the terminal device supports reader / writer capabilities; and the AMF sending the reader / writer identifier to an access network device.

[0018] In combination with the second aspect, in one possible implementation, the AMF obtains the reader / writer identifier of the terminal device, including: the AMF sends fourth information to the UDM, the fourth information indicating that the terminal device supports reader / writer capabilities; and the AMF receives fifth information from the UDM, the fifth information including the reader / writer identifier.

[0019] In combination with the second aspect, in another possible implementation, the AMF obtains the reader / writer identifier of the terminal device, including: the AMF receives seventh information from the access network device, and the seventh information indicates that the terminal device supports reader / writer capabilities; and the AMF allocates the reader / writer identifier to the terminal device based on the seventh information.

[0020] In combination with the second aspect, in another possible implementation, the AMF sends the reader / writer identifier to the access network device, including: the AMF sends eighth information to the access network device, and the eighth information includes the reader / writer identifier.

[0021] In combination with the second aspect, in another possible implementation, the method further includes: the AMF sends ninth information to the UDM, and the ninth information includes the reader / writer identifier.

[0022] In combination with the second aspect, in another possible implementation, the AMF obtains the reader / writer identifier of the terminal device, including: the AMF receives a second notification from the UDM, and the second notification includes the reader / writer identifier.

[0023] In a third aspect, a communication method is provided, the method comprising: UDM obtaining a reader / writer identifier of a terminal device, the terminal device supporting reader / writer capabilities; and the UDM sending the reader / writer identifier to AMF.

[0024] In combination with the third aspect, in a possible implementation, the method also includes: the UDM receives second information from the Internet of Things functional network element, the second information includes the identification of the terminal device; and the UDM sends third information to the Internet of Things functional network element, the third information includes the reader identification.

[0025] In combination with the third aspect, in another possible implementation, the UDM obtains the reader / writer identifier of the terminal device, including: the UDM receives fourth information from the AMF, and the fourth information indicates that the terminal device supports reader / writer capabilities; and the UDM allocates the reader / writer identifier to the terminal device based on the fourth information.

[0026] In combination with the third aspect, in another possible implementation, the UDM sends the reader / writer identifier to the AMF, including: the UDM sends fifth information to the AMF, and the fifth information includes the reader / writer identifier.

[0027] In combination with the third aspect, in another possible implementation, the UDM obtains the reader / writer identification of the terminal device, including: the UDM receives the ninth information from the AMF, and the ninth information includes the reader / writer identification; and the UDM saves the correspondence between the identification of the terminal device and the reader / writer identification.

[0028] In combination with the third aspect, in another possible implementation, the UDM obtains the reader / writer identification of the terminal device, including: the UDM receives a subscription request from the Internet of Things functional network element, and the subscription request is used to subscribe to the status notification of the terminal device that supports reader / writer capabilities; the UDM sends a first notification to the Internet of Things functional network element, and the first notification includes the identification of the terminal device, and the first notification indicates that the terminal device accesses the network; the UDM receives tenth information from the Internet of Things functional network element, and the tenth information includes the reader / writer identification; and the UDM correspondingly saves the identification of the terminal device and the reader / writer identification.

[0029] In combination with the third aspect, in another possible implementation, the UDM sends the reader / writer identifier to the AMF, including: the UDM sends a second notification to the AMF, and the second notification includes the reader / writer identifier.

[0030] In combination with the third aspect, in another possible implementation, the method also includes: the UDM receives twelfth information from the Internet of Things functional network element, the twelfth information includes the identification of the terminal device; and the UDM sends thirteenth information to the Internet of Things functional network element, the thirteenth information includes the tracking area information TAI corresponding to the terminal device.

[0031] In a fourth aspect, a communication system is provided, which includes a terminal device, an Internet of Things functional network element and an access network device; wherein: the Internet of Things functional network element is used to receive a service request message, and the service request message includes an identifier of the terminal device as a reader / writer; and the Internet of Things functional network element is also used to send a first information to the access network device, and the first information instructs the terminal device to perform a service operation on the Internet of Things device, and the first information includes a reader / writer identifier, and the reader / writer identifier is determined based on the identifier of the terminal device.

[0032] In combination with the fourth aspect, in one possible implementation, the system also includes a unified data management function UDM; wherein: the Internet of Things functional network element is also used to send second information to the UDM, and the second information includes the identification of the terminal device; and the Internet of Things functional network element is also used to receive third information from the UDM, and the third information includes the reader / writer identification.

[0033] In combination with the fourth aspect, in another possible implementation, the system also includes an access and mobility management function AMF; wherein: the AMF is used to send fourth information to the UDM, the fourth information indicating that the terminal device supports reader / writer capabilities; and the UDM is used to allocate the reader / writer identifier to the terminal device based on the fourth information.

[0034] In combination with the fourth aspect, in another possible implementation, the UDM is also used to send fifth information to the AMF, and the fifth information includes the reader / writer identifier; and the AMF is also used to send sixth information to the access network device, and the sixth information includes the reader / writer identifier.

[0035] In combination with the fourth aspect, in another possible implementation, the AMF is used to receive seventh information sent by the access network device, and the seventh information indicates that the terminal device supports reader / writer capabilities; the AMF is also used to allocate the reader / writer identifier to the terminal device based on the seventh information; and the AMF is also used to send eighth information to the access network device, and the eighth information includes the reader / writer identifier.

[0036] In combination with the fourth aspect, in another possible implementation, the UDM is used to receive the ninth information sent by the AMF, and the ninth information includes the reader / writer identifier; and the UDM is also used to save the correspondence between the identifier of the terminal device and the reader / writer identifier.

[0037] In combination with the fourth aspect, in another possible implementation, the Internet of Things functional network element is also used to send a subscription request to the UDM, and the subscription request is used to subscribe to the status notification of the terminal device that supports reader / writer capabilities; the UDM is used to send a first notification to the Internet of Things functional network element, and the first notification includes the identifier of the terminal device, and the first notification indicates that the terminal device has accessed the network; and the Internet of Things functional network element is also used to allocate the reader / writer identifier to the terminal device.

[0038] In combination with the fourth aspect, in another possible implementation, the Internet of Things functional network element is also used to send a tenth message to the UDM, and the tenth message includes the reader / writer identifier; and the UDM is also used to save the correspondence between the identifier of the terminal device and the reader / writer identifier.

[0039] In combination with the fourth aspect, in another possible implementation, the UDM is also used to send a second notification to the AMF, wherein the second notification includes the reader / writer identifier; and the AMF is used to send an eleventh message to the access network device, wherein the eleventh message includes the reader / writer identifier.

[0040] In combination with the fourth aspect, in another possible implementation, the Internet of Things functional network element is also used to send twelfth information to the UDM, and the twelfth information includes the identification of the terminal device; the UDM is also used to send thirteenth information to the Internet of Things functional network element, and the thirteenth information includes the tracking area information TAI corresponding to the terminal device; and the Internet of Things functional network element is also used to determine the access network device based on the TAI of the terminal device.

[0041] In combination with the fourth aspect, in another possible implementation, the access network device is used to determine the terminal device based on the reader / writer identifier; and the access network device is also used to instruct the terminal device to perform business operations on the Internet of Things device.

[0042] In a fifth aspect, a communication device is provided for implementing the communication method in the second aspect or any one of the implementations of the second aspect. The device may be an AMF, or a module applied to an AMF (such as a processor, chip, or chip system), or a logical node, logic module, or software that can implement all or part of the AMF functions.

[0043] Exemplarily, the communication device includes a transceiver unit and a processing unit; wherein:

[0044] The processing unit is used to obtain a reader / writer identification of a terminal device, and the terminal device supports reader / writer capabilities; and the transceiver unit is used to send the reader / writer identification to an access network device.

[0045] Optionally, the transceiver unit is further used to send fourth information to the UDM, where the fourth information indicates that the terminal device supports reader / writer capabilities; and the transceiver unit is further used to receive fifth information from the UDM, where the fifth information includes the reader / writer identifier.

[0046] Optionally, the transceiver unit is further used to receive seventh information from the access network device, where the seventh information indicates that the terminal device supports reader / writer capabilities; and the processing unit is further used to allocate the reader / writer identifier to the terminal device based on the seventh information.

[0047] Optionally, the transceiver unit is further configured to send eighth information to the access network device, where the eighth information includes the reader / writer identifier.

[0048] Optionally, the transceiver unit is further configured to send ninth information to the UDM, where the ninth information includes the reader / writer identifier.

[0049] Optionally, the transceiver unit is further configured to receive a second notification from the UDM, where the second notification includes the reader / writer identifier.

[0050] In a sixth aspect, a communication device is provided for implementing the communication method of the third aspect or any one of the implementations of the third aspect. The device may be a UDM, a module (e.g., a processor, a chip, or a chip system) applied to a UDM, or a logical node, a logical module, or software capable of implementing all or part of the UDM functionality.

[0051] Exemplarily, the communication device includes a transceiver unit and a processing unit; wherein:

[0052] The processing unit is used to obtain the reader / writer identification of the terminal device, and the terminal device supports the reader / writer capability; and the transceiver unit is used to send the reader / writer identification to the AMF.

[0053] Optionally, the transceiver unit is further used to receive second information from the Internet of Things functional network element, the second information including the identification of the terminal device; and the transceiver unit is further used to send third information to the Internet of Things functional network element, the third information including the reader / writer identification.

[0054] Optionally, the transceiver unit is further used to receive fourth information from the AMF, where the fourth information indicates that the terminal device supports reader / writer capabilities; and the processing unit is further used to allocate the reader / writer identifier to the terminal device based on the fourth information.

[0055] Optionally, the transceiver unit is also used to send fifth information to the AMF, and the fifth information includes the reader / writer identifier.

[0056] Optionally, the transceiver unit is further used to receive ninth information from the AMF, where the ninth information includes the reader / writer identifier; and the processing unit is further used to save the correspondence between the identifier of the terminal device and the reader / writer identifier.

[0057] Optionally, the transceiver unit is further used to receive a subscription request from an Internet of Things functional network element, the subscription request being used to subscribe to status notifications of terminal devices that support reader / writer capabilities; the transceiver unit is further used to send a first notification to the Internet of Things functional network element, the first notification including an identifier of the terminal device, the first notification indicating that the terminal device has accessed the network; the transceiver unit is further used to receive tenth information from the Internet of Things functional network element, the tenth information including the reader / writer identifier; and the processing unit is further used to correspondingly save the identifier of the terminal device and the reader / writer identifier.

[0058] Optionally, the transceiver unit is further used to send a second notification to the AMF, where the second notification includes the reader / writer identifier.

[0059] Optionally, the transceiver unit is further used to receive twelfth information from the Internet of Things functional network element, and the twelfth information includes the identification of the terminal device; and the transceiver unit is further used to send thirteenth information to the Internet of Things functional network element, and the thirteenth information includes the tracking area information TAI corresponding to the terminal device.

[0060] In one possible implementation, the communication device of the fifth to sixth aspects includes a unit, module, or means for respectively executing the method of any one of the second to third aspects or any one of their implementations. The unit, module, or means may be implemented in software, hardware, or a combination of software and hardware.

[0061] In another possible implementation, the communication device in the fifth to sixth aspects includes a processor coupled to a memory; the processor is configured to enable the device to perform the corresponding functions in the above-mentioned communication method. The memory is used to couple with the processor and store the necessary programs (instructions) and / or data for the device. Optionally, the communication device may further include a communication interface for enabling communication between the device and other network elements. Optionally, the memory may be located inside or outside the communication device.

[0062] In another possible implementation, the communication device in the fifth to sixth aspects includes a processor and a transceiver, the processor being coupled to the transceiver, and the processor being used to execute a computer program or instruction to control the transceiver to receive and send information; when the processor executes the computer program or instruction, the processor is also used to implement the above method through a logic circuit or execution code instruction. The transceiver may be a transceiver, a transceiver circuit, or an input / output interface, configured to receive signals from other communication devices other than the communication device and transmit them to the processor, or to send signals from the processor to other communication devices other than the communication device. When the communication device is a chip, the transceiver is a transceiver circuit or an input / output interface.

[0063] When the communication device in the fifth and sixth aspects above is a chip, the transmitting unit may be an output unit, such as an output circuit or a communication interface; and the receiving unit may be an input unit, such as an input circuit or a communication interface. When the communication device is a terminal device, the transmitting unit may be a transmitter or a transmitter; and the receiving unit may be a receiver or a receiver.

[0064] In a seventh aspect, a computer-readable storage medium is provided, in which a computer program or instruction is stored. When the computer program or instruction is executed, the methods described in the above aspects are implemented.

[0065] In an eighth aspect, a computer program product comprising instructions is provided, which, when executed on a communication device, causes the communication device to execute the methods described in the above aspects.

[0066] In the ninth aspect, a communication system is provided, which includes an Internet of Things functional network element, the communication device described in the fifth aspect, and the communication device described in the sixth aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0067] FIG1 is a schematic diagram of a communication system provided in an embodiment of the present application;

[0068] Figure 2 is a schematic diagram of the architecture of the environmental Internet of Things;

[0069] Figure 3a is a schematic diagram of the existing network architecture under different reader / writer forms;

[0070] FIG3 b is a schematic diagram of a network architecture under different reader / writer configurations according to an embodiment of the present application;

[0071] FIG4 is a schematic diagram of an existing UE registration process;

[0072] Figure 5 is a schematic diagram of the business process of the base station as a reader;

[0073] Figure 6a is a schematic diagram of an access network device acting as a reader / writer;

[0074] Figure 6b is a schematic diagram of a UE acting as a reader / writer;

[0075] FIG7 is a flow chart of a communication method provided in an embodiment of the present application;

[0076] FIG8 is a flow chart of another communication method provided in an embodiment of the present application;

[0077] FIG9 is a flow chart of another communication method provided in an embodiment of the present application;

[0078] FIG10 is a flow chart of another communication method provided in an embodiment of the present application;

[0079] FIG11 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0080] FIG12 is a schematic structural diagram of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0081] The solution of this application is further described below with reference to the accompanying drawings.

[0082] Figure 1 shows a schematic diagram of a possible, non-limiting communication system. As shown in Figure 1 , communication system 1000 includes a radio access network (RAN) 100 and a core network (CN) 200. Communication system 1000 may also include the Internet 300. RAN 100 includes at least one RAN node (e.g., 110a and 110b in Figure 1 , collectively referred to as 110) and at least one terminal device (e.g., 120a-120j in Figure 1 , collectively referred to as 120). RAN 100 may also include other RAN nodes, such as wireless relay devices and / or wireless backhaul devices (not shown in Figure 1 ). Terminal device 120 is wirelessly connected to RAN node 110. RAN node 110 is wirelessly or wiredly connected to core network 200. The core network devices in core network 200 and RAN node 110 in RAN 100 may be separate physical devices, or they may be a single physical device that integrates core network logical functions and radio access network logical functions.

[0083] The RAN 100 may be a cellular system related to the Third Generation Partnership Project (3GPP), such as a 4G or 5G mobile communication system, or a future-oriented evolutionary system (such as a 6G mobile communication system). The RAN 100 may also be an open radio access network (O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) system. The RAN 100 may also be a communication system that integrates two or more of the above systems.

[0084] RAN node 110, sometimes also referred to as access network equipment, RAN entity, or access node, constitutes part of the communication system and facilitates wireless access for terminal devices. Multiple RAN nodes 110 in communication system 1000 can be of the same type or different types. In some scenarios, the roles of RAN node 110 and terminal device 120 are relative. For example, network element 120i in Figure 1 can be a helicopter or drone, which can be configured as a mobile base station. For terminal device 120j accessing RAN 100 via network element 120i, network element 120i is a base station; however, for base station 110a, network element 120i is a terminal device. RAN node 110 and terminal device 120 are sometimes referred to as communication devices. For example, network elements 110a and 110b in Figure 1 can be understood as communication devices with base station functionality, and network elements 120a-120j can be understood as communication devices with terminal device functionality.

[0085] In one possible scenario, a RAN node can be a base station (BS), an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB), a next-generation NodeB in a sixth-generation (6G) mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system. A RAN node can be a macro base station (such as 110a in Figure 1), a micro base station or an indoor station (such as 110b in Figure 1), a relay node or a donor node, or a wireless controller in a CRAN scenario. Alternatively, a RAN node can be a server, a wearable device, a vehicle, or an onboard device. For example, the access network device in vehicle-to-everything (V2X) technology can be a roadside unit (RSU).

[0086] In another possible scenario, multiple RAN nodes assist terminal devices in achieving wireless access, and different RAN nodes respectively implement part of the functions of the base station. For example, the RAN node can be a centralized unit (CU), a distributed unit (DU), a centralized unit-control plane (CU-CP), a centralized unit-user plane (CU-UP), or a radio unit (RU). The CU and DU can be set separately, or they can be included in the same network element, such as a baseband unit (BBU). The RU can be included in a radio frequency device or a radio frequency unit, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).

[0087] In different systems, CU (or CU-CP and CU-UP), DU or RU may also have different names, but those skilled in the art can understand their meanings. For example, in the ORAN system, CU may also be called an open-centralized unit (open-CU, O-CU), DU may also be called an open-distributed unit (open-distributed unit, O-DU), CU-CP may also be called an open-centralized unit-control plane (open-central unit-control plane, O-CU-CP), CU-UP may also be called an open-centralized unit-user plane (open-central unit-user plane, O-CU-UP), and RU may also be called an open-radio unit (open-radio unit, O-RU). For convenience of description, this application uses CU, CU-CP, CU-UP, DU and RU as examples for description. Any of the CU (or CU-CP, CU-UP), DU and RU in this application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0088] Terminal devices may also be referred to as terminals, user equipment (UE), mobile stations, mobile terminal devices, etc. Terminal devices 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 grid, smart furniture, smart office, smart wearable, smart transportation, smart city, etc. Terminal devices can be mobile phones, tablet computers, computers with wireless transceiver functions, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc. The embodiments of the present application do not limit the device form of the terminal device.

[0089] The communication between the access network device and the terminal device follows a certain protocol layer structure. The protocol layer may include a control plane protocol layer and a user plane protocol layer. The control plane protocol layer may include at least one of the following: a radio resource control (RRC) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, a media access control (MAC) layer, or a physical (PHY) layer. The user plane protocol layer may include at least one of the following: a service data adaptation protocol (SDAP) layer, a PDCP layer, an RLC layer, a MAC layer, or a physical layer.

[0090] Base stations and terminal devices can be fixed or mobile. They can be deployed on land, indoors or outdoors, handheld or vehicle-mounted; on water; or on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of base stations and terminal devices.

[0091] The roles of base stations and terminal devices can be relative. For example, the helicopter or drone 120i in Figure 1 can be configured as a mobile base station. For terminal devices 120j accessing the wireless access network 100 via 120i, terminal device 120i is a base station. However, for base station 110a, 120i is a terminal device, meaning that communication between 110a and 120i occurs via a wireless air interface protocol. Of course, communication between 110a and 120i can also occur via a base station-to-base station interface protocol. In this case, 120i is also a base station relative to 110a. Therefore, base stations and terminal devices can be collectively referred to as communication devices. 110a and 110b in Figure 1 can be referred to as communication devices with base station functionality, and 120a-120j in Figure 1 can be referred to as communication devices with terminal functionality.

[0092] In the embodiments of the present application, a base station is also referred to as an access network device. The device used to implement the functions of the access network device can be the access network device; it can also be a device that can support the access network device in implementing the functions, such as a chip system, a hardware circuit, a software module, or a hardware circuit and a software module. The device can be installed in the access network device or used in conjunction with the access network device. In the embodiments of the present application, only the device used to implement the functions of the access network device is used as an example, and the embodiments of the present application are not limited to the solutions of the embodiments of the present application.

[0093] It can be understood that the present application can be applied between access network equipment and terminal equipment.

[0094] It should be understood that the number and type of each device in the communication system shown in Figure 1 are for illustration only, and the present application is not limited to this. In actual applications, the communication system may also include more terminal devices, more access network devices, and other network elements, such as core network devices, and / or network elements for implementing artificial intelligence functions.

[0095] It is understandable that all or part of the functions implemented by one or more of the terminal equipment, access network equipment, core network equipment, or network elements for implementing artificial intelligence functions can be virtualized, that is, implemented by one or more of the proprietary processors or general-purpose processors and the corresponding software modules. Among them, since the terminal equipment and the access network equipment involve interfaces for air interface transmission, the transceiver functions of the interfaces can be implemented by hardware. Core network equipment, such as operation administration and maintenance (OAM) network elements, can be virtualized. Optionally, one or more functions of the virtualized terminal equipment, access network equipment, core network equipment, or network elements for implementing artificial intelligence functions can be implemented by cloud devices, such as cloud devices in over the top (OTT) systems.

[0096] The embodiments of the present application relate to the ambient Internet of Things (AmbientIoT, A-IoT) (also known as the ambient energy-enabled Internet of Things, or the passive Internet of Things (Passive IoT, P-IoT)), that is, some network nodes may be passive, and they can obtain energy through solar energy, radio frequency, wind energy, water energy or tidal energy, and the method of obtaining energy is not limited. These nodes themselves are not equipped with or do not rely on power devices such as batteries, but obtain energy from the environment to support data perception, transmission and distributed computing. The nodes can also store the obtained energy. As shown in the architectural diagram of the ambient Internet of Things in Figure 2, the ambient Internet of Things architecture may include an Internet of Things device (IoT device) (also known as an Internet of Things terminal), a reader (reader) (also known as a reader), an Internet of Things functional network element, and a server (or an application function (AF) network element). The Internet of Things device can be in the form of a sensor, a tag, etc., or any other terminal form, without limitation. The reader / writer can be an access network device, such as a base station, pole station, micro base station, macro station, integrated access and backhaul (IAB), etc.; or, the reader / writer can be a terminal device, such as a mobile phone, IoT device, handheld reader / writer, etc.

[0097] The following uses IoT devices as tags as an example to explain its communication principle. The reader uses wireless radio frequency to perform contactless two-way data communication, and uses wireless radio frequency to read and write electronic tags or radio frequency cards, thereby achieving the purpose of identifying targets and exchanging data. It works in two ways. One is that when the tag enters the effective identification range of the reader, it receives the radio frequency signal emitted by the reader, and uses the energy obtained from the induced current to send the information stored in the chip (corresponding to a passive tag, or corresponding to passive communication / backscatter communication); the other is that the tag can store part of the electrical energy through solar energy and other means, so that it can actively send a signal of a certain frequency (this can also 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. This technology is widely used in various industries and fields. The following briefly lists two application scenarios:

[0098] Warehouse / Transportation / Supplies: Passive or semi-passive IoT tags are embedded or affixed to goods. During the logistics process of goods stored in warehouses, shopping malls, etc., the relevant information of the goods is automatically collected by readers and writers. Managers can quickly query the goods information in the system, reducing the risk of abandonment or theft, speeding up the delivery of goods, improving the accuracy, and preventing channeling and counterfeiting.

[0099] Fixed asset management: Places with large assets or valuable items, such as libraries, art galleries, and museums, require complete management procedures or rigorous protection measures. When there are abnormal changes in the storage information of books or valuable items, the administrator will be reminded in the system immediately to deal with the relevant situation.

[0100] 2 is an example of a reader / writer being a base station (pole station or macro station), but the present application does not limit the device form of the reader / writer. The base station may also be referred to as a radio access network (RAN) device.

[0101] When a server performs an operation on an IoT device, it can send an operation instruction through the core network. The operation instruction may include, but is not limited to, obtaining tag information, performing an inventory operation (also known as an inventory operation), a read operation, a write operation, an invalidation operation, and exchanging information with the IoT device. The instruction may include regional location information, IoT device identification information, and so on. The base station sends an access instruction to the IoT device. When the tag random access is successful, the base station sends an instruction to the IoT device (the base station may forward the instruction sent by the core network to the IoT device). The IoT device obtains or sends the corresponding information based on the instruction. For example, when the instruction is an inventory instruction or an inventory operation, the IoT device sends its identification information; when the instruction is a read instruction or a read operation, the IoT device sends data stored in its storage area; when the instruction is a write instruction or a write operation, the IoT device stores the data to be written to the IoT device included in the instruction in its storage area. The base station sends (or forwards) the information sent by the IoT device to the core network; and the core network sends this information to the server.

[0102] The server can send instructions through the control plane channel, and the server sends instructions to the IoT management function (IoTF) network element; in this case, the server can be an AF, an application server (AS), or an ambient IoT / passive IoT application function (A-IoT / P-IoT AF) network element. In one possible implementation, the A-IoTAF sends instructions to the IoTF. In another possible implementation, the A-IoT AF sends instructions to the IoTF through a control plane device. The control plane device can be a network exposure function (NEF), a session management function (SMF), a policy control function (PCF), a unified data management (UDM), a network slice-specific and SNPN Authentication and Authorization Function (NSSAAF). The IoT function network element can send instructions to the reader or send instructions through the access and mobility management function (AMF). In addition, the server can also send instructions to the reader / writer through the user plane channel. In one possible implementation, the server sends instructions to the base station through the user plane function (UPF) network element. In another possible implementation, the server sends instructions to the IoTF through the UPF and SMF, and the IoTF sends instructions to the tag through the reader / writer (such as the RAN). In yet another possible implementation, the server sends instructions to the reader / writer through the UPF and access network equipment (when the reader / writer is a terminal device).

[0103] Among them, the Internet of Things functional network element: the name of this function is not limited, and can be ambient IoT function (AIoTF), ambient IoT management function (AIoTMF), IoT terminal management function (IDMF), IoT management function (IoTMF), tag management function (TMF), ambient IoT device management function (AIDMF). This application does not limit the naming of the network element that executes the Internet of Things function, and it can be other names. This application takes AIoTMF as the abbreviation name of the Internet of Things functional network element as an example. AIoTMF can process business requests from business requesters (such as AF) and perform corresponding business operations (such as instructing the reader to perform the inventory process of the Internet of Things device) and transmit instructions (such as read operations, write operations, deactivation operations, etc.). Manage Internet of Things devices, execute security authentication processes, data transmission, etc.

[0104] Access and mobility management function: also known as access and mobility management equipment, access and mobility management function entity, access and mobility management function network element, mobile management equipment, mobile management network element, mobility management entity, is a type of core network equipment. This device can be used to manage access control and mobility of UE. In actual applications, it includes the access and mobility management function in the mobility management entity (MME) in the network framework in long term evolution (LTE), and adds access management functions, which can be responsible for the registration of the user equipment, mobility management, tracking area update process, reachability detection, selection of session management network element, mobile state transition management, etc. For example, in 5G, the access and mobility management network element can be AMF. In future communications, such as 6G, the access and mobility management network element can still be AMF, or have other names, which are not limited in this application. When the access and mobility management network element is AMF, AMF can provide Namf services.

[0105] Unified Data Management: This term may also be referred to as a unified data management device, unified data management network element, data management device, or unified data management entity. The unified data management network element is used to process UE identification, access authentication, registration, and mobility management. In 5G communication systems, unified data management may be referred to as a UDM or unified data management device. In future communication systems, unified data management may also be referred to as a UDM, or may have other names, which are not limited in the embodiments of this application. The unified data management device may be a core network device. The unified data management device may be a control plane device.

[0106] Among them, operations for the environmental Internet of Things may include the following types of operations:

[0107] 1. Inventory operation (or inventory operation), as described above. In one possible implementation, the inventory operation may also include an inventory operation of all IoT devices, that is, obtaining the identification of IoT devices within the coverage range of the reader. It is understandable that this type of operation may be named differently to distinguish the above-mentioned inventory operation, such as an inventory operation of all IoT devices or an unrestricted inventory operation; or, when the identification range of IoT devices in the above-mentioned inventory operation is not limited, it can be understood that the inventory operation is to obtain the identification of IoT devices within the coverage range of the reader.

[0108] 2. Read operations (readcommands) involve reading data from an IoT device. IoT devices can have storage capabilities, and their storage areas can store data. If the requester wishes to read from an IoT device, they send a service request to the network. Based on the service request, the network sends instructions to the reader / writer. The reader / writer then performs a read operation on the IoT device, reading the data from the IoT device's storage area and sending it to the server.

[0109] 3. Write operation (write command), that is, writing data to the IoT device. The operation requester can send a write command to the reader / writer. The reader / writer performs the write operation on the IoT device according to the command and writes data to the storage area of ​​the IoT device.

[0110] 4. Disable or kill operations, which disable an IoT device. The requester can send a service request to the network to disable the IoT device. The network then sends a disable instruction to the reader. This instruction can include the IoT device's identifier (i.e., the identifier of the IoT device to be disabled). The reader then disables the IoT device based on the disable instruction. Once the operation is complete, the IoT device becomes disabled and cannot be inventoried or subjected to other operations.

[0111] 5. Obtain the information of the IoT device. In one possible implementation, the reader / writer obtains or receives the information of the IoT device sent by the IoT device. The reader / writer sends the information of the IoT device to the operation requester or the core network device. In one possible implementation, before the reader / writer obtains the information of the IoT device sent by the IoT device, the reader / writer may receive an operation instruction and send the operation instruction to the IoT device; the operation instruction may come from the operation requester or from the core network device, and this application does not impose any restrictions. In one possible implementation, the information of the IoT device may include identification information of the IoT device and / or information stored by the IoT device.

[0112] 6. Message Interaction with IoT Devices. In one possible implementation, the reader sends a message from the operation requester (server or application) to the IoT device. In another possible implementation, the reader receives the message from the IoT device and sends the message from the IoT device to the operation requester (server or application). In another possible implementation, the reader can exchange messages with the IoT device, such as exchanging random numbers, before receiving the message from the IoT device.

[0113] 7. Send a payload to the IoT device. In one possible implementation, the server or AF can send a payload to the IoT device through a reader / writer. After the reader / writer receives the payload from the server or AF, it sends the payload to the IoT device. In another possible implementation, the core network device can send a payload to the IoT device through a reader / writer. After the reader / writer receives the payload from the core network device, it sends the payload to the IoT device. For example, the payload here can be an instruction sent by the core network device, server or AF to the IoT device, data written by the core network device, server or AF to the IoT device, application layer information sent by the core network device, server or AF to the IoT device, etc., or the payload here can also be other information related to the IoT device, which is not limited in this application.

[0114] 8. Positioning operation. That is, locating the IoT device or obtaining the location information of the IoT device. In one possible implementation, the obtained location information may include one or more of coordinate values, longitude and latitude, cell identifier, tracking area identifier, network identifier, and the like. In one possible implementation, the positioning operation may include the IoT device sending a signal for performing positioning, the reader receiving the signal to perform positioning, or receiving the signal and sending it to a functional device that performs location calculation (such as a location management function (LMF)) to perform location calculation.

[0115] The reader / writer may have various forms, for example, the reader / writer may be a base station or a terminal device.

[0116] Figure 3a shows a schematic diagram of the existing network architecture for different reader / writer configurations. When a base station (e.g., RAN) acts as a reader / writer, an IoT functional network element (e.g., AIoTMF) can establish a direct communication interface (e.g., the N2' interface) with the base station. When the reader / writer is a terminal device (e.g., UE), it can access the network as a 3GPP UE. Therefore, an AMF serving the UE exists, and an interface exists between the AMF and the AIoTMF.

[0117] Figure 3b shows a schematic diagram of the network architecture under different reader / writer forms in an example embodiment of the present application. Unlike the architecture shown in Figure 3a, when the reader / writer is a UE, there is no interface between the AMF and the AIoTMF, and the AIoTMF sends IoT device service operation instructions to the UE through the RAN.

[0118] The embodiments of this application will involve the UE registration process. First, let's understand the existing UE registration process.

[0119] FIG4 is a schematic diagram of an existing UE registration process. The process includes the following steps:

[0120] S401. The UE sends a registration request message to the RAN, which carries the registration type and the UE's identification information (subscription concealed identifier (SUCI), 5G globally unique temporary identifier (5G-GUTI), or permanent equipment identifier (PEI)). The registration types are as follows:

[0121] 1) Initial registration: The registration process initiated when the UE is in the deregistered state;

[0122] 2) Mobility registration update: A registration process initiated when the UE moves.

[0123] 3) Periodic registration update: When the UE is in the registered state, the registration process is initiated due to the periodic registration update counter timeout;

[0124] 4) Emergency registration: A registration procedure initiated when the UE is in a service-restricted state.

[0125] For the UE's identification information, when the UE has a valid 5G-GUTI (a temporary identity assigned by the AMF serving it), the 5G-GUTI is carried in the registration request; if the UE does not have a valid 5G-GUTI, it carries SUCI; in an emergency registration, if the UE has no valid 5G-GUTI and no SUPI (i.e. no SUCI, SUCI is an encrypted SUPI), it carries PEI.

[0126] S402.RAN selects a suitable AMF.

[0127] S403.RAN sends the registration request message sent by the UE to the AMF. After receiving the registration request message sent by the UE, the AMF can determine the narrowband Internet of Things (NB-IoT) access technology for the UE based on the cell accessed by the UE (in this case, the cell accessed by the UE is a NB-IoT dedicated cell).

[0128] S404.AMF selects an appropriate authentication server function (AUSF) network element to perform authentication and other security processes; the UE, AMF, AUSF, and UDM interact to complete the authentication and other security processes; for 3GPP UEs, the authentication process is a two-way authentication between the UE and the network.

[0129] S405. After the UE and the network successfully authenticate each other, the AMF interacts with the UDM to obtain the UE's subscription data.

[0130] S406. The AMF sends an N2 message to the RAN, which includes a non-access-stratum (NAS) message that the RAN needs to forward to the UE. The NAS message includes a registration acceptance message sent by the AMF to the UE.

[0131] S407. RAN forwards the registration accept message sent by AMF to the UE.

[0132] The following describes the business process when the base station acts as a reader:

[0133] Figure 5 shows a schematic diagram of the service process when the base station acts as a reader / writer. The process may include the following steps:

[0134] S501. The AF sends a service request (e.g., an inventory service request) to the NEF. The message may include the AF identifier and, optionally, the location information where the service operation needs to be performed. In one possible implementation, the message may be Nnef_AIoT_Inventory Request, indicating a request to perform an inventory operation.

[0135] S502.NEF selects AIoTMF according to the configuration, for example, selects AIoTMF according to the AF identifier and / or location information.

[0136] S503.NEF sends a service request message to AIoTMF, which may include AF identification and, optionally, location information where the service operation needs to be performed. In one possible implementation, the message may be Naiotmf_AIoT_Inventory Request, indicating a request to perform an inventory operation.

[0137] S504.AIoTMF can interact with UDM to perform authorization of business requests. For example, UDM can store information related to the AF, such as area information where operations are allowed to be performed, and identification information of the IoT device corresponding to the AF, such as an identification prefix. AIoTMF can select a base station (i.e., select a reader) based on location information; optionally, mask information (i.e., an identification prefix) can be generated; subsequent readers can broadcast the mask information, so that the IoT device corresponding to the mask information will respond to the network and send the identification of the IoT device to the network. Therefore, when the mask information indicates the IoT device corresponding to the AF, the IoT device that is within the coverage of the reader and corresponds to the AF will respond to the network to send an identification, so that the inventory operation can be performed only on the IoT device corresponding to the AF.

[0138] S505. AIoTMF sends an inventory message to RAN, including task ID and mask information.

[0139] S506. RAN broadcasts the mask information to the IoT device.

[0140] S507. The IoT device matching the mask information performs random access.

[0141] S508. The IoT device that has successfully random accessed sends a device identifier to the RAN. In one possible implementation, the device identifier is encapsulated in a NAS message and sent to the RAN via an RRC message.

[0142] S509.RAN sends the device identifier from the IoT device to AIoTMF.

[0143] S510.AIoTMF can interact with UDM to perform device identification verification, determine the identification of the IoT device corresponding to the AF, and then execute subsequent steps.

[0144] S511.AIoTMF sends a response message to NEF, carrying the device identifier of the IoT device.

[0145] S512.NEF sends a response message to AF, carrying the device identifier of the IoT device.

[0146] The current architecture design primarily considers scenarios where the access network device acts as a reader / writer (or, more accurately, the current architecture design primarily considers the reader / writer as the access network device). Figure 6a shows a schematic diagram of an access network device acting as a reader / writer. Supporting the UE as a reader / writer also requires consideration (see Figure 6b for a schematic diagram of a UE acting as a reader / writer). IoT devices are low-power and low-complexity, especially passive ones (or those that rely on reflected carriers for communication). They require network stimulation or receive energy from the environment, such as solar energy or wind power. Furthermore, after a power outage, IoT devices cannot record status information (such as session identification or registration status) and are not connected. Therefore, whether the access network device acts as a reader / writer or the UE acts as a reader / writer, the communication mechanism and process of IoT devices should be kept consistent to minimize the complexity and impact on IoT devices. Specifically, the design approach is to avoid the need to design multiple signaling processes for IoT device-reader interaction due to the diverse form factors of readers / writers. Instead, IoT devices should utilize a single mechanism to interact with readers / writers of different form factors.

[0147] Currently, for the base station as a reader / writer, the network uses the Internet of Things functional network element (for example, called AIoTMF or AIoTF) to execute service requests from AF and perform service authorization based on the service requests; send operation instructions to the base station, so that the reader / writer can send operation instructions to the Internet of Things device to complete the corresponding operations (such as reading, writing, inventory, invalidation, etc.).

[0148] If a UE can be used as a reader / writer and can be compatible with a process similar to that shown in Figure 5, network deployment costs can be greatly reduced or the flexibility of reader / writer deployment can be improved. Therefore, a communication method is urgently needed to enable the UE to use a similar communication interface architecture and process to complete operations when used as a reader / writer.

[0149] Since AIoTMF has the ability to process business requests from application function network elements and perform business request authorization, in order to be compatible with the scenario where the reader is a UE, AIoTMF needs to send instructions to the UE in some way. There are currently two possible alternatives: one is that AIoTMF issues instructions through the AMF serving the UE; the other is that AIoTMF issues instructions through the RAN serving the UE. The former requires that AIoTMF needs to have a communication interface with AMF, while the latter does not. Therefore, if the former idea is adopted, when using UE as a reader, the enterprise also needs to deploy AMF and AIoTMF, which is costly, and the transmission of data through the upper network will bring security issues. If the latter idea is adopted, the enterprise does not need to deploy AMF, and the AMF serving the UE can be a regular AMF in the public network.

[0150] Therefore, this application intends to improve how to send instructions to the reader / writer (UE) without the participation of AMF based on the latter idea, so that a set of architectures can be used to enable RAN as a reader / writer and UE as a reader / writer.

[0151] In view of this, the present application provides a communication solution, in which the IoT functional network element obtains a reader / writer identifier and carries the reader / writer identifier in the first information sent to the access network device, and the access network device obtains the reader / writer identifier from the core network device. Therefore, the access network device can determine to send a service request message to the target terminal device serving as a reader / writer based on the reader / writer identifier obtained from the IoT functional network element and the core network device, so that the target terminal device can perform service operations on the IoT device, thereby improving the IoT operation process of the terminal device as a reader / writer, and there is no need to deploy a new AMF, reducing the network functions involved and reducing deployment costs.

[0152] The following describes the communication method provided by the embodiment of the present application based on the above communication system:

[0153] As shown in Figure 7, a flow chart of a communication method provided in an embodiment of the present application is shown. Exemplarily, the method may include the following steps:

[0154] S701. AF sends a service request message to the IoT function. Correspondingly, the IoT function receives the service request message.

[0155] In this embodiment, a third-party application initiates a business operation on an IoT device. Exemplarily, the AF may send a business request message to the IoT function through the NEF. When the AF sends a business request message to the IoT function through the NEF, the message name of the business request message sent by the AF to the NEF and the business request message sent by the NEF to the IoT function may be the same or different. It is understandable that the business request message sent by the NEF to the IoT function is determined based on the business request message sent by the AF to the NEF. The IoT function is a function for processing IoT services, managing IoT devices, etc., and may be set up in an enterprise campus. The business request message may, for example, be a request to perform at least one business operation such as: inventory, reading, writing, invalidation, obtaining information of IoT devices, performing message interaction operations with IoT devices, sending loads to IoT devices, and positioning. This application does not limit the specific content of the business request message.

[0156] In this embodiment, the UE acts as a reader / writer of the IoT device.

[0157] In one possible implementation, the service request message may include an identifier of the UE serving as the reader / writer. For example, the UE identifier may be an external identifier of the UE (e.g., a general public subscription identifier (GPSI)) or a permanent identifier (e.g., a user permanent identifier (SUPI)).

[0158] Exemplarily, the service request message may include identifiers of one or more UEs.

[0159] In another possible implementation, the service request message may not include the identifier of the UE acting as a reader / writer; the IoT function may determine that the service operation needs to be performed on the IoT device through the UE acting as a reader / writer based on the configuration information or the location information included in the service request message.

[0160] S702: The IoT function sends first information to the access network device. Correspondingly, the access network device receives the first information.

[0161] For AIoT services, without the participation of AMF, there is currently no corresponding operation process for how AIoTMF sends business operation instructions to UE so that UE can perform business operations on IoT devices.

[0162] After receiving the above-mentioned service request message, the IoT function determines the reader / writer. In one possible implementation, the reader / writer is determined to be a UE. In one possible implementation, the service request message may include the identifier of the UE serving as a reader / writer, and the IoT function may determine the reader / writer based on the identifier of the UE. In another possible implementation, the service request message may not include the identifier of the UE serving as a reader / writer; the IoT function may determine that it is necessary to perform service operations on the IoT device through the UE serving as a reader / writer based on the configuration information or the location information included in the service request message. In one possible implementation, the configuration information may indicate the UE serving as a reader / writer corresponding to the service request from the AF, for example, the configuration information may include the identification information of one or more UEs serving as readers / writers corresponding to the AF. In another possible implementation, one or more UEs serving as readers / writers are deployed in the area corresponding to the location information included in the service request message, and the IoT function may determine that service operations on the IoT device are performed through the UE serving as a reader / writer based on the location information.

[0163] Specifically, the Internet of Things function can determine the access network device accessed by the UE, or determine the area information or location information where the UE is located, and determine the access network device corresponding to the area information or location information. For example, the area information or location information can be a tracking area identity (TAI), and the Internet of Things function determines the access network device corresponding to the TAI based on the TAI. Therefore, the Internet of Things function network element can send a first message to the access network device. The first information indicates that a service operation is performed on the Internet of Things device through the UE. In this application, the area information or location information where the UE is located may include one or more of the following information: TAI, the AMF identifier of the serving UE, the Internet of Things function identifier of the serving UE, the UDM identifier of the serving UE, the RAN identifier to which the UE is connected, the base station identifier to which the UE is connected (for example, gNB ID or basestation ID), the cell identifier to which the UE is connected, the tracker identifier where the UE is located, the closed access group identifier (CAG) to which the UE is connected, longitude and latitude, and coordinate values.

[0164] In this embodiment, the first information includes a reader ID. The reader ID is an identifier used to distinguish the UE. The reader ID can be other names, which is not limited in this application. In one possible implementation, the reader ID can include one or more of the following information: the AMF identifier serving the UE, the IoT function identifier serving the UE, the UDM identifier serving the UE, the RAN identifier to which the UE is connected, the base station identifier to which the UE is connected (e.g., gNB ID), the cell identifier to which the UE is connected, the tracker identifier to which the UE is located, the closed access group identifier to which the UE is connected, and an identifier used to distinguish different UEs.

[0165] The reader / writer identifier is determined according to the UE identifier and can be generated by the IoT functional network element itself or obtained from other network elements.

[0166] In a possible implementation, the first information includes information indicating a business operation, such as inventory information.

[0167] S703. The access network device determines the UE according to the reader identifier.

[0168] The access network device receives the first information and obtains the reader / writer identifier carried in the first information (the reader / writer identifier can be regarded as the first reader / writer identifier).

[0169] The access network device determines the identifier of the UE corresponding to the reader / writer identifier based on the correspondence between the identifier of the terminal device and the reader / writer identifier, for example, based on the correspondence between the radio network temporary identifier (RNTI) and the reader / writer identifier. In one possible implementation, the access network device may include the reader / writer identifier corresponding to the UE in the context of the UE. When the access network device receives the first information and obtains the reader / writer identifier, it may determine the context of the UE containing the reader / writer identifier based on the context of one or more UEs, thereby determining the target UE. In another possible implementation, the access network device may store the correspondence between the UE identifier and the reader / writer identifier, for example, using the reader / writer identifier as an index. When the access network device obtains the reader / writer identifier from the first information, it may retrieve the identifier of the UE corresponding to the reader / writer identifier based on the reader / writer identifier, thereby determining the target UE.

[0170] Exemplarily, the access network device compares the reader / writer identifier (second reader / writer identifier) ​​obtained from the core network device with the reader / writer identifier (first reader / writer identifier) ​​carried in the first message and, if they are identical, determines that the UE is the reader / writer. Optionally, the first message is sent to the UE, or information included in the first message indicating the execution of a service operation is sent to the UE. Specifically, the first message instructs the UE corresponding to the reader / writer identifier to perform a service operation on the IoT device.

[0171] For example, the first information may include a list of reader identifiers, which may include the reader identifiers of one or more UEs. Thus, after receiving the first information, the access network device retrieves the context of each UE and compares the reader identifier included in each UE's context with the reader identifier carried in the first information, thereby determining one or more target UEs.

[0172] S704. The access network device instructs the UE to perform service operations on the IoT device.

[0173] After the access network device determines the target UE, it instructs the target UE to perform service operations on the IoT device.

[0174] In one possible implementation, the access network device instructing the UE to perform a service operation on the IoT device can be understood or replaced by the access network device sending an inventory request (e.g., an inventory request) to the UE. The inventory request is used to trigger one or more IoT devices to initiate random access, and after successful random access, information about the IoT devices (e.g., IoT device identifiers and / or stored data) is sent to the network.

[0175] According to a communication method provided in an embodiment of the present application, the Internet of Things functional network element obtains a reader / writer identifier and carries the reader / writer identifier in the first information sent to the access network device, and the access network device obtains the reader / writer identifier from the core network device. Therefore, the access network device can determine to send a service request message to the target UE serving as a reader / writer based on the reader / writer identifier obtained from the Internet of Things functional network element and the core network device, so that the target UE can perform service operations on the Internet of Things device, thereby improving the Internet of Things operation process of the UE serving as a reader / writer.

[0176] The above embodiment describes the issuance of service operation instructions through reader identification. The following three embodiments will describe how to determine the reader identification:

[0177] The following embodiments are described using the IoT functional network element as AIoTMF as an example.

[0178] FIG8 is a flow chart of another communication method provided in an embodiment of the present application. In this embodiment, the reader identifier is assigned by the UDM. Exemplarily, the method may include the following steps:

[0179] S801. The UE sends a registration request message to the RAN, and the RAN receives the registration request message.

[0180] For the specific content of the registration request message, please refer to step S401 of the embodiment shown in FIG. 4 .

[0181] Optionally, the UE may further include first indication information (which may be understood as reader capability information) in the registration request message to indicate that the UE has reader capability. In one possible implementation, the UE may include a displayed indication information (e.g., reader capability indication (readercapableindication)) in the registration request message, or add an information element (IE) (e.g., adding a preferred network behavior in the preferred network behavior IE) to indicate that the UE is a reader. The IE may be used to indicate whether it supports being a reader (whethersupportreadercapability) or whether to activate reader mode (whetheractivatereadermode).

[0182] The RAN selects an appropriate AMF and sends the Registration Request message sent by the UE to the AMF.

[0183] S802. The UE executes a security process with the AMF, AUSF, and UDM to complete two-way authentication between the UE and the network.

[0184] S803.AMF registers with UDM / UDR.

[0185] The AMF and UDM / UDR learn that the UE has reader / writer capabilities or is allowed to act as a reader / writer.

[0186] In one possible implementation, after receiving the registration request message sent by the UE, the AMF may send fourth information to the UDM / UDR according to the first indication information in S801, indicating that the UE supports the reader / writer capability. That is, the UDM / UDR may determine whether the UE supports the reader / writer capability based on the fourth information sent by the AMF.

[0187] In another possible implementation, the UE does not include the first indication information in S801. The UDM / UDR includes in the subscription data the subscription data indicating that the UE has reader / writer capability or is allowed to act as a reader / writer. The UDM / UDR may send the reader / writer capability information to the AMF. Through the above steps, the AMF and UDM / UDR may learn that the UE has reader / writer capability or is allowed to act as a reader / writer.

[0188] S804. UDM obtains the reader / writer identification.

[0189] After the UDM learns that the UE is a reader / writer, it obtains the reader / writer identification.

[0190] In a possible implementation, the UDM allocates / generates a reader / writer identifier.

[0191] In another possible implementation, the UDM is configured with reader identifiers, and the UDM selects one as the reader identifier of the UE.

[0192] In another possible implementation, the UE's subscription data stored by the UDM includes an external identifier, such as GPSI. The UDM can use this information as the reader identifier, that is, the reader identifier is the external identifier (such as GPSI). The UDM can store the reader identifier in the UE's subscription data.

[0193] S805a.AMF sends a subscription data acquisition request message (eg, Nudm_SDM get Request) to the UDM. Correspondingly, the UDM receives the subscription data acquisition request message.

[0194] S805b. The UDM sends the fifth message to the AMF. In response, the AMF receives the fifth message, which includes the reader / writer identifier.

[0195] For example, in the subscription data acquisition process, the UDM may send a subscription data acquisition response message (e.g., Nudm_SDM get Response) to the AMF. Accordingly, the AMF receives the subscription data acquisition response message. The subscription data acquisition response message includes the reader identifier obtained by the UDM.

[0196] S806. The AMF sends the sixth information to the access network device. Correspondingly, the access network device receives the sixth information, wherein the sixth information includes the reader / writer identifier.

[0197] For example, during the registration process, the AMF may send an N2 message to the RAN, and the RAN receives the N2 message accordingly.

[0198] The N2 message includes the reader identifier of the UE.

[0199] In one possible implementation, the UE context sent by the AMF includes the reader identifier.

[0200] In another possible implementation, the RAN stores the reader identifier in the UE context (i.e., using the RAN UE NGAP ID as an index to obtain the reader identifier), or in independent context information, such as reader information (i.e., using the reader identifier as an index to obtain the corresponding per UE (per UE) information, such as the UE's N2 identifier, the UE's identifier on the air interface side, or the radio network temporary identifier (RNTI), etc.

[0201] S807.AMF sends a registration accept message to the UE. Correspondingly, the UE receives the registration accept message.

[0202] Optionally, the registration acceptance message may include the reader identifier.

[0203] S808. AF sends a service request message (eg, inventory service request) to NEF. Correspondingly, NEF receives the service request message.

[0204] The service request message may include an AF identifier and an identifier of the UE serving as the reader / writer (e.g., GPSI) (or may include identifiers of one or more UEs (e.g., a GPSI list)). Optionally, the service request message may include location information requiring the UE to perform service operations on the IoT device.

[0205] S809. NEF sends a service request message to AIoTMF. Correspondingly, AIoTMF receives the service request message.

[0206] Exemplarily, NEF selects AIoTMF based on the service request message, for example, selects AIoTMF based on the AF identifier and / or location information; or when AF provides GPSI information, NEF obtains the corresponding SUPI information based on GPSI; in one possible implementation method, NEF can select AIoTMF based on SUPI (for example, select AIoTMF based on the SUPI number segment).

[0207] NEF sends a service request message to AIoTMF, where the service request message includes AF identity and / or SUPI information.

[0208] S810. AIoTMF interacts with UDM to obtain the reader identifier corresponding to the SUPI.

[0209] In one possible implementation, the service request message sent by NEF to AIoTMF includes SUPI information. AIoTMF sends second information to UDM, where the second information includes the UE identifier. Exemplarily, the second information indicates the acquisition of the reader / writer identifier of the UE. After receiving the second information, UDM sends third information to AIoTMF, where the third information includes the reader / writer identifier. Optionally, the third information may include the location information corresponding to the UE (e.g., one or more of TAI, cell identifier, RAN identifier, gNB identifier, and base station identifier).

[0210] In addition, the AIoTMF may send twelfth information to the UDM, where the twelfth information includes the identifier of the UE. For example, the twelfth information indicates the acquisition of the location information corresponding to the UE. After receiving the twelfth information, the UDM may send thirteenth information to the AIoTMF, and accordingly, the AIoTMF receives the thirteenth information. The thirteenth information includes the location information corresponding to the UE, such as one or more of the tracking area information (TAI), cell identifier, RAN identifier, gNB identifier, base station identifier, longitude and latitude, and coordinate values ​​corresponding to the UE.

[0211] In another possible implementation, when the service request message sent by NEF to AIoTMF does not include SUPI information, AIoTMF can determine the identifier of the AF corresponding to the reader UE based on the configuration information, and interact with UDM to obtain the reader identifier corresponding to the UE identifier.

[0212] In another possible implementation, when the service request sent by NEF to AIoTMF includes location information, AIoTMF can determine the reader / writer deployed in the area corresponding to the location information based on the location information. When the reader / writer is a UE, AIoTMF obtains the reader / writer identifier or obtains the identifier of the UE. Exemplarily, if AIoTMF obtains the identifier of the UE, it can interact with UDM to obtain the reader / writer identifier corresponding to the identifier of the UE. For example, AIoTMF can send location information to UDM, and UDM obtains the information of the UE corresponding to the location information (such as UE identifier) ​​or the information of the UE as a reader / writer (such as reader / writer identifier and / or UE identifier) ​​based on the configuration or other network functions (such as positioning management function, LMF). UDM sends the information of the UE corresponding to the location information (such as UE identifier) ​​or the information of the UE as a reader / writer (such as reader / writer identifier and / or UE identifier) ​​to AIoTMF.

[0213] S811. The AIoTMF selects a RAN based on the location information and / or TAI. The AIoTMF sends the first information to the selected RAN (e.g., via an N2' message). Accordingly, the RAN receives the first information. In one possible implementation, the location information may include latitude and longitude, coordinate values, cell identifier, RAN identifier, base station identifier, gNB identifier, TAI, etc.

[0214] The first information indicates that a service operation is performed on the IoT device through the UE. The first information includes a reader / writer identifier.

[0215] S812. RAN determines the target UE according to the reader identifier.

[0216] For example, after receiving the first information, the RAN retrieves the context of each UE. If the reader / writer identifier contained in the UE context is the same as the reader / writer identifier from the AIoTMF, the UE is determined to be the reader / writer that needs to perform the service operation. Alternatively, if the RAN separately stores the correspondence between the reader / writer identifier and the UE's N2 / air interface identifier, the RAN can obtain the UE's N2 / air interface identifier based on the reader / writer identifier and determine the target UE.

[0217] S813. RAN sends a service operation to the target UE (eg, via an RRC message). In one possible implementation, RAN sends an inventory (eg, Inventory) to the target UE.

[0218] S814. The reader / writer UE interacts with the IoT device to complete a business operation (eg, completing an inventory or read operation).

[0219] S815. The UE sends information from the IoT device, such as an identifier of the IoT device, to the RAN (e.g., via an RRC message).

[0220] S816.RAN sends information from the IoT device, such as the identifier of the IoT device, to the AIoTMF (e.g., via an N2' message).

[0221] S817. AIoTMF sends a service request response message to NEF. The service request response message includes information about the IoT device, such as an identifier of the IoT device.

[0222] S818.NEF sends a service request response message to AF. The service request response message includes information of the IoT device, such as an identifier of the IoT device.

[0223] According to a communication method provided in an embodiment of the present application, after UDM learns that a UE with reader / writer capabilities or that performs reader / writer functions has registered (accessed the network), a reader / writer identifier is assigned to the UE, and the reader / writer identifier is sent to the RAN through AMF, so that when the IoT business process is subsequently executed, the target UE can be determined only by the reader / writer identifier. The AIoTMF does not need to send business operations to the RAN through the AMF, thus avoiding the participation of the AMF, reducing the core network devices that need to participate, reducing the tortuous paths of business transmission in the IoT business process, reducing deployment costs, and improving the IoT operation process of the UE as a reader / writer.

[0224] FIG9 is a flow chart of another communication method provided in an embodiment of the present application. In this embodiment, the reader / writer identifier is assigned by the AMF. Exemplarily, the method may include the following steps:

[0225] S901. The UE sends a registration request message to the RAN, and the RAN receives the registration request message.

[0226] For the specific content of the registration request message, please refer to step S401 of the embodiment shown in FIG. 4 .

[0227] Optionally, the UE may also include first indication information (which may be understood as reader capability information) in the registration request message, for indicating that the UE has reader capability. For the specific implementation of the first indication information, reference may be made to step S801 of the embodiment shown in FIG8 .

[0228] RAN selects the appropriate AMF.

[0229] The RAN sends the seventh information to the AMF. Accordingly, the AMF receives the seventh information. The seventh information indicates that the UE supports the reader / writer capability. For example, in the registration process, the RAN may send a registration request message sent by the UE to the AMF, where the registration request message indicates that the UE supports the reader / writer capability.

[0230] S902. The UE executes a security process with the AMF, AUSF, and UDM to complete two-way authentication between the UE and the network.

[0231] S903.AMF obtains the reader / writer identifier.

[0232] After the AMF learns that the UE is a reader / writer, it obtains the reader / writer identifier.

[0233] In one possible implementation, AMF allocates / generates a reader / writer identifier.

[0234] In another possible implementation, the AMF is configured with a reader / writer identifier, and the AMF selects one as the reader / writer identifier of the UE.

[0235] The AMF may store the UE identifier and the reader identifier accordingly.

[0236] S904.AMF sends the reader / writer identifier of the UE to the UDM. Optionally, the AMF may send the reader / writer capability information and / or location information (e.g., TAI) of the UE to the UDM. In one possible implementation, the AMF sends a connection management registration message to the UDM. Accordingly, the UDM receives the UE connection management registration message. In one possible implementation, if the AMF does not send the reader / writer identifier to the UDM in step 904, it may send it to the UDM in step 905a, or send the reader / writer identifier to the UDM after the UDM authorizes the UE to act as a reader / writer.

[0237] The UE connection management registration message includes the UE's reader capability information, TAI, and the UE's reader identifier.

[0238] The UDM can determine whether the UE is allowed to act as a reader / writer based on the contract data, and indicate to the AMF in the UE Connection Management Registration Response message whether the UE is authorized to act as a reader / writer. Optionally, the UDM can also feedback the authorization information in S905b. In one possible implementation, when the UDM does not authorize the UE to act as a reader / writer, it can send information to the AMF indicating that the UE is not authorized to act as a reader / writer.

[0239] S905a. Optionally, the AMF sends ninth information to the UDM. Accordingly, the UDM receives the ninth information. The ninth information includes a reader identifier. In one possible implementation, if the AMF sends the reader identifier in step 904, then there is no need to send the reader identifier in step 905a. Alternatively, if the UDM indicates in step 904 that the UE is not authorized to act as a reader, the AMF may not send the reader identifier in step 905a and may not send the reader identifier to the RAN in the subsequent step 906.

[0240] For example, in the subscription data acquisition process, the AMF may send a subscription data acquisition request message (eg, Nudm_SDM get Request) to the UDM. Correspondingly, the UDM receives the subscription data acquisition request message.

[0241] UDM stores the correspondence between the UE identifier and the reader identifier.

[0242] S905b. UDM sends a subscription data acquisition response message (e.g., Nudm_SDM get Response) to AMF. Correspondingly, AMF receives the subscription data acquisition response message.

[0243] Optionally, the subscription data acquisition response message includes information indicating that the UE is authorized to act as a reader / writer.

[0244] S906. The AMF sends the eighth information to the RAN. Correspondingly, the RAN receives the eighth information, wherein the eighth information includes the reader / writer identifier.

[0245] For example, in the registration process, the AMF may send an N2 message to the RAN, and the RAN receives the N2 message accordingly.

[0246] The N2 message includes the reader identifier of the UE.

[0247] In one possible implementation, the UE context sent by the AMF includes the reader identifier.

[0248] In another possible implementation, the RAN stores the reader identifier in the UE context (i.e., using the RAN UE NGAP ID as an index to obtain the reader identifier), or stores it in independent context information, such as reader information (i.e., using the reader identifier as an index to obtain the corresponding per-UE information, such as the UE's N2 identifier, the UE's identifier on the air interface side, or the RNTI, etc.

[0249] S907. The AMF sends a registration accept message to the UE. Correspondingly, the UE receives the registration accept message.

[0250] Optionally, the reader identifier may be included in the registration acceptance message.

[0251] S908. AF sends a service request message (eg, inventory service request) to NEF. Correspondingly, NEF receives the service request message.

[0252] The service request message may include an AF identifier and an identifier of the UE serving as the reader / writer (e.g., GPSI) (or may include identifiers of one or more UEs (e.g., a GPSI list)). Optionally, the service request message may also include location information requiring the UE to perform service operations on the IoT device.

[0253] S909. NEF sends a service request message to AIoTMF. Correspondingly, AIoTMF receives the service request message.

[0254] Exemplarily, NEF selects AIoTMF based on the service request message, for example, selects AIoTMF based on the AF identifier and / or location information; or when AF provides GPSI information, NEF obtains the corresponding SUPI information based on GPSI; in one possible implementation method, NEF can select AIoTMF based on SUPI (for example, select AIoTMF based on the SUPI number segment).

[0255] NEF sends a service request message to AIoTMF, where the service request message includes AF identity and / or SUPI information.

[0256] S910. AIoTMF interacts with UDM to obtain the reader identifier corresponding to the SUPI.

[0257] In one possible implementation, when the service request message sent by NEF to AIoTMF includes SUPI information. AIoTMF sends second information to UDM, where the second information includes the UE identifier. Exemplarily, the second information indicates the acquisition of the reader / writer identifier of the UE. After receiving the second information, UDM sends third information to AIoTMF, where the third information includes the reader / writer identifier. Optionally, the third information may include the location information corresponding to the UE (e.g., one or more of TAI, cell identifier, RAN identifier, gNB identifier, and base station identifier).

[0258] In addition, the AIoTMF may send twelfth information to the UDM, where the twelfth information includes the UE identifier. For example, the twelfth information indicates obtaining the location information corresponding to the UE. After receiving the twelfth information, the UDM may send thirteenth information to the AIoTMF, and accordingly, the AIoTMF receives the thirteenth information. The thirteenth information includes the location information corresponding to the UE, such as one or more of the TAI, cell identifier, RAN identifier, gNB identifier, base station identifier, longitude and latitude, and coordinate values ​​corresponding to the UE.

[0259] In another possible implementation, when the service request message sent by NEF to AIoTMF does not include SUPI information, AIoTMF can determine the identifier of the AF corresponding to the reader UE based on the configuration information, and interact with UDM to obtain the reader identifier corresponding to the UE identifier.

[0260] In another possible implementation, when the service request sent by NEF to AIoTMF includes location information, AIoTMF can determine the reader / writer deployed in the area corresponding to the location information based on the location information. When the reader / writer is a UE, AIoTMF obtains the reader / writer identifier or obtains the identifier of the UE. Exemplarily, if AIoTMF obtains the identifier of the UE, it can interact with UDM to obtain the reader / writer identifier corresponding to the identifier of the UE. For example, AIoTMF can send location information to UDM, and UDM obtains the information of the UE corresponding to the location information (such as UE identifier) ​​or the information of the UE as a reader / writer (such as reader / writer identifier and / or UE identifier) ​​based on the configuration or other network functions (such as positioning management function, LMF). UDM sends the information of the UE corresponding to the location information (such as UE identifier) ​​or the information of the UE as a reader / writer (such as reader / writer identifier and / or UE identifier) ​​to AIoTMF.

[0261] S911. The AIoTMF selects a RAN based on the location information and / or TAI. The AIoTMF sends (e.g., via an N2' message) first information to the selected RAN. Accordingly, the RAN receives the first information. In one possible implementation, the location information may include latitude and longitude, coordinate values, cell identifier, RAN identifier, base station identifier, gNB identifier, TAI, etc.

[0262] The first information indicates that a service operation is performed on the IoT device through the UE. The first information includes a reader / writer identifier.

[0263] S912. RAN determines the target UE according to the reader identifier.

[0264] For example, the RAN retrieves the context of each UE. If the reader / writer identifier contained in the UE context is the same as the reader / writer identifier from the AIoTMF, the UE is determined to be the reader / writer that needs to perform the service operation. Alternatively, if the RAN separately stores the correspondence between the reader / writer identifier and the UE's N2 / air interface identifier, the RAN can obtain the UE's N2 / air interface identifier based on the reader / writer identifier and determine the target UE.

[0265] S913. RAN sends a service operation to the target UE (eg, via an RRC message). In one possible implementation, RAN sends an inventory (eg, Inventory) to the target UE.

[0266] S914. The reader / writer UE interacts with the IoT device to complete a business operation (eg, completing an inventory or read operation).

[0267] S915. The UE sends information from the IoT device, such as an identifier of the IoT device, to the RAN (e.g., via an RRC message).

[0268] S916.RAN sends information from the IoT device, such as the identifier of the IoT device, to the AIoTMF (e.g., via an N2' message).

[0269] S917. AIoTMF sends a service request response message to NEF. The service request response message includes information about the IoT device, such as an identifier of the IoT device.

[0270] S918. The NEF sends a service request response message to the AF. The service request response message includes information about the IoT device, such as an identifier of the IoT device.

[0271] According to a communication method provided by an embodiment of the present application, after AMF learns that a UE with reader / writer capabilities or that performs reader / writer functions has registered (accessed the network), it allocates a reader / writer identifier and sends the reader / writer identifier to UDM and RAN respectively, so that when the IoT business process is subsequently executed, the target UE can be determined only by the reader / writer identification information. The AIoTMF does not need to send business operations to the RAN through the AMF, thus avoiding the participation of the AMF, reducing the core network equipment that needs to be involved, reducing the tortuous paths of business transmission in the IoT business process, reducing deployment costs, and improving the IoT operation process with the UE as a reader / writer.

[0272] As shown in Figure 10, a flow chart of another communication method provided in an embodiment of the present application is provided. In this embodiment, the reader / writer identifier is allocated by the AIoTMF. Exemplarily, the method may include the following steps:

[0273] S1001. AIoTMF sends a subscription request to UDM. In response, UDM receives the subscription request.

[0274] AIoTMF can subscribe to the UDM (or UDR) for status notifications of UEs that support reader / writer capabilities (or subscribe to events of UEs with reader / writer capabilities). When a UE can act as a reader / writer or supports (has) reader / writer capabilities, it can notify AIoTMF.

[0275] Optionally, the subscription request may include notifying the AIoTMF of the status of the UE with reader capability (for example, one or more different states such as registration state, deregistration state, connection state or idle state) or the core network device information serving the UE (for example, information of core network devices such as AMF, SMF, PCF, etc.).

[0276] The subscription request may not include a UE identifier (ie, does not indicate any UE), which can be understood as not subscribing to events of a specific UE, but rather any UE with reader / writer capabilities or allowed to act as a reader / writer may be included in the subscription.

[0277] Optionally, when AIoTMF obtains (for example, pre-configures) which UEs can have a reader / writer, the subscription request may correspond to the UE. At this time, the subscription response may include identification information of one or more UEs, such as SUPI, GPSI, SUCI, etc. This application does not limit the identification information of the UE.

[0278] Typically, the UE's subscription data stored in the UDM (or UDR) may include information that the UE has reader / writer capabilities, or information that the UE is allowed to be a reader / writer. Based on this information (or when this information is added, updated, or deleted), the UDM (or UDR) can send a subscription response to the AIoTMF. The subscription response may include the identification information of one or more UEs and the information of one or more core network devices serving the UE (such as the identification information of core network devices such as AMF, SMF, PCF, such as identifier (ID), internet protocol (IP) address, or fully qualified domain name (FQDN)).

[0279] S1002. The UE sends a registration request message to the RAN, and the RAN receives the registration request message.

[0280] For the specific content of the registration request message, please refer to step S401 of the embodiment shown in FIG. 4 .

[0281] Optionally, the UE may also include first indication information (which may be understood as reader capability information) in the registration request message, for indicating that the UE has reader capability. For the specific implementation of the first indication information, reference may be made to step S801 of the embodiment shown in FIG8 .

[0282] The RAN selects an appropriate AMF and sends the Registration Request message sent by the UE to the AMF.

[0283] S1003. The UE executes a security process with the AMF, AUSF, and UDM to complete two-way authentication between the UE and the network.

[0284] S1004.AMF registers with UDM.

[0285] For example, the AMF sends a UE Connection Management Registration message to the UDM, which includes the UE's reader / writer capability information and TAI. The UDM can determine whether the UE is allowed to act as a reader / writer based on the subscription data and indicate to the AMF in the Connection Management Registration Response message whether the UE is authorized to act as a reader / writer. Optionally, the UDM can also feedback the authorization information in S1005.

[0286] S1005a. The AMF sends a subscription data acquisition request message (eg, Nudm_SDM get Request) to the UDM. Correspondingly, the UDM receives the subscription data acquisition request message.

[0287] S1005b. UDM sends a subscription data acquisition response message (e.g., Nudm_SDM get Response) to AMF. Correspondingly, AMF receives the subscription data acquisition response message.

[0288] Optionally, the subscription data acquisition response message includes information indicating that the UE is authorized to act as a reader / writer.

[0289] S1006. UDM sends a notification to AIoTMF, and AIoTMF receives the notification accordingly.

[0290] The notification may include the SUPI of the UE and, optionally, the location information of the UE (e.g., TAI). Optionally, the notification may include the GPSI of the UE and information about the network element serving the UE (e.g., AMF information). The notification may indicate that the UE has accessed the network (or that the UE has registered with the network as a reader / writer).

[0291] The notification instructs the UE to access the network. “Instructing the UE to access the network” may be “instructing the UE to register with the network”, “instructing the UE to be in a registered state”, or “instructing the UE to be in a connected state”, etc.

[0292] S1007.AIoTMF obtains the reader / writer identification.

[0293] In one possible implementation, AIoTMF can allocate / generate a reader / writer identifier.

[0294] Exemplarily, the reader / writer identifier may include identification information of the AIoTMF, thereby ensuring that the reader / writer identifier is unique.

[0295] In another possible implementation, the AIoTMF is configured with one or more reader / writer identifiers, and the AIoTMF selects one and assigns it to the UE, so that the UE corresponds to one of the reader / writer identifiers.

[0296] AIoTMF records the correspondence between the UE's SUPI and the reader identifier. Optionally, AIoTMF can record the correspondence between the UE's SUPI and the reader identifier and TAI.

[0297] S1008. The AIoTMF sends the tenth information to the UDM. Correspondingly, the UDM receives the tenth information, wherein the tenth information includes the reader / writer identifier.

[0298] After UDM obtains the reader / writer identification from AIoTMF, it can be stored in the UE's subscription data (or context).

[0299] S1009. The UDM sends a first notification to the AMF. Accordingly, the AMF receives the first notification. The first notification includes the UE identifier and the reader identifier. Exemplarily, the first notification is used to notify the user of a subscription data update.

[0300] For example, in the subscription data acquisition process, the UDM may send a subscription data notification message to the AMF. Correspondingly, the AMF receives the subscription data notification message.

[0301] The subscription data notification message is used to notify the AMF of subscription data updates. The subscription data notification message includes the UE's SUPI and reader identifier.

[0302] S1010. The AMF sends the eleventh message to the RAN. Correspondingly, the RAN receives the eleventh message, wherein the eleventh message includes the reader / writer identifier.

[0303] For example, during the registration process, the AMF may send an N2 message to the RAN, and the RAN receives the N2 message accordingly.

[0304] The N2 message includes the NGAP identifier corresponding to the UE and the reader identifier of the UE.

[0305] In one possible implementation, the UE context sent by the AMF includes the reader identifier.

[0306] In another possible implementation, the RAN stores the reader identifier in the UE context (i.e., using the RAN UE NGAP ID as an index to obtain the reader identifier), or stores it in independent context information, such as reader information (i.e., using the reader identifier as an index to obtain the corresponding per-UE information, such as the UE's N2 identifier, the UE's identifier on the air interface side, or the RNTI, etc.

[0307] S1011. The AMF sends a registration accept message to the UE. Correspondingly, the UE receives the registration accept message.

[0308] Optionally, the reader identifier may be included in the registration acceptance message.

[0309] S1012. The AF sends a service request message (eg, an inventory service request) to the NEF. Correspondingly, the NEF receives the service request message.

[0310] The service request message may include an AF identifier and an identifier of the UE serving as the reader / writer (e.g., GPSI) (or may include identifiers of one or more UEs (e.g., a GPSI list)). Optionally, the service request message may also include location information requiring the UE to perform service operations on the IoT device.

[0311] S1013. NEF sends a service request message to AIoTMF. Correspondingly, AIoTMF receives the service request message.

[0312] Exemplarily, NEF selects AIoTMF based on the service request message, for example, selects AIoTMF based on the AF identifier and / or location information; or when AF provides GPSI information, NEF obtains the corresponding SUPI information based on GPSI; in one possible implementation method, NEF can select AIoTMF based on SUPI (for example, select AIoTMF based on the SUPI number segment).

[0313] NEF sends a service request message to AIoTMF, where the service request message includes AF identity and / or SUPI information.

[0314] In another possible implementation, when the service request message sent by NEF to AIoTMF does not include SUPI information, AIoTMF can determine the identifier of the AF corresponding to the reader UE based on the configuration information, and interact with UDM to obtain the reader identifier corresponding to the UE identifier.

[0315] In another possible implementation, when the service request sent by NEF to AIoTMF includes location information, AIoTMF can determine the reader / writer deployed in the area corresponding to the location information based on the location information. When the reader / writer is a UE, AIoTMF obtains the reader / writer identifier or obtains the identifier of the UE. Exemplarily, if AIoTMF obtains the identifier of the UE, it can interact with UDM to obtain the reader / writer identifier corresponding to the identifier of the UE. For example, AIoTMF can send location information to UDM, and UDM obtains the information of the UE corresponding to the location information (such as UE identifier) ​​or the information of the UE as a reader / writer (such as reader / writer identifier and / or UE identifier) ​​based on the configuration or other network functions (such as positioning management function, LMF). UDM sends the information of the UE corresponding to the location information (such as UE identifier) ​​or the information of the UE as a reader / writer (such as reader / writer identifier and / or UE identifier) ​​to AIoTMF.

[0316] S1014. The AIoTMF selects a RAN based on the location information and / or TAI. The AIoTMF sends the first information to the selected RAN (e.g., via an N2' message). Accordingly, the RAN receives the first information. In one possible implementation, the location information may include latitude and longitude, coordinate values, cell identifier, RAN identifier, base station identifier, gNB identifier, TAI, etc.

[0317] The first information indicates that a service operation is performed on the IoT device through the UE. The first information includes a reader / writer identifier.

[0318] S1015. RAN determines the target UE according to the reader identifier.

[0319] For example, the RAN retrieves the context of each UE. If the reader / writer identifier contained in the UE context is the same as the reader / writer identifier from the AIoTMF, the UE is determined to be the reader / writer that needs to perform the service operation. Alternatively, if the RAN separately stores the correspondence between the reader / writer identifier and the UE's N2 / air interface identifier, the RAN can obtain the UE's N2 / air interface identifier based on the reader / writer identifier and determine the target UE.

[0320] S1016. RAN sends a service operation to the target UE (eg, via an RRC message). In one possible implementation, RAN sends an inventory (eg, Inventory) to the target UE.

[0321] S1017. The reader / writer UE interacts with the IoT device to complete a business operation (eg, completing an inventory or read operation).

[0322] S1018. The UE sends information from the IoT device, such as an identifier of the IoT device, to the RAN (e.g., via an RRC message).

[0323] S1019.RAN sends information from the IoT device, such as the identifier of the IoT device, to the AIoTMF (e.g., via an N2' message).

[0324] S1020. AIoTMF sends a service request response message to NEF. The service request response message includes information about the IoT device, such as an identifier of the IoT device.

[0325] S1021. The NEF sends a service request response message to the AF. The service request response message includes information about the IoT device, such as an identifier of the IoT device.

[0326] According to a communication method provided in an embodiment of the present application, the status notification of the UE supporting the reader / writer capability is subscribed to the UDM through AIoTMF, so that after knowing that the UE supporting the reader / writer function has accessed the network, a reader / writer identifier is assigned to the UE, and the reader / writer identifier is sent to the UDM, so that when the IoT business process is subsequently executed, the target UE can be determined only by the reader / writer identification information. The AIoTMF sends the business operation to the RAN through the AMF, avoiding the participation of the AMF, reducing the core network equipment that needs to participate, reducing the circuitous path of business transmission in the IoT business process, reducing the deployment cost, and improving the IoT operation process of the UE as a reader / writer.

[0327] It can be understood that in each of the above embodiments, the methods and / or steps implemented by the IoT functional network element can also be implemented by components (such as chips or circuits) that can be used for IoT functional network elements; the methods and / or steps implemented by UDM can also be implemented by components (such as chips or circuits) that can be used for UDM; the methods and / or steps implemented by AMF can also be implemented by components (such as chips or circuits) that can be used for AMF.

[0328] The above primarily describes the solutions provided by the embodiments of the present application from the perspective of interaction between various network elements. Accordingly, the embodiments of the present application also provide a communication device for implementing the various methods described above. This communication device can be an IoT functional network element in the aforementioned method embodiments, or a component that can be used for an IoT functional network element; alternatively, this communication device can be a UDM in the aforementioned method embodiments, or a component that can be used for a UDM; alternatively, this communication device can be an AMF in the aforementioned method embodiments, or a component that can be used for an AMF. It will be understood that, to implement the aforementioned functions, the communication device includes hardware structures and / or software modules corresponding to each function. Those skilled in the art will readily appreciate that, in conjunction with the various exemplary units and algorithm steps described in the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is implemented in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this application.

[0329] In the embodiment of the present application, the functional modules of the communication device can be divided according to the above method embodiment. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing unit. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. In actual implementation, there may be other division methods.

[0330] Based on the same concept of the above communication method, the present application also provides the following communication device:

[0331] As shown in FIG11 , it is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. The communication device 1100 includes a transceiver unit 1101 and a processing unit 1102.

[0332] Illustratively, the transceiver unit 1101 may include a receiving unit and a sending unit. The receiving unit and the sending unit may be a whole or independent units.

[0333] When the communication device 1100 is used to implement the function of UDM, the transceiver unit 1101 is used to implement one or more operations performed by the UDM in steps S803, S805a, S805b, and S810 of the embodiment shown in Figure 8, and the processing unit 1102 is used to implement step S804 of the embodiment shown in Figure 8; or, the transceiver unit 1101 is used to implement one or more operations performed by the UDM in steps S904, S905a, S905b, and S910 of the embodiment shown in Figure 9; or, the transceiver unit 1101 is used to implement one or more operations performed by the UDM in steps S1001, S1004, S1005a, S1005b, S1006, S1008, and S1009 of the embodiment shown in Figure 10.

[0334] When the communication device 1100 is used to implement the functions of the Internet of Things functional network element, the transceiver unit 1101 is used to implement one or more operations performed by the Internet of Things functional network element in steps S701 and S702 of the embodiment shown in Figure 7; or, the transceiver unit 1101 is used to implement one or more operations performed by the Internet of Things functional network element in steps S809, S810, S811, S816, and S817 of the embodiment shown in Figure 8; or, the transceiver unit 1101 is used to implement one or more operations performed by the Internet of Things functional network element in steps S909, S910, S911, S916, and S917 of the embodiment shown in Figure 9; or, the transceiver unit 1101 is used to implement one or more operations performed by the Internet of Things functional network element in steps S1001, S1004, S1005a, S1005b, S1006, S1008, and S1009 of the embodiment shown in Figure 10, and the processing unit 1102 is used to implement step S1007 of the embodiment shown in Figure 10.

[0335] When the communication device 1100 is used to implement the function of AMF, the transceiver unit 1101 is used to implement one or more operations performed by the AMF in steps S801, S802, S803, S805a, S805b, S806, and S807 of the embodiment as shown in Figure 8; or, the transceiver unit 1101 is used to implement one or more operations performed by the AMF in steps S901, S902, S904, S905a, S905b, S906, and S907 of the embodiment as shown in Figure 9, and the processing unit 1102 is used to implement step S903 of the embodiment as shown in Figure 9; or, the transceiver unit 1101 is used to implement one or more operations performed by the AMF in steps S1002, S1003, S1004, S1005a, S1005b, S1009, S1010, and S1011 of the embodiment as shown in Figure 10.

[0336] For the specific implementation of the above-mentioned transceiver unit 1101 and the processing unit 1102, reference may be made to the relevant descriptions in the embodiments shown in FIG. 7 to FIG. 10 .

[0337] The division of modules in this application is illustrative and represents only a logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional modules in the examples of this application may be integrated into a single processor, exist physically as separate modules, or two or more modules may be integrated into a single module. The aforementioned integrated modules may be implemented in either hardware or software functional modules.

[0338] As shown in Figure 12, it is a schematic diagram of the structure of another communication device provided in an embodiment of the present application, and the communication device 1200 includes a processor 1201. Optionally, the communication device 1200 may further include an interface circuit 1202 (indicated by a dotted line in the figure), and the processor 1201 and the interface circuit 1202 are coupled to each other. It will be understood that the interface circuit 1202 may be a transceiver or an input / output interface. Optionally, the communication device 1200 may further include a memory 1203 (indicated by a dotted line in the figure), and the memory 1203 is used to store instructions executed by the processor 1201, or to store input data required by the processor 1201 to run the instructions, or to store data generated after the processor 1201 runs the instructions.

[0339] When the communication device 1200 is used to implement the function of UDM, the interface circuit 1202 is used to implement one or more operations performed by the UDM in steps S803, S805a, S805b, and S810 of the embodiment shown in Figure 8, and the processor 1201 is used to implement step S804 of the embodiment shown in Figure 8; or, the interface circuit 1202 is used to implement one or more operations performed by the UDM in steps S904, S905a, S905b, and S910 of the embodiment shown in Figure 9; or, the interface circuit 1202 is used to implement one or more operations performed by the UDM in steps S1001, S1004, S1005a, S1005b, S1006, S1008, and S1009 of the embodiment shown in Figure 10.

[0340] When the communication device 1200 is used to implement the functions of the Internet of Things functional network element, the interface circuit 1202 is used to implement one or more operations performed by the Internet of Things functional network element in steps S701 and S702 of the embodiment shown in Figure 7; or, the interface circuit 1202 is used to implement one or more operations performed by the Internet of Things functional network element in steps S809, S810, S811, S816, and S817 of the embodiment shown in Figure 8; or, the interface circuit 1202 is used to implement one or more operations performed by the Internet of Things functional network element in steps S909, S910, S911, S916, and S917 of the embodiment shown in Figure 9; or, the interface circuit 1202 is used to implement one or more operations performed by the Internet of Things functional network element in steps S1001, S1004, S1005a, S1005b, S1006, S1008, and S1009 of the embodiment shown in Figure 10, and the processor 1201 is used to implement step S1007 of the embodiment shown in Figure 10.

[0341] When the communication device 1200 is used to implement the function of AMF, the interface circuit 1202 is used to implement one or more operations performed by the AMF in steps S801, S802, S803, S805a, S805b, S806, and S807 of the embodiment shown in Figure 8; or, the interface circuit 1202 is used to implement one or more operations performed by the AMF in steps S901, S902, S904, S905a, S905b, S906, and S907 of the embodiment shown in Figure 9, and the processor 1201 is used to implement step S903 of the embodiment shown in Figure 9; or, the interface circuit 1202 is used to implement one or more operations performed by the AMF in steps S1002, S1003, S1004, S1005a, S1005b, S1009, S1010, and S1011 of the embodiment shown in Figure 10.

[0342] When the above-mentioned communication device is a chip applied to an IoT functional network element, the chip implements the functions of the IoT functional network element in the above-mentioned method embodiment. The chip receives information from other modules (such as a radio frequency module or antenna) in the IoT functional network element, and the information is sent by the UDM to the IoT functional network element or the AMF; or the chip sends information to other modules (such as a radio frequency module or antenna) in the IoT functional network element, and the information is sent by the IoT functional network element to the UDM or the AMF.

[0343] When the communication device is a chip used in a UDM, the chip implements the UDM functionality in the method embodiment. The chip receives information from other modules in the UDM (such as a radio frequency module or antenna), which is sent to the UDM by an IoT functional network element or an AMF; or the chip sends information to other modules in the UDM (such as a radio frequency module or antenna), which is sent to the UDM by an IoT functional network element or an AMF.

[0344] When the above-mentioned communication device is a chip applied to AMF, the chip implements the functions of AMF in the above-mentioned method embodiment. The chip receives information from other modules in the AMF (such as a radio frequency module or antenna), and the information is sent to the AMF by the IoT functional network element or UDM; or the chip sends information to other modules in the AMF (such as a radio frequency module or antenna), and the information is sent to the IoT functional network element or UDM by the AMF.

[0345] In addition, it should be noted that the aforementioned transceiver unit and / or processing unit may be implemented through virtual modules, for example, the processing unit may be implemented through a software function unit or a virtual device, and the transceiver unit may be implemented through a software function or a virtual device. Alternatively, the processing unit or transceiver unit may also be implemented through a physical device, for example, if the device is implemented using a chip / chip circuit, the transceiver unit may be an input / output circuit and / or a communication interface, performing input operations (corresponding to the aforementioned receiving operations) and output operations (corresponding to the aforementioned sending operations); the processing unit is an integrated processor or microprocessor or integrated circuit.

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

[0347] An embodiment of the present application further provides a computer-readable storage medium, in which a computer program or instruction is stored. When the computer program or instruction is executed, the method in the above embodiment is implemented.

[0348] An embodiment of the present application further provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the method in the above embodiment.

[0349] An embodiment of the present application also provides a communication system, including the above-mentioned communication device.

[0350] The present application also provides a circuit, which is coupled to a memory and is used to execute the method shown in the above embodiment. The circuit may include a chip circuit.

[0351] An embodiment of the present application also provides a chip device, including a processor, for calling a computer program or computer instruction stored in the memory so that the processor executes the method provided in any one of the embodiments shown in Figures 7 to 10 above.

[0352] In one possible implementation, the input of the chip device corresponds to the receiving operation in any one of the embodiments shown in FIG. 7 to FIG. 10 , and the output of the chip device corresponds to the sending operation in any one of the embodiments shown in FIG. 7 to FIG. 10 .

[0353] Optionally, the processor is coupled to the memory via an interface.

[0354] Optionally, the chip device further includes a memory, in which computer programs or computer instructions are stored.

[0355] When the above-mentioned communication device is a module applied to a network device, the network device module implements the functions of the network device in the above-mentioned method embodiment. The network device module receives information from other modules in the network device (such as a radio frequency module or an antenna), and the information is sent by the terminal device to the network device; or, the network device module sends information to other modules in the network device (such as a radio frequency module or an antenna), and the information is sent by the network device to the terminal device. The network device module here can be a baseband chip of the network device, or a CU, DU or other module, or a device under the O-RAN architecture, such as an open CU, open DU and other devices.

[0356] It should be noted that the above units or one or more of the units can be implemented by software, hardware, or a combination of the two. When any of the above units or units is implemented by software, the software exists in the form of computer program instructions and is stored in a memory, and a processor can be used to execute the program instructions and implement the above method flow.

[0357] In this application, a processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the methods, steps, and logic block diagrams disclosed in this application. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in this application may be directly executed by a hardware processor, or by a combination of hardware and software modules within the processor.

[0358] When the above units or units are implemented in hardware, the hardware can be any one or any combination of a CPU, a microprocessor, a digital signal processing (DSP) chip, a microcontroller unit (MCU), an artificial intelligence processor, an ASIC, a SoC, an FPGA, a programmable logic device (PLD), a dedicated digital circuit, a hardware accelerator or a non-integrated discrete device, which can run the necessary software or not rely on the software to execute the above method flow.

[0359] Optionally, an embodiment of the present application further provides a chip system, comprising: at least one processor and an interface, wherein the at least one processor is coupled to a memory via the interface, and when the at least one processor executes a computer program or instruction in the memory, the chip system executes the method in any of the above method embodiments. Optionally, the chip system may be composed of a chip, or may include a chip and other discrete devices, which is not specifically limited in the embodiments of the present application.

[0360] The memory in the present application may also be a circuit or any other device capable of implementing a storage function for storing program instructions and / or data. A memory is any other medium that can be used to carry or store a desired program code in the form of an instruction or data structure and can be accessed by a computer, but is not limited thereto. For example, the memory may be a non-volatile memory, such as a digital versatile disc (DVD), a hard disk drive (HDD), or a solid-state drive (SSD), or a volatile memory, such as a random-access memory (RAM).

[0361] It is understood that, in this application, "indication" can include direct indication, indirect indication, explicit indication, and implicit indication. When describing a certain indication information as indicating A, it can be understood that the indication information carries A, directly indicates A, or indirectly indicates A. In this application, the information indicated by the indication information is referred to as the information to be indicated. In the specific implementation process, there are many ways to indicate the information to be indicated. For example, but not limited to, the information to be indicated can be directly indicated, such as the information to be indicated itself or an index of the information to be indicated, or it can be indirectly indicated by indicating other information, where there is an association between the other information and the information to be indicated. It is also possible to indicate only a part of the information to be indicated, while the rest of the information to be indicated is known or agreed in advance. For example, it is also possible to indicate specific information by using a pre-agreed (e.g., protocol-specified) order of arrangement of various information, thereby reducing the indication overhead to a certain extent. The information to be indicated can be sent as a whole or divided into multiple sub-information and sent separately, and the sending period and / or sending time of these sub-information can be the same or different. The specific sending method is not limited in this application. The sending period and / or sending timing of these sub-information may be predefined, for example, predefined according to a protocol, or may be configured by the transmitting end device by sending configuration information to the receiving end device.

[0362] The at least one (item) involved in this application indicates one (item) or more (items). More than one (item) refers to two (items) or more than two (items). "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. In addition, it should be understood that although the terms first, second, etc. may be used to describe each object in this application, these objects should not be limited to these terms. These terms are only used to distinguish each object from each other.

[0363] The terms "including" and "having" mentioned above and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include other steps or units that are not listed, or may optionally include other steps or units that are inherent to these processes, methods, products or devices. It should be noted that, in this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or explanations. Any method or design described in this application as "exemplary" or "for example" should not be interpreted as being more preferred or more advantageous than other methods or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a concrete way.

[0364] A network element in a communication system can send a signal to another network element or receive a signal from another network element. The signal may include information, signaling, or data, etc. The network element can also be replaced by an entity, a network entity, a device, a terminal device, a communication module, a node, a communication node, etc. The present application uses the network element as an example for description. For example, the communication system may include at least one terminal device and at least one network device. The network device can send a downlink signal to the terminal device, and / or the terminal device can send an uplink signal to the network device. In addition, it can be understood that if the communication system includes multiple terminal devices, the multiple terminal devices can also send signals to each other, that is, the signal sending network element and the signal receiving network element can both be terminal devices.

[0365] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using a software program, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means.

[0366] Although the present application is described herein in conjunction with various embodiments, in the process of implementing the claimed application, those skilled in the art can understand and implement other changes to the disclosed embodiments by reviewing the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude multiple situations. A single processor or other unit can implement several functions listed in the claims. Certain measures are recorded in different dependent claims, but this does not mean that these measures cannot be combined to produce good results.

[0367] It is understood that the various numbers used in the embodiments of this application are merely for ease of description and are not intended to limit the scope of the embodiments of this application. The order of the sequence numbers of the above-mentioned processes does not necessarily imply a specific order of execution; the order of execution of the processes should be determined by their functions and inherent logic.

[0368] In the above embodiments, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0369] The components in the device of the embodiment of the present application can be merged, divided, or deleted according to actual needs. Those skilled in the art can combine or combine the different embodiments and features of the different embodiments described in this specification.

[0370] In this application, under the premise of no logical contradiction, the examples can reference each other, for example, the methods and / or terms between method embodiments can reference each other, for example, the functions and / or terms between device embodiments can reference each other, for example, the functions and / or terms between device examples and method examples can reference each other.

Claims

1. A communication method, characterized in that: The method comprises: The Internet of Things functional network element receives a service request message, where the service request message includes an identifier of a terminal device serving as a reader / writer; The Internet of Things functional network element sends first information to the access network device, where the first information instructs the terminal device to perform business operations on the Internet of Things device. The first information includes a reader / writer identifier, which is determined based on the identifier of the terminal device.

2. The method according to claim 1, wherein The method further comprises: The Internet of Things functional network element sends second information to the unified data management function UDM, where the second information includes an identifier of the terminal device; The Internet of Things functional network element receives third information from the UDM, where the third information includes the reader / writer identifier.

3. The method according to claim 2, wherein The method further comprises: The access and mobility management function AMF sends fourth information to the UDM, where the fourth information indicates that the terminal device supports reader / writer capabilities; The UDM allocates the reader / writer identification to the terminal device based on the fourth information.

4. The method according to claim 2 or 3, wherein: The method further comprises: The UDM sends fifth information to the AMF, where the fifth information includes the reader identifier; The AMF sends sixth information to the access network device, where the sixth information includes the reader / writer identifier.

5. The method according to claim 2, wherein The method further comprises: The AMF receives seventh information sent by the access network device, where the seventh information indicates that the terminal device supports reader / writer capabilities; The AMF allocates the reader / writer identifier to the terminal device based on the seventh information; The AMF sends the eighth information to the access network device, where the eighth information includes the reader / writer identifier.

6. The method according to claim 5, wherein The method further comprises: The UDM receives the ninth information sent by the AMF, where the ninth information includes the reader identifier; The UDM stores the correspondence between the identifier of the terminal device and the identifier of the reader / writer.

7. The method according to claim 1, wherein The method further comprises: The IoT functional network element sends a subscription request to the UDM, where the subscription request is used to subscribe to status notifications of terminal devices that support reader / writer capabilities; The UDM sends a first notification to the Internet of Things functional network element, where the first notification includes an identifier of the terminal device and instructs the terminal device to access a network; The Internet of Things functional network element allocates the reader / writer identifier to the terminal device.

8. The method according to claim 7, wherein The method further comprises: The Internet of Things functional network element sends tenth information to the UDM, where the tenth information includes the reader identifier; The UDM stores the correspondence between the identifier of the terminal device and the identifier of the reader / writer.

9. The method according to claim 8, wherein The method further comprises: The UDM sends a second notification to the AMF, where the second notification includes the reader identifier; The AMF sends an eleventh message to the access network device, where the eleventh message includes the reader / writer identifier.

10. The method according to any one of claims 1 to 9, wherein Before the Internet of Things functional network element sends the first information to the access network device, the method further includes: The Internet of Things functional network element sends twelfth information to the UDM, where the twelfth information includes an identifier of the terminal device; The UDM sends thirteenth information to the Internet of Things functional network element, where the thirteenth information includes tracking area information TAI corresponding to the terminal device; The Internet of Things functional network element determines the access network device based on the TAI of the terminal device.

11. The method according to any one of claims 1 to 10, wherein The method further comprises: The access network device determines the terminal device according to the reader / writer identifier; The access network device instructs the terminal device to perform service operations on the Internet of Things device.

12. A communication method, characterized in that: The method comprises: The access and mobility management function AMF obtains the reader / writer identification of the terminal device, and the terminal device supports the reader / writer capability; The AMF sends the reader identifier to the access network device.

13. The method according to claim 12, wherein: The AMF obtains the reader / writer identification of the terminal device, including: The AMF sends fourth information to the UDM, where the fourth information indicates that the terminal device supports reader / writer capabilities; The AMF receives fifth information from the UDM, where the fifth information includes the reader / writer identifier.

14. The method according to claim 12, wherein: The AMF obtains the reader / writer identification of the terminal device, including: The AMF receives seventh information from the access network device, where the seventh information indicates that the terminal device supports reader / writer capabilities; The AMF allocates the reader / writer identifier to the terminal device based on the seventh information.

15. The method according to any one of claims 12 to 14, wherein: The AMF sends the reader / writer identifier to the access network device, including: the AMF sends the eighth information to the access network device, and the eighth information includes the reader / writer identifier.

16. The method according to any one of claims 12 to 15, wherein: The method also includes: the AMF sending ninth information to the UDM, where the ninth information includes the reader / writer identifier.

17. The method according to claim 12, wherein The AMF obtains the reader / writer identifier of the terminal device, including: the AMF receives a second notification from the UDM, where the second notification includes the reader / writer identifier.

18. A communication method, characterized in that: The method comprises: The unified data management function UDM obtains a reader / writer identifier of a terminal device, where the terminal device supports reader / writer capabilities; The UDM sends the reader identifier to the AMF.

19. The method according to claim 18, wherein The method further comprises: The UDM receives second information from the IoT functional network element, where the second information includes an identifier of the terminal device; The UDM sends third information to the Internet of Things functional network element, where the third information includes the reader / writer identifier.

20. The method according to claim 18 or 19, wherein The UDM obtains the reader / writer identification of the terminal device, including: The UDM receives fourth information from the AMF, where the fourth information indicates that the terminal device supports reader / writer capabilities; The UDM allocates the reader / writer identification to the terminal device based on the fourth information.

21. The method according to claim 20, wherein The UDM sends the reader identifier to the AMF, including: The UDM sends fifth information to the AMF, where the fifth information includes the reader / writer identifier.

22. The method according to claim 18 or 19, wherein: The UDM obtains the reader / writer identification of the terminal device, including: The UDM receives ninth information from the AMF, where the ninth information includes the reader / writer identifier; The UDM stores the correspondence between the identifier of the terminal device and the identifier of the reader / writer.

23. The method according to claim 18 or 19, wherein: The UDM obtains the reader / writer identification of the terminal device, including: The UDM receives a subscription request from an IoT functional network element, wherein the subscription request is used to subscribe to status notifications of terminal devices supporting reader / writer capabilities; The UDM sends a first notification to the Internet of Things functional network element, where the first notification includes an identifier of the terminal device and instructs the terminal device to access a network; The UDM receives tenth information from the IoT functional network element, where the tenth information includes the reader / writer identifier; The UDM stores the identifier of the terminal device and the identifier of the reader / writer.

24. The method according to claim 23, wherein The UDM sends the reader / writer identifier to the AMF, including: the UDM sends a second notification to the AMF, where the second notification includes the reader / writer identifier.

25. The method according to any one of claims 18 to 24, wherein The method further comprises: The UDM receives twelfth information from the Internet of Things functional network element, where the twelfth information includes an identifier of the terminal device; The UDM sends thirteenth information to the Internet of Things functional network element, and the thirteenth information includes the tracking area information TAI corresponding to the terminal device.

26. A communication system, characterized in that: The system includes terminal equipment, IoT functional network elements and access network equipment; wherein: The Internet of Things functional network element is used to receive a service request message, where the service request message includes an identifier of the terminal device serving as a reader / writer; The Internet of Things functional network element is also used to send first information to the access network device, where the first information instructs the terminal device to perform business operations on the Internet of Things device. The first information includes a reader / writer identifier, and the reader / writer identifier is determined based on the identifier of the terminal device.

27. The system of claim 26, wherein: The system also includes a unified data management function UDM; wherein: The Internet of Things functional network element is further configured to send second information to the UDM, where the second information includes an identifier of the terminal device; The Internet of Things functional network element is further used to receive third information from the UDM, where the third information includes the reader / writer identifier.

28. The system of claim 27, wherein: The system further includes an access and mobility management function (AMF); wherein: The AMF is used to send fourth information to the UDM, where the fourth information indicates that the terminal device supports reader / writer capabilities; The UDM is used to allocate the reader / writer identification to the terminal device based on the fourth information.

29. The system according to claim 27 or 28, characterized in that: The UDM is further configured to send fifth information to the AMF, where the fifth information includes the reader identifier; The AMF is also used to send sixth information to the access network device, where the sixth information includes the reader / writer identifier.

30. The system of claim 27, wherein: The AMF is used to receive seventh information sent by the access network device, where the seventh information indicates that the terminal device supports reader / writer capabilities; The AMF is further used to allocate the reader / writer identifier to the terminal device based on the seventh information; The AMF is also used to send eighth information to the access network device, where the eighth information includes the reader / writer identifier.

31. The system of claim 30, wherein: The UDM is used to receive the ninth information sent by the AMF, where the ninth information includes the reader identifier; The UDM is further used to store the correspondence between the identifier of the terminal device and the identifier of the reader / writer.

32. The system of claim 26, wherein: The IoT functional network element is further configured to send a subscription request to the UDM, wherein the subscription request is used to subscribe to status notifications of terminal devices supporting reader / writer capabilities; The UDM is used to send a first notification to the Internet of Things functional network element, where the first notification includes an identifier of the terminal device and instructs the terminal device to access the network; The Internet of Things functional network element is also used to allocate the reader / writer identifier to the terminal device.

33. The system of claim 32, wherein: The Internet of Things functional network element is further configured to send tenth information to the UDM, wherein the tenth information includes the reader / writer identifier; The UDM is further used to store the correspondence between the identifier of the terminal device and the identifier of the reader / writer.

34. The system of claim 33, wherein: The UDM is further configured to send a second notification to the AMF, where the second notification includes the reader identifier; The AMF is used to send the eleventh information to the access network device, and the eleventh information includes the reader / writer identifier.

35. The system according to any one of claims 26 to 34, wherein: The Internet of Things functional network element is further configured to send twelfth information to the UDM, where the twelfth information includes an identifier of the terminal device; The UDM is further configured to send thirteenth information to the IoT functional network element, where the thirteenth information includes tracking area information TAI corresponding to the terminal device; The Internet of Things functional network element is also used to determine the access network device based on the TAI of the terminal device.

36. The system according to any one of claims 26 to 35, wherein: The access network device is used to determine the terminal device according to the reader identifier; The access network device is also used to instruct the terminal device to perform business operations on the Internet of Things device.

37. A chip, characterized in that: The chip is used to execute the method according to any one of claims 1 to 25.

38. A chip module, characterized in that: The invention comprises an interface component and a chip, wherein the chip is used to execute the method according to any one of claims 1 to 25.

39. A computer-readable storage medium, characterized in that The storage medium stores a computer program or instruction. When the computer program or instruction is executed by the communication device, the method according to any one of claims 1 to 25 is implemented.

40. A computer program product, characterized in that The computer program product comprises program instructions, and when the program instructions are executed, the method according to any one of claims 1 to 25 is implemented.

Images