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

Abstract

The invention discloses a communication method and apparatus, and a communication device. The method comprises the following steps: a first network function sends a UE context release instruction based on first information or after obtaining the first information; the method comprises the following steps: a first network function sends registration removal request information or access removal request information based on fourth information or after obtaining the fourth information; or, the first network function rejects the registration request information or the access request information of the at least one UE based on the fourth information or after obtaining the fourth information.

Description

Technical Field

[0001] The present application relates to the field of mobile communication technologies, and in particular to a communication method and apparatus, communication equipment, and a computer-readable storage medium. Background Art

[0002] After a user equipment (UE) registers with the network, the network will save the UE's context and reserve radio air interface resources for the UE for a period of time. When a large number of UEs register with the network, network resources will be wasted to a certain extent. Summary of the Invention

[0003] The present application provides a communication method and apparatus, a communication device, a computer program product, and a computer-readable storage medium.

[0004] The present application provides a communication method, which is applied to a first network function and includes:

[0005] The first network function sends a UE context release instruction based on the first information or after obtaining the first information.

[0006] The present application provides a communication method, which is applied to a first network function and includes:

[0007] The first network function sends a deregistration request message or a deaccess request message based on the fourth information or after obtaining the fourth information; or

[0008] The first network function rejects the registration request information or access request information of at least one UE based on the fourth information or after obtaining the fourth information.

[0009] The present application provides a communication device, which is applied to a first network function, and includes:

[0010] A sending unit is configured to send a UE context release instruction based on the first information or after obtaining the first information.

[0011] The present application provides a communication device, which is applied to a first network function, and includes:

[0012] a sending unit, configured to send deregistration request information or deaccess request information based on the fourth information or after obtaining the fourth information; or

[0013] The processing unit is configured to reject registration request information or access request information of at least one UE based on the fourth information or after obtaining the fourth information.

[0014] The present application provides a communication device, comprising: a processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory, and execute any one of the above-mentioned communication methods.

[0015] The computer program product provided in the embodiments of the present application includes computer program instructions, which enable a computer to execute any one of the above-mentioned communication methods.

[0016] The present application provides a computer-readable storage medium for storing a computer program, wherein the computer program enables a computer to execute any one of the above-mentioned communication methods.

[0017] In the technical solution of the present application, the network side releases the UE context, deregisters or deaccesses the UE, or rejects the UE's registration request or access request by sending a UE context release instruction, or sending a deregistration request message or a deaccession request message, or rejects the registration request information or access request information of at least one UE, thereby saving network resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1-1 This is the first diagram of the Ambient IoT device connection mode;

[0019] Figure 1-2 This is the connection mode of Ambient IoT device Figure 2 ;

[0020] Figure 1-3 This is the connection mode of Ambient IoT device Figure 3 ;

[0021] Figure 1-4 This is the connection mode of Ambient IoT device Figure 4 ;

[0022] Figure 2 This is a schematic diagram of the 5G non-roaming network architecture;

[0023] Figure 3 It is a simplified diagram of the network architecture;

[0024] Figure 4 1 is a flow chart of the communication method provided in an embodiment of the present application;

[0025] Figure 5 This is a flow diagram of the communication method provided in the embodiment of the present application. Figure 2 ;

[0026] Figure 6 This is a flow diagram of the communication method provided in the embodiment of the present application. Figure 3 ;

[0027] Figure 7 This is a flow diagram of the communication method provided in the embodiment of the present application. Figure 4 ;

[0028] Figure 8 This is a flow diagram of the communication method provided in the embodiment of the present application. Figure 5 ;

[0029] Figure 9 This is a flow diagram of the communication method provided in the embodiment of the present application. Figure 6 ;

[0030] Figure 10 This is a flow diagram of the communication method provided in the embodiment of the present application. Figure 7 ;

[0031] Figure 11 This is a flow diagram of the communication method provided in the embodiment of the present application. Figure 8 ;

[0032] Figure 12 Schematic diagram 1 of the structure of the communication device provided in an embodiment of the present application;

[0033] Figure 13 This is a schematic diagram of the structure of the communication device provided in the embodiment of the present application. Figure 2 ;

[0034] Figure 14 This is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0035] Figure 15 It is a schematic structural diagram of the chip of an embodiment of the present application. DETAILED DESCRIPTION

[0036] It should be noted that the term "and / or" in this document is merely a description of the association relationship between associated objects, indicating that three relationships may exist. For example, A and / or B can represent three situations: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this document generally indicates that the previous and subsequent associated objects are in an "or" relationship. It should also be understood that the "indication" mentioned in this document can be a direct indication, an indirect indication, or an indication of an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association relationship between A and B. It should also be understood that the "protocol" mentioned in this document can refer to a standard protocol in the communication field, such as the NR protocol and related protocols used in future communication systems, and this application does not limit this.

[0037] To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following relevant technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the protection scope of the embodiments of the present application.

[0038] 1. Passive IoT

[0039] The Internet of Things (IoT), driven by the principle that everything can be connected to the internet and ultimately achieving the interconnection of everything, has enabled billions of devices to connect and interoperate. However, with the booming market, issues such as device power supply and battery life are becoming new challenges for IoT development. Achieving low-power, low-cost, and long-life networks has become a key challenge for the next phase of IoT development.

[0040] Against this background, low-power Internet of Things began to take shape. After development, a series of mature low-power Internet of Things technologies were formed, represented by Bluetooth Low Energy (BLE), Long Range Radio (LoRa), Narrow Band IoT (NB-IoT), and Reduced Capability (RedCap).

[0041] While the aforementioned low-power IoT technologies aim to achieve low power consumption and massive connectivity, with the continuous evolution of technology and the increasing application of 5G in various industries, the variety of connected objects is expanding, placing higher demands on the price and power consumption of communication terminals. Against this backdrop, passive IoT has emerged on the industry stage and is gradually gaining attention. Passive IoT utilizes ambient energy harvesting to convert available energy into power to drive its own circuits. In passive IoT, a scattering-based communication model enables information transmission to target nodes. The most notable feature of passive IoT is its independence from traditional battery power. This effectively addresses bottlenecks in the development of low-power IoT and represents a key technology for the next generation of IoT, with widespread applications in smart warehousing, logistics, asset management, and other fields.

[0042] 2. Radio Frequency Identification (RFID)

[0043] Improvements and applications in radar have given rise to RFID, the most representative passive IoT technology. RFID systems consist of tags, readers, and a control platform. The readers utilize inductive coupling or backscatter coupling to send electromagnetic signals to the tags, which then convert the signals into energy, activating the tag chip and returning information, enabling tag identification. Mainstream RFID systems support multiple frequency bands. Ultra-high frequency (850MHz to 910MFz) RFID systems, based on electromagnetic backscatter technology, have a theoretical transmission range of 1-10 meters and are widely used in numerous industries, including logistics, manufacturing, and aviation.

[0044] 3. Ambient IoT

[0045] The passive IoT research project of the 3rd Generation Partnership Project (3GPP) is named Ambient IoT. The progress of the standards in the 3GPP working groups is as follows:

[0046] The TR 22.840 standard defines several Ambient IoT application scenarios, broadly encompassing both indoor and outdoor scenarios. Indoor scenarios (also known as local-area scenarios) include inventory management, electronic price tags, and small item locating. Outdoor scenarios (also known as wide-area scenarios) include logistics and transportation, public facility monitoring, and smart ranching. Ambient IoT application scenarios are subject to further development in the future.

[0047] In the standard TR 38.848, three types of Ambient IoT devices and four connection modes of Ambient IoT devices are defined. The definitions of the three types of Ambient IoT devices are shown in Table 1 below, and the four connection modes of Ambient IoT devices are shown in Figures 1-1 to 1-4 .

[0048] Table 1: Definition of Ambient IoT device types

[0049]

[0050] As shown in Table 1, there are three types of Ambient IoT devices: Class A (referred to as Class A in Table 1), Class B (referred to as Class B in Table 1), and Class C (referred to as Class C in Table 1). These three types of Ambient IoT devices are defined based on four dimensions: energy storage capability, active signaling capability, device complexity, and power consumption.

[0051] like Figures 1-1 to 1-4As shown in the figure, the four Ambient IoT device connection modes include direct connection (connection mode 1), relay connection (connection mode 2), downlink / uplink relay connection (connection mode 3), and independent connection (connection mode 4). Figure 1-1 As shown in Figure 2, in the direct connection mode, the Ambient IoT device is directly connected to the base station for downlink / uplink transmission. Figure 1-2 As shown in the figure, in the relay mode, the Ambient IoT device is connected to the base station through an intermediate node for downlink / uplink transmission. Figure 1-3 As shown in the upper part of , in the downlink relay mode, the Ambient IoT device is connected to the base station through the auxiliary node for downlink transmission, and the Ambient IoT device is directly connected to the base station for uplink transmission; Figure 1-3 As shown in the lower half of the figure, in the uplink relay mode, the Ambient IoT device is connected to the base station through the auxiliary node for uplink transmission, and the Ambient IoT device is directly connected to the base station for downlink transmission. Figure 1-4 As shown, in the standalone mode, the Ambient IoT device connects to other devices (such as UE) for sideline transmission.

[0052] 4. Basic network architecture

[0053] 5G non-roaming network architecture Figure 2As shown, the network elements involved in the network architecture include: User Equipment (UE), Radio Access Network (RAN), User Plane Function (UPF), Data Network (DN), Access and Mobility Management Function (AMF), Session Management Function (SMF), Policy Control Function (PCF), Application Function (AF), Network Slice Selection Function (NSSF), Authentication Server Function (AUSF), Network Slice Selection Authentication and Authorization Function (NSSAAF), Unified Data Management (UDM), Network Slice Admission Control Function (NSACF). It should be noted that, Figure 2 The network architecture shown may further include more or fewer network elements, for example, a unified data repository (UDR), a network exposure function (NEF), etc.

[0054] Ambient IoT devices are simple and usually require relatively simple services, but they are often in large quantities and many scenarios may actually be deployed within the park. Figure 2 The network architecture shown can be further simplified to Figure 3 The network architecture shown in Figure 1 is as follows. Figure 3 The network architecture shown is only one possible simplified architecture. The actual network architecture may be similar or even the same as it, or it may be different or reused. Figure 2 The network architecture shown, no matter which network architecture is adopted, can be applied to the technical solution of this application.

[0055] like Figure 3As shown, AMF and NFx are required core network elements, the Network Repository Function (NRF) is an optional core network element (for example, it may be involved in some scenarios involving Ambient IoT devices or certain processes), and the AF is a non-core network element. This network architecture includes an unnamed new network element (temporarily referred to as NFx). This NF may have one or more of the following functions: contract information management for Ambient IoT devices, registration management for Ambient IoT devices, and subscription information management for Ambient IoT devices. NFx may be a standalone network function or integrated with other network functions (such as AMF, UDM, etc.). In the technical solution of this application, NFx is used as an example to manage contract information, replacing the UDM function. This does not mean that NFx will exist in actual deployments or that NFx will replace the UDM function. For example, the NFx function may be implemented by enhancing the AMF and / or UDM. If a new network function is defined, the NFx may be called, for example, the Tag Management Function (TMF) or another name. This application does not specifically limit the name of NFx. It should be noted that the network architecture only includes the network functions involved in this application. In fact, the network architecture supporting Ambient IoT devices may include other mandatory and / or optional network functions (or may not include them).

[0056] It should be noted that with the development of communication standards and the evolution of network architecture, Figure 2 and Figure 3 The names and functions of the network elements may change. For example, some architecture designs hope to use a dedicated new network element to replace (or partially replace) the AMF to perform registration management of Ambient IoT devices, or NFx can also integrate the charging function (CHF).

[0057] After the UE registers and joins the network, the network (such as AMF) will save the UE context and reserve wireless air interface resources for a period of time. For UEs of the Ambient IoT device type, the Ambient IoT device registers with the network, which can combine the passive device with the mobile network, and introduce the capabilities of the mobile network into the management of the passive device and related information processing, which has at least the following beneficial effects: a) It is convenient for the unified management of Ambient IoT devices, b) It is convenient for the transmission of massive data of Ambient IoT devices or large-scale / long-distance transmission of data, and c) It can utilize the data processing capabilities of the core network. However, there are often a large number of UEs of this type, such as Ambient IoT devices. In this case, saving context and wireless air interface resources for the UE will cause a certain degree of waste of network resources. To this end, the following technical solution of the present application is proposed.

