Communication method, apparatus and device, and readable storage medium

Abstract

The embodiment of the invention provides a communication method and device, equipment and a readable storage medium. The method comprises the steps that a first function sends first information to a second function; the first information comprises at least one of the following items: all or part of identifiers of all or part of at least one first terminal, a group identifier, passive Internet of Things indication information, a session identifier or a connection identifier, and all or part of device types of the at least one first terminal; the position information of all or part of the at least one first terminal is DNN and S-NSSAI.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communication technology, and specifically to a communication method, apparatus, device, and readable storage medium. Background Art

[0002] In related technologies, session management processes are designed for active devices. For passive devices, larger-scale terminal access and simplified tagging capabilities require simpler and more efficient session management methods.

[0003] Currently, how to establish a session or connection for Ambient IoT (devices) to transmit data through the user plane is an urgent problem to be solved. Summary of the Invention

[0004] The embodiments of the present application provide a communication method, apparatus, device, and readable storage medium to solve the problem of how AmbientIoT devices establish sessions or connections for transmission through the user plane.

[0005] In a first aspect, a communication method is provided, applied to a first function, the method comprising:

[0006] The first function sends the first information to the second function;

[0007] Among them, the first information includes at least one of the following: all or part of the identification of all or part of at least one first terminal, group identification, passive Internet of Things indication information, session identification or connection identification, all or part of the device type of at least one first terminal, all or part of the location information of at least one first terminal, DNN, S-NSSAI.

[0008] In a second aspect, a communication method is provided, which is applied to the second function, and the method includes:

[0009] The second function obtains seventh information from the fourth function, where the seventh information includes at least one of the following: contract information of the first terminal, contract information related to the RAN, and contract information of the second terminal related to the RAN.

[0010] In a third aspect, a communication method is provided, which is applied to the fourth function, and the method includes:

[0011] The fourth function stores seventh information, where the seventh information includes at least one of the following: contract information of the first terminal, contract information related to the RAN, and contract information of the second terminal related to the RAN.

[0012] In a fourth aspect, a communication method is provided, applied to the fifth function, the method comprising:

[0013] The fifth function generates or determines or locally determines DNN and / or S-NSSAI.

[0014] In a fifth aspect, a communication method is provided, applied to the sixth function, the method comprising:

[0015] The sixth function receives eleventh information from the seventh function, and the eleventh information includes at least one of the following: all or part of the terminal identifier of the first terminal, a group identifier, a session identifier or a connection identifier, passive Internet of Things indication information, a device type of the first terminal, and location information of the first terminal.

[0016] In a sixth aspect, a communication method is provided, applied to the ninth function, the method comprising:

[0017] The ninth function associates the data related to the first terminal with the first session, the first tunnel, or the first connection.

[0018] In a seventh aspect, a communication device is provided, applied to the first function, including:

[0019] A first sending module, configured to send first information to a second function;

[0020] Among them, the first information includes at least one of the following: all or part of the identification of all or part of at least one first terminal, group identification, passive Internet of Things indication information, session identification or connection identification, all or part of the device type of at least one first terminal, all or part of the location information of at least one first terminal, DNN, S-NSSAI.

[0021] In an eighth aspect, a communication device is provided, applied to the second function, including:

[0022] The third receiving module is used to obtain seventh information from the fourth function, where the seventh information includes at least one of the following: contract information of the first terminal, contract information related to the RAN, and contract information of the second terminal related to the RAN.

[0023] In a ninth aspect, a communication device is provided, applied to the fourth function, including:

[0024] The storage module is used to store seventh information, where the seventh information includes at least one of the following: contract information of the first terminal, contract information related to the RAN, and contract information of the second terminal related to the RAN.

[0025] In a tenth aspect, a communication device is provided, applied to the fifth function, including:

[0026] A fifth processing module is configured to generate or determine or locally determine a DNN and / or an S-NSSA.

[0027] According to an eleventh aspect, a communication device is provided, adapted for the sixth function, including:

[0028] The fifth receiving module is used to receive the eleventh information from the seventh function, and the eleventh information includes at least one of the following: all or part of the terminal identifier of the first terminal, the group identifier, the session identifier or the connection identifier, the passive Internet of Things indication information, the device type of the first terminal, and the location information of the first terminal.

[0029] According to a twelfth aspect, a communication device is provided, applied to the ninth function, including:

[0030] a seventh processing module, configured to associate the data related to the first terminal with the first session, the first tunnel, or the first connection;

[0031] The first session is an existing session, and / or the first connection is an existing connection, and / or the first tunnel is an existing tunnel or a previous tunnel or a tunnel associated with an existing session.

[0032] In the thirteenth aspect, a network function is provided, including a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method described in the first aspect, the second aspect, the third aspect, the fourth aspect, the fifth aspect, or the sixth aspect.

[0033] In the fourteenth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect, the second aspect, the third aspect, the fourth aspect, the fifth aspect, or the sixth aspect are implemented.

[0034] In the present application, by sending the first information to the second function through the first function, it is possible to manage the first terminal (for example, an Ambient IoT device) through the mobile network, and / or to manage the session or connection of the first terminal, and / or to associate the data of at least one first terminal through a session or connection, thereby achieving the purpose of saving costs and facilitating management. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] Various other advantages and benefits will become apparent to those skilled in the art upon reading the detailed description of the preferred embodiment below. The accompanying drawings are for illustration purposes only and are not to be considered as limiting the present application. The same reference symbols are used throughout the drawings to represent the same components. In the drawings:

[0036] Figure 1 It is a schematic diagram of direct connection;

[0037] Figure 2It is a schematic diagram of the relay type;

[0038] Figure 3a and Figure 3b This is a schematic diagram of an uplink / downlink relay type;

[0039] Figure 4 It is a freestanding schematic diagram;

[0040] Figure 5 It is a schematic diagram of the network architecture;

[0041] Figure 6 It is a simplified diagram of the network architecture;

[0042] Figure 7 It is the existing user plane protocol stack;

[0043] Figure 8a 、 Figure 8b and Figure 8c Schematic diagram of a user plane protocol stack supporting Ambient IoT devices provided by an embodiment of the present application;

[0044] Figure 9 This is one of the flow charts of the communication method provided in the embodiment of the present application;

[0045] Figure 10 This is the second flow chart of the communication method provided in the embodiment of the present application;

[0046] Figure 11 This is the third flow chart of the communication method provided in the embodiment of the present application;

[0047] Figure 12 This is the fourth flow chart of the communication method provided in the embodiment of the present application;

[0048] Figure 13 This is the fifth flow chart of the communication method provided in the embodiment of the present application;

[0049] Figure 14 This is the sixth flow chart of the communication method provided in the embodiment of the present application;

[0050] Figure 15 This is the seventh flow chart of the communication method provided in the embodiment of the present application;

[0051] Figure 16 This is the eighth flow chart of the communication method provided in the embodiment of the present application;

[0052] Figure 17 This is a schematic diagram of the field description of the EPC provided in the embodiment of the present application;

[0053] Figure 18 This is one of the schematic diagrams of the communication device provided in the embodiment of the present application;

[0054] Figure 19 This is a second schematic diagram of a communication device provided in an embodiment of the present application;

[0055] Figure 20 This is the third schematic diagram of the communication device provided in an embodiment of the present application;

[0056] Figure 21 This is the fourth schematic diagram of the communication device provided in an embodiment of the present application;

[0057] Figure 22 This is the fifth schematic diagram of the communication device provided in an embodiment of the present application;

[0058] Figure 23 This is the sixth schematic diagram of the communication device provided in an embodiment of the present application;

[0059] Figure 24 It is a schematic diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0060] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0061] The term "comprise" and any variations thereof in the specification and claims of this application are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units that are not explicitly listed or that are inherent to the process, method, product, or apparatus. In addition, the use of "and / or" in the specification and claims to indicate at least one of the connected objects, such as A and / or B, means that A alone, B alone, and both A and B are included.

[0062] In the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this application should not be interpreted as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0063] In order to better understand the embodiments of this application, the following technical points are first introduced:

[0064] (1) Passive IoT

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

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

[0067] While the aforementioned low-power IoT technologies aim to achieve low power consumption and widespread connectivity for IoT terminals, the continuous evolution of technology and the increasing industry adoption of fifth-generation mobile communications (5G) technology are increasing the variety of connected objects, placing higher demands on the price and power consumption of communication terminals. Against this backdrop, passive IoT has emerged on the industry stage and has become a hot topic in the past two years. Passive IoT utilizes ambient energy harvesting to convert available signals and energy into electrical energy that can drive its own circuits, using a scattering-based communication model to transmit information to target nodes. Its most notable feature is its independence from traditional battery power, effectively addressing bottlenecks in the development of low-power IoT. It is a key technology for the next generation of IoT, with widespread applications in smart warehousing, logistics, asset management, and other fields.

[0068] (2) Radio Frequency Identification (RFID)

[0069] In the 1940s, improvements and applications in radar gave rise to RFID, the most representative passive IoT technology. RFID systems consist of tags, readers, and a control platform. The readers utilize the principles of inductive coupling or backscatter coupling to send electromagnetic signals to the tags. The tags convert the electromagnetic signals into energy, activating the tag chip and returning information, enabling the identification of the target object. Currently, mainstream RFID systems internationally support multiple frequency bands. Ultra-high frequency (UHF) RFID systems (850MHz to 910MFz) utilize electromagnetic backscatter technology, offering a theoretical transmission range of 1-10 meters and a wide range of applications across numerous industries, including logistics, manufacturing, and aviation.

[0070] (3) Ambient IoT device types and connection modes

[0071] Related technologies define several application scenarios of Ambient IoT, which generally include indoor and outdoor. Indoor scenarios (or local scenarios) include inventory management, electronic price tags, and indoor small item search, while outdoor scenarios (or wide-area scenarios) include logistics and transportation, public facility monitoring, and smart ranches.

[0072] Table 1: Three types of Ambient IoT devices.

[0073]

[0074] See also Figure 1 、 Figure 2 、 Figure 3a and Figure 3b ,as well as Figure 4 The figure shows four Ambient IoT device connection modes.