[0058] To facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The above related technologies can be combined arbitrarily with the technical solutions of the embodiments of the present application as optional solutions, and all of them fall within the scope of protection of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

[0059] It should be noted that the "passive Internet of Things" in the embodiments of the present application may be "Ambient IoT". In some implementations, "passive Internet of Things" and "Ambient IoT" may be used interchangeably.

[0060] It should be noted that in the embodiments of the present application, "registration" and "access" can be used interchangeably.

[0061] It should be noted that the "UE" in the embodiments of the present application may be a passive IoT device and / or a tag. In some embodiments, "UE," "passive IoT device," "Ambient IoT device," and "tag" may be used interchangeably. Alternatively, the "UE" in the embodiments of the present application may be a function or entity that can provide an Ambient IoT identifier and / or a tag identifier, such as a tag, an access network, a tag reader, a relay node, an auxiliary node, or a combination of two or more of the above functions.

[0062] It should be noted that the "first network function" in the embodiment of the present application may include at least one of the following: AMF, TMF, UDM, and UDR.

[0063] It should be noted that the "second network function" in the embodiment of the present application may include at least one of the following: TMF, UDM, UDR, PCF, NEF.

[0064] It should be noted that the "third network function" in the embodiment of the present application may include at least one of the following: AF, NEF, PCF, UDM, and UDR.

[0065] It should be noted that the "fourth network function" in the embodiment of the present application may include at least one of the following: NEF, PCF, SMF, TMF, UDM, and UDR.

[0066] It should be noted that the above-mentioned function or network function includes at least one of the listed items, which may refer to the function or network function being one or more of the listed items, for example, the first network function is AMF, or the first network function is a network function jointly established by AMF and TMF; it may refer to the function or network function having one or more of the listed functions, for example, the second network function has the UDM registration function and the PCC policy sending function of PCF (but does not have the UE policy sending function of PCF).

[0067] It should be noted that the technical solution of the embodiment of the present application can be applied to Figure 1-1 The connection mode shown is not limited to this, and the technical solution of the embodiment of the present application can also be applied to Figures 1-2 to 1-4 The connection mode shown may be applied to other connection modes. Although most of the technical solutions of the embodiments of the present application are based on Figure 1-1 The connection mode shown is used as the basis for explanation, but Figures 1-2 to 1-4 The other connection modes shown can also be applied to the technical solutions of the embodiments of the present application.

[0068] Figure 4 1 is a flow chart of a communication method provided in an embodiment of the present application, wherein the communication method is applied to a first network function, such as Figure 4 As shown, the communication method includes the following steps:

[0069] Step 401: The first network function sends a UE context release instruction based on the first information or after obtaining the first information.

[0070] In an embodiment of the present application, the first network function sends a UE context release instruction based on the first information. Alternatively, the first network function sends a UE context release instruction after obtaining the first information. The manner in which the first network function obtains the first information includes the following manners:

[0071] Mode 1: The first network function obtains the first information from a local configuration. In some implementations, the first network function locally configures all or part of the first information, and the first network function obtains all or part of the first information from the local configuration.

[0072] Method 2: The first network function obtains the first information from another network function. In some implementations, the first network function receives all or part of the first information from the second network function.

[0073] In an embodiment of the present application, the first information includes at least one of the following: the second information, the third information, the first air interface resource related information, the first deregistration related information, the first deaccession related information, and all or part of the UE's subscription information.

[0074] 1) In some embodiments, the second information includes at least one of the following: not reserving air interface resources, releasing air interface resources, not reserving air interface resources after registration or access, and releasing air interface resources after registration or access. Alternatively, it can be understood that the second information indicates at least one of the following: not reserving air interface resources, releasing air interface resources, not reserving air interface resources after registration or access, and releasing air interface resources after registration or access. Alternatively, it can be understood that the second information includes indication information of at least one of the following: not reserving air interface resources, releasing air interface resources, not reserving air interface resources after registration or access, and releasing air interface resources after registration or access.

[0075] 2) In some embodiments, the third information includes at least one of the following: not registering, not registering after registration, retaining registration status after registration, not rejecting registration, accepting registration, not accessing, not accessing after accessing, retaining access status after accessing, not rejecting access, and accepting access. Alternatively, it can be understood that the third information indicates at least one of the following: not registering, not registering after registration, retaining registration status after registration, not rejecting registration, accepting registration, not accessing, not accessing after accessing, retaining access status after accessing, not rejecting access, and accepting access. Alternatively, it can be understood that the third information includes indication information of at least one of the following: not registering, not registering after registration, retaining registration status after registration, not rejecting registration, accepting registration, not accessing, not accessing after accessing, retaining access status after accessing, not rejecting access, and accepting access.

[0076] 3) In some embodiments, the first air interface resource-related information includes at least one of the following: not reserving air interface resources, releasing air interface resources, not reserving air interface resources after registration or access, and releasing air interface resources after registration or access. Alternatively, it can be understood that the first air interface resource-related information indicates at least one of the following: not reserving air interface resources, releasing air interface resources, not reserving air interface resources after registration or access, and releasing air interface resources after registration or access. Alternatively, it can be understood that the first air interface resource-related information includes at least one of the following indication information: not reserving air interface resources, releasing air interface resources, not reserving air interface resources after registration or access, and releasing air interface resources after registration or access.

[0077] 4) In some embodiments, the first deregistration-related information includes at least one of the following: not registering, not registering after registration, retaining the registration status after registration, not rejecting the registration, and accepting the registration. Alternatively, it can be understood that the first deregistration-related information indicates at least one of the following: not registering, not registering after registration, retaining the registration status after registration, not rejecting the registration, and accepting the registration. Alternatively, it can be understood that the first deregistration-related information includes at least one of the following indicative information: not registering, not registering after registration, retaining the registration status after registration, not rejecting the registration, and accepting the registration.

[0078] 5) In some embodiments, the first access-departure related information includes at least one of the following: not accessing, not accessing after accessing, retaining access status after accessing, not denying access, and accepting access. Alternatively, it can be understood that the first access-departure related information indicates at least one of the following: not accessing, not accessing after accessing, retaining access status after accessing, not denying access, and accepting access. Alternatively, it can be understood that the first access-departure related information includes indication information of at least one of the following: not accessing, not accessing after accessing, retaining access status after accessing, not denying access, and accepting access.

[0079] 6) In some embodiments, the subscription information of the above-mentioned UE includes at least one of the following: all or part of the UE identifier, group identifier, passive Internet of Things indication information, device type, public land mobile network (PLMN) identifier, mobility management related information, session management related information, transmission related information, positioning or ranging related information, positioning format, positioning or ranging accuracy, billing method, validity period of the UE identifier, valid times of the UE identifier, validity period of the subscription information, valid times of the subscription information, second air interface resource related information, second deregistration related information, second deaccession related information, and network openness related information.

[0080] In some embodiments, the mobility management-related information includes at least one of the following: whether mobility management is allowed or not allowed, whether mobility management is supported or not supported, and whether mobility management is required or not required. Alternatively, it can be understood that the mobility management-related information indicates at least one of the following: whether mobility management is allowed or not allowed, whether mobility management is supported or not supported, and whether mobility management is required or not required. Alternatively, it can be understood that the mobility management-related information includes information indicating at least one of the following: whether mobility management is allowed or not allowed, whether mobility management is supported or not supported, and whether mobility management is required or not required.

[0081] In some embodiments, the session management related information includes at least one of the following: allowing or not allowing session establishment, supporting or not supporting session establishment, or requiring or not requiring session establishment. Alternatively, it can be understood that the session management related information indicates at least one of the following: allowing or not allowing session establishment, supporting or not supporting session establishment, or requiring or not requiring session establishment. Alternatively, it can be understood that the session management related information includes information indicating at least one of the following: allowing or not allowing session establishment, supporting or not supporting session establishment, or requiring or not requiring session establishment.

[0082] In some embodiments, the above-mentioned transmission-related information includes at least one of the following: allowing or not allowing control plane transmission, supporting or not supporting control plane transmission, requiring or not requiring control plane transmission, allowing or not allowing user plane transmission, supporting or not supporting user plane transmission, requiring or not requiring user plane transmission. Alternatively, it can also be understood that: the transmission-related information indicates at least one of the following: allowing or not allowing control plane transmission, supporting or not supporting control plane transmission, requiring or not requiring control plane transmission, allowing or not allowing user plane transmission, supporting or not supporting user plane transmission, requiring or not requiring user plane transmission. Alternatively, it can also be understood that: the transmission-related information includes at least one of the following indication information: allowing or not allowing control plane transmission, supporting or not supporting control plane transmission, requiring or not requiring control plane transmission, allowing or not allowing user plane transmission, supporting or not supporting user plane transmission, requiring or not requiring user plane transmission.

[0083] In some embodiments, the above-mentioned positioning or ranging related information includes at least one of the following: whether positioning or ranging is allowed or not, whether positioning or ranging is supported or not, whether positioning or ranging is required or not, the format of positioning or ranging, and the accuracy of positioning or ranging. Alternatively, it can also be understood that the positioning or ranging related information indicates at least one of the following: whether positioning or ranging is allowed or not, whether positioning or ranging is supported or not, whether positioning or ranging is required or not, the format of positioning or ranging, and the accuracy of positioning or ranging. Alternatively, it can also be understood that the positioning or ranging related information includes at least one of the following indication information: whether positioning or ranging is allowed or not, whether positioning or ranging is supported or not, whether positioning or ranging is required or not, the format of positioning or ranging, and the accuracy of positioning or ranging.

[0084] In some embodiments, the second air interface resource related information includes at least one of the following: whether or not air interface resources need to be reserved, whether or not air interface resources need to be released, whether or not air interface resources need to be reserved after registration, and whether or not air interface resources need to be released after registration. Alternatively, it can also be understood that the second air interface resource related information indicates at least one of the following: whether or not air interface resources need to be reserved, whether or not air interface resources need to be released, whether or not air interface resources need to be reserved after registration, and whether or not air interface resources need to be released after registration. Alternatively, it can also be understood that the second air interface resource related information includes at least one of the following indication information: whether or not air interface resources need to be reserved, whether or not air interface resources need to be released, whether or not air interface resources need to be reserved after registration, and whether or not air interface resources need to be released after registration.

[0085] In some embodiments, the second deregistration related information includes at least one of the following: to register or not to register, to register after registration or not to register, to retain or not retain the registration status after registration, to refuse registration or not to refuse registration, to accept registration or not to accept registration. Alternatively, it can also be understood that the second deregistration related information indicates at least one of the following: to register or not to register, to register after registration or not to register, to retain or not retain the registration status after registration, to refuse registration or not to refuse registration, to accept registration or not to accept registration. Alternatively, it can also be understood that the second deregistration related information includes at least one of the following indication information: to register or not to register, to register after registration or not to register, to retain or not retain the registration status after registration, to refuse registration or not to refuse registration, to accept registration or not to accept registration.

[0086] In some embodiments, the second de-access related information includes at least one of the following: de-access or not de-access, de-access after access or not de-access, retaining or not retaining the access status after access, refusing access or not refusing access, accepting access or not accepting access. Alternatively, it can also be understood that the second de-access related information indicates at least one of the following: de-access or not de-access, de-access after access or not de-access, retaining or not retaining the access status after access, refusing access or not refusing access, accepting access or not accepting access. Alternatively, it can also be understood that the second de-access related information includes indication information of at least one of the following: de-access or not de-access, de-access after access or not de-access, retaining or not retaining the access status after access, refusing access or not refusing access, accepting access or not accepting access.

[0087] Several examples are listed below, but the technical solutions of the embodiments of the present application are not limited to the following examples, and the following examples can be combined in any way.

[0088] Example 1-1

[0089] The first network function obtains first air interface resource-related information from a local configuration or a second network function, where the first air interface resource-related information includes at least one of: not reserving the air interface resource and releasing the air interface resource. The first network function determines to initiate air interface resource release, i.e., access network (AN) release, based on the first air interface resource-related information, and sends a UE context release instruction.

[0090] Example 1-2

[0091] The first network function obtains the UE's subscription information from a local configuration or a second network function, where the UE's subscription information includes information related to a second air interface resource, and the information related to the second air interface resource includes at least one of the following: whether the air interface resource needs to be retained or not, and whether the air interface resource needs to be released or not. In one scenario, if the first network function determines, based on the information related to the second air interface resource, that the air interface resource does not need to be retained and / or needs to be released, then the first network function may determine to initiate an air interface resource release, i.e., an AN release, and the first network function sends a UE context release instruction.

[0092] Example 1-3

[0093] The first network function obtains the subscription information of the UE from a local configuration or a second network function, wherein the subscription information of the UE includes mobility management-related information, and the mobility management-related information includes at least one of the following: allowing or not allowing mobility management, supporting or not supporting mobility management, and requiring or not requiring mobility management. In one case, the first network function determines, based on the mobility management-related information, that mobility management is not allowed and / or is not supported and / or is not required (an example is that the subscription information includes information related to infrequent use of UE air interface resources / not used immediately after registration, such as the subscription information includes information that data transmission and positioning are not supported, or indicates that the UE is only used for inventory functions. Based on the above information, the first network function can infer that air interface resources do not need to be reserved for the UE). Then, the first network function can determine to initiate air interface resource release, i.e., AN release, and the first network function sends a UE context release instruction.

[0094] Example 1-4

[0095] The first network function obtains the UE's subscription information from a local configuration or a second network function, where the UE's subscription information includes session management related information, and the session management related information includes at least one of the following: allowing or not allowing session establishment, supporting or not supporting session establishment, and requiring or not requiring session establishment. In one scenario, if the first network function determines, based on the session management related information, that session establishment is not allowed, / or is not supported, and / or is not required, then the first network function may determine to initiate air interface resource release, i.e., AN release, and the first network function sends a UE context release instruction.

[0096] Example 1-5

[0097] The first network function obtains the subscription information of the UE from the local configuration or the second network function, wherein the subscription information of the UE includes transmission-related information, and the transmission-related information includes at least one of the following: allowing or not allowing control plane transmission, supporting or not supporting control plane transmission, requiring or not requiring control plane transmission, allowing or not allowing user plane transmission, supporting or not supporting user plane transmission, requiring or not requiring user plane transmission. As a case, the first network function determines, based on the transmission-related information, that control plane transmission is not allowed and / or control plane transmission is not supported and / or control plane transmission is not required and / or user plane transmission is not allowed and / or user plane transmission is not supported and / or user plane transmission is not required, then the first network function may determine to initiate air interface resource release, i.e., AN release, and the first network function sends a UE context release instruction.

[0098] Example 1-6

[0099] The first network function obtains the subscription information of the UE from the local configuration or the second network function, wherein the subscription information of the UE includes positioning or ranging related information, and the positioning or ranging related information includes at least one of the following: allowing or not allowing positioning or ranging, supporting or not supporting positioning or ranging, requiring or not requiring positioning or ranging, the format of positioning or ranging, and the accuracy of positioning or ranging. As a case, the first network function determines, based on the positioning or ranging related information, that positioning or ranging is not allowed and / or positioning or ranging is not supported and / or positioning or ranging is not required and / or the format of positioning or ranging is not supported and / or the accuracy of positioning or ranging is not supported. Then, the first network function can determine to initiate air interface resource release, i.e., AN release, and the first network function sends a UE context release instruction.

[0100] Example 1-7

[0101] The first network function obtains first deregistration related information from a local configuration or a second network function, wherein the first deregistration related information includes: not deregistering and retaining a registration state. The first network function determines not to deregister and / or retain the registration state based on the first deregistration related information.

[0102] Example 1-8

[0103] The first network function obtains subscription information of the UE from a local configuration or a second network function, where the subscription information of the UE includes second deregistration related information, and the second deregistration related information includes at least one of the following: deregistration or non-deregistration, and retention or non-retention of a registration state. In one embodiment, the first network function determines whether to deregister and / or retain the registration state based on the second deregistration related information.

[0104] In some embodiments, the communication method further comprises the following steps:

[0105] The first network function receives at least one of the following from the UE and / or the access network: UE identity, group identity, passive Internet of Things (Ambient IoT) indication information, device type, and UE-related information.

[0106] Exemplarily, the first network function may receive at least one of the following from the UE and / or the access network during the UE registration process or access process: UE identification, group identification, passive Internet of Things (Ambient IoT) indication information, device type, and UE-related information.

[0107] In some embodiments, the UE identifier described in the embodiments of the present application includes at least one of the following: all or part of the Electronic Product Code (EPC), the General Manager Number, the Object Class, the PLMN identifier, the group identifier, the Subscription Permanent Identifier (SUPI), the Subscription Concealed Identifier (SUCI), the Generic Public Subscription Identifier (GPSI), the Globally Unique Temporary Identifier (GUTI), the Temporary Mobile Subscription Identifier (TMSI), and the Permanent Equipment Identifier (PEI).

[0108] It should be noted that the UE identifier includes at least one of the following items: the UE identifier may be all or part of the above item, or any combination of all or parts of multiple items; or the UE identifier may be all or part of the above item, or any combination of all or parts of multiple items. For example, the UE identifier includes multiple fields, one or more of which are part of the EPC.

[0109] In one example, the UE identifier described in the embodiments of the present application is an EPC or a partial field of an EPC.

[0110] Here, using EPC or part of the EPC field as the UE identifier of the passive IoT device and / or tag has the following benefits: reusing the management mechanism of the current passive device, and realizing unified management of the passive devices using the capabilities of the core network without making major modifications to the existing passive tag management mechanism, which is simple and easy to implement; at the same time, since there is no major change to the current passive device, the passive device can also be compatible with other existing passive IoT device usage methods. For example, for the processing of a small number of tags or home scenarios, a simple handheld barcode scanner can also use the passive device without the need to purchase core network services separately, which is more flexible and economical.

[0111] In some implementations, the device type described in the embodiments of the present application is one of the following: Class A passive IoT device, Class B passive IoT device, and Class C passive IoT device. The specific definitions of Class A passive IoT device, Class B passive IoT device, and Class C passive IoT device can be found in Table 1 above.

[0112] In some embodiments, the UE-related information described in the embodiments of the present application includes at least one of the following: UE-related data information, sensor-related data information, and information related to UE perception, detection, exploration, or measurement.

[0113] In an embodiment of the present application, the first network function sends a UE context release instruction, including: the first network function sends a UE context release instruction to the UE and / or the access network.

[0114] In one example, for a UE supporting NAS capabilities, the first network function sends a UE context release instruction to the UE.

[0115] In one example, for a UE that does not support NAS capabilities, the first network function sends a UE context release instruction to the access network. Further, optionally, the access network sends a UE context release instruction to the UE.

[0116] In some embodiments, step 401 further includes: the first network function triggering, instructing, or requesting the access network or the reader / writer device to send deactivation or invalidation related information to the UE. In some embodiments, the deactivation or invalidation related information is used for at least one of the following: permanently deactivating the UE, permanently invalidating the UE, temporarily deactivating the UE, temporarily invalidating the UE, deactivating the UE within a certain period of time, or invalidating the UE within a certain period of time.

[0117] The above-mentioned technical solution of the embodiment of the present application realizes the release of the air interface resources of the UE after registration, and has at least the following beneficial effects: for certain passive devices and / or certain application scenarios of passive devices, the passive device does not need to use the air interface resources after completing the registration, for example, it will not send or receive data through the air interface. The air interface resources of the UE are released immediately after the UE is registered, thereby saving network resources.

[0118] Figure 5 This is a flow diagram of the communication method provided in the embodiment of the present application. Figure 2 , the communication method is applied to a first network function, such as Figure 5 As shown, the communication method includes the following steps:

[0119] Step 501: The first network function sends a deregistration request message or a deaccess request message based on the fourth information or after obtaining the fourth information; or, the first network function rejects the registration request message or the access request message of at least one UE based on the fourth information or after obtaining the fourth information.

[0120] In an embodiment of the present application, the first network function sends a deregistration request message or a deaccess request message based on the fourth information, or rejects the registration request message or the access request message of at least one UE. Alternatively, after obtaining the fourth information, the first network function sends a deregistration request message or a deaccess request message, or rejects the registration request message or the access request message of at least one UE. The manner in which the first network function obtains the fourth information includes the following manners:

[0121] Mode 1: The first network function obtains the fourth information from a local configuration. In some implementations, the first network function locally configures all or part of the fourth information, and the first network function obtains all or part of the fourth information from the local configuration.

[0122] Method 2: The first network function obtains the fourth information from another network function. In some implementations, the first network function receives all or part of the fourth information from the second network function.

[0123] In an embodiment of the present application, the fourth information includes at least one of the following: the fifth information, the third deregistration related information, the third deaccess related information, and all or part of the UE's contract information.

[0124] 1) In some embodiments, the fifth information includes at least one of the following: deregistration, deregistration after registration, not retaining registration status after registration, registration rejection, access removal, access removal after access, not retaining access status after access, or access rejection. Alternatively, it can be understood that the fifth information indicates at least one of the following: deregistration, deregistration after registration, not retaining registration status after registration, registration rejection, access removal, access removal after access, not retaining access status after access, or access rejection. Alternatively, it can be understood that the fifth information includes indication information of at least one of the following: deregistration, deregistration after registration, not retaining registration status after registration, registration rejection, access removal, access removal after access, not retaining access status after access, or access rejection.

[0125] 2) In some embodiments, the third deregistration-related information includes at least one of the following: deregistration, deregistration after registration, not retaining the registration status after registration, or registration rejection. Alternatively, the third deregistration-related information may indicate at least one of the following: deregistration, deregistration after registration, not retaining the registration status after registration, or registration rejection. Alternatively, the third deregistration-related information may include information indicating at least one of the following: deregistration, deregistration after registration, not retaining the registration status after registration, or registration rejection.

[0126] 3) In some embodiments, the third de-access related information includes at least one of the following: de-access, de-access after access, not retaining access status after access, and access denied. Alternatively, it can be understood that the third de-access related information indicates at least one of the following: de-access, de-access after access, not retaining access status after access, and access denied. Alternatively, it can be understood that the third de-access related information includes information indicating at least one of the following: de-access, de-access after access, not retaining access status after access, and access denied.

[0127] 4) In some embodiments, the subscription information of the above-mentioned UE includes at least one of the following: all or part of the UE identifier, group identifier, passive Internet of Things indication information, device type, PLMN identifier, mobility management related information, session management related information, transmission related information, positioning or ranging related information, positioning format, positioning or ranging accuracy, billing method, validity period of the UE identifier, valid times of the UE identifier, validity period of the subscription information, valid times of the subscription information, second air interface resource related information, second deregistration related information, second deaccession related information, and network openness related information.

[0128] In some embodiments, the mobility management-related information includes at least one of the following: whether mobility management is allowed or not allowed, whether mobility management is supported or not supported, and whether mobility management is required or not required. Alternatively, it can be understood that the mobility management-related information indicates at least one of the following: whether mobility management is allowed or not allowed, whether mobility management is supported or not supported, and whether mobility management is required or not required. Alternatively, it can be understood that the mobility management-related information includes information indicating at least one of the following: whether mobility management is allowed or not allowed, whether mobility management is supported or not supported, and whether mobility management is required or not required.

[0129] In some embodiments, the session management related information includes at least one of the following: allowing or not allowing session establishment, supporting or not supporting session establishment, or requiring or not requiring session establishment. Alternatively, it can be understood that the session management related information indicates at least one of the following: allowing or not allowing session establishment, supporting or not supporting session establishment, or requiring or not requiring session establishment. Alternatively, it can be understood that the session management related information includes information indicating at least one of the following: allowing or not allowing session establishment, supporting or not supporting session establishment, or requiring or not requiring session establishment.

[0130] In some embodiments, the above-mentioned transmission-related information includes at least one of the following: allowing or not allowing control plane transmission, supporting or not supporting control plane transmission, requiring or not requiring control plane transmission, allowing or not allowing user plane transmission, supporting or not supporting user plane transmission, requiring or not requiring user plane transmission. Alternatively, it can also be understood that: the transmission-related information indicates at least one of the following: allowing or not allowing control plane transmission, supporting or not supporting control plane transmission, requiring or not requiring control plane transmission, allowing or not allowing user plane transmission, supporting or not supporting user plane transmission, requiring or not requiring user plane transmission. Alternatively, it can also be understood that: the transmission-related information includes at least one of the following indication information: allowing or not allowing control plane transmission, supporting or not supporting control plane transmission, requiring or not requiring control plane transmission, allowing or not allowing user plane transmission, supporting or not supporting user plane transmission, requiring or not requiring user plane transmission.