[0075] Existing session establishment solutions have the following problems for Ambient IoT devices:

[0076] 1. Class B devices (and possibly some Class C devices) cannot actively initiate session establishment;

[0077] 2. Considering the maintenance cost of sessions and the low cost of Ambient IoT devices, establishing sessions for Ambient IoT devices in the current way is not commercially sensible;

[0078] 3. Ambient IoT devices may not support the application layer.

[0079] (4) Basic network architecture

[0080] The current 5G non-roaming network architecture is as follows Figure 5As shown in the figure. Since Ambient IoT devices are simple and require relatively simple services, but the number of them is often large, and many scenarios may actually be deployed within the park, there is an idea to simplify the network architecture, for example Figure 6 The architecture shown.

[0081] It should be noted that this architecture is an implementation method of simplifying the basic network architecture. The Access and Mobility Management Function (AMF), Session Management Function (SMF), and User Plane Function (UPF) in the figure are necessary core network elements, the Network Repository Function (NRF) is an optional core network element (for example, it may be involved in some scenarios of Ambient IoT devices or certain processes), and the Application Function (AF) and Application Server (AS) are non-core network elements. It should be noted that this architecture only includes the network functions used in this application. In fact, the network architecture that supports Ambient IoT devices may include other mandatory and / or optional network functions (or may not include them). Another point that needs to be noted is that with the development of communication standards and the evolution of network architecture, the names and functions of the network elements in the figure may change. For example, some architectural designs use a dedicated new network element to replace (or partially replace) AMF.

[0082] In this application, Ambient IoT devices (or A-IoT devices for short) are also commonly referred to as "tags". Figure 1 The solution is a direct-connected architecture, so in the application, the tag is the UE. It should be noted that in the embodiments of the application, the Ambient IoT device is sometimes referred to as a tag for ease of understanding; and because the embodiments of this application are illustrated according to the direct-connected architecture, it is assumed that UE, tag, and Ambient IoT device are equivalent. That is, the words "tag", "UE", "Ambient IoT device", etc. can be replaced arbitrarily; in addition, it should be noted that the UE is not necessarily a tag or an Ambient IoT device, but may be any function or entity that can provide an Ambient IoT identifier (for example, an entity that collects and stores tag identifiers and / or other information, not necessarily a 3rd Generation Partnership Project (3GPP) network function).

[0083] It should be pointed out that since the complexity of Ambient IoT devices can be lower than any UE defined in the existing 3GPP standards, the protocol stacks in the existing standards (such as Figure 7 Not all Ambient IoT devices support the same protocol (as shown in the figure). For example, some Ambient IoT devices may not support application layer messages, or they may not support the sending and receiving of Non-Access Stratum (NAS) messages. In such cases, the user plane protocol stack in the existing standard may not function properly. Alternatively, a different user plane protocol stack may be used to better adapt to existing RFID-related technologies. Figures 8a to 8c Three possible user plane protocol stacks are listed.

[0084] See also Figure 8a The first user plane protocol stack is closest to existing technologies and is also a more feasible solution. There are no restrictions on the protocol between the UE and the Radio Access Network (RAN), for example, a certain RFID protocol can be used (of course, the 5G-AN protocol in existing technologies may also be used). The protocol between the RAN and the UPF follows the underlying protocols in existing technologies, namely Layer 1 (L1), Layer 2 (L2), User Datagram Protocol (UDP) / Internet Protocol (IP), and GPRS Tunneling Protocol-User Plane (GTP-U). The application layer between the PDU Session Anchor (PSA) and the application function (AF) or application server (AS) can use the Message Queuing Telemetry Transport (MQTT) or Low Level Reader Protocol (LLRP), or other reasonable protocols applicable to Ambient IoT or RFID data transmission. There are no restrictions on the underlying protocols.

[0085] See also Figure 8b The second user plane protocol stack establishes an application layer protocol (such as MQTT or LLRP) between RAN and PSA, that is, RAN acts as the reader and writer of the application layer protocol, and PSA acts as the client. Figure 5In the N3 (and N9) tunnel transmission in the illustrated architecture, new application layer protocols and underlying protocols are used (this application is not limited to the protocol, for example, the application layer uses MQTT or LLRP protocols).

[0086] See also Figure 8c The third user plane protocol stack establishes an application layer protocol (such as MQTT or LLRP) between the RAN and the AF or AS. That is, the RAN acts as the reader and writer of the application layer protocol, and the AF or AS acts as the client. Figure 5 In the N3 (and N9) and N6 tunnel transmission in the illustrated architecture, new application layer protocols and underlying protocols are used (the present invention is not limited to the protocol, for example, the application layer uses MQTT or LLRP protocols).

[0087] It should be noted that the current definition of the Protocol Data Unit (PDU) session in the relevant technology is: the association between the UE and the data network that provides the PDU connection service. In fact, since Ambient IoT devices do not necessarily have active signaling capabilities, the "session" referred to in this application is not necessarily the connection / association between the UE and the data network (DN), but may also be the connection / association between the RAN and the PSA / UPF, the UE and the PSA / UPF, and the RAN and the DN. In some senses, "session" can actually be called "connection", "tunnel", etc. That is, "session", "connection" and "tunnel" in this application can be used interchangeably.

[0088] See also Figure 9 , an embodiment of the present application provides a communication method, the execution subject may be a first function, for example, the first function includes but is not limited to at least one of the following: radio access network (Radio Access Network, RAN), terminal, and the specific steps include: step 901.

[0089] Step 901: The first function sends a first message to the second function;

[0090] Among them, the first information includes at least one of the following items: all or part of the identification of all or part of at least one first terminal, group identification, passive Internet of Things indication information (or called Ambient IoT indication information), session identification or connection identification, all or part of the device type of at least one first terminal, all or part of the location information of at least one first terminal, data network name (Data Network Name, DNN), single network slice selection assistance information (Single Network Slice Selection Assistance Information, S-NSSAI).

[0091] Optionally, the first information is used to establish or modify a session, or the first information is used to establish or modify a connection.

[0092] It should be noted that in this application, the terminal (UE), tag, and Ambient IoT device can be interchangeable, that is, the above-mentioned first terminal can also be called a first tag or a first Ambient IoT device.

[0093] Optionally, the first information may also include all or part of the identifier of the second terminal. It should be noted that the second terminal can be understood as a virtual UE. For example, a virtual UE is maintained in the RAN. After the RAN receives one or more UE identifiers, the RAN sends the virtual UE identifier to the AMF or SMF. The RAN itself maintains the correspondence between the virtual UE identifier and one or more UE identifiers, but the network side can only see the virtual UE identifier. That is, from the perspective of the core network, there is no difference from establishing a normal session.

[0094] Optionally, the second function may include at least one of the following: SMF, AMF, tag management function (Tag Management Function, TMF), and RAN.

[0095] In one embodiment of the present application, the method further includes:

[0096] The first function receives second information from the at least one first terminal, and the second information includes at least one of the following: all or part of the terminal identifier of the first terminal, the group identifier, the passive Internet of Things indication information, the session identifier or connection identifier, the device type of the first terminal, and the location information of the first terminal.

[0097] Optionally, the terminal identifier includes at least one of the following: an electronic product code, a part of the electronic product code, a universal administrator number, an item category, a public land mobile network (PLMN) identifier, a group identifier, a user permanent identifier (SUbscription Permanent Identifier, SUPI), a user concealed identifier (Subscription concealed identifier, SUCI), a generic public user identifier (Generic Public Subscription Identifier, GPSI), a globally unique temporary UE identifier (Globally Unique Temporary UE Identity, GUTI), a temporary mobile user identifier (Temporary Mobile Subscriber Identity, TMSI), and a permanent equipment identifier (Permanent Equipment identifier, PEI).

[0098] Optionally, the device type is at least one of the following: Class A passive Internet of Things device, Class B passive Internet of Things device, and Class C passive Internet of Things device.

[0099] Optionally, the first terminal includes a passive Internet of Things device and / or a tag.

[0100] In an embodiment of the present application, the second information may be received by the first function within a period of time, and / or the second information is received by the first terminal from a terminal of a specific type.

[0101] In one embodiment of the present application, the method further comprises:

[0102] The first function determines and / or generates third information, and the third information includes at least one of the following: the session identifier or connection identifier, DNN, and S-NSSAI.

[0103] In one embodiment of the present application, the method further comprises:

[0104] The first function sends fourth information to the at least one first terminal, where the fourth information is used to trigger establishment or modification of a session or connection of the at least one first terminal.

[0105] In one embodiment of the present application, the method further comprises:

[0106] The first function determines, according to the fifth information, triggering establishment or modification of a session or connection of the at least one first terminal;

[0107] The fifth information is used to instruct the first function to send the fourth information to the at least one first terminal, and / or the fifth information is used to trigger the at least one first terminal to initiate establishment or modification of a session or connection.

[0108] In one embodiment of the present application, the method further comprises:

[0109] The first function receives the first information from a third function.

[0110] Optionally, the third function includes at least one of the following: application function (AF), network exposure function (NEF), policy control function (PCF), unified data storage (UDR), and unified data management (UDM).

[0111] In one embodiment of the present application, the method further comprises:

[0112] The first function determines a destination address for forwarding the downlink message according to the at least one terminal identifier and / or group identifier and / or location information of the at least one first terminal.

[0113] In one embodiment of the present application, the method further comprises:

[0114] The first function sends sixth information to the second function via Next Generation Application Protocol (NGAP);

[0115] Among them, the sixth information includes at least one of the following: all or part of the identifier of the at least one first terminal, all or part of the identifier of the second terminal related to the RAN, the group identifier, the passive Internet of Things indication information, the session identifier or the connection identifier, the device type of the at least one first terminal, and the location information of the at least one first terminal.

[0116] It should be noted that the RAN-related second terminal can be understood as a RAN-related virtual UE. For example, a virtual UE is maintained in the RAN. After the RAN receives one or more UE identifiers, the RAN can send the virtual UE identifier to the AMF or SMF. The RAN itself maintains the correspondence between the identifier of the virtual UE (second terminal) and the identifiers of one or more UEs (first terminal).

[0117] In this application, by sending the first information to the second function through the first function, the following technical effects can be achieved:

[0118] (1) Implementing management of a first terminal (e.g., an Ambient IoT device) via a mobile network. The first terminal is integrated with the mobile network, and the capabilities of the mobile network are introduced into the management and related information processing of the first terminal. Specifically, the present invention has at least the following beneficial effects: a) facilitating unified management of the first terminal, b) facilitating the transmission of massive amounts of data from the first terminal or large-scale / long-distance transmission of data, and c) utilizing the data processing capabilities of the core network.