[0131] In some embodiments, the above-mentioned positioning or ranging related information includes at least one of the following: whether positioning or ranging is allowed or not, whether positioning or ranging is supported or not, whether positioning or ranging is required or not, the format of positioning or ranging, and the accuracy of positioning or ranging. Alternatively, it can also be understood that the positioning or ranging related information indicates at least one of the following: whether positioning or ranging is allowed or not, whether positioning or ranging is supported or not, whether positioning or ranging is required or not, the format of positioning or ranging, and the accuracy of positioning or ranging. Alternatively, it can also be understood that the positioning or ranging related information includes at least one of the following indication information: whether positioning or ranging is allowed or not, whether positioning or ranging is supported or not, whether positioning or ranging is required or not, the format of positioning or ranging, and the accuracy of positioning or ranging.

[0132] In some embodiments, the second air interface resource related information includes at least one of the following: whether or not air interface resources need to be reserved, whether or not air interface resources need to be released, whether or not air interface resources need to be reserved after registration, and whether or not air interface resources need to be released after registration. Alternatively, it can also be understood that the second air interface resource related information indicates at least one of the following: whether or not air interface resources need to be reserved, whether or not air interface resources need to be released, whether or not air interface resources need to be reserved after registration, and whether or not air interface resources need to be released after registration. Alternatively, it can also be understood that the second air interface resource related information includes at least one of the following indication information: whether or not air interface resources need to be reserved, whether or not air interface resources need to be released, whether or not air interface resources need to be reserved after registration, and whether or not air interface resources need to be released after registration.

[0133] In some embodiments, the second deregistration-related information includes at least one of the following: to register or not to register, to register after registration or not to register, to retain or not retain the registration status after registration, to refuse registration or not to refuse registration, to refuse registration or accept registration. Alternatively, it can also be understood that the second deregistration-related information indicates at least one of the following: to register or not to register, to register after registration or not to register, to retain or not retain the registration status after registration, to refuse registration or not to refuse registration, to refuse registration or accept registration. Alternatively, it can also be understood that the second deregistration-related information includes at least one of the following indication information: to register or not to register, to register after registration or not to register, to retain or not retain the registration status after registration, to refuse registration or not to refuse registration, to refuse registration or accept registration.

[0134] In some embodiments, the second de-access related information includes at least one of the following: de-access or not de-access, de-access after access or not de-access, retaining or not retaining the access status after access, denying access or not denying access, denying access or accepting access. Alternatively, it can also be understood that the second de-access related information indicates at least one of the following: de-access or not de-access, de-access after access or not de-access, retaining or not retaining the access status after access, denying access or not denying access, denying access or accepting access. Alternatively, it can also be understood that the second de-access related information includes indication information of at least one of the following: de-access or not de-access, de-access after access or not de-access, retaining or not retaining the access status after access, denying access or not denying access, denying access or accepting access.

[0135] Several examples are listed below, but the technical solutions of the embodiments of the present application are not limited to the following examples, and the following examples can be combined in any way.

[0136] Example 2-1

[0137] The first network function obtains third deregistration related information from a local configuration or the second network function, wherein the third deregistration related information includes deregistration. The first network function determines to initiate deregistration based on the third deregistration related information, and sends a deregistration request message.

[0138] Example 2-2

[0139] The first network function obtains third de-access related information from a local configuration or the second network function, wherein the third de-access related information includes: de-access. The first network function determines to initiate de-access based on the third de-access related information, and the first network function sends de-access request information.

[0140] Example 2-3

[0141] The first network function obtains the UE's subscription information from a local configuration or a second network function, where the UE's subscription information includes second deregistration related information, and the second deregistration related information includes: deregistration after registration or non-registration. In one scenario, if the first network function determines to deregister after registration based on the second deregistration related information, the first network function may determine to initiate deregistration and send a deregistration request message.

[0142] Example 2-4

[0143] The first network function obtains the UE's subscription information from a local configuration or a second network function, where the UE's subscription information includes second deregistration-related information, and the second deregistration-related information includes registration rejection or registration acceptance. In one embodiment, if the first network function determines to reject the registration based on the second deregistration-related information, the first network function rejects the UE's registration request information.

[0144] Example 2-5

[0145] The first network function obtains subscription information of the UE from a local configuration or a second network function, where the subscription information of the UE includes second de-access related information, and the second de-access related information includes: de-access after access or not de-access. In one case, if the first network function determines to de-access after access based on the second de-access related information, the first network function may determine to initiate de-access, and the first network function may send de-access request information.

[0146] Example 2-6

[0147] The first network function obtains the UE's subscription information from a local configuration or a second network function, where the UE's subscription information includes second access-related information, and the second access-related information includes: access rejection or access acceptance. In one case, if the first network function determines to reject access based on the second access-related information, then the first network function rejects the UE's access request information.

[0148] Example 2-7

[0149] The first network function obtains the UE's subscription information from a local configuration or a second network function, where the UE's subscription information includes at least the following: mobility management related information, session management related information, transmission related information, and positioning or ranging related information. The contents of the mobility management related information, session management related information, transmission related information, and positioning or ranging related information may refer to the above description.

[0150] As a case, the first network function determines, based on the mobility management related information, that mobility management is not allowed and / or mobility management is not supported and / or mobility management is not required. Then, the first network function may determine to initiate deregistration or initiate deaccess or reject this registration or reject this access. The first network function sends a deregistration request message or sends an access request message or rejects the UE's registration request information or rejects the UE's access request information.

[0151] As a case, the first network function determines, based on the session management related information, that session establishment is not allowed and / or session establishment is not supported and / or session establishment is not required, then the first network function may determine to initiate deregistration or initiate deaccess or reject this registration or reject this access, and the first network function sends deregistration request information or sends deaccess request information or rejects the UE's registration request information or rejects the UE's access request information.

[0152] As a case, the first network function determines, based on the transmission related information, that control plane transmission is not allowed and / or control plane transmission is not supported and / or control plane transmission is not required and / or user plane transmission is not allowed and / or user plane transmission is not supported and / or user plane transmission is not required. Then, the first network function can determine to initiate deregistration or initiate deaccess or reject this registration or reject this access. The first network function sends a deregistration request message or sends an access request message or rejects the UE's registration request information or rejects the UE's access request information.

[0153] As a case, the first network function determines, based on the positioning or ranging related information, that positioning or ranging is not allowed and / or positioning or ranging is not supported and / or positioning or ranging is not required and / or the format of positioning or ranging is not supported and / or the accuracy of positioning or ranging is not supported. Then, the first network function can determine to initiate deregistration or initiate deaccess or reject this registration or reject this access, and the first network function sends a deregistration request message or sends an access request message or rejects the UE's registration request information or rejects the UE's access request information.

[0154] In some embodiments, the communication method further includes:

[0155] The first network function sends at least one of the following to the third network function, or sends at least one of the following to the third network function through the fourth network function: all or part of the UE's subscription information, all or part of the UE's context, the UE identifier, and UE-related information.

[0156] Here, the content of the UE's subscription information can refer to the above description.

[0157] Here, the UE context includes at least one of the following: all or part of the UE identity, the group identity, the passive Internet of Things indication information, the device type, the PLMN identity, mobility management related information, session management related information, transmission related information, positioning or ranging related information, positioning format, positioning or ranging accuracy, billing method, validity period of the UE identity, number of valid times of the UE identity, validity period of the subscription information, number of valid times of the subscription information, second air interface resource related information, second deregistration related information, second access related information, and network opening related information. The content of the second deregistration related information and the second access related information can refer to the above description.

[0158] In some embodiments, the UE identifier described in the embodiments of the present application includes at least one of the following: all or part of the EPC, universal administrator number, item category, PLMN identifier, group identifier, SUPI, SUCI, GPSI, GUTI, TMSI, PEI.

[0159] In one example, the UE identifier described in the embodiments of the present application is an EPC or a partial field of an EPC.

[0160] Here, using EPC or part of the EPC field as the UE identifier of the passive IoT device and / or tag has the following benefits: reusing the management mechanism of the current passive device, and realizing unified management of the passive devices using the capabilities of the core network without making major modifications to the existing passive tag management mechanism, which is simple and easy to implement; at the same time, since there is no major change to the current passive device, the passive device can also be compatible with other existing passive IoT device usage methods. For example, for the processing of a small number of tags or home scenarios, a simple handheld barcode scanner can also use the passive device without the need to purchase core network services separately, which is more flexible and economical.

[0161] In some implementations, the device type described in the embodiments of the present application is one of the following: Class A passive IoT device, Class B passive IoT device, and Class C passive IoT device. The specific definitions of Class A passive IoT device, Class B passive IoT device, and Class C passive IoT device can be found in Table 1 above.

[0162] In some embodiments, the UE-related information described in the embodiments of the present application includes at least one of the following: UE-related data information, sensor-related data information, and information related to UE perception, detection, exploration, or measurement.

[0163] In an embodiment of the present application, the first network function sends deregistration request information or deaccess request information, including: the first network function sends deregistration request information or deaccess request information to at least one UE and / or access network.

[0164] In one example, for at least one UE supporting NAS capability, the first network function sends a deregistration request message or a deaccess request message to the at least one UE.

[0165] In one example, for at least one UE that does not support NAS capabilities, the first network function sends a deregistration request message or a deaccess request message to the access network. Further, optionally, the access network sends a deregistration request message or a deaccess request message to the at least one UE.

[0166] In some embodiments, the communication method further includes:

[0167] The first network function sends a sending cause value to at least one UE and / or access network, wherein the cause value includes at least one of the following: data has been transmitted, registration status does not need to be retained, and access status does not need to be retained.

[0168] In some embodiments, step 501 further includes: the first network function triggering, instructing, or requesting the access network or the reader / writer device to send deactivation or invalidation related information to the UE. In some embodiments, the deactivation or invalidation related information is used for at least one of the following: permanently deactivating the UE, permanently invalidating the UE, temporarily deactivating the UE, temporarily invalidating the UE, deactivating the UE within a certain period of time, or invalidating the UE within a certain period of time.

[0169] The technical solution of the embodiment of the present application realizes deregistration after UE registration, and has at least the following beneficial effects: for some passive devices and / or some application scenarios of passive devices, the passive device only needs to perceive the behavior of the passive device registering to the network after completing the registration, and it is not necessary to maintain the registration status. By deregistering after registration or refusing registration after transmitting registration information, network resources can be saved.

[0170] It should be noted that the embodiments of this application Figure 4 and Figure 5 The relevant solutions of the present invention can be implemented separately or in any combination. Figure 4 and Figure 5 The relevant scheme determines whether it is necessary to retain the air interface resources and / or registration status of the UE when the UE registers, and allows the air interface resources of the UE to be released and / or the UE to be deregistered immediately when or after registration is completed, so as to save air interface resources and storage resources.

[0171] The technical solutions of the embodiments of the present application are further illustrated below with reference to specific application examples.

[0172] Application Example 1

[0173] In this application example, the first network function is AMF and the second network function is UDM. Of course, the first network function and the second network function can also be implemented in other ways, refer to the description of the first network function and the second network function above. In other words, the AMF in this embodiment can be replaced by the first network function or the aforementioned function or entity that can serve as the first network function, and the UDM can be replaced by the second network function or the aforementioned function or entity that can serve as the second network function.

[0174] Figure 6 This is a flow diagram of the communication method provided in the embodiment of the present application. Figure 3 ,like Figure 6As shown, the communication method includes the following steps:

[0175] Step 601: Execute the UE registration process.

[0176] This embodiment does not limit the specific execution method of the registration process.

[0177] The following steps can be nested in the registration process, that is, at least one of the following steps is performed as part of the registration process or after the registration process is completed.

[0178] Step 602: The AMF obtains first air interface resource-related information from the UDM, including at least one of the following: not reserving air interface resources, releasing air interface resources, not reserving air interface resources after registration, and releasing air interface resources after registration. The first air interface resource-related information may also be described as second information. And / or, the AMF obtains first deregistration-related information from the UDM, including at least one of the following: not deregistering, not deregistering after registration, retaining registration status after registration, not rejecting registration, and accepting registration. The first deregistration-related information may also be described as third information.

[0179] In another implementation, the AMF may locally configure the first air interface resource related information and / or the first deregistration related information, for example, through network management configuration.

[0180] In another implementation, the AMF may not obtain the first air interface resource-related information or the first deregistration-related information, but may obtain information equivalent to the first air interface resource-related information and / or the first deregistration-related information in other ways, for example, inferring not to reserve air interface resources and / or not to deregister based on other information. One possibility of this situation is that the contract information includes infrequent use / non-immediate use of air interface resources, for example, the contract information includes non-support for features such as data transmission and positioning, or indicates that it is only used for inventory scenarios, etc. The AMF can infer from this information that the air interface resources are not reserved and the registration status is retained.

[0181] Optionally, the first air interface resource related information may be included in the subscription information, and / or the first deregistration related information may be included in the subscription information.

[0182] Step 603: The AMF sends a registration acceptance message to the RAN and / or UE.

[0183] Here, step 603 may not be performed, that is, step 603 is an optional step.

[0184] Step 604: The AMF initiates air interface resource release based on the first air interface resource related information and / or the first deregistration related information.

[0185] Step 605: The AMF sends a UE context release instruction to the RAN and / or UE.

[0186] If the UE is an Ambient IoT device and is capable of sending and receiving NAS messages, the UE context release instruction can be sent to the UE via a NAS message. The RAN forwards the NAS message (but does not process it). The scenario described in this paragraph can be understood as the AMF sending the UE context release instruction to the UE, or as the AMF sending the UE context release instruction to the RAN.

[0187] If the UE is an Ambient IoT device but does not have the ability to send and receive NAS messages, the UE context release instruction can be sent by the AMF to the RAN, and then the RAN sends it to the UE through a certain air interface protocol (for example, an existing or newly defined RFID protocol, which is not limited by this application), or the RAN may receive the UE context release instruction but not send it to the UE. It should be noted that in the first case of this paragraph (i.e., the case where the RAN sends it to the UE through a certain air interface protocol), the information or message sent by the RAN to the UE is not necessarily the UE context release instruction, but may also be any other information or message that releases the UE context or air interface resources; in the second case of this paragraph (i.e., the case where the RAN does not send it to the UE), the RAN can release the air interface resources / release the UE context by itself. The situation described in this paragraph can be understood as the AMF sending a UE context release instruction to the RAN.

[0188] If the UE is not an Ambient IoT device but a reader / writer or transceiver, or the UE is actually a virtual UE maintained by the base station to manage Ambient IoT devices, or the UE can also be the RAN (i.e., the UE is actually the UE and / or the RAN), or the RAN and UE are co-located, then the RAN receiving the UE context release instruction is actually equivalent to the UE receiving the UE context release instruction. The situation described in this paragraph can be understood as the AMF sending the UE context release instruction to the UE, or the AMF sending the UE context release instruction to the RAN.

[0189] It should be noted that step 604 and step 605 can also be collectively described as: the AMF sends a UE context release instruction to the RAN and / or the UE based on the first air interface resource related information and / or the first deregistration related information.

[0190] Step 606: Execute the air interface resource release process.

[0191] As a possible implementation manner, the air interface resource release process in this embodiment is all or part of the access network release process.

[0192] In this application example, the AMF determines not to retain the UE's air interface resources and / or release the UE's air interface resources based on the first air interface resource related information, thereby immediately releasing the UE's air interface resources after the UE registration is completed, ensuring that the air interface resources are not wasted. Optionally, the AMF determines not to deregister the UE and / or retain the UE's registration status based on the first deregistration related information.

[0193] Application Example 2

[0194] In this application example, the first network function is AMF and the second network function is UDM. Of course, the first network function and the second network function can also be implemented in other ways, refer to the description of the first network function and the second network function above. In other words, the AMF in this embodiment can be replaced by the first network function or the aforementioned function or entity that can serve as the first network function, and the UDM can be replaced by the second network function or the aforementioned function or entity that can serve as the second network function.

[0195] Figure 7 This is a flow diagram of the communication method provided in the embodiment of the present application. Figure 4 ,like Figure 7 As shown, the communication method includes the following steps:

[0196] Step 701: Execute the UE registration process.

[0197] This embodiment does not limit the specific execution method of the registration process.

[0198] The following steps can be nested in the registration process, that is, at least one of the following steps is performed as part of the registration process or after the registration process is completed.

[0199] Step 702: The AMF obtains second air interface resource related information from the UE's subscription information from the UDM, where the second air interface resource related information includes at least one of the following: whether or not to retain air interface resources, whether or not to release air interface resources, whether or not to retain air interface resources after registration, and whether or not to release air interface resources after registration. And / or, optionally, the AMF obtains second deregistration related information from the UE's subscription information from the UDM, where the second deregistration related information includes at least one of the following: deregister or not deregister, deregister after registration or not deregister, retain or not retain registration status after registration, reject registration or not reject registration, accept registration or not accept registration.

[0200] In another implementation, the second air interface resource related information may not be included in the subscription information, and / or the second deregistration related information may not be included in the subscription information. In one case, the second air interface resource related information and / or the second deregistration related information are not related to the subscription information.

[0201] As an implementation method, the AMF can locally configure the second air interface resource related information and / or the second deregistration related information, for example, through network management configuration.

[0202] As another implementation method, the AMF may not obtain the second air interface resource-related information or the second deregistration-related information, but may obtain information equivalent to the second air interface resource-related information and / or the second deregistration-related information in other ways, for example, inferring that there is no need to retain air interface resources and / or not to register based on other information. One possibility of this situation is that the contract information contains infrequent use / non-immediate use of air interface resources, for example, the contract information contains non-support for features such as data transmission and positioning, or indicates that it is only used for inventory scenarios, etc. The AMF can infer from this information that there is no need to retain air interface resources and retain the registration status.

[0203] Step 703: The AMF sends a registration acceptance message to the RAN and / or UE.

[0204] Here, step 703 may not be performed, that is, step 703 is an optional step.

[0205] Step 704: The AMF initiates air interface resource release based on the second air interface resource related information and / or the second deregistration related information.

[0206] Here, if the second air interface resource related information indicates that the air interface resource does not need to be retained or needs to be released, the AMF initiates the release of the air interface resource.

[0207] Step 705: The AMF sends a UE context release instruction to the RAN and / or UE.

[0208] If the UE is an Ambient IoT device and is capable of sending and receiving NAS messages, the UE context release instruction can be sent to the UE via a NAS message. The RAN forwards the NAS message (but does not process it). The scenario described in this paragraph can be understood as the AMF sending the UE context release instruction to the UE, or as the AMF sending the UE context release instruction to the RAN.

[0209] If the UE is an Ambient IoT device but does not have the ability to send and receive NAS messages, the UE context release instruction can be sent by the AMF to the RAN, and then the RAN sends it to the UE through a certain air interface protocol (for example, an existing or newly defined RFID protocol, which is not limited by this application), or the RAN may receive the UE context release instruction but not send it to the UE. It should be noted that in the first case of this paragraph (i.e., the case where the RAN sends it to the UE through a certain air interface protocol), the information or message sent by the RAN to the UE is not necessarily the UE context release instruction, but may also be any other information or message that releases the UE context or air interface resources; in the second case of this paragraph (i.e., the case where the RAN does not send it to the UE), the RAN can release the air interface resources / release the UE context by itself. The situation described in this paragraph can be understood as the AMF sending a UE context release instruction to the RAN.

[0210] If the UE is not an Ambient IoT device but a reader / writer or transceiver, or the UE is actually a virtual UE maintained by the base station to manage Ambient IoT devices, or the UE can also be the RAN (i.e., the UE is actually the UE and / or the RAN), or the RAN and UE are co-located, then the RAN receiving the UE context release instruction is actually equivalent to the UE receiving the UE context release instruction. The situation described in this paragraph can be understood as the AMF sending the UE context release instruction to the UE, or the AMF sending the UE context release instruction to the RAN.

[0211] It should be noted that step 704 and step 705 can also be collectively described as: the AMF sends a UE context release instruction to the RAN and / or the UE based on the first air interface resource related information and / or the first deregistration related information.

[0212] Step 706: Execute the air interface resource release process.

[0213] As a possible implementation manner, the air interface resource release process in this embodiment is all or part of the access network release process.

[0214] In this application example, the AMF determines not to retain the UE's air interface resources and / or release the UE's air interface resources based on the second air interface resource related information, thereby immediately releasing the UE's air interface resources after the UE registration is completed, ensuring that the air interface resources are not wasted. Optionally, the AMF determines not to deregister the UE and / or retain the UE's registration status based on the second deregistration related information.

[0215] Application Example 3

[0216] In this application example, the first network function is AMF, the second network function is UDM, the third network function is AF, and the fourth network function is NEF. Of course, the first network function, the second network function, the third network function, and the fourth network function can also be implemented in other ways, refer to the description of the first network function, the second network function, the third network function, and the fourth network function in the above text. That is to say, the AMF in this embodiment can be replaced by the first network function or the aforementioned function or entity that can serve as the first network function, the UDM can be replaced by the second network function or the aforementioned function or entity that can serve as the second network function, the AF can be replaced by the third network function or the aforementioned function or entity that can serve as the third network function, and the NEF can be replaced by the fourth network function or the aforementioned function or entity that can serve as the fourth network function.

[0217] Figure 8 This is a flow diagram of the communication method provided in the embodiment of the present application. Figure 5 ,like Figure 8 As shown, the communication method includes the following steps:

[0218] Step 801: Execute the UE registration process.

[0219] This embodiment does not limit the specific execution method of the registration process.

[0220] The following steps can be nested in the registration process, that is, at least one of the following steps is performed as part of the registration process or after the registration process is completed.

[0221] Step 802: The AMF obtains the third deregistration related information from the UDM, including: deregistration, deregistration after registration, and not retaining the registration status after registration. The third deregistration related information can also be described as the fifth information.

[0222] In another implementation, the AMF may locally configure the third-party deregistration related information, for example, through network management configuration.

[0223] In another implementation, the AMF may not obtain the third-party deregistration-related information, but may obtain information equivalent to the third-party deregistration-related information through other means, such as inferring deregistration based on other information. One possible case is that the subscription information contains information related to the tag not supporting actions other than network access, and the AMF can infer that the registration status will not be retained based on this information.

[0224] Optionally, the third deregistration related information may be included in the contract information.

[0225] Step 803: The AMF determines to initiate deregistration based on the third deregistration related information.

[0226] Step 804: The AMF sends at least one of the following to the AF: all or part of the UE's subscription information, all or part of the UE's context, the UE identifier, and UE-related information.

[0227] Here, step 804 may not be performed, that is, step 804 is an optional step.

[0228] Here, the UE's subscription information, UE's context, UE identification, and UE-related information can refer to the above description.

[0229] This application does not limit the method, message or service by which AMF sends the above information to AF.

[0230] As an implementation method, the AMF may send the above information directly to the AF without going through the NEF. As another implementation method, the AMF may send the above information to the AF via the NEF.

[0231] As an implementation method, the AMF may proactively send the above information to the AF. As another implementation method, the AF subscribes to the above information from the AMF, and the AMF sends the above information to the AF based on the subscription event. Here, if the AF subscribes to the information from the AMF, this application does not limit the subscription method and subscription timing of the AF. The AF may subscribe to the information before or during the registration process.

[0232] As another implementation, the UDM sends at least one of the following to the AF (via or without the NEF): all or part of the UE's subscription information, all or part of the UE's context, the UE identifier, and UE-related information. In this implementation, the order of executing steps 804 and 803 is not limited.

[0233] Step 805: AMF initiates the deregistration process.

[0234] This application does not limit the execution method of the deregistration process, for example, it can be executed in accordance with all or part of the deregistration process described in the prior art.

[0235] Application Example 4