[0119] (2) Manage the session or connection of the first terminal. In some scenarios, such as temperature sensing scenarios for precision equipment or extreme environmental conditions, the first terminal (such as an Ambient IoT device) needs to achieve high-frequency data transmission, so it is necessary to use sessions or connections to transmit data on the user side. However, due to its simple structure and low capabilities, the Ambient IoT device may not have the ability to actively send signaling, so how to manage sessions or connections becomes a problem that needs to be solved. In this application, the first information sent by the first function to the second function can manage the session or connection of the first terminal.

[0120] (3) Associating the data of at least one first terminal with the same session or connection. As a passive IoT device terminal, the first terminal has the important features of low cost and high clustering when used in some scenarios, that is, a large number of first terminals are used for data transmission in the same scenario and the same area. Combining the above two points, since sessions or connections have certain maintenance costs and there may be a large number of first terminals that transmit data through the same user plane path, associating the data of these first terminals with the same session or connection has the advantages of easy management and cost savings.

[0121] See also Figure 10 , an embodiment of the present application provides a communication method, the execution subject may be a second function, the second function may include at least one of the following: SMF, AMF, TMF, RAN, the specific steps include: step 1001.

[0122] Step 1001: The second function obtains seventh information from the fourth function, where the seventh information includes at least one of the following: contract information of the first terminal, contract information related to the RAN, and contract information of the second terminal related to the RAN.

[0123] It should be noted that the second terminal can be understood as a virtual UE. For example, a virtual UE is maintained in the RAN. After the RAN receives one or more UE identifiers, it sends the virtual UE identifier to the AMF or SMF. The RAN itself maintains the correspondence between the identifier of the virtual UE (second terminal) and the identifiers of one or more UEs (first terminal). However, the network side can only see the identifier of the virtual UE (second terminal). In other words, from the perspective of the core network, there is no difference from a normal session establishment.

[0124] Optionally, the fourth function may include at least one of the following: UDM, UDR, TMF, PCF, NEF, SMF.

[0125] In one embodiment of the present application, the contract information may include at least one of the following: all or part of the terminal identifier, group identifier, passive Internet of Things indication information, device type, public land mobile network (PLMN) identifier, mobility management related information, session or connection management related information, transmission related information, positioning or ranging related information, positioning format, positioning or ranging accuracy, billing method, validity period of the terminal identifier, valid number of terminal identifiers, validity period of contract information, valid number of contract information, air interface resource related information, deregistration or deaccession related information, and network openness related information.

[0126] In an embodiment of the present application, the mobility management related information may include one or more of the following: allowing or not allowing mobility management, supporting or not supporting mobility management, requiring or not requiring mobility management.

[0127] In one embodiment of the present application, the session or connection management related information may include one or more of the following: allowing or not allowing establishment of a session or connection, supporting or not supporting establishment of a session or connection, requiring or not requiring establishment of a session or connection.

[0128] In one embodiment of the present application, the transmission-related information may include one or more 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.

[0129] In one embodiment of the present application, the positioning or ranging related information may include one or more 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.

[0130] In one embodiment of the present application, the air interface resource related information may include one or more 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, and the need or non-necessity to release air interface resources after registration.

[0131] In one embodiment of the present application, the deregistration related information may include one or more of the following: deregistering or not deregistering, deregistering after registration or not deregistering, retaining or not retaining the registration status after registration, refusing registration or not refusing registration / accepting registration.

[0132] In one embodiment of the present application, the de-access related information may include one or more 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, rejecting access or not rejecting access / accepting access.

[0133] In one embodiment of the present application, the method may further include:

[0134] The second function receives first information from the first function;

[0135] The first information may include at least one of the following: all or part of the identification of all or part of at least one first terminal, a group identification, passive Internet of Things indication information, a session identification or a connection identification, all or part of the device type of the at least one first terminal, all or part of the location information of the at least one first terminal, DNN, S-NSSAI.

[0136] Optionally, the first information is used to establish or modify a session, or the first information is used to establish or modify a connection.

[0137] Optionally, the first function may include but is not limited to at least one of the following: RAN, terminal.

[0138] In one embodiment of the present application, the terminal identifier includes at least one of the following: an electronic product code, a part of the electronic product code, a universal administrator number, an item category, a PLMN identifier, a group identifier, SUPI, SUCI, GPSI, GUTI, TMSI, or PEI.

[0139] In one embodiment of the present application, the device type may be at least one of the following: Class A passive Internet of Things device, Class B passive Internet of Things device, Class C passive Internet of Things device.

[0140] In one embodiment of the present application, the first terminal may include a passive Internet of Things device and / or a tag.

[0141] In the present application, the session or connection establishment of the first terminal can be realized to simplify the session or connection process, save resources and costs, and facilitate batch first terminal management and batch data transmission.

[0142] See also Figure 11 The embodiment of the present application provides a communication method, the execution subject may be a fourth function, for example, the fourth function may include at least one of the following: UDM, UDR, TMF, PCF, NEF, SMF, the specific steps include:

[0143] Step 1101: The fourth function stores seventh information, where the seventh information includes at least one of the following: contract information of the first terminal, contract information related to the RAN, and contract information of the second terminal related to the RAN.

[0144] In one embodiment of the present application, the method further includes:

[0145] The fourth function sends the seventh information to the second function.

[0146] In one embodiment of the present application, the method further includes:

[0147] The fourth function authenticates the request to establish or modify the session or connection based on the eighth information;

[0148] Among them, the eighth information may include at least one of the following: all or part of the contract information of the first terminal, all or part of the contract information related to the RAN, and all or part of the contract information of the second terminal related to the RAN.

[0149] In one embodiment of the present application, the contract information may include at least one of the following: all or part of the terminal identification, group identification, passive Internet of Things indication information, device type, PLMN ID, mobility management related information, session or connection management related information, transmission related information, positioning or ranging related information, positioning format, positioning or ranging accuracy, billing method, validity period of the terminal identification, valid number of terminal identification, validity period of contract information, valid number of contract information, air interface resource related information, deregistration or deaccession related information, and network openness related information.

[0150] In an embodiment of the present application, the mobility management related information may include one or more of the following: allowing or not allowing mobility management, supporting or not supporting mobility management, requiring or not requiring mobility management.

[0151] In one embodiment of the present application, the session or connection management related information may include one or more of the following: allowing or not allowing establishment of a session or connection, supporting or not supporting establishment of a session or connection, requiring or not requiring establishment of a session or connection.

[0152] In one embodiment of the present application, the transmission-related information may include one or more 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.

[0153] In one embodiment of the present application, the positioning or ranging related information may include one or more 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.

[0154] In one embodiment of the present application, the air interface resource related information may include one or more 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, and the need or non-necessity to release air interface resources after registration.

[0155] In one embodiment of the present application, the deregistration related information may include one or more of the following: deregistering or not deregistering, deregistering after registration or not deregistering, retaining or not retaining the registration status after registration, refusing registration or not refusing registration / accepting registration.

[0156] In one embodiment of the present application, the de-access related information may include one or more 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, rejecting access or not rejecting access / accepting access.

[0157] In one embodiment of the present application, the terminal identifier may include at least one of the following: electronic product code, part of the electronic product code, universal administrator number, item category, PLMN identifier, group identifier, SUPI, SUCI, GPSI, GUTI, TMSI, PEI.

[0158] In one embodiment of the present application, the device type may include at least one of the following: Class A passive Internet of Things device, Class B passive Internet of Things device, and Class C passive Internet of Things device.

[0159] In one embodiment of the present application, the first terminal includes a passive Internet of Things device and / or a tag.

[0160] In the present application, it is possible to manage a first terminal (e.g., an Ambient IoT device) through a mobile network, and / or manage a session or connection of the first terminal, and / or associate data of at least one first terminal through a session or connection, thereby achieving cost savings and facilitating management.

[0161] See also Figure 12 , an embodiment of the present application provides a communication method, the execution subject may be the fifth function, for example, the fifth function may include at least one of the following: AMF, TMF, RAN, SMF, and the specific steps include: step 1201.

[0162] Step 1201: The fifth function generates or determines or locally determines a DNN and / or S-NSSAI.

[0163] Optionally, the DNN and / or S-NSSAI is used to establish or modify a session or connection of the first terminal.

[0164] Optionally, the fifth function generates or determines or locally determines a DNN and / or S-NSSAI for establishing or modifying a session or connection of the first terminal.

[0165] In one embodiment of the present application, the method further includes:

[0166] The fifth function sends the DNN and / or S-NSSAI to the second function.

[0167] Optionally, the second function may be at least one of the following: SMF, AMF, TMF, RAN.

[0168] In one embodiment of the present application, the fifth function generates or determines or locally determines the DNN and / or S-NSSAI, including:

[0169] The fifth function generates or determines or / locally determines the DNN and / or S-NSSAI based on the ninth information;

[0170] Among them, the ninth information may include at least one of the following: all or part of the identification of all or part of at least one first terminal, group identification, passive Internet of Things indication information, session identification or connection identification, all or part of the device type of at least one first terminal, and all or part of the location information of at least one first terminal.

[0171] In one embodiment of the present application, the fifth function generates or determines or locally determines the DNN and / or S-NSSAI, including:

[0172] The fifth function generates or determines or locally determines the DNN and / or S-NSSAI based on the tenth information;

[0173] Among them, the tenth information may include at least one of the following: all or part of the identification of all or part of at least one first terminal, group identification, passive Internet of Things indication information, session identification or connection identification, all or part of the device type of at least one first terminal, and all or part of the location information of at least one first terminal.

[0174] In one embodiment of the present application, the terminal identifier may include at least one of the following: electronic product code, part of the electronic product code, universal administrator number, item category, PLMN identifier, group identifier, SUPI, SUCI, GPSI, GUTI, TMSI, PEI.

[0175] In one embodiment of the present application, the device type is at least one of the following: Class A passive Internet of Things device, Class B passive Internet of Things device, Class C passive Internet of Things device.

[0176] In one embodiment of the present application, the first terminal may include a passive Internet of Things device and / or a tag.

[0177] In the present application, it is possible to manage a first terminal (e.g., an Ambient IoT device) through a mobile network, and / or manage a session or connection of the first terminal, and / or associate data of at least one first terminal through a session or connection, thereby achieving cost savings and facilitating management.

[0178] See also Figure 13 An embodiment of the present application provides a communication method, the execution subject may be the sixth function, for example, the sixth function may include at least one of the following: SMF, UDM, UDR, PCF, TMF, AMF, and the specific steps include: step 1301.

[0179] Step 1301: The sixth function receives eleventh information from the seventh function, and the eleventh information includes at least one of the following: all or part of the terminal identifier of the first terminal, the group identifier, the session identifier or the connection identifier, the passive Internet of Things indication information, the device type of the first terminal, and the location information of the first terminal.

[0180] Optionally, the eleventh information is used to establish or modify a session or connection, and / or the eleventh information is used to establish or modify a session or connection management context, and / or the eleventh information is a session or connection establishment request, or a session or connection modification request, and / or the eleventh information is a session or connection management context establishment request or a session or connection management context modification request.

[0181] Optionally, the seventh function may include at least one of the following: AMF, TMF, RAN.

[0182] In one embodiment of the present application, the method may further include:

[0183] The sixth function associates the eleventh information and / or the first terminal with a first session or a first connection, where the first session is an existing session and the first connection is a non-existing connection.

[0184] In one embodiment of the present application, the sixth function of associating the eleventh information and / or the first terminal with the first session includes:

[0185] The sixth function associates the first request and / or the first terminal with the first session according to the twelfth information;

[0186] The twelfth information may include at least one of the following: all or part of the terminal identifier of the first terminal, the group identifier, the device type of the first terminal, the passive Internet of Things indication information, the location information of the first terminal, the establishment time of the first session or the first connection, the time when the sixth function receives the eleventh information, the subscription information, and the RAN identifier.

[0187] In one embodiment of the present application, the method may further include:

[0188] The sixth function sends at least one of the following to the eighth function: address information of the first terminal (eg, IP address), address information of the ninth function (eg, IP address), access network tunnel information, and first indication information.

[0189] Optionally, the access network may be an access network serving the first terminal.

[0190] Optionally, the first indication information instructs the ninth function to associate the message of the first terminal and the first session or first connection with the same tunnel information, and / or instructs the eighth function to update the packet detection rule (Packet Detection Rule, PDR) to associate the data related to the first terminal with an existing tunnel or a previous tunnel or a tunnel associated with an existing session.

[0191] Optionally, the eighth function is a UPF. Further, the eighth network function may include a UPF serving the first session or the first connection.

[0192] Optionally, the ninth function includes at least one of the following: RAN, terminal.

[0193] In one embodiment of the present application, the method may further include:

[0194] The sixth function sends an identifier of a first session or a first connection to the seventh function and / or the ninth function, where the first session is an existing session and the first connection is an existing connection.

[0195] In one embodiment of the present application, the terminal identifier may include at least one of the following: electronic product code, part of the electronic product code, universal administrator number, item category, PLMN identifier, group identifier, SUPI, SUCI, GPSI, GUTI, TMSI, PEI.

[0196] In one embodiment of the present application, the device type may be at least one of the following: Class A passive Internet of Things device, Class B passive Internet of Things device, Class C passive Internet of Things device.

[0197] In one embodiment of the present application, the first terminal may include a passive Internet of Things device and / or a tag.

[0198] In the present application, it is possible to manage a first terminal (e.g., an Ambient IoT device) through a mobile network, and / or manage a session or connection of the first terminal, and / or associate data of at least one first terminal through a session or connection, thereby achieving cost savings and facilitating management.

[0199] See also Figure 14 An embodiment of the present application provides a communication method, the execution subject may be the ninth function, for example, the ninth function includes at least one of the following: RAN, terminal, and the specific steps include: step 1401.

[0200] Step 1401: A ninth function associates data related to a first terminal with a first session, a first tunnel, or a first connection;

[0201] The first session is an existing session, and / or the first tunnel is an existing tunnel or a previous tunnel or a tunnel associated with an existing session, and / or the first connection is an existing connection.

[0202] In one embodiment of the present application, the first terminal includes at least one passive Internet of Things device and / or tag.

[0203] In the present application, it is possible to manage a first terminal (e.g., an Ambient IoT device) through a mobile network, and / or manage a session or connection of the first terminal, and / or associate data of at least one first terminal through a session or connection, thereby achieving cost savings and facilitating management.

[0204] The following describes the implementation of the present application in conjunction with Example 1 and Example 2.

[0205] Example 1:

[0206] This embodiment is for the case where the network side triggers the session establishment and the UE does not support the Non-Access Stratum (NAS). By establishing a shared session for multiple UEs, resources are saved. The process is as follows Figure 15 The specific steps are as follows:

[0207] Step 1501 (optional step): AF sends a message to AMF to indicate triggering session establishment.

[0208] Optionally, the indication triggers session establishment, which may be implemented by at least one of the following methods:

[0209] (1) The AF sends an indication message, which triggers the establishment of a session.

[0210] (2) The message itself indicates that the session establishment is triggered, such as calling a message or service that indicates session establishment;

[0211] (3) The internal logic of the message receiving end determines that a session establishment needs to be triggered.

[0212] Optionally, the message sent by the AF may include a range, that is, only triggering the RAN within the range to send an incentive, or triggering the establishment / modification of a session related to a UE within a certain range. The range may be, for example, a location range.

[0213] Optionally, the message may include at least one UE identifier to indicate the UEs associated with this session establishment. That is, it indicates which UEs' session establishment is to be triggered. In this embodiment, the UE includes at least one passive IoT device and / or tag.

[0214] As a possible scenario, such as a regional deployment scenario, it may be possible to trigger only the UE of the enterprise to establish a session. For example, when a supermarket of a certain company takes inventory of goods, only the UE related to the certain company needs to transmit data. The reason for this is that in some deployment scenarios, the base station may broadcast incentives to the UE. If there are tags within the broadcast range that do not require the establishment of a session (or do not allow the establishment of a session), these UEs may also be stimulated and triggered to establish a session. If the AMF learns about the UE that needs to trigger the establishment of a session this time, it can reject the session establishment of other UEs to save signaling and resources.

[0215] Optionally, the UE identifier (that is, the identifier of the first terminal) is one or more of the following:

[0216] (1) All or part of the fields of the Electronic Product Code (EPC);

[0217] (2) General manager number, a field in the EPC;

[0218] (3) Object class, another field of EPC;

[0219] (4) Group ID;

[0220] (5) General administrator number;

[0221] (6)SUPI;

[0222] (7)SUCI;

[0223] (8)GPSI;

[0224] (9) GUTI;

[0225] (10)TMSI;

[0226] (11)PEI;

[0227] (12) Information about any Ambient IoT device;

[0228] The information of any Ambient IoT device can be implemented in the form of any Ambient IoT indication information or other forms, which is not limited in this application.

[0229] (13)PLMN identification;

[0230] (14) Group identification.

[0231] It should be noted that, if UE identities of multiple UEs are to be sent, the UE identity may be a collection or list of multiple UE identities, or a group ID, or a part of a field of a UE identity.

[0232] In one possible implementation, if a portion of the UE ID field is sent, it means all UE IDs matching that field. For example, if the enterprise ID is 0x000001F, it is equivalent to sending all UEs that meet the 28-bit value of the enterprise ID of 0x000001F. For example, in the above example, the AF can carry the enterprise ID of the supermarket of XXXX Company.

[0233] It should be noted that this application does not limit the path for the AF to send the above message to the AMF, such as whether it is forwarded via the NEF, whether it is forwarded via the UDM, whether it is forwarded via the SMF, and if it is forwarded via the SMF, whether the SMF saves the message; nor does it limit whether there are any changes in the encapsulation during the forwarding process. It only focuses on the messages sent from the AF to the AMF. If the message is forwarded, the aforementioned instructions may trigger the establishment of a session in different ways during the forwarding process. For example, the AF sends the message to the AMF via the NEF. The AF carries the instruction information to trigger the UE to establish a session according to the aforementioned method 1 to the NEF, but when the NEF forwards it to the AMF, it instructs the UE to establish a session by calling a specific service in method 2.

[0234] See also Figure 17 The figure shows the fields of GID-96 (a commonly used EPC). It contains an 8-bit EPC header, a 28-bit enterprise number, a 24-bit item category, and a 36-bit serial number:

[0235] Step 1502 (optional step): The AMF sends a message to the RAN to instruct the UE (i.e., the first terminal) to establish a session.

[0236] It should be noted that even if the message sent by the AF in step 1501 carries the UE identifier, the message sent by the AMF to the RAN may not carry the UE identifier.

[0237] Optionally, the AMF may instruct the RAN to send incentives only to UEs within a certain range, or trigger the establishment or modification of sessions related to UEs within a certain range. The range may be a location range.

[0238] Step 1503: The RAN determines to send an incentive to the UE to trigger session establishment or modification.

[0239] Optionally, the RAN may locally determine whether to trigger session establishment or modification, or determine whether to trigger session establishment or modification based on the message of step 1502 received from the AMF.

[0240] Step 1504: The RAN sends an incentive to the UE.

[0241] Step 1505: One or more UEs are stimulated to send UE identities to the RAN node.

[0242] It should be noted that the meaning of the UE identifier in step 1505 can be found in the relevant description of the UE identifier in step 1501.

[0243] Optionally, when the UE does not support NAS, the UE directly sends the UE identity to the RAN through the air interface protocol.

[0244] In this embodiment, multiple UEs may send UE identities to the RAN respectively.