[0236] In this application example, the first network function is AMF, the second network function is UDM, the third network function is AF, and the fourth network function is NEF. Of course, the first network function, the second network function, the third network function, and the fourth network function can also be implemented in other ways, refer to the description of the first network function, the second network function, the third network function, and the fourth network function in the above text. That is to say, the AMF in this embodiment can be replaced by the first network function or the aforementioned function or entity that can serve as the first network function, the UDM can be replaced by the second network function or the aforementioned function or entity that can serve as the second network function, the AF can be replaced by the third network function or the aforementioned function or entity that can serve as the third network function, and the NEF can be replaced by the fourth network function or the aforementioned function or entity that can serve as the fourth network function.

[0237] Figure 9 This is a flow diagram of the communication method provided in the embodiment of the present application. Figure 6 ,like Figure 9 As shown, the communication method includes the following steps:

[0238] Step 901: Execute the UE registration process.

[0239] This embodiment does not limit the specific execution method of the registration process.

[0240] The following steps can be nested in the registration process, that is, at least one of the following steps is performed as part of the registration process or after the registration process is completed.

[0241] Step 902: The AMF obtains the second deregistration related information in the UE's subscription information from the UDM, including: deregister or not deregister, deregister after registration or not deregister, retain the registration status after registration or not retain the registration status.

[0242] In another implementation, the second deregistration related information may not be included in the contract information. In one case, the second deregistration related information is not related to the contract information.

[0243] As an implementation method, the AMF can locally configure the second deregistration related information, for example, through network management configuration.

[0244] As another implementation method, the AMF may not obtain the second deregistration related information, but may obtain information equivalent to the second deregistration related information through other means, such as inferring deregistration based on other information. One possible situation in this case is that the contract information contains information related to the tag not supporting actions other than network access, and the AMF can infer that the registration status will not be retained based on this information.

[0245] Step 903: The AMF determines to initiate deregistration based on the second deregistration related information.

[0246] Here, if the second deregistration related information is deregistration, the AMF determines to initiate deregistration.

[0247] Step 904: The AMF sends at least one of the following to the AF: all or part of the UE's subscription information, all or part of the UE's context, the UE identifier, and UE-related information.

[0248] Here, step 904 may not be performed, that is, step 904 is an optional step.

[0249] Here, the UE's subscription information, UE's context, UE identification, and UE-related information can refer to the above description.

[0250] This application does not limit the method, message or service by which AMF sends the above information to AF.

[0251] As an implementation method, the AMF may send the above information directly to the AF without going through the NEF. As another implementation method, the AMF may send the above information to the AF via the NEF.

[0252] As an implementation method, the AMF may proactively send the above information to the AF. As another implementation method, the AF subscribes to the above information from the AMF, and the AMF sends the above information to the AF based on the subscription event. Here, if the AF subscribes to the information from the AMF, this application does not limit the subscription method and subscription timing of the AF. The AF may subscribe to the information before or during the registration process.

[0253] As another implementation, the UDM sends at least one of the following to the AF (via or without the NEF): all or part of the UE's subscription information, all or part of the UE's context, the UE identifier, and UE-related information. In this implementation, the order of executing steps 904 and 903 is not limited.

[0254] Step 905: AMF initiates the deregistration process.

[0255] This application does not limit the execution method of the deregistration process, for example, it can be executed in accordance with all or part of the deregistration process described in the prior art.

[0256] Application Example 5

[0257] In this application example, the first network function is AMF, the second network function is UDM, the third network function is AF, and the fourth network function is NEF. Of course, the first network function, the second network function, the third network function, and the fourth network function can also be implemented in other ways, refer to the description of the first network function, the second network function, the third network function, and the fourth network function in the above text. That is to say, the AMF in this embodiment can be replaced by the first network function or the aforementioned function or entity that can serve as the first network function, the UDM can be replaced by the second network function or the aforementioned function or entity that can serve as the second network function, the AF can be replaced by the third network function or the aforementioned function or entity that can serve as the third network function, and the NEF can be replaced by the fourth network function or the aforementioned function or entity that can serve as the fourth network function.

[0258] Figure 10 This is a flow diagram of the communication method provided in the embodiment of the present application. Figure 7 ,like Figure 10 As shown, the communication method includes the following steps:

[0259] Step 1001: Execute the UE registration process.

[0260] This embodiment does not limit the specific execution method of the registration process.

[0261] The following steps can be nested and executed in the registration process, that is, at least one of the following steps is performed as part of the registration process.

[0262] Step 1002: The AMF obtains the third deregistration related information from the UDM, including registration rejection. The third deregistration related information can also be described as fifth information.

[0263] In another implementation, the AMF may locally configure the third-party deregistration related information, for example, through network management configuration.

[0264] In another implementation, the AMF may not obtain the third deregistration related information, but may obtain information equivalent to the third deregistration related information through other means, such as inferring registration rejection based on other information. One possible case in this case is that the contract information contains information related to the tag not supporting actions other than network access, and the AMF can infer registration rejection based on this information.

[0265] Optionally, the third deregistration related information may be included in the contract information.

[0266] Step 1003: The AMF determines to reject this registration based on the third-party registration related information.

[0267] Step 1004: The AMF sends at least one of the following to the AF: all or part of the UE's subscription information, all or part of the UE's context, the UE identifier, and UE-related information.

[0268] Here, step 1004 may not be performed, that is, step 1004 is an optional step.

[0269] Here, the UE's subscription information, UE's context, UE identification, and UE-related information can refer to the above description.

[0270] This application does not limit the method, message or service by which AMF sends the above information to AF.

[0271] As an implementation method, the AMF may send the above information directly to the AF without going through the NEF. As another implementation method, the AMF may send the above information to the AF via the NEF.

[0272] As an implementation method, the AMF may proactively send the above information to the AF. As another implementation method, the AF subscribes to the above information from the AMF, and the AMF sends the above information to the AF based on the subscription event. Here, if the AF subscribes to the information from the AMF, this application does not limit the subscription method and subscription timing of the AF. The AF may subscribe to the information before or during the registration process.

[0273] As another implementation, the UDM sends at least one of the following to the AF (via or without the NEF): all or part of the UE's subscription information, all or part of the UE's context, the UE identifier, and UE-related information. In this implementation, the order of executing steps 1004 and 1003 is not limited.

[0274] Step 1005: The AMF sends a registration rejection message to the UE and / or access network, including a rejection cause value.

[0275] Here, the rejection reason value includes at least one of the following: data has been transmitted and the registration status does not need to be retained.

[0276] In another embodiment, the data has been transmitted and / or the relevant information of the registration status does not need to be retained, and may not be included in the cause value. In this embodiment, step 1005 may not send a cause value.

[0277] Application Example 6

[0278] In this application example, the first network function is AMF, the second network function is UDM, the third network function is AF, and the fourth network function is NEF. Of course, the first network function, the second network function, the third network function, and the fourth network function can also be implemented in other ways, refer to the description of the first network function, the second network function, the third network function, and the fourth network function in the above text. That is to say, the AMF in this embodiment can be replaced by the first network function or the aforementioned function or entity that can serve as the first network function, the UDM can be replaced by the second network function or the aforementioned function or entity that can serve as the second network function, the AF can be replaced by the third network function or the aforementioned function or entity that can serve as the third network function, and the NEF can be replaced by the fourth network function or the aforementioned function or entity that can serve as the fourth network function.

[0279] Figure 11 This is a flow diagram of the communication method provided in the embodiment of the present application. Figure 8 ,like Figure 11 As shown, the communication method includes the following steps:

[0280] Step 1101: Execute the UE registration process.

[0281] This embodiment does not limit the specific execution method of the registration process.

[0282] The following steps can be nested and executed in the registration process, that is, at least one of the following steps is part of the registration process.

[0283] Step 1102: The AMF obtains the second deregistration related information in the UE's subscription information from the UDM, including: rejecting registration or not rejecting registration, accepting registration or not accepting registration.

[0284] In another implementation, the second deregistration related information may not be included in the contract information. In one case, the second deregistration related information is not related to the contract information.

[0285] In another implementation, the AMF may locally configure the second deregistration related information, for example, through network management configuration.

[0286] In another implementation, the AMF may not obtain the second deregistration-related information, but may obtain information equivalent to the second deregistration-related information through other means, such as inferring registration rejection based on other information. One possible case is that the contract information contains information related to the tag not supporting actions other than network access, and the AMF can infer registration rejection based on this information.

[0287] Step 1103: The AMF determines to reject this registration based on the second deregistration related information.

[0288] Here, if the second registration-related information is to reject the registration, the AMF determines to reject this registration.

[0289] Step 1104: AMF sends at least one of the following to AF: all or part of the UE's subscription information, all or part of the UE's context, UE identity, and UE-related information.

[0290] Here, step 1104 may not be performed, that is, step 1104 is an optional step.

[0291] Here, the UE's subscription information, UE's context, UE identification, and UE-related information can refer to the above description.

[0292] This application does not limit the method, message or service by which AMF sends the above information to AF.

[0293] As an implementation method, the AMF may send the above information directly to the AF without going through the NEF. As another implementation method, the AMF may send the above information to the AF via the NEF.

[0294] As an implementation method, the AMF may proactively send the above information to the AF. As another implementation method, the AF subscribes to the above information from the AMF, and the AMF sends the above information to the AF based on the subscription event. Here, if the AF subscribes to the information from the AMF, this application does not limit the subscription method and subscription timing of the AF. The AF may subscribe to the information before or during the registration process.

[0295] As another implementation, the UDM sends at least one of the following to the AF (via or without the NEF): all or part of the UE's subscription information, all or part of the UE's context, the UE identifier, and UE-related information. In this implementation, the order of executing steps 1004 and 1003 is not limited.

[0296] Step 1105: The AMF sends a registration rejection message to the UE and / or access network, including a rejection cause value.

[0297] Here, the rejection reason value includes at least one of the following: data has been transmitted and the registration status does not need to be retained.

[0298] In another embodiment, the data has been transmitted and / or the relevant information of the registration status does not need to be retained, and may not be included in the cause value. In this embodiment, step 1105 may also not send a cause value.

[0299] Figure 12 This is a schematic diagram of the structure of the communication device provided in the embodiment of the present application. The first network function is applied, such as Figure 12 As shown, the communication device includes:

[0300] The sending unit 1201 is configured to send a UE context release instruction based on the first information or after obtaining the first information.

[0301] In some embodiments, the first information includes at least one of the following: second information, third information, first air interface resource related information, first deregistration related information, first deaccess related information, and all or part of the subscription information of the UE.

[0302] In some embodiments, the second information includes at least one of the following: not reserving air interface resources, releasing air interface resources, not reserving air interface resources after registration or access, and releasing air interface resources after registration or access; and / or, the third information includes at least one of the following: not registering, not registering after registration, retaining registration status after registration, not rejecting registration, accepting registration, not accessing, not accessing after access, retaining access status after access, not rejecting access, and accepting access; and / or, the first air interface resource-related information includes at least one of the following: not reserving air interface resources, releasing air interface resources, not reserving air interface resources after registration or access, and releasing air interface resources after registration or access; and / or, the first de-registration-related information includes at least one of the following: not registering, not registering after registration, retaining registration status after registration, not rejecting registration, and accepting registration; and / or, the first de-access-related information includes at least one of the following: not accessing, not accessing after access, retaining access status after access, not rejecting access, and accepting access.

[0303] In some embodiments, the contract information includes at least one of the following: all or part of the UE identifier, group identifier, passive Internet of Things indication information, device type, PLMN identifier, mobility management related information, session management related information, transmission related information, positioning or ranging related information, positioning format, positioning or ranging accuracy, billing method, validity period of the UE identifier, valid times of the UE identifier, validity period of the contract information, valid times of the contract information, second air interface resource related information, second deregistration related information, second deaccession related information, and network openness related information.

[0304] In some embodiments, the mobility management related information includes at least one of the following: allowing or not allowing mobility management, supporting or not supporting mobility management, requiring or not requiring mobility management; and / or, the session management related information includes at least one of the following: allowing or not allowing session establishment, supporting or not supporting session establishment, requiring or not requiring session establishment; and / or, the transmission related information includes at least one of the following: allowing or not allowing control plane transmission, supporting or not supporting control plane transmission, requiring or not requiring control plane transmission, allowing or not allowing user plane transmission, supporting or not supporting user plane transmission, requiring or not requiring user plane transmission; and / or, the positioning or ranging related information includes at least one of the following: allowing or not allowing positioning or ranging, supporting or not supporting positioning or ranging, requiring or not requiring Positioning or ranging, the format of positioning or ranging, the accuracy of positioning or ranging; and / or, the second air interface resource-related information includes at least one of the following: the need or non-necessity to retain air interface resources, the need or non-necessity to release air interface resources, the need or non-necessity to retain air interface resources after registration, the need or non-necessity to release air interface resources after registration; and / or, the second de-registration-related information includes at least one of the following: de-register or not de-register, de-register after registration or not de-register, retain or not retain the registration status after registration, refuse registration or not refuse registration, accept registration or not accept registration; and / or, the second de-access-related information includes at least one of the following: access or not access, access after access or not access, retain or not retain access status after access, refuse access or not refuse access, accept access or not accept access.

[0305] In some embodiments, the apparatus further includes: a receiving unit 1202, configured to receive at least one of the following from the UE and / or access network: a UE identifier, a group identifier, passive Internet of Things indication information, a device type, and information related to the UE.

[0306] In some embodiments, the UE-related information includes at least one of the following: data information related to the UE, sensor-related data information, and information related to perception, detection, exploration, or measurement by the UE.

[0307] In some embodiments, the UE identifier includes at least one of the following: all or part of the EPC, a universal administrator number, an item category, a PLMN identifier, a group identifier, SUPI, SUCI, GPSI, GUTI, TMSI, PEI; and / or, the device type is one of the following: Class A passive IoT device, Class B passive IoT device, Class C passive IoT device.

[0308] In some embodiments, the apparatus further includes: a configuration unit, configured to locally configure all or part of the first information.

[0309] In some implementations, the receiving unit 1202 is configured to receive all or part of the first information from a second network function.

[0310] In some implementations, the sending unit 1201 is configured to send the UE context release instruction to the UE and / or access network.

[0311] In some implementations, the sending unit 1201 is further configured to trigger, instruct, or request an access network or a reader / writer device to send deactivation or failure related information to the UE.

[0312] In some embodiments, the deactivation or invalidation related information is used for at least one of the following: permanently deactivating the UE, permanently invalidating the UE, temporarily deactivating the UE, temporarily invalidating the UE, deactivating the UE within a certain period of time, and invalidating the UE within a certain period of time.

[0313] In some implementations, the UE is a passive IoT device; and / or the UE is a tag.

[0314] In some embodiments, the first network function includes at least one of the following: AMF, TMF, UDM, UDR.

[0315] In some implementations, the second network function includes at least one of the following: TMF, UDM, UDR, PCF, NEF.

[0316] Those skilled in the art should understand that Figure 12 The implementation functions of each unit in the communication device shown can be understood by referring to the relevant description of the aforementioned method. Figure 12 The functions of the various units in the communication device shown may be implemented by a program running on a processor, or may be implemented by a specific logic circuit.

[0317] Figure 13 This is a schematic diagram of the structure of the communication device provided in the embodiment of the present application. Figure 2 , applied to the first network function, such as Figure 13 As shown, the communication device includes:

[0318] The sending unit 1301 is configured to send a deregistration request message or a deaccess request message based on the fourth information or after obtaining the fourth information; or

[0319] The processing unit 1302 is configured to reject registration request information or access request information of at least one UE based on the fourth information or after obtaining the fourth information.

[0320] In some embodiments, the fourth information includes at least one of the following: the fifth information, the third deregistration related information, the third deaccess related information, and all or part of the subscription information of the UE.

[0321] In some embodiments, the fifth information includes at least one of the following: deregistration, deregistration after registration, not retaining registration status after registration, refusal to register, deaccession, deaccession after access, not retaining access status after access, and refusal to access; and / or, the third deregistration related information includes at least one of the following: deregistration, deregistration after registration, not retaining registration status after registration, and refusal to register; and / or, the third deaccess related information includes at least one of the following: deaccession, deaccession after access, not retaining access status after access, and refusal to access.

[0322] In some embodiments, the contract information includes at least one of the following: all or part of the UE identifier, group identifier, passive Internet of Things indication information, device type, PLMN identifier, mobility management related information, session management related information, transmission related information, positioning or ranging related information, positioning format, positioning or ranging accuracy, billing method, validity period of the UE identifier, valid times of the UE identifier, validity period of the contract information, valid times of the contract information, second air interface resource related information, second deregistration related information, second deaccession related information, and network openness related information.

[0323] In some embodiments, the sending unit 1301 is configured to send at least one of the following to the third network function or to send at least one of the following to the third network function through the fourth network function: all or part of the subscription information of the UE, all or part of the context of the UE, the UE identifier, and information related to the UE.

[0324] In some embodiments, the UE-related information includes at least one of the following: data information related to the UE, sensor-related data information, and information related to perception, detection, exploration, or measurement by the UE.

[0325] In some embodiments, the contract information includes at least one of the following: all or part of the UE identifier, group identifier, passive Internet of Things indication information, device type, PLMN identifier, mobility management related information, session management related information, transmission related information, positioning or ranging related information, positioning format, positioning or ranging accuracy, billing method, validity period of the UE identifier, valid times of the UE identifier, validity period of the contract information, valid times of the contract information, second air interface resource related information, second deregistration related information, second deaccession related information, network openness related information; and / or, the context of the UE includes at least one of the following: all or part of the UE identifier, group identifier, passive Internet of Things indication information, device type, PLMN identifier, mobility management related information, session management related information, transmission related information, positioning or ranging related information, positioning format, positioning or ranging accuracy, billing method, validity period of the UE identifier, valid times of the UE identifier, validity period of the contract information, valid times of the contract information, second air interface resource related information, second deregistration related information, second deaccession related information, network openness related information.

[0326] In some embodiments, the mobility management related information includes at least one of the following: allowing or not allowing mobility management, supporting or not supporting mobility management, requiring or not requiring mobility management; and / or, the session management related information includes at least one of the following: allowing or not allowing session establishment, supporting or not supporting session establishment, requiring or not requiring session establishment; and / or, the transmission related information includes at least one of the following: allowing or not allowing control plane transmission, supporting or not supporting control plane transmission, requiring or not requiring control plane transmission, allowing or not allowing user plane transmission, supporting or not supporting user plane transmission, requiring or not requiring user plane transmission; and / or, the positioning or ranging related information includes at least one of the following: allowing or not allowing positioning or ranging, supporting or not supporting positioning or ranging, requiring or not requiring The positioning or ranging required, the format of positioning or ranging, the accuracy of positioning or ranging; and / or, the second air interface resource related information includes at least one of the following: the need or non-necessity to retain air interface resources, the need or non-necessity to release air interface resources, the need or non-necessity to retain air interface resources after registration, the need or non-necessity to release air interface resources after registration; and / or, the second de-registration related information includes at least one of the following: de-register or not de-register, de-register after registration or not de-register, retain or not retain the registration status after registration, refuse to register or not refuse to register, refuse to register or accept registration; and / or, the second de-access related information includes at least one of the following: access or not access, access after access or not access, retain or not retain the access status after access, refuse access or not refuse access, refuse access or accept access.

[0327] In some embodiments, the UE identifier includes at least one of the following: all or part of the EPC, a universal administrator number, an item category, a PLMN identifier, a group identifier, SUPI, SUCI, GPSI, GUTI, TMSI, PEI; and / or, the device type is one of the following: Class A passive IoT device, Class B passive IoT device, Class C passive IoT device.

[0328] In some implementations, the apparatus further includes: a configuration unit configured to locally configure all or part of the fourth information.

[0329] In some implementations, the apparatus further includes: a receiving unit 1303, configured to receive all or part of the fourth information from a second network function.

[0330] In some implementations, the sending unit 1301 is configured to send the deregistration request information or the deaccess request information to at least one of the UEs and / or access networks.

[0331] In some implementations, the sending unit 1301 is configured to send a sending cause value to at least one of the UEs and / or access networks.

[0332] In some implementations, the cause value includes at least one of the following: data has been transmitted, registration status does not need to be retained, and access status does not need to be retained.

[0333] In some implementations, the sending unit 1301 is further configured to trigger, instruct, or request an access network or a reader / writer device to send deactivation or failure related information to the UE.

[0334] In some embodiments, the deactivation or invalidation related information is used for at least one of the following: permanently deactivating the UE, permanently invalidating the UE, temporarily deactivating the UE, temporarily invalidating the UE, deactivating the UE within a certain period of time, and invalidating the UE within a certain period of time.

[0335] In some implementations, the UE is a passive IoT device; and / or the UE is a tag.

[0336] In some embodiments, the first network function includes at least one of the following: AMF, TMF, UDM, UDR.

[0337] In some implementations, the second network function includes at least one of the following: TMF, UDM, UDR, PCF, NEF.

[0338] In some embodiments, the third network function includes at least one of the following: AF, NEF, PCF, UDM, UDR; and / or the fourth network function includes at least one of the following: NEF, PCF, SMF, TMF, UDM, UDR.

[0339] Those skilled in the art should understand that Figure 13 The implementation functions of each unit in the communication device shown can be understood by referring to the relevant description of the aforementioned method. Figure 13 The functions of the various units in the communication device shown may be implemented by a program running on a processor, or may be implemented by a specific logic circuit.

[0340] Figure 14 This is a schematic structural diagram of a communication device 1400 provided in an embodiment of the present application. Figure 14 The communication device 1400 shown includes a processor 1410, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0341] Alternatively, as Figure 14 As shown, the communication device 1400 may further include a memory 1420. The processor 1410 may call and execute a computer program from the memory 1420 to implement the method in the embodiment of the present application.

[0342] The memory 1420 may be a separate device independent of the processor 1410 , or may be integrated into the processor 1410 .

[0343] Alternatively, as Figure 14 As shown, the communication device 1400 may further include a transceiver 1430 , and the processor 1410 may control the transceiver 1430 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices.

[0344] The transceiver 1430 may include a transmitter and a receiver. The transceiver 1430 may further include an antenna, and the number of antennas may be one or more.

[0345] The communication device 1400 may specifically be the first network function of the embodiment of the present application, and the communication device 1400 may implement the corresponding processes implemented by the first network function in the various methods of the embodiment of the present application. For the sake of brevity, they will not be described here.

[0346] Figure 15 It is a schematic structural diagram of the chip of an embodiment of the present application. Figure 15The chip 1500 shown includes a processor 1510, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0347] Alternatively, as Figure 15 As shown, the chip 1500 may further include a memory 1520. The processor 1510 may call and execute a computer program from the memory 1520 to implement the method in the embodiment of the present application.

[0348] The memory 1520 may be a separate device independent of the processor 1510 , or may be integrated into the processor 1510 .

[0349] Optionally, the chip 1500 may further include an input interface 1530. The processor 1510 may control the input interface 1530 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0350] Optionally, the chip 1500 may further include an output interface 1540. The processor 1510 may control the output interface 1540 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0351] This chip can be applied to the first network function in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the first network function in each method of the embodiment of the present application. For the sake of brevity, it will not be repeated here.

[0352] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0353] It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiment can be completed by hardware integrated logic circuits in the processor or software instructions. The above processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The various methods, steps, and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present application can be directly implemented as a hardware decoding processor, or can be implemented by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0354] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0355] It should be understood that the above-mentioned memories are exemplary but not restrictive. For example, the memories in the embodiments of the present application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM RAM (DR RAM), etc. In other words, the memories in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0356] The present application also provides a computer program product, including computer program instructions. This computer program product can be applied to the first network function in the present application, and the computer program instructions cause a computer to execute the corresponding processes implemented by the first network function in the various methods of the present application. For the sake of brevity, these instructions are not further described here.

[0357] The present application also provides a computer-readable storage medium for storing a computer program. The computer-readable storage medium can be applied to the first network function in the present application, and the computer program causes a computer to execute the corresponding processes implemented by the first network function in the various methods of the present application. For the sake of brevity, these procedures are not further described here.

[0358] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0359] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0360] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0361] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0362] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0363] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0364] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A communication method, characterized in that: The method is applied to a first network function, and the method includes: The first network function sends a user equipment UE context release instruction based on the first information or after obtaining the first information.

2. The method according to claim 1, characterized in that The first information includes at least one of the following: second information, third information, first air interface resource related information, first deregistration related information, first deaccess related information, and all or part of the subscription information of the UE.