[0245] It should be noted that the role of the group ID is to facilitate AMF and / or SMF to query the contract information and is optional information.

[0246] It should be noted that, in addition to Figure 15 In addition to the solution shown in , that is, RAN carries multiple UE identities to the core network NF (for example, AMF, SMF, etc.), there is another possible solution: RAN maintains a virtual UE, and waits for RAN to receive one or more UE identities ( Figure 15 After step 1505), the RAN sends the virtual UE identifier to the AMF or SMF. The RAN maintains the relationship between the virtual UE identifier and the one or more UE identifiers. However, the network side only sees the virtual UE identifier. That is, from the perspective of the core network, there is no difference from a normal session establishment (because only the UE identifier is perceived as network registration or request to establish or modify a session or connection).

[0247] Step 1506: The RAN generates a session ID.

[0248] In this embodiment, the RAN may generate (one) session ID for one or more UEs.

[0249] This application does not limit the implementation method of the RAN generating the session ID. One possible implementation method is: the RAN configures a time threshold (e.g., 1 second) so that after the first receipt of the message in step 1505, all messages in step 1505 (from other UEs) received within this time threshold (e.g., 1 second) can generate the same session ID. Because the time difference between the responses to a stimulus and the time it takes to receive them will not exceed the time it takes the UE to process the stimulus + the response UE identifier (if the stimulus and the corresponding transmission time are ignored), if the time threshold is set to be no less than a reasonable upper limit for the UE to process the stimulus + the response UE identifier, then the response to a single stimulus will definitely be sent to the RAN within this time threshold.

[0250] As a possible implementation, the RAN generates the DNN and / or S-NSSAI based on all or part of the subscription information.

[0251] Step 1507: The RAN sends at least one of the following to the AMF: all or part of the identifier of the at least one UE (i.e., the first terminal), all or part of the identifier of the virtual UE (i.e., the second terminal), the group identifier, the passive IoT indication information, the session identifier, the device type of the at least one UE, and the location information of the at least one UE.

[0252] That is, in the case of a virtual UE, the UE identifier sent by the RAN to the AMF is the identifier of the virtual UE, that is, the identifier of the second UE.

[0253] Step 1508 (optional step): If the AMF does not obtain the DNN and S-NSSAI from the RAN, the AMF determines the DNN and / or S-NSSAI.

[0254] It is understood that if the AMF does not receive the DNN from the RAN but receives the S-NSSAI, the AMF determines the DNN; if the AMF does not receive the S-NSSAI from the RAN but receives the DNN, the AMF determines the S-NSSAI; if the AMF receives neither the DNN nor the S-NSSAI from the RAN, the AMF determines both the DNN and the S-NSSAI.

[0255] Step 1509: AMF sends an SM context establishment request to SMF, including a session ID, which may include Ambient IoT indication information, and / or indication information of multiple UE sessions.

[0256] Step 1510: SMF obtains contract information from UDM or TMF;

[0257] Optionally, the contract information may include the following: 1) contract information of the UE, 2) contract information of the virtual UE, 3) contract information of the UE and contract information of the virtual UE.

[0258] Step 1511 (optional step): The SMF may determine whether to allow the one or more UEs to establish a session based on at least one of the following: UE identification, subscription information.

[0259] Regardless of which case in step 1510 occurs, the contract information may include information on whether to allow or not to allow the session to be established.

[0260] It is understandable that if the SMF receives multiple terminal identifiers (i.e., in the case of non-virtual UEs), all of these UEs may be allowed to establish a session, or none of them may be allowed to establish a session, or some may be allowed and some may not be allowed. If at least one of the UE identifiers received by the AMF in step 1507 does not allow session establishment, a session establishment response message or a rejection message is sent to the AMF or RAN. The session establishment response message or the rejection message includes a cause value: the current UE is not allowed to establish a session. Optionally, the session establishment response message or the rejection message may also include a set of UE identifiers that are not allowed to establish a session.

[0261] Step 1512: SMF sends an N4 session establishment request to UPF;

[0262] Optionally, the N4 session establishment request may include the RAN address. Further, optionally, the N4 session establishment request may also include Ambient IoT indication information and / or multi-UE session indication information. The UPF returns the CN tunnel information.

[0263] Optionally, before executing step 1511, the SMF may select the UPF based on the Ambient IoT indication information and / or the indication information of the multi-UE session.

[0264] Step 1513: SMF sends CN tunnel information to AMF.

[0265] Step 1514: AMF sends CN tunnel information to RAN.

[0266] Step 1515: RAN sends AN tunnel information to AMF.

[0267] Step 1516: AMF sends AN tunnel information to SMF.

[0268] Step 1517: The SMF sends the AN tunnel information to the UPF. Optionally, the RAN address is sent.

[0269] Example 2:

[0270] This embodiment is a case where the UE side triggers session establishment and the UE supports NAS. In this embodiment, since the UE side actively establishes the session, the method in Example 1 where the RAN determines which UEs can share the same session based on the time threshold may not be executed normally. Therefore, the method adopted in Example 2 is that a single UE requests to establish a session, and then the network side determines whether it can be associated with an existing session based on one or more of the UE identifier, Ambient IoT indication information, device type, location information, and session establishment time, that is, directly using an existing session. It should be noted that in addition to the cases in Examples 1 and 2, there may actually be a case where the UE has no active signaling or the network side triggers session establishment, but supports NAS, or the UE has active signaling but does not support NAS. These two cases are nothing more than a re-splicing of some steps in Examples 1 and 2, and will not be repeated here.

[0271] See also Figure 16 , the specific steps are as follows:

[0272] Step 1601: The UE sends a session establishment or modification request, including a UE identifier and a session ID.

[0273] Optionally, the session establishment request may include a UE identifier and / or a session ID.

[0274] It should be noted that the meaning of the UE identifier is described in the relevant description of Example 1.

[0275] Optionally, the session establishment request may further include: Ambient IoT indication information and / or device category.

[0276] The device category may include specific categories of Ambient IoT devices, such as Class A Ambient IoT devices, Class B Ambient IoT devices, and Class C Ambient IoT devices.

[0277] Optionally, the session establishment request may further include location information of the UE.

[0278] Optionally, the location information may include geographic location information (eg, latitude and longitude, province, city, district, street, location of a building, etc.), and / or topological location information (eg, cell identifier, TA identifier, DNAI, PLMN identifier, etc.).

[0279] In this embodiment, the UE supports NAS and can send the UE identity through NAS (i.e., the RAN is not aware of it). The AmbientIoT indication information and / or device category can be sent within and / or outside the NAS. As a possible scenario, the UE identity may also be included outside the NAS. The UE identity format inside and outside the NAS may be the same or different.

[0280] Step 1602: AMF sends an SM context establishment or modification request to SMF, including a session ID, which may include one or more of the following: Ambient IoT indication information, device type, and UE location information;

[0281] Step 1603: SMF obtains contract information from UDM or TMF.

[0282] It should be noted that, unlike step 1510 of embodiment 1, embodiment 2 does not require the implementation method of "virtual UE", so the contract information here is the contract information of the UE.

[0283] Step 1604: The SMF determines to associate the current UE with an existing session (recorded as session 0) based on one or more of the subscription information, UE identifier, device category, UE location, RAN identifier, and session establishment time.

[0284] For example, only sessions established within 60 seconds by a Class C passive IoT device in the same enterprise, same cell, and served by the same RAN as the current UE can be associated with the current session.

[0285] -The assumption is that UEs transmitting the same type of services usually have higher affinity in terms of UE identity, location, and session establishment time, or one or more of the UE identity, location, and session establishment time are more likely to be the same or close, making it more likely that the current session can be reused.

[0286] - Associate to session 0, including selecting the same UPF.

[0287] Step 1605: The SMF sends an N4 session establishment request (second message) to the UPF, which includes the UE IP address and the AN tunnel information for the session. It may also include an instruction to associate the messages of the UE IP address with the same tunnel. The UPF returns the CN tunnel information.

[0288] Step 1606: SMF sends to AMF, and AMF sends to RAN: UE IP and / or UE identity, CN tunnel information and / or session ID of the existing session (session 0).

[0289] Step 1607: The RAN sends a session establishment accept message to the UE.

[0290] See also Figure 18 An embodiment of the present application provides a communication device, which is applied to a first function. For example, the first function includes but is not limited to at least one of the following: a RAN, a terminal, and the device 1800 includes:

[0291] A first sending module 1801 is configured to send first information to a second function;

[0292] Among them, the first information includes at least one of the following: all or part of the identification of all or part of at least one first terminal, group identification, passive Internet of Things indication information, session identification or connection identification, all or part of the device type of at least one first terminal, all or part of the location information of at least one first terminal, DNN, S-NSSAI.

[0293] Optionally, the first information is used to establish or modify a session or connection.

[0294] Optionally, the second function includes at least one of the following: SMF, AMF, TMF, RAN.

[0295] In one embodiment of the present application, the device further includes:

[0296] The first receiving module is used to receive second information from the at least one first terminal, where the second information includes at least one of the following: all or part of the terminal identifier, the group identifier, the passive Internet of Things indication information, the session identifier or the connection identifier, the device type of the first terminal, and the location information of the first terminal.

[0297] Optionally, the terminal identifier includes at least one of the following: electronic product code, part of the electronic product code, universal manager number, item category, PLMN identifier, group identifier, SUPI, SUCI, GPSI, GUTI, TMSI, PEI.

[0298] Optionally, the device type is at least one of the following: Class A passive Internet of Things device, Class B passive Internet of Things device, and Class C passive Internet of Things device.

[0299] Optionally, the first terminal includes a passive Internet of Things device and / or a tag.

[0300] In an embodiment of the present application, the second information is received by the first function within a period of time, and / or the second information is received by the first terminal from a terminal of a specific type.

[0301] In one embodiment of the present application, the device further includes:

[0302] The first processing module is used to determine and / or generate third information, where the third information includes at least one of the following: the session identifier or connection identifier, DNN, and S-NSSAI.

[0303] In one embodiment of the present application, the device further includes:

[0304] The second sending module is configured to send fourth information to the at least one first terminal, where the fourth information is used to trigger establishment or modification of a session or connection of the at least one first terminal.