3. The method according to claim 2, characterized in that The second information includes at least one of the following: not reserving air interface resources, releasing air interface resources, not reserving air interface resources after registration or access, and releasing air interface resources after registration or access; and / or, The third information includes at least one of the following: not registering, not registering after registration, retaining registration status after registration, not rejecting registration, accepting registration, not accessing, not accessing after accessing, retaining access status after accessing, not rejecting access, accepting access; and / or, The first air interface resource related information includes at least one of the following: not reserving air interface resources, releasing air interface resources, not reserving air interface resources after registration or access, and releasing air interface resources after registration or access; and / or, The first deregistration related information includes at least one of the following: not registering, not registering after registering, retaining the registration status after registering, not rejecting registration, accepting registration; and / or, The first access-related information includes at least one of the following: not accessing, not accessing after accessing, retaining access status after accessing, not rejecting access, and accepting access.

4. The method according to claim 2, characterized in that The contract information includes at least one of the following: all or part of the UE identifier, group identifier, passive Internet of Things indication information, device type, public land mobile network PLMN identifier, mobility management related information, session management related information, transmission related information, positioning or ranging related information, positioning format, positioning or ranging accuracy, billing method, validity period of the UE identifier, valid number of UE identifiers, validity period of contract information, valid number of contract information, second air interface resource related information, second deregistration related information, second deaccession related information, and network openness related information.

5. The method according to claim 4, characterized in that The mobility management related information includes at least one of the following: allowing or not allowing mobility management, supporting or not supporting mobility management, requiring or not requiring mobility management; and / or, The session management related information includes at least one of the following: allowing or not allowing session establishment, supporting or not supporting session establishment, requiring or not requiring session establishment; and / or, The transmission related information includes at least one of the following: allowing or not allowing control plane transmission, supporting or not supporting control plane transmission, requiring or not requiring control plane transmission, allowing or not allowing user plane transmission, supporting or not supporting user plane transmission, requiring or not requiring user plane transmission; and / or, The positioning or ranging related information includes at least one of the following: whether positioning or ranging is allowed or not, whether positioning or ranging is supported or not, whether positioning or ranging is required or not, the format of positioning or ranging, and the accuracy of positioning or ranging; and / or, The second air interface resource related information includes at least one of the following: whether or not air interface resources need to be reserved, whether or not air interface resources need to be released, whether or not air interface resources need to be reserved after registration, and whether or not air interface resources need to be released after registration; and / or The second deregistration related information includes at least one of the following: to register or not to register, to register after registration or not to register, to retain or not retain the registration status after registration, to refuse registration or not to refuse registration, to accept registration or not to accept registration; and / or, The second de-access related information includes at least one of the following: de-access or not de-access, de-access after access or not de-access, retaining or not retaining access status after access, refusing access or not refusing access, accepting access or not accepting access.

6. The method according to claim 1, characterized in that The method further comprises: The first network function receives at least one of the following from the UE and / or the access network: UE identification, group identification, passive Internet of Things indication information, device type, and information related to the UE.

7. The method according to claim 6, characterized in that The UE-related information includes at least one of the following: data information related to the UE, data information related to the sensor, and information related to perception, detection, exploration, or measurement of the UE.

8. The method according to claim 4 or 6, characterized in that The UE identity includes at least one of the following: all or part of the Electronic Product Code (EPC), a universal administrator number, an item category, a PLMN identifier, a group identifier, a subscription permanent identifier (SUPI), a subscription hidden identifier (SUCI), a general public subscription identifier (GPSI), a global unique temporary identifier (GUTI), a temporary mobile subscription identifier (TMSI), and a permanent equipment identifier (PEI); and / or, The device type is one of the following: Class A passive IoT device, Class B passive IoT device, or Class C passive IoT device.

9. The method according to any one of claims 1 to 7, characterized in that The method further comprises: The first network function locally configures all or part of the first information; and / or, The first network function receives all or part of the first information from a second network function.

10. The method according to any one of claims 1 to 7, characterized in that The sending of the UE context release instruction includes: Send the UE context release instruction to the UE and / or access network.

11. The method according to claim 1, wherein The method further comprises: The first network function triggers, instructs, or requests an access network or a read / write device to send deactivation or failure related information to the UE.

12. The method according to claim 11, characterized in that The deactivation or invalidation related information is used for at least one of the following: permanently deactivating the UE, permanently invalidating the UE, temporarily deactivating the UE, temporarily invalidating the UE, deactivating the UE within a certain period of time, and invalidating the UE within a certain period of time.

13. The method according to any one of claims 1 to 7, characterized in that The UE is a passive IoT device; and / or, The UE is a tag.

14. The method according to any one of claims 1 to 7, characterized in that The first network function includes at least one of the following: access and mobility management function AMF, tag management function TMF, unified data management UDM, and unified data storage UDR.

15. The method according to claim 9, characterized in that The second network function includes at least one of the following: TMF, UDM, UDR, policy control function PCF, and network open function NEF.

16. A communication method, characterized in that: The method is applied to a first network function, and the method includes: The first network function sends a deregistration request message or a deaccess request message based on the fourth information or after obtaining the fourth information; or The first network function rejects the registration request information or access request information of at least one UE based on the fourth information or after obtaining the fourth information.

17. The method according to claim 16, characterized in that The fourth information includes at least one of the following: the fifth information, third deregistration related information, third deaccess related information, and all or part of the subscription information of the UE.

18. The method according to claim 17, characterized in that The fifth information includes at least one of the following: deregister, deregister after registration, not retain registration status after registration, refuse registration, deaccess, deaccess after access, not retain access status after access, refuse access; and / or, The third deregistration related information includes at least one of the following: deregistration, deregistration after registration, not retaining registration status after registration, and registration rejection; and / or, The third de-access related information includes at least one of the following: de-access, de-access after access, not retaining access status after access, and access rejection.

19. The method according to claim 17, wherein The contract information includes at least one of the following: all or part of the UE identifier, group identifier, passive Internet of Things indication information, device type, PLMN identifier, mobility management related information, session management related information, transmission related information, positioning or ranging related information, positioning format, positioning or ranging accuracy, billing method, validity period of the UE identifier, valid times of the UE identifier, validity period of the contract information, valid times of the contract information, second air interface resource related information, second deregistration related information, second deaccession related information, and network openness related information.

20. The method according to claim 16, wherein The method further comprises, The first network function sends at least one of the following to the third network function or sends at least one of the following to the third network function through the fourth network function: all or part of the subscription information of the UE, all or part of the context of the UE, the UE identifier, and the UE-related information.

21. The method according to claim 20, characterized in that The UE-related information includes at least one of the following: data information related to the UE, data information related to the sensor, and information related to perception, detection, exploration, or measurement of the UE.

22. The method according to claim 20, characterized in that The subscription information includes at least one of the following: all or part of the UE identifier, group identifier, passive Internet of Things indication information, device type, PLMN identifier, mobility management related information, session management related information, transmission related information, positioning or ranging related information, positioning format, positioning or ranging accuracy, billing method, validity period of the UE identifier, number of valid times of the UE identifier, validity period of the subscription information, number of valid times of the subscription information, second air interface resource related information, second deregistration related information, second deaccession related information, network openness related information; and / or, The context of the UE includes at least one of the following: all or part of the UE identifier, group identifier, passive Internet of Things indication information, device type, PLMN identifier, mobility management related information, session management related information, transmission related information, positioning or ranging related information, positioning format, positioning or ranging accuracy, billing method, validity period of the UE identifier, valid number of UE identifiers, validity period of the contract information, valid number of contract information, second air interface resource related information, second deregistration related information, second deaccession related information, and network openness related information.

23. The method according to claim 19 or 22, characterized in that The mobility management related information includes at least one of the following: allowing or not allowing mobility management, supporting or not supporting mobility management, requiring or not requiring mobility management; and / or, The session management related information includes at least one of the following: allowing or not allowing session establishment, supporting or not supporting session establishment, requiring or not requiring session establishment; and / or, The transmission related information includes at least one of the following: allowing or not allowing control plane transmission, supporting or not supporting control plane transmission, requiring or not requiring control plane transmission, allowing or not allowing user plane transmission, supporting or not supporting user plane transmission, requiring or not requiring user plane transmission; and / or, The positioning or ranging related information includes at least one of the following: whether positioning or ranging is allowed or not, whether positioning or ranging is supported or not, whether positioning or ranging is required or not, the format of positioning or ranging, and the accuracy of positioning or ranging; and / or, The second air interface resource related information includes at least one of the following: whether or not air interface resources need to be reserved, whether or not air interface resources need to be released, whether or not air interface resources need to be reserved after registration, and whether or not air interface resources need to be released after registration; and / or The second deregistration related information includes at least one of the following: to register or not to register, to register after registration or not to register, to retain or not retain the registration status after registration, to refuse registration or not to refuse registration, to refuse registration or to accept registration; and / or, The second access de-access related information includes at least one of the following: de-access or not de-access, de-access after access or not de-access, retaining or not retaining access status after access, refusing access or not refusing access, refusing access or accepting access.

24. The method according to claim 19 or 22, characterized in that The UE identity includes at least one of the following: all or part of the Electronic Product Code (EPC), a universal administrator number, an item category, a PLMN identifier, a group identifier, a subscription permanent identifier (SUPI), a subscription hidden identifier (SUCI), a general public subscription identifier (GPSI), a global unique temporary identifier (GUTI), a temporary mobile subscription identifier (TMSI), and a permanent equipment identifier (PEI); and / or, The device type is one of the following: Class A passive IoT device, Class B passive IoT device, or Class C passive IoT device.

25. The method according to any one of claims 16 to 22, characterized in that The method further comprises: The first network function locally configures all or part of the fourth information; and / or, The first network function receives all or part of the fourth information from the second network function.

26. The method according to any one of claims 16 to 22, characterized in that The sending of the deregistration request information or the deaccess request information includes: Sending the deregistration request information or the deaccess request information to at least one of the UEs and / or the access network.

27. The method according to any one of claims 16 to 22, characterized in that The method further comprises: Sending a sending cause value to at least one of the UEs and / or access networks.

28. The method according to claim 27, characterized in that The reason value includes at least one of the following: data has been transmitted, registration status does not need to be retained, and access status does not need to be retained.

29. The method according to claim 16, wherein The method further comprises: The first network function triggers, instructs, or requests an access network or a read / write device to send deactivation or failure related information to the UE.

30. The method according to claim 29, wherein The deactivation or invalidation related information is used for at least one of the following: permanently deactivating the UE, permanently invalidating the UE, temporarily deactivating the UE, temporarily invalidating the UE, deactivating the UE within a certain period of time, and invalidating the UE within a certain period of time.

31. The method according to any one of claims 16 to 22, characterized in that The UE is a passive IoT device; and / or, The UE is a tag.

32. The method according to any one of claims 16 to 22, characterized in that The first network function includes at least one of the following: AMF, TMF, UDM, UDR.

33. The method according to claim 25, wherein The second network function includes at least one of the following: TMF, UDM, UDR, PCF, NEF.

34. The method according to claim 20, wherein The third network function includes at least one of the following: AF, NEF, PCF, UDM, UDR; and / or, The fourth network function includes at least one of the following: NEF, PCF, SMF, TMF, UDM, and UDR.

35. A communication device, characterized in that: The device is applied to a first network function, and the device includes: A sending unit is configured to send a UE context release instruction based on the first information or after obtaining the first information.

36. The device according to claim 35, characterized in that The first information includes at least one of the following: second information, third information, first air interface resource related information, first deregistration related information, first deaccess related information, and all or part of the subscription information of the UE.

37. A communication device, characterized in that: The device is applied to a first network function, and the device includes: a sending unit, configured to send deregistration request information or deaccess request information based on the fourth information or after obtaining the fourth information; or The processing unit is configured to reject registration request information or access request information of at least one UE based on the fourth information or after obtaining the fourth information.

38. The device according to claim 37, characterized in that The fourth information includes at least one of the following: the fifth information, third deregistration related information, third deaccess related information, and all or part of the subscription information of the UE.

39. A communication device, characterized in that: include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method according to any one of claims 1 to 34.

40. A computer program product, characterized in that The method comprises computer program instructions for causing a computer to perform the method according to any one of claims 1 to 34.

41. A computer-readable storage medium, characterized in that Used to store a computer program, the computer program causing a computer to execute the method according to any one of claims 1 to 34.

Images