[0305] In one embodiment of the present application, the device further includes:

[0306] a second processing module, configured to determine, based on the fifth information, triggering establishment or modification of a session or connection of the at least one first terminal;

[0307] The fifth information is used to instruct the first function to send the fourth information to the at least one first terminal, and / or the fifth information is used to trigger the at least one first terminal to initiate establishment or modification of a session or connection.

[0308] In one embodiment of the present application, the device further includes:

[0309] The second receiving module is configured to receive the first information from a third function.

[0310] Optionally, the third function includes at least one of the following: AF, NEF, PCF, UDR, and UDM.

[0311] In one embodiment of the present application, the device further includes:

[0312] The third processing module is configured to determine a destination address for forwarding the downlink message according to the terminal identifier and / or the group identifier and / or the location information of the at least one first terminal.

[0313] In one embodiment of the present application, the device further includes:

[0314] A third sending module, configured to send sixth information to the second function via NGAP;

[0315] Among them, the sixth information includes at least one of the following: all or part of the identifier of the at least one first terminal, all or part of the identifier of the second terminal related to the RAN, the group identifier, the passive Internet of Things indication information, the session identifier or the connection identifier, the device type of the at least one first terminal, and the location information of the at least one first terminal.

[0316] The device provided in the embodiment of the present application can achieve Figure 9 The various processes implemented in the method embodiment shown achieve the same technical effect, and to avoid repetition, they will not be described again here.

[0317] See also Figure 19 The embodiment of the present application provides a communication device for a second function, where the second function may include at least one of the following: SMF, AMF, TMF, and RAN. The device 1900 includes:

[0318] The third receiving module 1901 is configured to obtain seventh information from the fourth function, where the seventh information includes at least one of the following: contract information of the first terminal, contract information related to the RAN, and contract information of the second terminal related to the RAN.

[0319] Optionally, the fourth function includes at least one of the following: UDM, UDR, TMF, PCF, NEF, SMF.

[0320] In one embodiment of the present application, the contract information includes at least one of the following: all or part of the terminal identification, group identification, passive Internet of Things indication information, device type, PLMN identification, mobility management related information, session or connection management related information, transmission related information, positioning or ranging related information, positioning format, positioning or ranging accuracy, billing method, validity period of the terminal identification, valid number of terminal identification, validity period of contract information, valid number of contract information, air interface resource related information, deregistration or deaccession related information, and network openness related information.

[0321] In an embodiment of the present application, the mobility management related information includes one or more of the following: allowing or not allowing mobility management, supporting or not supporting mobility management, and requiring or not requiring mobility management.

[0322] In one embodiment of the present application, the session or connection management related information includes one or more of the following: allowing or not allowing establishment of a session or connection, supporting or not supporting establishment of a session or connection, and requiring or not requiring establishment of a session or connection.

[0323] In one embodiment of the present application, the transmission-related information includes one or more 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.

[0324] In one embodiment of the present application, the positioning or ranging related information includes one or more 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.

[0325] In one embodiment of the present application, the air interface resource related information includes one or more 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, and the need or non-necessity to release air interface resources after registration.

[0326] In one embodiment of the present application, the deregistration related information includes one or more of the following: deregistering or not deregistering, deregistering after registration or not deregistering, retaining or not retaining the registration status after registration, refusing registration or not refusing registration / accepting registration.

[0327] In one embodiment of the present application, the de-access related information includes one or more 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, rejecting access or not rejecting access / accepting access.

[0328] In one embodiment of the present application, the device further comprises:

[0329] a fourth receiving module, configured to receive first information from the first function;

[0330] The first information includes at least one of the following: all or part of the identification of all or part of at least one first terminal, a group identification, passive Internet of Things indication information, a session identification or a connection identification, all or part of the device type of the at least one first terminal, all or part of the location information of the at least one first terminal, DNN, S-NSSAI.

[0331] Optionally, the first information is used to establish or modify a session or connection.

[0332] Optionally, the first function includes but is not limited to at least one of the following: RAN, terminal.

[0333] In one embodiment of the present application, the terminal identifier includes at least one of the following: an electronic product code, a part of the electronic product code, a universal administrator number, an item category, a PLMN identifier, a group identifier, SUPI, SUCI, GPSI, GUTI, TMSI, or PEI.

[0334] In one embodiment of the present application, the device type is at least one of the following: Class A passive Internet of Things device, Class B passive Internet of Things device, Class C passive Internet of Things device.

[0335] In one embodiment of the present application, the first terminal includes a passive Internet of Things device and / or a tag.

[0336] The device provided in the embodiment of the present application can achieve Figure 10 The various processes implemented in the method embodiment shown achieve the same technical effect, and to avoid repetition, they will not be described again here.

[0337] See also Figure 20 The embodiment of the present application provides a communication device for a fourth function. For example, the fourth function may include at least one of the following: UDM, UDR, TMF, PCF, NEF, SMF. The device 2000 includes:

[0338] The storage module 2001 is configured to store seventh information, where the seventh information includes at least one of the following: contract information of the first terminal, contract information related to the RAN, and contract information of the second terminal related to the RAN.

[0339] In one embodiment of the present application, the device further comprises:

[0340] a fourth processing module, configured to authenticate a request to establish or modify a session or connection based on the eighth information;

[0341] Among them, the eighth information includes at least one of the following: all or part of the contract information of the first terminal, all or part of the contract information related to the RAN, and all or part of the contract information of the second terminal related to the RAN.

[0342] In one embodiment of the present application, the contract information includes at least one of the following: all or part of the terminal identification, group identification, passive Internet of Things indication information, device type, PLMN ID, mobility management related information, session or connection management related information, transmission related information, positioning or ranging related information, positioning format, positioning or ranging accuracy, billing method, validity period of the terminal identification, valid number of terminal identification, validity period of contract information, valid number of contract information, air interface resource related information, deregistration or deaccession related information, and network openness related information.

[0343] In an embodiment of the present application, the mobility management related information includes one or more of the following: allowing or not allowing mobility management, supporting or not supporting mobility management, and requiring or not requiring mobility management.

[0344] In one embodiment of the present application, the session or connection management related information includes one or more of the following: allowing or not allowing establishment of a session or connection, supporting or not supporting establishment of a session or connection, and requiring or not requiring establishment of a session or connection.

[0345] In one embodiment of the present application, the transmission-related information includes one or more 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.

[0346] In one embodiment of the present application, the positioning or ranging related information includes one or more 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.

[0347] In one embodiment of the present application, the air interface resource related information includes one or more 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, and the need or non-necessity to release air interface resources after registration.

[0348] In one embodiment of the present application, the deregistration related information includes one or more of the following: deregistering or not deregistering, deregistering after registration or not deregistering, retaining or not retaining the registration status after registration, refusing registration or not refusing registration / accepting registration.

[0349] In one embodiment of the present application, the de-access related information includes one or more 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, rejecting access or not rejecting access / accepting access.

[0350] In one embodiment of the present application, the terminal identifier includes at least one of the following: an electronic product code, a part of the electronic product code, a universal administrator number, an item category, a PLMN identifier, a group identifier, SUPI, SUCI, GPSI, GUTI, TMSI, or PEI.

[0351] In one embodiment of the present application, the device type includes at least one of the following: Class A passive Internet of Things device, Class B passive Internet of Things device, and Class C passive Internet of Things device.

[0352] In one embodiment of the present application, the first terminal includes a passive Internet of Things device and / or a tag.

[0353] The device provided in the embodiment of the present application can achieve Figure 11 The various processes implemented in the method embodiment shown achieve the same technical effect, and to avoid repetition, they will not be described again here.

[0354] See also Figure 21 The embodiment of the present application provides a communication device for a fifth function. For example, the fifth function may include at least one of the following: AMF, TMF, RAN, SMF. The device 2100 includes:

[0355] The fifth processing module 2101 is used to generate or determine or locally determine DNN and / or S-NSSAI.

[0356] Optionally, the DNN and / or S-NSSAI is used to establish or modify a session or connection of the first terminal.

[0357] Optionally, the fifth function generates or determines or locally determines a DNN and / or S-NSSAI for establishing or modifying a session or connection of the first terminal.

[0358] In one embodiment of the present application, the device further comprises:

[0359] The fourth sending module is used to send the DNN and / or S-NSSAI to the second function, where the DNN and / or S-NSSAI is used to establish or modify a session or connection.

[0360] Optionally, the second function is at least one of the following: SMF, AMF, TMF, RAN.

[0361] In one embodiment of the present application, the fifth processing module 2101 is further configured to:

[0362] Generate or determine or / and locally determine the DNN and / or S-NSSAI according to the ninth information;

[0363] Among them, the ninth information includes at least one of the following: all or part of the identification of all or part of at least one first terminal, group identification, passive Internet of Things indication information, session identification or connection identification, all or part of the device type of at least one first terminal, and all or part of the location information of at least one first terminal.

[0364] In one embodiment of the present application, the fifth processing module 2101 is further configured to:

[0365] generating or determining or locally determining the DNN and / or S-NSSAI based on the tenth information;

[0366] Among them, the tenth information includes at least one of the following: all or part of the identification of all or part of at least one first terminal, group identification, passive Internet of Things indication information, session identification or connection identification, all or part of the device type of at least one first terminal, and all or part of the location information of at least one first terminal.

[0367] In one embodiment of the present application, the terminal identifier may include at least one of the following: electronic product code, part of the electronic product code, universal administrator number, item category, PLMN identifier, group identifier, SUPI, SUCI, GPSI, GUTI, TMSI, PEI.

[0368] In one embodiment of the present application, the device type is at least one of the following: Class A passive Internet of Things device, Class B passive Internet of Things device, Class C passive Internet of Things device.

[0369] In one embodiment of the present application, the first terminal includes a passive Internet of Things device and / or a tag.

[0370] The device provided in the embodiment of the present application can achieve Figure 12 The various processes implemented in the method embodiment shown achieve the same technical effect, and to avoid repetition, they will not be described again here.

[0371] See also Figure 22 The embodiment of the present application provides a communication device for a sixth function, for example, the sixth function is at least one of the following: SMF, UDM, UDR, PCF, TMF, AMF, and the device 2200 includes:

[0372] The fifth receiving module 2201 is used to receive the eleventh information from the seventh function, and the eleventh information includes at least one of the following: all or part of the terminal identifier of the first terminal, the group identifier, the session identifier or the connection identifier, the passive Internet of Things indication information, the device type of the first terminal, and the location information of the first terminal.

[0373] Optionally, the eleventh information is used for establishing or modifying a session or connection, and / or, the eleventh information is used for establishing or modifying a session or connection management context, and / or, the eleventh information is a session or connection establishment request / session or connection modification request, and / or, the eleventh information is a session or connection management context establishment request / session or connection management context modification request.

[0374] Optionally, the seventh function includes at least one of the following: AMF, TMF, RAN.

[0375] In one embodiment of the present application, the device further includes:

[0376] The sixth processing module is configured to associate the eleventh information and / or the first terminal with a first session or a first connection, where the first session is an existing session and the first connection is an existing connection.

[0377] In one embodiment of the present application, the sixth processing module is further configured to:

[0378] associating the eleventh information and / or the first terminal with the first session or first connection according to the twelfth information;

[0379] The twelfth information includes at least one of the following: all or part of the terminal identifier of the first terminal, the group identifier, the device type of the first terminal, the passive Internet of Things indication information, the location information of the first terminal, the establishment time of the first session or the first connection, the time when the sixth function receives the eleventh information, the subscription information, and the RAN identifier.

[0380] In one embodiment of the present application, the device further includes:

[0381] a fifth sending module, configured to send at least one of the following to the eighth function: address information of the first terminal, address information of the ninth function, access network tunnel information, and first indication information;

[0382] Optionally, the access network is an access network serving the first terminal.

[0383] Optionally, the first indication information instructs the ninth function to associate the message of the first terminal and the first session or first connection to the same tunnel information, and / or instructs the eighth function to update the packet detection rule (Packet Detection Rule, PDR) to associate the data related to the first terminal to an existing tunnel or a previous tunnel or a tunnel associated with an existing session or connection.

[0384] Optionally, the eighth function is a user plane function (UPF). The eighth network function includes the UPF serving the first session.

[0385] Optionally, the ninth function includes at least one of the following: RAN, terminal.

[0386] In one embodiment of the present application, the device further includes:

[0387] The sixth sending module is configured to send an identifier of a first session or a first connection to the seventh function and / or the ninth function, where the first session is an existing session and the first connection is an existing connection.

[0388] In one embodiment of the present application, the terminal identifier includes at least one of the following: an electronic product code, a part of the electronic product code, a universal administrator number, an item category, a PLMN identifier, a group identifier, SUPI, SUCI, GPSI, GUTI, TMSI, or PEI.

[0389] In one embodiment of the present application, the device type is at least one of the following: Class A passive Internet of Things device, Class B passive Internet of Things device, Class C passive Internet of Things device.

[0390] In one embodiment of the present application, the first terminal includes a passive Internet of Things device and / or a tag.

[0391] The device provided in the embodiment of the present application can achieve Figure 13 The various processes implemented in the method embodiment shown achieve the same technical effect, and to avoid repetition, they will not be described again here.

[0392] See also Figure 23 The embodiment of the present application provides a communication device, which is applied to the ninth function. For example, the ninth function includes at least one of the following: RAN, terminal, and the device 2300 includes:

[0393] A seventh processing module 2301 is configured to associate data related to the first terminal with the first session, the first tunnel, or the first connection;

[0394] The first session is an existing session, and / or the first connection is an existing connection, and / or the first tunnel is an existing tunnel or a previous tunnel or a tunnel associated with an existing session or connection.

[0395] In one embodiment of the present application, the first terminal includes at least one passive Internet of Things device and / or tag.

[0396] The device provided in the embodiment of the present application can achieve Figure 14The various processes implemented in the method embodiment shown achieve the same technical effect, and to avoid repetition, they will not be described again here.

[0397] like Figure 24 As shown, the embodiment of the present application further provides a network function 2400, including a processor 2401, a memory 2402, a program or instruction stored in the memory 2402 and executable on the processor 2401, and the program or instruction is executed by the processor 2401 to implement the above Figure 9 or Figure 10 or Figure 11 or Figure 12 or Figure 13 or Figure 14 The various processes of the method embodiment can achieve the same technical effect. To avoid repetition, they will not be described here.

[0398] The embodiment of the present application also provides a readable storage medium on which a program or instruction is stored, and when the program or instruction is executed by the processor, the above Figure 9 or Figure 10 or Figure 11 or Figure 12 or Figure 13 or Figure 14 The various processes of the method embodiment shown can achieve the same technical effect, and to avoid repetition, they will not be described again here.

[0399] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), random access memory (RAM), a magnetic disk, or an optical disk.

[0400] The steps of the method or algorithm described in conjunction with the contents disclosed in this application can be implemented in hardware or by executing software instructions on a processor. The software instructions can be composed of corresponding software modules, and the software modules can be stored in RAM, flash memory, ROM, EPROM, EEPROM, registers, hard disk, mobile hard disk, read-only optical disk or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and the storage medium can be carried in an ASIC. In addition, the ASIC can be carried in a core network interface device. Of course, the processor and the storage medium can also exist in the core network interface device as discrete components.

[0401] Those skilled in the art will appreciate that, in one or more of the examples above, the functions described herein may be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions may be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any medium that facilitates the transmission of a computer program from one place to another. The storage medium may be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0402] The specific implementation methods described above further illustrate the purpose, technical solutions and beneficial effects of this application. It should be understood that the above description is only the specific implementation methods of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent replacements, improvements, etc. made on the basis of the technical solutions of this application should be included in the scope of protection of this application.

[0403] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the embodiments of the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the embodiments of the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0404] The embodiments of the present application are described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the steps in the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0405] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1The function specified in one or more boxes.

[0406] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0407] Obviously, those skilled in the art may make various changes and modifications to the embodiments of the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the embodiments of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations.

Claims

1. A communication method, characterized in that: Applied to the first function, the method comprises: The first function sends the first information to the second function; Among them, the first information includes at least one of the following: all or part of the identification of all or part of at least one first terminal, group identification, passive Internet of Things indication information, session identification or connection identification, all or part of the device type of at least one first terminal, all or part of the location information of at least one first terminal, data network name DNN, and single network slice selection auxiliary information S-NSSAI.

2. The method according to claim 1, characterized in that The first information is used to establish or modify a session or connection.

3. The method according to claim 1, characterized in that The method further comprises: The first function receives second information from the at least one first terminal, and the second information includes at least one of the following: all or part of the terminal identifier, the group identifier, the passive Internet of Things indication information, the session identifier or connection identifier, the device type of the first terminal, and the location information of the first terminal.

4. The method according to claim 3, characterized in that The second information is received by the first function within a period of time, and / or the second information is received by the first terminal from a terminal of a specific type.

5. The method according to claim 1, wherein The method further comprises, The first function determines and / or generates third information, and the third information includes at least one of the following: the session identifier or connection identifier, DNN, and S-NSSAI.

6. The method according to claim 1 or 3, characterized in that The method further comprises, The first function sends fourth information to the at least one first terminal, where the fourth information is used to trigger establishment or modification of a session or connection of the at least one first terminal.

7. The method according to claim 6, characterized in that The method further comprises, The first function determines, according to the fifth information, triggering establishment or modification of a session or connection of the at least one first terminal; The fifth information is used to instruct the first function to send the fourth information to the at least one first terminal, and / or the fifth information is used to trigger the at least one first terminal to initiate establishment or modification of a session or connection.

8. The method according to claim 7, characterized in that The method further comprises, The first function receives the first information from a third function.

9. The method according to claim 1, characterized in that The method further comprises, The first function sends sixth information to the second function via the next generation application protocol NGAP; Among them, the sixth information includes at least one of the following: all or part of the identifier of the at least one first terminal, all or part of the identifier of the second terminal related to the RAN, the group identifier, the passive Internet of Things indication information, the session identifier or the connection identifier, the device type of the at least one first terminal, and the location information of the at least one first terminal.

10. The method according to any one of claims 1 to 9, characterized in that The terminal identifier includes at least one of the following: an electronic product code, a part of the electronic product code, a general administrator number, an item category, a public land mobile network PLMN identifier, a group identifier, a user permanent identifier SUPI, a user hidden identifier SUCI, a general public user identifier GPSI, a global unique temporary UE identifier GUTI, a temporary mobile user identifier TMSI, a permanent equipment identifier PEI; and / or, The device type is at least one of the following: Class A passive IoT device, Class B passive IoT device, or Class C passive IoT device.

11. The method according to any one of claims 1 to 9, characterized in that The first terminal includes a passive Internet of Things device and / or a tag.

12. The method according to any one of claims 1 to 9, characterized in that The second function includes at least one of the following: a session management function SMF, an access and mobility management function AMF, a tag management function TMF, and a radio access network RAN; and / or, and / or, The first function includes at least one of the following: RAN, terminal.

13. The method according to claim 8, characterized in that The third function includes at least one of the following: an application function AF, a network exposure function NEF, a policy control function PCF, a unified data repository UDR, and a unified data management function UDM.

14. A communication method, characterized in that: Applied to the second function, the method includes: The second function obtains seventh information from the fourth function, where the seventh information includes at least one of the following: contract information of the first terminal, contract information related to the RAN, and contract information of the second terminal related to the RAN.

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

16. The method according to claim 15, characterized in that The mobility management related information includes one or more 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 or connection management related information includes one or more of the following: allowing or not allowing the establishment of a session or connection, supporting or not supporting the establishment of a session or connection, requiring or not requiring the establishment of a session or connection; and / or, The transmission related information includes one or more 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 one or more 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 air interface resource related information includes one or more 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 deregistration related information includes one or more 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 / accept registration; and / or, The de-access related information includes one or more 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.

17. The method according to claim 14, characterized in that The method further comprises: The second function receives first information from the first function; The first information includes at least one of the following: all or part of the identification of all or part of at least one first terminal, a group identification, passive Internet of Things indication information, a session identification or a connection identification, all or part of the device type of the at least one first terminal, all or part of the location information of the at least one first terminal, DNN, S-NSSAI.

18. The method according to claim 17, characterized in that The first information is used to establish or modify a session or connection.

19. The method according to any one of claims 15 to 18, characterized in that The terminal identification includes at least one of the following: electronic product code, part of the electronic product code, universal administrator number, item category, PLMN identifier, group identifier, SUPI, SUCI, GPSI, GUTI, TMSI, PEI; and / or, The device type is at least one of the following: Class A passive IoT device, Class B passive IoT device, or Class C passive IoT device.

20. The method according to any one of claims 14 to 19, characterized in that The first terminal includes a passive Internet of Things device and / or a tag.

21. The method according to any one of claims 14 to 19, characterized in that The second function includes at least one of the following: SMF, AMF, TMF, RAN; and / or, The fourth function is at least one of the following: UDM, UDR, TMF, PCF, NEF, SMF.

22. A communication method, applied to the fourth function, characterized in that: The method comprises: The fourth function stores seventh information, where the seventh information includes at least one of the following: contract information of the first terminal, contract information related to the RAN, and contract information of the second terminal related to the RAN.

23. The method according to claim 22, characterized in that The method further comprises: The fourth function authenticates the request to establish or modify the session or connection based on the eighth information; The eighth information includes at least one of the following: all or part of the contract information of the first terminal, all or part of the contract information related to the RAN, and all or part of the contract information of the second terminal related to the RAN.

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

25. The method according to claim 24, characterized in that The mobility management related information includes one or more 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 or connection management related information includes one or more of the following: allowing or not allowing the establishment of a session or connection, supporting or not supporting the establishment of a session or connection, requiring or not requiring the establishment of a session or connection; and / or, The transmission related information includes one or more 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 one or more 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 air interface resource related information includes one or more 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 deregistration related information includes one or more 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 / accept registration; and / or, The de-access related information includes one or more 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.

26. The method according to any one of claims 24 to 25, characterized in that The terminal identification includes at least one of the following: electronic product code, part of the electronic product code, universal administrator number, item category, PLMN identifier, group identifier, SUPI, SUCI, GPSI, GUTI, TMSI, PEI; and / or, The device type includes at least one of the following: Class A passive Internet of Things device, Class B passive Internet of Things device, and Class C passive Internet of Things device.

27. The method according to any one of claims 22 to 25, characterized in that The first terminal includes a passive Internet of Things device and / or a tag.

28. The method according to any one of claims 22 to 25, characterized in that The fourth function includes at least one of the following: UDM, UDR, TMF, PCF, NEF, SMF.

29. A communication method, applied to the fifth function, characterized in that: The method comprises: The fifth function generates or determines or locally determines DNN and / or S-NSSAI.

30. The method according to claim 29, wherein The DNN and / or S-NSSAI is used to establish or modify a session or connection of the first terminal; or, The fifth function generates or determines or locally determines the DNN and / or S-NSSAI for establishing or modifying a session or connection of the first terminal.

31. The method according to claim 29, wherein The method further comprises: The fifth function sends the DNN and / or S-NSSAI to the second function.

32. The method according to claim 29, wherein The fifth function generates or determines or locally determines the DNN and / or S-NSSAI, including: The fifth function generates or determines or locally determines the DNN and / or S-NSSAI based on the ninth information; The ninth information includes at least one of the following: all or part of the identification of all or part of at least one first terminal, a group identification, passive Internet of Things indication information, a session identification or a connection identification, all or part of the device type of at least one first terminal, and all or part of the location information of at least one first terminal.

33. The method according to claim 29, wherein The fifth function generates or determines or locally determines the DNN and / or S-NSSAI, including: The fifth function generates or determines or locally determines the DNN and / or S-NSSAI based on the tenth information; The tenth information includes at least one of the following: all or part of the identification of all or part of at least one first terminal, a group identification, passive Internet of Things indication information, a session identification or a connection identification, all or part of the device type of at least one first terminal, and all or part of the location information of at least one first terminal.

34. The method according to claim 32 or 33, characterized in that The terminal identification includes at least one of the following: electronic product code, part of the electronic product code, universal administrator number, item category, PLMN identifier, group identifier, SUPI, SUCI, GPSI, GUTI, TMSI, PEI; and / or, The device type is at least one of the following: Class A passive IoT device, Class B passive IoT device, or Class C passive IoT device.

35. The method according to any one of claims 30 to 34, characterized in that The first terminal includes a passive Internet of Things device and / or a tag.

36. The method according to claim 31, wherein The second function is at least one of the following: SMF, AMF, TMF, RAN.

37. The method according to any one of claims 29 to 36, characterized in that The fifth function includes at least one of the following: AMF, TMF, RAN, SMF.

38. A communication method, applied to the sixth function, characterized in that: The method comprises: The sixth function receives eleventh information from the seventh function, and the eleventh information includes at least one of the following: all or part of the terminal identifier, the group identifier, the session identifier or the connection identifier, the passive Internet of Things indication information, the device type of the first terminal, and the location information of the first terminal.

39. The method according to claim 38, characterized in that The eleventh information is used for session establishment or modification, and / or, the eleventh information is used for session or connection management context establishment or modification, and / or, the eleventh information is a session or connection establishment request or a session modification request, and / or, the eleventh information is a session or connection management context establishment request or a session or connection management context modification request.

40. The method according to claim 38, wherein The method further comprises, The sixth function associates the eleventh information and / or the first terminal with a first session or a first connection, where the first session is an existing session and the first connection is an existing connection.

41. The method according to claim 40, wherein Associating the eleventh information and / or the first terminal with a first session or a first connection, comprising: The sixth function associates the eleventh information and / or the first terminal with the first session or first connection according to the twelfth information; The twelfth information includes at least one of the following: all or part of the terminal identifier, the group identifier, the device type of the first terminal, the passive Internet of Things indication information, the location information of the first terminal, the establishment time of the first session or the first connection, the time when the sixth function receives the eleventh information, the subscription information, and the RAN identifier.

42. The method according to any one of claims 38 to 41, characterized in that The method further comprises, The sixth function sends at least one of the following to the eighth function: address information of the first terminal, address information of the ninth function, access network tunnel information, and first indication information.

43. The method according to claim 42, characterized in that The access network is an access network serving the first terminal; and / or, The first indication information instructs the ninth function to associate the message of the first terminal and the first session or first connection to the same tunnel information, and / or, the first indication information instructs the eighth function to update the data packet detection rule PDR to associate the data related to the first terminal to an existing tunnel or a previous tunnel or a tunnel associated with an existing session.

44. The method according to claim 38, wherein The method further comprises, An identifier of a first session or a first connection is sent to the seventh function and / or the ninth function, where the first session is an existing session and the first connection is an existing connection.

45. The method according to any one of claims 38 to 44, characterized in that The terminal identification includes at least one of the following: electronic product code, part of the electronic product code, universal administrator number, item category, PLMN identifier, group identifier, SUPI, SUCI, GPSI, GUTI, TMSI, PEI; and / or, The device type is at least one of the following: Class A passive IoT device, Class B passive IoT device, or Class C passive IoT device.

46. The method according to any one of claims 38 to 44, characterized in that The first terminal includes a passive Internet of Things device and / or a tag.

47. The method according to any one of claims 37 to 44, characterized in that The seventh function includes at least one of the following: AMF, TMF, RAN; and / or, The sixth function includes at least one of the following: SMF, UDM, UDR, PCF, TMF, AMF.

48. The method according to claim 42, wherein The eighth function is a user plane function UPF; and / or, The ninth function includes at least one of the following: RAN, terminal.

49. The method according to claim 48, characterized in that The eighth network function includes a UPF serving the first session or the first connection.

50. A communication method, applied to the ninth function, characterized in that: The method comprises: The ninth function is to associate the data related to the first terminal with the first session or the first tunnel or the first connection; The first session is an existing session, and / or the first connection is an existing connection, and / or the first tunnel is an existing tunnel or a previous tunnel or a tunnel associated with an existing session or connection.

51. The method according to claim 50, characterized in that The first terminal includes at least one passive Internet of Things device and / or tag.

52. The method according to any one of claims 50 to 51, characterized in that The ninth function includes at least one of the following: RAN, terminal.

53. A communication device, applied to a first function, characterized in that: include: A first sending module, configured to send first information to a second function; Among them, the first information includes at least one of the following: all or part of the identification of all or part of at least one first terminal, group identification, passive Internet of Things indication information, session identification or connection identification, all or part of the device type of at least one first terminal, all or part of the location information of at least one first terminal, DNN, S-NSSAI.

54. A communication device, applied to a second function, characterized in that: include: The third receiving module is used to obtain seventh information from the fourth function, where the seventh information includes at least one of the following: contract information of the first terminal, contract information related to the RAN, and contract information of the second terminal related to the RAN.

55. A communication device, applied to the fourth function, characterized in that: include: The storage module is used to store seventh information, where the seventh information includes at least one of the following: contract information of the first terminal, contract information related to the RAN, and contract information of the second terminal related to the RAN.

56. A communication device, applied to the fifth function, characterized in that: include: A fifth processing module is used to generate or determine or locally determine DNN and / or S-NSSAI.

57. A communication device, applied to the sixth function, characterized in that: include: The fifth receiving module is used to receive the eleventh information from the seventh function, and the eleventh information includes at least one of the following: all or part of the terminal identifier of the first terminal, the group identifier, the session identifier or the connection identifier, the passive Internet of Things indication information, the device type of the first terminal, and the location information of the first terminal.

58. A communication device, applied to the ninth function, characterized in that: include: a seventh processing module, configured to associate the data related to the first terminal with the first session or the first tunnel, or the first connection; The first session is an existing session, and / or the first connection is an existing connection, and / or the first tunnel is an existing tunnel or a previous tunnel or a tunnel associated with an existing session.

59. A network function, characterized in that The method comprises a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method according to any one of claims 1 to 52.

60. A readable storage medium, characterized in that The readable storage medium stores a program or instruction, and when the program or instruction is executed by a processor, the steps of the method according to any one of claims 1 to 52 are implemented.

Images