Method and device for establishing session of Internet of Things device

Abstract

The present application discloses a method and apparatus for establishing a session for an Internet of Things device, belonging to the field of wireless communication technology. A method for establishing a session for an Internet of Things device in an embodiment of the present application includes: a terminal obtaining an Internet of Things device group policy, wherein the Internet of Things device group policy instructs the terminal to establish a session channel based on an Internet of Things device group; and the terminal establishes a target session channel for a target Internet of Things device connected to the terminal based on the Internet of Things device group policy.

Description

Technical Field

[0001] The present application belongs to the field of wireless communication technology, and specifically relates to a method and apparatus for establishing a session of an Internet of Things device. Background Art

[0002] A communication system (e.g., a 5G system) can provide a data channel between a terminal and a data network, so that the terminal can access services in the data network through the data channel. The data channel between the terminal and the data network can be a protocol data unit (PDU) session, or it can be an IP stream. The data network can be identified by a data network name (DNN). A PDU session can be associated with a DNN, that is, the terminal can access the data network identified by the DNN through the PDU session. A PDU session can also be associated with a network slice (which can be identified using Single-Network Slice Selection Assistance Information (S-NSSAI)), that is, the UE can access the network slice or use the resources provided by the network slice through the PDU session.

[0003] IoT terminals generally refer to devices used in specific scenarios or for specific services, such as smart home devices, smart city devices, smart utilities, e-health devices, and smart wearables. In some cases, IoT devices require access to communication networks to access services on data networks. Therefore, establishing data channels for IoT devices is necessary. Conventional technology requires establishing independent session channels for each IoT device, which can sometimes inefficiently utilize communication network resources and lead to resource waste. Summary of the Invention

[0004] The embodiments of the present application provide a method and apparatus for establishing a session for an IoT device. Based on an IoT device group policy, a session channel is established for an IoT device accessing a terminal, which can effectively utilize the resources of a communication network and avoid wasting resources.

[0005] In a first aspect, a method for establishing a session of an Internet of Things device is provided, comprising: a terminal obtaining an Internet of Things device group policy, wherein the Internet of Things device group policy instructs the terminal to establish a session channel based on an Internet of Things device group; and the terminal establishing a target session channel for a target Internet of Things device connected to the terminal based on the Internet of Things device group policy.

[0006] In a second aspect, a session establishment device for an Internet of Things device is provided, which is applied to a terminal. The device includes: a first acquisition module, used to obtain an Internet of Things device group policy, wherein the Internet of Things device group policy instructs the terminal to establish a session channel based on the Internet of Things device group; and an establishment module, used to establish a target session channel for a target Internet of Things device connected to the terminal based on the Internet of Things device group policy.

[0007] According to a third aspect, a method for establishing a session of an Internet of Things device is provided, including: a first network-side device obtains a first Internet of Things device group policy, wherein the first Internet of Things device group policy indicates that a session channel is established in units of Internet of Things device groups; the first network-side device sends a second Internet of Things device group policy to a terminal based on the first Internet of Things device group policy, wherein the terminal has Internet of Things device access capability, and the second Internet of Things device group policy indicates that the terminal establishes a target session channel for a target Internet of Things device accessing the terminal in units of Internet of Things device groups.

[0008] In a fourth aspect, a session establishment device for an Internet of Things device is provided, which is applied to a first network side device, and the device includes: a second acquisition module, used to obtain a first Internet of Things device group policy, wherein the first Internet of Things device group policy indicates that a session channel is established in units of Internet of Things device groups; a second sending module, used to send the second Internet of Things device group policy to a terminal based on the first Internet of Things device group policy, wherein the terminal has Internet of Things device access capability, and the second Internet of Things device group policy indicates that the terminal establishes a target session channel for a target Internet of Things device accessing the terminal in units of Internet of Things device groups.

[0009] In a fifth aspect, a method for establishing a session of an Internet of Things device is provided, comprising: a second network side device receives Internet of Things device access capability information from a first network side device, wherein the Internet of Things device access capability information is used to indicate that the terminal can access the Internet of Things device to the communication network; the second network side device sends an Internet of Things device group policy to the first network side device, wherein the Internet of Things device group policy instructs the terminal to establish a session channel based on an Internet of Things device group.

[0010] In a sixth aspect, a session establishment device for an Internet of Things device is provided, which is applied to a second network side device, and the device includes: a receiving module for receiving an Internet of Things device group policy acquisition request from a first network side device; and a third sending module for sending a first Internet of Things device group policy to the first network side device, wherein the first Internet of Things device group policy indicates that a session channel is established based on an Internet of Things device group.

[0011] In a seventh aspect, a terminal is provided, comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the first aspect are implemented.

[0012] In an eighth aspect, a terminal is provided, comprising a processor and a communication interface, wherein the processor is used to implement the steps of the method described in the first aspect, and the communication interface is used to communicate with a network side device.

[0013] In the ninth aspect, a network side device is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the third aspect are implemented, or the steps of the method described in the fifth aspect are implemented.

[0014] In the tenth aspect, a network side device is provided, comprising a processor and a communication interface, wherein the processor is used to implement the steps of the method described in the third aspect, or to implement the steps of the method described in the fifth aspect, and the communication interface is used to communicate with the terminal.

[0015] In the eleventh 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 are implemented, or the steps of the method described in the third aspect are implemented, or the steps of the method described in the third aspect are implemented.

[0016] In the tenth aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instructions to implement the steps of the method described in the first aspect, or to implement the steps of the method described in the third aspect, or to implement the steps of the method described in the third aspect.

[0017] In the eleventh aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the steps of the method described in the first aspect, or the steps of the method described in the third aspect, or the steps of the method described in the third aspect.

[0018] In an embodiment of the present application, the terminal establishes a session channel for the IoT devices accessing the terminal based on the IoT device group policy and in units of IoT device groups, which can effectively utilize the resources of the communication network and avoid resource waste. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1A schematic diagram illustrating a wireless communication system to which embodiments of the present application may be applied;

[0020] Figure 2 A schematic diagram illustrating a flow chart of a method for establishing a session for an IoT device provided in an embodiment of the present application is shown;

[0021] Figure 3 Another flowchart of the method for establishing a session for an IoT device provided in an embodiment of the present application is shown;

[0022] Figure 4 Another flow chart illustrating a method for establishing a session for an IoT device according to an embodiment of the present application is shown;

[0023] Figure 5 Another flow chart illustrating a method for establishing a session for an IoT device according to an embodiment of the present application is shown;

[0024] Figure 6 Another flow chart illustrating a method for establishing a session for an IoT device according to an embodiment of the present application is shown;

[0025] Figure 7 A schematic diagram illustrating the structure of a session establishment apparatus for an IoT device provided in an embodiment of the present application is shown;

[0026] Figure 8 Another structural diagram of the apparatus for establishing a session for an IoT device according to an embodiment of the present application is shown;

[0027] Figure 9 Another structural diagram of the apparatus for establishing a session for an IoT device according to an embodiment of the present application is shown;

[0028] Figure 10 A schematic diagram showing the structure of a communication device provided in an embodiment of the present application is shown;

[0029] Figure 11 A schematic diagram showing the hardware structure of a terminal provided in an embodiment of the present application is shown;

[0030] Figure 12 A schematic diagram of the hardware structure of a network-side device provided in an embodiment of the present application is shown. DETAILED DESCRIPTION

[0031] The following will be combined with the accompanying drawings in the embodiments of this application to clearly 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 the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.

[0032] The terms "first," "second," and the like in the specification and claims of this application are used to distinguish similar objects, and are not used to describe a specific order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate, so that the embodiments of this application can be implemented in an order other than that illustrated or described herein, and that the objects distinguished by "first" and "second" are generally of the same type, and do not limit the number of objects. For example, the first object can be one or more. In addition, the term "and / or" in the specification and claims refers to at least one of the connected objects, and the character " / " generally indicates that the objects connected are in an "or" relationship.

[0033] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency Division Multiple Access (SC-FDMA), Next Generation (NG) system and other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for example purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to applications other than NR system applications, such as 6th Generation (6G) communication systems.

[0034] Figure 1A block diagram of a wireless communication system applicable to the embodiments of the present application is shown. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR) / virtual reality (VR) device, a robot, a wearable device (Wearable Device), a vehicle-mounted device (VUE), a pedestrian terminal (PUE), a smart home (home appliances with wireless communication functions, such as refrigerators, televisions, washing machines, or furniture), a game console, a personal computer (PC), an ATM or a self-service machine, and other terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiments of the present application. The network side device 12 may include an access network device and / or a core network device, wherein the access network device 12 may also be referred to as a radio access network device, a radio access network (RAN), a radio access network function, or a radio access network unit. The access network device 12 may include a base station, a WLAN access point, or a WiFi node, etc. The base station may be referred to as a node B, an evolved node B (eNB), an access point, a base transceiver station (BTS), a radio base station, a radio transceiver, a basic service set (BSS), an extended service set (ESS), a home node B, a home evolved node B, a transmitting and receiving point (TRP), or other appropriate terms in the field. As long as the same technical effect is achieved, the base station is not limited to a specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.The core network device may also be referred to as a core network node or core network function, and may include but is not limited to at least one of the following: Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized Network Configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (L-NEF), Binding Support Function (Binding Support Function) Function, BSF), application function (AF), policy control function (PCF), etc. It should be noted that in the embodiment of the present application, only the core network device in the NR system is introduced as an example, and the specific type of the core network device is not limited. It is worth noting that the functions of the above-mentioned core network device can be implemented by multiple devices together, or the functions of multiple core network devices can be implemented by one device, and the embodiment of the present application does not limit this. In the embodiment of the present application, if the functions of multiple core network devices are implemented by one device, the interaction between the multiple core network devices in the embodiment of the present application is the internal operation of the device.

[0035] IoT devices need to be connected to a communication network to access services in a data network. According to existing technologies, terminals that access IoT devices need to establish independent session channels for each IoT device. However, since many IoT devices are only used in specific scenarios or for specific services, the amount of data they interact with the network each time is relatively small, or the time interval between two interactions is long. Establishing an independent session channel for each IoT device sometimes results in inefficient use of communication network resources. In addition, the number of IoT devices is huge, and establishing an independent session channel for each IoT device will also result in a waste of resources. Therefore, in an embodiment of the present application, the terminal establishes a session channel for IoT devices that access the terminal in groups based on the IoT device group policy, which can effectively utilize the resources of the communication network and avoid resource waste.

[0036] The following, in conjunction with the accompanying drawings, describes in detail some embodiments and their application scenarios of the session establishment solution for the IoT device provided by the embodiments of the present application.

[0037] It should be noted that, in the embodiment of the present application, the session channel includes but is not limited to the PDU session channel, and the IoT device includes but is not limited to a passive IoT device.

[0038] Figure 2 A flow chart of a method for establishing a session of an IoT device in an embodiment of the present application is shown. The method 200 can be executed by a terminal. In other words, the method can be executed by software or hardware installed on the terminal. Figure 2 As shown, the method may include the following steps.

[0039] S210: The terminal obtains an IoT device group policy, where the IoT device group policy instructs the terminal to establish a session channel based on an IoT device group.

[0040] In an embodiment of the present application, the IoT device group policy is used to describe how a terminal establishes a session channel for an IoT device.

[0041] In this embodiment of the present application, the IoT device group policy instructs the terminal to establish a session channel based on the IoT device group. IoT devices belonging to the same IoT device group share a single session channel. In other words, when the terminal establishes a session channel for an IoT device group, it establishes a session channel for one or more IoT devices belonging to the same IoT device group.

[0042] In the application embodiment, a terminal with IoT device access capability can configure the IoT device group policy or obtain the IoT device group policy from a network-side device. For example, the operator or enterprise to which the terminal belongs configures the IoT device group policy for the terminal, or the terminal obtains the IoT device group policy from the AMF and / or SMF.

[0043] In one possible implementation, before the terminal obtains the IoT device group policy from the network device, the terminal sends IoT device access capability information to the network device, where the IoT device access capability information indicates that the terminal is capable of connecting IoT devices to the communication network. In this possible implementation, after obtaining information that the terminal has IoT device access capability, the network device sends the IoT device group policy to the terminal. For example, the terminal may include the IoT device access capability information in a registration request message sent to the network device; alternatively, the terminal may include the IoT device access capability information in a session establishment request sent to the network device.

[0044] In another possible implementation, the network device obtains the IoT device access capability information of the terminal. For example, the IoT device access capability information of the terminal may be stored in the terminal's contract data. The network device obtains the IoT device access capability information of the terminal from the terminal's contract data based on the terminal's identifier.

[0045] In the above possible implementation, the IoT device access capability information includes at least one of the following:

[0046] (1) The types of IoT devices supported by the terminal;

[0047] (2) The third-party identifier of the terminal. The third-party identifier of the terminal means that when a third party deploys the terminal as a reader / writer for an IoT device (e.g., a Passive IoT device), the terminal has the identifier of the third party that deployed it. This third-party identifier indicates that the terminal can support access to the third-party IoT device. The third party may be the entity that deploys, produces, or manages the terminal.

[0048] (3) The terminal's identification. For example, the terminal's identification can indicate that the terminal has IoT device access capability.

[0049] In a possible implementation of the embodiment of the present application, the IoT device group policy may further describe a method for grouping IoT devices. In this possible implementation, the IoT device group policy is further used to describe at least one of the following information:

[0050] (1) The terminal establishes a session channel for all IoT devices connected to the terminal, that is, all IoT devices connected to the terminal belong to the same IoT device group.

[0051] (2) The terminal establishes a session channel for IoT devices of the same type connected to the terminal. In other words, IoT devices connected to the terminal are grouped according to type, and IoT devices of the same type belong to the same IoT device group.

[0052] Optionally, the type (i.e., the type of IoT device) may include at least one of the following: an IoT service type and an IoT device type. Exemplarily, the IoT service type may include at least one of the following: environmental measurement, tag tracking, and material management. The IoT device type may include at least one of the following: a sensor and a tag.

[0053] It should be noted that in the embodiments of the present application, the IoT device accessed to the terminal may also be referred to as an IoT device connected to the terminal, an IoT device scanned by the terminal, an IoT device acquired by the terminal, an IoT device accessed to the communication network through the terminal, or an IoT device that the terminal can access to the communication network, etc., which is not limited in the specific embodiments of the present application.

[0054] S212: The terminal establishes a target session channel for a target IoT device connected to the terminal based on the IoT device group policy.

[0055] In an embodiment of the present application, optionally, when establishing a target session channel for the target IoT device, the terminal may first determine whether a target session channel corresponding to the target IoT device group to which the target IoT device belongs has been established, and if not, establish the target session channel. Therefore, S212 may optionally further include: the terminal establishing a target session channel for the target IoT device connected to the terminal based on the IoT device group policy, if a target session channel corresponding to the target IoT device group has not been established, wherein the target IoT device group is the IoT device group to which the target IoT device belongs.

[0056] In one possible implementation of the embodiment of the present application, the IoT device group policy may further include establishment parameters for the target session channel. When establishing a target session channel for the target IoT device, the terminal may establish a corresponding target session channel based on the establishment parameters for the target session channel.

[0057] Optionally, the establishment parameters of the target session channel include but are not limited to at least one of the following:

[0058] (1) First indication information, wherein the first indication information is used to indicate that the target session channel is of IP type.

[0059] (2) Second indication information, wherein the second indication information is used to indicate that the target session channel is of Ethernet type.

[0060] (3) Third indication information, wherein the third indication information is used to indicate a service continuity mode of the target session channel.

[0061] (4) Fourth indication information, wherein the fourth indication information is used to indicate that the target session channel is a control plane channel.

[0062] (5) Fifth indication information, wherein the fifth indication information is used to indicate that the target session channel is a user plane channel.

[0063] (6) Sixth indication information, wherein the sixth indication information is used to indicate that the target session channel is an optimized user plane channel. The optimized user plane channel may refer to an air interface being a user plane channel, and a control plane channel being used between the base station and the core network. Exemplarily, the following channel path is used: UE-RAN-AMF-SMF-NEF-server.

[0064] In one implementation, the target session channel establishment parameters may include one of the above (1)-(6), or may include multiple of the above (1)-(6). For example, the above (1) and (5) may be included to indicate that the target session channel is an IP-type user plane channel. Alternatively, the above (3) and (5) may be included to indicate that the target session channel is a user plane channel and the service continuity mode is the mode indicated by the third indication information.

[0065] In one possible implementation, if the IoT device group policy describes that the terminal establishes a session channel for IoT devices of the same type as those connected to the terminal, then establishing a target session channel for a target IoT device connected to the terminal in S212 may include:

[0066] Step 1: The terminal obtains the target type of the target IoT device;

[0067] Step 2: Establish a target session channel for the target IoT device based on the IoT device group policy and the target type. Optionally, in step 2, if a target session channel corresponding to the target type has not been established, establish a target session channel for the target IoT device.

[0068] As a method for a terminal to obtain the target type of a target IoT device, the terminal obtains an identifier of the target IoT device, which indicates the target type of the target IoT device. For example, the identifier of the target IoT device includes Field 1, which indicates the IoT service type and / or IoT device type of the target IoT device. Alternatively, the identifier of the target IoT device includes Field 2 and Field 3, which indicate the IoT service type and IoT device type of the target IoT device, respectively.

[0069] Through the above-mentioned scheme provided in the embodiment of the present application, the terminal obtains the IoT device group policy, and based on the IoT device group policy, establishes a session channel for the IoT device accessing the terminal in units of IoT device groups, which can effectively utilize the resources of the communication network and avoid resource waste.

[0070] Figure 3 Another flow chart of the session establishment method of the IoT device in the embodiment of the present application is shown. The method 300 can be executed by a first network side device. In other words, the method can be executed by software or hardware installed on the first network side device, and the first network side device can be the AMF and / or SMF in the core network. Figure 3 As shown, the method may include the following steps.

[0071] S310: The first network-side device obtains a first IoT device group policy, where the first IoT device group policy indicates establishing a session channel based on an IoT device group.

[0072] In a possible implementation, the first network-side device acquiring the first IoT device group policy may include: the first network-side device receiving the first IoT device group policy from the UDM and / or PCF.

[0073] In one possible implementation, before S310, the method further includes: the first network-side device obtaining IoT device access capability information of the terminal, wherein the IoT device access capability information is used to indicate that an IoT device can access the terminal. In this possible implementation, after obtaining the IoT device access capability information of the terminal, the first network-side device learns that the terminal has IoT device access capability, and then obtains the first IoT device group policy; or, after obtaining the IoT device access capability information of the terminal, the first network-side device sends the IoT device access capability information to the UDM and / or PCF to obtain the first IoT device group policy.

[0074] In one possible implementation, the first network-side device obtaining the IoT device access capability information of the terminal may include: the first network-side device receiving a first message from the terminal, wherein the first message carries the IoT device access capability information, and the first message includes one of the following: a registration message or a session establishment request message. In this possible implementation, the terminal may send the IoT device access capability information in the registration message or the session establishment request message.

[0075] In the embodiment of the present application, the IoT device access capability information and obtaining the IoT device access capability information can be specifically referred to the relevant description in method 200, which will not be repeated here.

[0076] In one possible implementation, before the first network-side device receives the first IoT device group policy from the UDM and / or PCF, the method may further include: the first network-side device sending the IoT device access capability information to the UDM and / or PCF. After receiving the IoT device access capability information, the UDM and / or PCF sends the first IoT device group policy to the first network-side device.

[0077] At step S312, the first network-side device sends the second IoT device group policy to the terminal based on the first IoT device group policy, wherein the terminal has IoT device access capability, and the second IoT device group policy instructs the terminal to establish a target session channel for a target IoT device connected to the terminal in units of IoT device groups.

[0078] In an embodiment of the present application, the second IoT device group policy may be the same as or different from the first IoT device group policy. For example, the second IoT device group policy may be a subset of the first IoT device group policy, wherein the first IoT device group policy may include methods for establishing session channels corresponding to various types of IoT device groups in the communication network, while the second IoT device group policy may only include methods for establishing session channels corresponding to IoT device groups of the type supported by the terminal. For example, the first network-side device may select a policy applicable to the terminal from the first IoT device group policy from the UDM and / or PCF as the second IoT device group policy. Exemplarily, the first network-side device selects a policy applicable to the terminal based on the IoT device access capability information of the terminal. For example, if the IoT device access capability information of the terminal indicates that the terminal supports tag-type IoT device access, the first network-side device sends the policy related to tag-type IoT devices in the first IoT device group policy to the terminal.

[0079] The second IoT device group policy may be the IoT device group policy acquired by the terminal in method 200 .

[0080] In one possible implementation, the second IoT device group policy is used to describe at least one of the following information:

[0081] (1) Establishing a target session channel for all IoT devices connected to the terminal; in this case, all IoT devices connected to the terminal belong to the same IoT device group.

[0082] (2) Establishing a target session channel for IoT devices of the same type connected to the terminal. In this case, IoT devices connected to the terminal are grouped by type, and IoT devices of the same type belong to one IoT device.

[0083] In one possible implementation, the IoT device type includes at least one of the following: an IoT service type and an IoT device type. Optionally, the IoT service type includes, but is not limited to, at least one of the following: environmental measurement, tag tracking, and material management. The IoT device type includes, but is not limited to, at least one of the following: a sensor and a tag.

[0084] In one possible implementation, the second IoT device group policy further includes establishment parameters for the target session channel, and the terminal is instructed to establish the target session channel corresponding to the establishment parameters through the establishment parameters.

[0085] In one possible implementation, the target session channel establishment parameters include but are not limited to at least one of the following:

[0086] (1) first indication information, wherein the first indication information is used to indicate that the target session channel is of IP type;

[0087] (2) second indication information, wherein the second indication information is used to indicate that the target session channel is of Ethernet type;

[0088] (3) third indication information, wherein the third indication information is used to indicate a service continuity mode of the target session channel;

[0089] (4) fourth indication information, wherein the fourth indication information is used to indicate that the target session channel is a control plane channel;

[0090] (5) Fifth indication information, wherein the fifth indication information is used to indicate that the target session channel is a user plane channel.

[0091] (6) Sixth indication information, wherein the sixth indication information is used to indicate that the target session channel is an optimized user plane channel. The optimized user plane channel may refer to an air interface being a user plane channel, and a control plane channel being used between the base station and the core network. Exemplarily, the following channel path is used: UE-RAN-AMF-SMF-NEF-server.

[0092] Through the above-mentioned scheme provided in the embodiment of the present application, the first network side device sends the second IoT device group policy to the terminal, instructing the terminal to establish a session channel for the IoT devices accessing the terminal based on the IoT device group policy and in units of IoT device groups, thereby effectively utilizing the resources of the communication network and avoiding resource waste.

[0093] Figure 4 Another flow chart of the method for establishing a session of an IoT device in an embodiment of the present application is shown. The method 400 can be executed by a second network side device. In other words, the method can be executed by software or hardware installed on the second network side device, which can be a UDM and / or PCF in the core network. Figure 4 As shown, the method may include the following steps.

[0094] S410: The second network-side device receives an IoT device group policy acquisition request from the first network-side device.

[0095] In one possible implementation, the IoT device group policy acquisition request includes IoT device access capability information, where the IoT device access capability information indicates that the terminal is capable of connecting the IoT device to the communication network. For example, upon receiving a first message carrying the IoT device access capability information, the first network-side device may send the IoT device group policy acquisition request to the second network-side device.

[0096] In one or more possible implementations, the IoT device group policy acquisition request may be a Nudm_UECM_Registration or Nudm_SDM_Get request, or may be an AM policy association (PolicyAssociation) establishment or modification request.

[0097] S412: The second network-side device sends a first IoT device group policy to the first network-side device, wherein the first IoT device group policy indicates establishing a session channel based on an IoT device group.

[0098] The first IoT device group policy may be the same as the first IoT device group policy in method 300 .

[0099] In one possible implementation, the first IoT device group policy is used to describe at least one of the following information:

[0100] (1) Establish a session channel for all IoT devices connected to the same terminal; that is, IoT devices are grouped according to the terminals they are connected to. IoT devices connected to different terminals belong to different IoT device groups, while IoT devices connected to the same terminal belong to the same IoT device group.

[0101] (2) Establish a session channel for IoT devices of the same type connected to the same terminal. That is, for a terminal, IoT devices of the same type are grouped according to their types. IoT devices of the same type belong to the same IoT device group, while IoT devices of different types belong to different IoT device groups.

[0102] In one possible implementation, the type (i.e., the type of IoT device) includes at least one of the following: an IoT service type and an IoT device type. Optionally, the IoT service type includes at least one of the following: environmental measurement, tag tracking, and material management. The IoT device type includes at least one of the following: a sensor and a tag.

[0103] In one possible implementation, the first IoT device group policy also includes session channel establishment parameters. In a specific application, if the first IoT device group policy is used to describe establishing a session channel for IoT devices of the same type connected to the same terminal, the first IoT device group policy can set session channel establishment parameters for different types of IoT devices.

[0104] In one possible implementation, the session channel establishment parameters include at least one of the following:

[0105] (1) first indication information, wherein the first indication information is used to indicate that the session channel is of IP type;

[0106] (2) second indication information, wherein the second indication information is used to indicate that the session channel is of Ethernet type;

[0107] (3) third indication information, wherein the third indication information is used to indicate a service continuity mode of the session channel;

[0108] (4) fourth indication information, wherein the fourth indication information is used to indicate that the session channel is a control plane channel;

[0109] (5) Fifth indication information, wherein the fifth indication information is used to indicate that the session channel is a user plane channel.

[0110] (6) Sixth indication information, wherein the sixth indication information is used to indicate that the target session channel is an optimized user plane channel. The optimized user plane channel may refer to an air interface being a user plane channel, and a control plane channel being used between the base station and the core network. Exemplarily, the following channel path is used: UE-RAN-AMF-SMF-NEF-server.

[0111] Through the above-mentioned scheme provided in the embodiment of the present application, the second network side device sends the first IoT device group policy to the first network side device, so that the first network side device can instruct the terminal to establish a session channel for the IoT device accessing the terminal based on the IoT device group, thereby effectively utilizing the resources of the communication network and avoiding resource waste.

[0112] Figure 5 Another flow chart of the method for establishing a session of an IoT device provided in an embodiment of the present application is shown as follows: Figure 5 As shown, the method mainly includes the following steps.

[0113] S501. The UE sends the UE's Passive IoT device access capability information to the AMF. The UE's Passive IoT device access capability information indicates that the Passive IoT device can access the 5G network from the UE. A Passive IoT device refers to an IoT device that does not have its own power supply or battery and needs to obtain energy from other devices or the environment to transmit signals. For example, the UE can be a reader / writer that scans Passive IoT devices; or the UE can establish a PDU session for the Passive IoT device to transmit data from the Passive IoT device.

[0114] The Passive IoT device access capability information of the UE may include at least one of the following: the Passive IoT type supported by the UE, the third-party identifier to which the UE belongs, the identifier of the UE, and the transmission method of Passive IoT device data supported by the UE. Among them, the Passive IoT type may include the Passive IoT business type (such as environmental monitoring, tag tracking, material management, etc.) and / or the Passive IoT device type (such as sensors, tags, etc.). The third-party identifier to which the UE belongs means: when a third party deploys the UE as a reader / writer for a Passive IoT device, the UE has the identifier of the third party that deploys it. At this time, the UE can support the access of the third-party Passive IoT device.

[0115] The supported transmission methods of Passive IoT device data include at least one of the following: uplink data transmission of Passive IoT device, downlink data transmission of Passive IoT device, data transmission of Passive IoT device, UE as a relay for uplink data of Passive IoT device, UE as a relay for downlink data of Passive IoT device, UE as a relay for data transmission of Passive IoT device, data transmission of Passive IoT device in group mode, and UE as a relay for data transmission of Passive IoT device in group mode.

[0116] Optionally, the UE identifier can indicate that the terminal has IoT device access capability. Optionally, it can also indicate the Passive IoT type supported by the UE and / or the identifier of the third party to which the UE belongs.

[0117] As a possible implementation, the UE sends the UE's Passive IoT device access capability information to the AMF via a NAS message. For example, the UE may send the UE's Passive IoT device access capability information via a registration message. Optionally, the UE may also send the UE's Passive IoT device access capability information to the RAN in an RRC message.

[0118] As another possible implementation, the UE may send the UE's Passive IoT device access capability information to the AMF via the RAN. For example, the UE sends the UE's Passive IoT device access capability information to the RAN via an RRC message; and the RAN sends the UE's Passive IoT device access capability information to the AMF via an NGAP message.

[0119] In the two possible implementations described above, the RAN may optionally further send the RAN's Passive IoT device access capability information to the AMF. The RAN's Passive IoT device access capability information may include at least one of the following: the Passive IoT type supported by the RAN, the identifier of the third party associated with the RAN, and the Passive IoT device data transmission method supported by the RAN.

[0120] The third party associated with RAN can be understood as: RAN can support the access of the third party's Passive IoT devices.

[0121] S502: AMF sends the UE's Passive IoT device access capability information to the UDM / PCF.

[0122] Exemplarily, the AMF may send a Nudm_UECM_Registration or Nudm_SDM_Get request to the UDM, which carries the UE's Passive IoT device access capability information.

[0123] Exemplarily, the AMF may carry the UE's Passive IoT device access capability information in the AM Policy Association establishment or modification request. For example, the AMF sends an Npcf_AMPolicyControl_Create or Npcf_AMPolicyControl_Update request to the PCF, which carries the UE's Passive IoT device access capability information.

[0124] Optionally, the AMF also sends the RAN's Passive IoT device access capability information to the UDM / PCF.

[0125] S503: UDM / PCF sends the Passive IoT device group policy to AMF.

[0126] The Passive IoT device group policy can be used to describe how the UE establishes a PDU session for a Passive IoT device. The Passive IoT device group policy can describe at least one of the following: all Passive IoT devices scanned by the UE share a PDU session, the UE establishes session channels based on the Passive IoT type, and the data transmission method for the Passive IoT device.

[0127] The transmission method of Passive IoT device data may include at least one of the following: UE transmitting uplink data of Passive IoT device, UE receiving downlink data of Passive IoT device, data transmission of Passive IoT device via UE, RAN receiving uplink data of Passive IoT device, RAN transmitting downlink data of Passive IoT device, and data transmission of Passive IoT device via RAN.

[0128] For example, you can group them according to the Passive IoT service type, and different groups use different session channels.

[0129] Optionally, the Passive IoT device group policy may further include session channel establishment parameters corresponding to the Passive IoT type. For example, different groups may establish session channels using different establishment parameters.

[0130] The session channel establishment parameters may include at least one of the following: IP type indication information, Ethernet type indication information, service continuity mode indication information, control plane channel indication information, user plane channel indication information, and optimized user plane channel indication information. The session channel establishment parameters can be used to indicate the establishment of different types of session channels, such as a PDU session for establishing a user plane channel (i.e., using the user plane to transmit data), a PDU session for a control plane channel (i.e., using control plane signaling to transmit data), an optimized user plane PDU session (i.e., using the control plane and the user plane to transmit data, such as using the user plane for the air interface and the control plane between the RAN and the core network), an IP type PDU session (or Ethernet type PDU session), a PDU session with a service continuity mode of SSC mode 1, 2, or 3, etc.

[0131] Optionally, the UDM / PCF may determine, based on the UE's subscription data and / or operator configuration information, that the UE can allow access to the Passive IoT device.

[0132] Exemplarily, the UDM may send a Nudm_UECM_Registration or Nudm_SDM_Get response to the AMF, which carries the Passive IoT device group policy.

[0133] Exemplarily, the PCF may send the Passive IoT device group policy to the AMF during the establishment or modification of the AM Policy Association. For example, the PCF sends an Npcf_AMPolicyControl_Create or Npcf_AMPolicyControl_Update response to the AMF, which carries the Passive IoT device group policy.

[0134] S504: AMF sends the Passive IoT device group policy to the UE.

[0135] As a possible implementation, the AMF sends the Passive IoT device group policy to the UE via a NAS message. For example, the AMF may send the Passive IoT device group policy to the UE via a Registration Response message. Optionally, the AMF may also send the Passive IoT device group policy to the RAN. Optionally, the AMF may also send the UE's Passive IoT device access capability information to the RAN, indicating that the UE has Passive IoT device access capability.

[0136] As another possible implementation, the AMF can send the Passive IoT device group policy to the UE via the RAN. For example, the AMF sends the Passive IoT device group policy to the RAN via an NGAP message; the RAN then sends the Passive IoT device group policy to the UE via an RRC message. Optionally, the AMF can also send Passive IoT device access capability information to the RAN via an NGAP message, indicating that the UE has Passive IoT device access capability. It is worth noting that the Passive IoT device group policy itself can also serve as information indicating that the UE has Passive IoT device access capability.

[0137] It is worth noting that steps S501-S504 are optional. For example, the UE and / or RAN may also obtain the Passive IoT device group policy through configuration.

[0138] S505: The UE obtains the identifier of the Passive IoT device.

[0139] For example, the UE can act as a reader to obtain the identification or signal sent by the Passive IoT device. The UE can also not act as a reader to obtain the identification or signal sent by other devices (for example, the RAN acts as a reader to read the identification or signal sent by the Passive IoT device).

[0140] The identifier of the Passive IoT device may be an Electronic Product Code (EPC), a MAC address, or other information that can be used to identify the Passive IoT device.

[0141] S506: The UE obtains the type of the Passive IoT device.

[0142] As a possible implementation, the UE may query the Passive IoT application (App) / network function (NF) for the type of the Passive IoT device. S506 may include: Figure 5 S506a-506b shown in .

[0143] For example, the UE sends the Passive IoT device identifier to the Passive IoT App / NF, and the UE receives the Passive IoT device type sent by the Passive IoT App / NF.

[0144] Specifically, the UE can communicate with the PassiveIoT App / NF through its own control plane or user plane session channel (e.g., PDU session). If communication is through a PDU session, the UE needs to establish the PDU session first. The UE can configure or receive PDU session establishment parameters (e.g., DNN and / or S-NSSAI) from the network-side device. Exemplarily, the UE can receive a UE routing policy (URSP) during the registration process, which includes parameters for establishing the PDU session.

[0145] As another possible implementation, the UE may obtain the type of the Passive IoT device through configuration information.

[0146] As another possible implementation, the UE may obtain the type of the Passive IoT device from the identification information of the Passive IoT device. For example, the identification information of the Passive IoT device includes a type field indicating the type information of the Passive IoT device.

[0147] Of course, the UE may only support one type of Passive IoT device. In this case, the UE may assume that all Passive IoT devices connected to the UE are of this type, and there is no need to execute S506. That is, S506 is an optional step.

[0148] S507: The UE sends a PDU session establishment request to the AMF according to the Passive IoT device group policy obtained in step S504, requesting to establish a PDU session for the Passive IoT device.

[0149] Optionally, before S507, the UE determines whether a PDU session corresponding to the Passive IoT device type already exists. If so, the PDU session establishment request is not established. If not, the PDU session establishment request is sent.

[0150] The UE can send a PDU session establishment request to the AMF through the RAN, that is, the UE sends the PDU session establishment request to the RAN, and the RAN forwards the PDU session establishment request to the AMF. Optionally, the UE can also send indication information of the transmission mode of the Passive IoT device data to the RAN. For example, the indication information of the transmission mode of the Passive IoT device data indicates "uplink" and / or "downlink", indicating that the PDU session is used to transmit the uplink and / or downlink data of the PIoT device. The UE can send indication information of the transmission mode of the Passive IoT device data to the RAN according to the transmission mode of the Passive IoT device data in the Passive IoT device group policy.

[0151] Exemplarily, the UE sends an RRC message to the RAN, including a PDU session establishment request.

[0152] S508, AMF sends a PDU session establishment request to SMF, requesting the Passive IoT device to establish a PDU session.

[0153] S509, SMF establishes a PDU session according to the PDU session establishment request and sends a PDU session establishment response to AMF.

[0154] S510, AMF returns a PDU session establishment response to the UE, establishing a PDU session for the Passive IoT device.

[0155] After the PDU session is established, the RAN may route the uplink and / or downlink data of the Passive IoT device according to the transmission mode of the Passive IoT device data obtained in the aforementioned steps.

[0156] For example, if the transmission mode of Passive IoT device data indicates that the UE transmits the uplink data of the Passive IoT device, or the RAN transmits the downlink data of the Passive IoT device, when the RAN receives the downlink data of the Passive IoT device, the RAN sends the downlink data to the Passive IoT device; when the RAN receives the uplink data of the Passive IoT device from the UE, the RAN sends the uplink data to the UPF of the PDU session.

[0157] The above S501-S504 may occur during the UE registration process. For example, in step S501, the UE sends a registration request message to the AMF, which includes the Passive IoT device access capability information; in step S504, the AMF sends a registration acceptance message to the UE, which includes the Passive IoT device group policy.

[0158] Of course, the present invention is not limited thereto, and the above steps S501-S504 may also occur at any time after the UE registers. Accordingly, steps S501 and S504 may be replaced with other Non-Access-Stratum (NAS) messages.

[0159] The execution order of S506 and steps S507-S510 is not limited. For example, in step S505, if Passive IoT device is the first Passive IoT device identifier obtained by the UE, the UE may first execute S507-S510 and then execute step 506.

[0160] Figure 6 Another flow chart of the method for establishing a session of an IoT device provided in an embodiment of the present application is shown as follows: Figure 6 As shown, the method mainly includes the following steps.

[0161] In step S601, the UE sends its Passive IoT device access capability information to the SMF. This information indicates that the Passive IoT device can access the 5G network from the UE. For example, the UE can be a reader / writer, scanning for Passive IoT devices; or the UE can establish a PDU session for the Passive IoT device to transmit data from the Passive IoT device.

[0162] The Passive IoT device access capability information of the UE may refer to the description in S501 of method 500 .

[0163] As an example, the UE may send a PDU session establishment request message to the SMF, which includes the UE's PassiveIoT device access capability information.

[0164] As another example, the UE may also send the UE's Passive IoT device access capability information to the SMF in other processes, such as a PDU session modification request message. This is not limited in the embodiments of the present application.

[0165] UE can send UE's Passive IoT device access capability information to SMF through AMF, such as Figure 6As shown, S601 may include steps S601a and S601b.

[0166] As a possible implementation, the UE sends the UE's Passive IoT device access capability information to the AMF via a NAS message. Optionally, the UE may also send the UE's Passive IoT device access capability information to the RAN in an RRC message.

[0167] As another possible implementation, the UE may send the UE's Passive IoT device access capability information to the AMF via the RAN. For example, the UE sends the UE's Passive IoT device access capability information to the RAN via an RRC message; and the RAN sends the UE's Passive IoT device access capability information to the AMF via an NGAP message.

[0168] In the two possible implementations described above, the AMF forwards the UE's Passive IoT device access capability information to the SMF. Optionally, the RAN may also send the RAN's PIoT device access capability information to the AMF. For details about the RAN's Passive IoT device access capability information, refer to S501 of method 500. In this case, the AMF may forward the RAN's Passive IoT device access capability information to the SMF.

[0169] S602, SMF sends the UE's Passive IoT device access capability information to UDM / PCF.

[0170] Exemplarily, the SMF sends a Nudm_SDM_Get or Nudm_SDM_Subscribe or Nudm_SDM_Get request to the UDM, which carries the Passive IoT device access capability information of the UE.

[0171] Exemplarily, the SMF may also carry the UE's Passive IoT device access capability information in the SM Policy Association establishment or modification request. For example, the SMF may send an Npcf_SMPolicyControl_Create or Npcf_SMPolicyControl_Update request to the PCF, which carries the UE's Passive IoT device access capability information.

[0172] Optionally, the AMF also sends the RAN's Passive IoT device access capability information to the UDM / PCF.

[0173] S603, UDM / PCF sends the Passive IoT device group policy to SMF.

[0174] For S603 , please refer to the description of S503 in method 500 .

[0175] Exemplarily, the UDM sends a Nudm_SDM_Get or Nudm_SDM_Subscribe response to the SMF, which carries the Passive IoT device group policy.

[0176] Exemplarily, the PCF sends the Passive IoT device group policy to the SMF during the process of establishing or modifying the SM Policy Association. For example, the PCF sends an Npcf_SMPolicyControl_Create or Npcf_SMPolicyControl_Update response to the SMF, which carries the Passive IoT device group policy.

[0177] S604, SMF sends the Passive IoT device group policy to the UE.

[0178] As an example, the SMF may send a PDU session establishment response message including the Passive IoT device group policy to the SMF.

[0179] As another example, the SMF may also send the Passive IoT device group policy to the UE in other processes, such as a PDU session modification response message. This application does not impose any restrictions.

[0180] Optionally, SMF can send Passive IoT device group policy to UE via AMF, such as Figure 6 As shown, S604 may include steps S604a and S604b. The implementation method of SMF sending the Passive IoT device group policy to AMF and AMF sending the Passive IoT device group policy to UE can refer to the description in S504.

[0181] Optionally, the SMF sends the UE's Passive IoT device access capability information to the RAN, indicating that the UE has the Passive IoT device access capability.

[0182] Optionally, the SMF sends the Passive IoT device group policy to the RAN.

[0183] The exemplary SMF may send the UE's Passive IoT device access capability information and / or Passive IoT device group policy to the RAN via the N2 session management parameters.

[0184] It is worth noting that the UE and / or RAN can also obtain the Passive IoT device group policy through configuration.

[0185] For S605 - S610 , please refer to the description of S505 - S510 in method 500 .

[0186] Through the technical solution provided in the embodiments of the present application, the communication system establishes a session for the IoT device based on the group to which the IoT device belongs and the group policy information, thereby effectively utilizing network resources.

[0187] The session method for an IoT device provided in the embodiment of the present application can be performed by a session establishment device of the IoT device. In the embodiment of the present application, the session establishment device of the IoT device is used as an example to illustrate the session establishment device of the IoT device provided in the embodiment of the present application.

[0188] In the embodiments of the present application, Passive IoT is sometimes referred to as PIOT; identification is sometimes referred to as ID; and device is sometimes referred to as equipment.

[0189] Figure 7 A schematic diagram of a structure of a session establishment device for an Internet of Things device provided in an embodiment of the present application is shown, and the device can be applied to a terminal. Figure 7 As shown, the device 700 mainly includes: a first acquisition module 701, which is used to obtain an IoT device group policy, wherein the IoT device group policy instructs the terminal to establish a session channel based on the IoT device group; an establishment module 702, which is used to establish a target session channel for a target IoT device connected to the terminal based on the IoT device group policy.

[0190] In one possible implementation, the IoT device group policy is used to describe at least one of the following information:

[0191] Establish a session channel for all IoT devices connected to the terminal;

[0192] A session channel is established for IoT devices of the same type connected to the terminal.

[0193] In one possible implementation, the establishing module 702 establishes a target session channel for a target IoT device connected to the terminal based on the IoT device group policy, including:

[0194] Obtaining a target type of the target IoT device;

[0195] Based on the IoT device group policy, a target session channel is established for the target IoT device.

[0196] In one possible implementation, the establishing module 702 establishes a target session channel corresponding to the target type for the target IoT device based on the IoT device group policy, including:

[0197] If a target session channel corresponding to the target type is not established, a target session channel is established for the target Internet of Things device.

[0198] In one possible implementation, the type includes at least one of the following: an Internet of Things service type and an Internet of Things device type.

[0199] In a possible implementation, the IoT service type includes at least one of the following: environmental measurement, tag tracking, and material management.

[0200] In a possible implementation, the IoT device type includes at least one of the following: a sensor, a tag.

[0201] In a possible implementation, the IoT device group policy also includes establishment parameters for the target session channel.

[0202] In one possible implementation, the target session channel establishment parameter includes at least one of the following:

[0203] First indication information, wherein the first indication information is used to indicate that the target session channel is of IP type;

[0204] Second indication information, wherein the second indication information is used to indicate that the target session channel is of Ethernet type;

[0205] third indication information, wherein the third indication information is used to indicate a service continuity mode of the target session channel;

[0206] Fourth indication information, wherein the fourth indication information is used to indicate that the target session channel is a control plane channel;

[0207] Fifth indication information, wherein the fifth indication information is used to indicate that the target session channel is a user plane channel.

[0208] In a possible implementation, the first obtaining module 701 obtains the IoT device group policy, including:

[0209] Obtain the IoT device group policy from the network side device.

[0210] In one possible implementation, the device further includes: a first sending module, configured to send Internet of Things device access capability information to a network side device, wherein the Internet of Things device access capability information is used to indicate that the terminal is capable of accessing the Internet of Things device to a communication network.

[0211] In one possible implementation, the first sending module is further configured to send Internet of Things device access capability information to a network-side device, wherein the Internet of Things device access capability information is configured to indicate that the terminal is capable of accessing the Internet of Things device to a communication network.

[0212] In one possible implementation, the IoT device access capability information includes at least one of the following:

[0213] The types of IoT devices supported by the terminal;

[0214] The third-party identifier to which the terminal belongs;

[0215] an identifier of the terminal;

[0216] The transmission method of IoT device data supported by the terminal.

[0217] Optionally, the IoT device data transmission method includes at least one of the following:

[0218] Uplink data transmission of IoT devices;

[0219] Downlink data transmission of IoT devices;

[0220] Data transmission from IoT devices;

[0221] The terminal acts as a relay for uplink data from IoT devices;

[0222] The terminal acts as a relay for downlink data from IoT devices;

[0223] The terminal acts as a relay for data transmission of IoT devices;

[0224] Transmit data from IoT devices in groups;

[0225] The terminal acts as a relay for transmitting data of IoT devices in a group manner.

[0226] Figure 8 Another structural diagram of the session establishment device of the Internet of Things device provided in an embodiment of the present application is shown, which can be applied to a first network side device, such as Figure 8As shown, the device 800 mainly includes: a second acquisition module 801, used to obtain a first Internet of Things device group policy, wherein the first Internet of Things device group policy indicates that a session channel is established in units of Internet of Things device groups; a second sending module 802, used to send the second Internet of Things device group policy to the terminal based on the first Internet of Things device group policy, wherein the terminal has Internet of Things device access capability, and the second Internet of Things device group policy indicates that the terminal establishes a target session channel for a target Internet of Things device accessing the terminal in units of Internet of Things device groups.

[0227] In a possible implementation, the second acquisition module 801 is further configured to acquire IoT device access capability information of the terminal, wherein the IoT device access capability information is used to indicate whether an IoT device can access the terminal.

[0228] In one possible implementation, the second IoT device group policy is used to describe at least one of the following information:

[0229] Establish a target session channel for all IoT devices connected to the terminal;

[0230] A target session channel is established for IoT devices of the same type connected to the terminal.

[0231] In one possible implementation, the type includes at least one of the following: an Internet of Things service type and an Internet of Things device type.

[0232] In a possible implementation, the IoT service type includes at least one of the following: environmental measurement, tag tracking, and material management.

[0233] In a possible implementation, the IoT device type includes at least one of the following: a sensor, a tag.

[0234] In a possible implementation, the second IoT device group policy further includes establishment parameters for the target session channel.

[0235] In one possible implementation, the target session channel establishment parameter includes at least one of the following:

[0236] First indication information, wherein the first indication information is used to indicate that the target session channel is of IP type;

[0237] Second indication information, wherein the second indication information is used to indicate that the target session channel is of Ethernet type;

[0238] third indication information, wherein the third indication information is used to indicate a service continuity mode of the target session channel;

[0239] Fourth indication information, wherein the fourth indication information is used to indicate that the target session channel is a control plane channel;

[0240] Fifth indication information, wherein the fifth indication information is used to indicate that the target session channel is a user plane channel.

[0241] In a possible implementation, the second obtaining module 801 obtains the IoT device access capability information of the terminal, including:

[0242] Receive a first message from the terminal, wherein the first message carries the access capability information of the Internet of Things device, and the first message includes one of the following: a registration message and a session establishment request message.

[0243] In a possible implementation, the second obtaining module 801 obtains the first IoT device group policy, including:

[0244] Receive the first IoT device group policy from a unified data management entity UDM or a policy control function entity PCF.

[0245] Figure 9 A schematic diagram of a structure of a session establishment device for an Internet of Things device provided in an embodiment of the present application is shown, which can be applied to a second network side device, such as Figure 9 As shown, the device 900 mainly includes: a receiving module 901, used to receive an IoT device group policy acquisition request from a first network side device; a third sending module 902, used to send a first IoT device group policy to the first network side device, wherein the first IoT device group policy indicates that a session channel is established based on an IoT device group.

[0246] In one possible implementation, the first IoT device group policy is used to describe at least one of the following information:

[0247] Establish a session channel for all IoT devices connected to the same terminal;

[0248] Establish a session channel for IoT devices of the same type connected to the same terminal.

[0249] In one possible implementation, the type includes at least one of the following: an Internet of Things service type and an Internet of Things device type.

[0250] In a possible implementation, the IoT service type includes at least one of the following: environmental measurement, tag tracking, and material management.

[0251] In a possible implementation, the IoT device type includes at least one of the following: a sensor, a tag.

[0252] In a possible implementation, the IoT device group policy also includes session channel establishment parameters.

[0253] In one possible implementation, the session channel establishment parameters include at least one of the following:

[0254] First indication information, wherein the first indication information is used to indicate that the session channel is of IP type;

[0255] Second indication information, wherein the second indication information is used to indicate that the session channel is of Ethernet type;

[0256] third indication information, wherein the third indication information is used to indicate a service continuity mode of the session channel;

[0257] Fourth indication information, wherein the fourth indication information is used to indicate that the session channel is a control plane channel;

[0258] Fifth indication information, wherein the fifth indication information is used to indicate that the session channel is a user plane channel.

[0259] In a possible implementation, the IoT device group policy acquisition request includes IoT device access capability information, wherein the IoT device access capability information is used to indicate that the terminal can access the IoT device to the communication network.

[0260] The session establishment device of the IoT device in the embodiment of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or chip. The electronic device can be a terminal or other device other than a terminal. For example, the terminal can include but is not limited to the types of terminal 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiment of the present application.

[0261] The session establishment device of the Internet of Things device provided in the embodiment of the present application can achieve Figures 2 to 6 The various processes implemented by the method embodiment achieve the same technical effect and are not described here again to avoid repetition.

[0262] Optional, such as Figure 10As shown, an embodiment of the present application further provides a communication device 1000, including a processor 1001 and a memory 1002. The memory 1002 stores a program or instruction that can be executed on the processor 1001. For example, when the communication device 1000 is a terminal, the program or instruction, when executed by the processor 1001, implements the various steps of the embodiment 200 of the session establishment method for the IoT device described above, and can achieve the same technical effects. When the communication device 1000 is a network-side device, the program or instruction, when executed by the processor 1001, implements the various steps of the embodiments 300 and 400 of the session establishment methods for the IoT device described above, and can achieve the same technical effects. To avoid repetition, they are not further described here.

[0263] The embodiment of the present application also provides a terminal, including a processor and a communication interface, wherein the processor is used to implement the various steps of the embodiment 200 of the session establishment method for the IoT device, or the various steps performed by the UE in the embodiments 500 or 600 of the method, and the communication interface is used to communicate with an external device. This terminal embodiment corresponds to the above-mentioned terminal-side method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to this terminal embodiment and can achieve the same technical effect. Specifically, Figure 11 A schematic diagram of the hardware structure of a terminal for implementing an embodiment of the present application.

[0264] The terminal 1100 includes but is not limited to: a radio frequency unit 1101, a network module 1102, an audio output unit 1103, an input unit 1104, a sensor 1105, a display unit 1106, a user input unit 1107, an interface unit 1108, a memory 1109 and at least some of the components of the processor 1110.

[0265] Those skilled in the art will understand that the terminal 1100 may also include a power supply (such as a battery) to power each component, and the power supply may be logically connected to the processor 1110 through a power management system, thereby implementing functions such as charging, discharging, and power consumption management through the power management system. Figure 11 The terminal structure shown in the figure does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be repeated here.

[0266] It should be understood that in an embodiment of the present application, the input unit 1104 may include a graphics processing unit (GPU) 11041 and a microphone 11042, and the graphics processor 11041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 1106 may include a display panel 11061, and the display panel 11061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 1107 includes a touch panel 11071 and at least one of other input devices 11072. The touch panel 11071 is also called a touch screen. The touch panel 11071 may include two parts: a touch detection device and a touch controller. Other input devices 11072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and an operating stick, which will not be repeated here.

[0267] In the embodiment of the present application, after receiving downlink data from a network-side device, the RF unit 1101 may transmit the data to the processor 1110 for processing. Furthermore, the RF unit 1101 may send uplink data to the network-side device. Typically, the RF unit 1101 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like.

[0268] The memory 1109 can be used to store software programs or instructions and various data. The memory 1109 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 1109 may include a volatile memory or a non-volatile memory, or the memory 1109 may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM), and a direct RAM bus random access memory (DRRAM). The memory 1109 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0269] Processor 1110 may include one or more processing units. Optionally, processor 1110 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 1110.

[0270] The processor 1110 is configured to:

[0271] Acquire an IoT device group policy, wherein the IoT device group policy instructs the terminal to establish a session channel based on an IoT device group;

[0272] Based on the IoT device group policy, a target session channel is established for the target IoT device connected to the terminal.

[0273] Through the terminal provided in the embodiment of the present application, the IoT device group policy can be obtained. Based on the IoT device group policy, a session channel can be established for the IoT devices accessing the terminal in units of IoT device groups, which can effectively utilize the resources of the communication network and avoid resource waste.

[0274] The present application also provides a network-side device including a processor and a communication interface. The processor is used to implement the various steps of the above-mentioned session establishment method 300 or 400 for the IoT device, or the various steps performed by the AMF, SMF, and UDM / PCF in the above-mentioned method 500 or 600. The communication interface is used to communicate with external devices. This network-side device embodiment corresponds to the above-mentioned network-side device method embodiment. The various implementation processes and implementation methods of the above-mentioned method embodiments are applicable to this network-side device embodiment and can achieve the same technical effects.

[0275] Specifically, the embodiment of the present application also provides a network side device. Figure 12 As shown, the network side device 1200 includes: a processor 1201, a network interface 1202 and a memory 1203. The network interface 1202 is, for example, a common public radio interface (CPRI).

[0276] Specifically, the network side device 1200 of the embodiment of the present invention further includes: instructions or programs stored in the memory 1203 and executable on the processor 1201, and the processor 1201 calls the instructions or programs in the memory 1203 to execute. Figure 8 Or the method executed by each module shown in 9, and achieves the same technical effect, to avoid repetition, it will not be repeated here.

[0277] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned session establishment method 200-400 embodiments of the Internet of Things device are implemented, and the same technical effects can be achieved. To avoid repetition, they are not described here.

[0278] 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), a random access memory (RAM), a magnetic disk, or an optical disk.

[0279] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned session establishment method 200-400 embodiments of the Internet of Things device, and can achieve the same technical effects. To avoid repetition, they are not described here.

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

[0281] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-mentioned session establishment method 200-400 embodiments of the Internet of Things device, and can achieve the same technical effects. To avoid repetition, they are not described here.

[0282] An embodiment of the present application also provides a session establishment system for an IoT device, including: a terminal and a network-side device, wherein the terminal can be used to execute the steps of the session establishment method 200 of the IoT device described above, and the network-side device can be used to execute the steps of the session establishment method 300 or 400 of the IoT device described above.

[0283] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the statement "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be noted that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0284] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus the necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a computer software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for enabling a terminal (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in each embodiment of the present application.

[0285] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms without departing from the purpose of this application and the scope of protection of the claims, all of which are within the protection of this application.

Claims

1. A method for establishing a session of an Internet of Things device, characterized in that: include: The terminal obtains an IoT device group policy, wherein the IoT device group policy instructs the terminal to establish a session channel based on the IoT device group; The terminal establishes a target session channel for a target IoT device connected to the terminal based on the IoT device group policy; The IoT device group policy is used to describe that the terminal establishes a session channel for IoT devices of the same type connected to the terminal, where the type includes an IoT service type and an IoT device type.

2. The method according to claim 1, characterized in that The terminal establishes a target session channel for a target IoT device connected to the terminal based on the IoT device group policy, including: The terminal obtains a target type of the target IoT device; Based on the IoT device group policy, a target session channel is established for the target IoT device.

3. The method according to claim 2, characterized in that Establishing a target session channel corresponding to the target type for the target IoT device based on the IoT device group policy includes: If a target session channel corresponding to the target type is not established, a target session channel is established for the target Internet of Things device.

4. The method according to claim 1, wherein The IoT service type includes at least one of the following: environmental measurement, tag tracking, and material management.

5. The method according to claim 1, wherein The IoT device type includes at least one of the following: sensor, tag.

6. The method according to claim 1, characterized in that The IoT device group policy also includes establishment parameters for the target session channel.

7. The method according to claim 6, characterized in that The target session channel establishment parameters include at least one of the following: First indication information, wherein the first indication information is used to indicate that the target session channel is of IP type; Second indication information, wherein the second indication information is used to indicate that the target session channel is of Ethernet type; third indication information, wherein the third indication information is used to indicate a service continuity mode of the target session channel; Fourth indication information, wherein the fourth indication information is used to indicate that the target session channel is a control plane channel; Fifth indication information, wherein the fifth indication information is used to indicate that the target session channel is a user plane channel.

8. The method according to any one of claims 1 to 7, characterized in that The terminal obtains the IoT device group policy, including: The terminal obtains the IoT device group policy from a network-side device.

9. The method according to claim 8, characterized in that Before the terminal obtains the IoT device group policy from the network-side device, the method further includes: The terminal sends the Internet of Things device access capability information to the network side device, wherein the Internet of Things device access capability information is used to indicate that the terminal can access the Internet of Things device to the communication network.

10. The method according to claim 9, characterized in that The IoT device access capability information includes at least one of the following: The types of IoT devices supported by the terminal; The third-party identifier to which the terminal belongs; an identifier of the terminal; The transmission method of IoT device data supported by the terminal.

11. The method according to claim 10, characterized in that The method for transmitting the IoT device data includes at least one of the following: Uplink data transmission of IoT devices; Downlink data transmission of IoT devices; Data transmission from IoT devices; The terminal acts as a relay for uplink data from IoT devices; The terminal acts as a relay for downlink data from IoT devices; The terminal acts as a relay for data transmission of IoT devices; Transmit data from IoT devices in groups; The terminal acts as a relay for transmitting data of IoT devices in a group manner.

12. The method according to claim 8, characterized in that The network side equipment includes: access mobility management function AMF and / or session management function SMF.

13. A method for establishing a session of an Internet of Things device, characterized in that: include: The first network-side device obtains a first IoT device group policy, wherein the first IoT device group policy indicates establishing a session channel based on an IoT device group; The first network-side device sends a second IoT device group policy to the terminal based on the first IoT device group policy, wherein the terminal has IoT device access capability, and the second IoT device group policy instructs the terminal to establish a target session channel for a target IoT device accessing the terminal based on an IoT device group; The second IoT device group policy is used to describe: establishing a target session channel for IoT devices of the same type accessing the terminal; the type includes at least one of the following: IoT service type and IoT device type.

14. The method according to claim 13, characterized in that Before the first network-side device obtains the first IoT device group policy, the method further includes: The first network-side device obtains the Internet of Things device access capability information of the terminal, wherein the Internet of Things device access capability information is used to indicate that the Internet of Things device can access the terminal.

15. The method according to claim 13, characterized in that The IoT service type includes at least one of the following: environmental measurement, tag tracking, and material management; and / or, The IoT device type includes at least one of the following: sensor, tag.

16. The method according to claim 13, characterized in that The second IoT device group policy also includes establishment parameters for the target session channel.

17. The method according to claim 16, characterized in that The target session channel establishment parameters include at least one of the following: First indication information, wherein the first indication information is used to indicate that the target session channel is of IP type; Second indication information, wherein the second indication information is used to indicate that the target session channel is of Ethernet type; third indication information, wherein the third indication information is used to indicate a service continuity mode of the target session channel; Fourth indication information, wherein the fourth indication information is used to indicate that the target session channel is a control plane channel; Fifth indication information, wherein the fifth indication information is used to indicate that the target session channel is a user plane channel.

18. The method according to claim 14, characterized in that The first network-side device obtains the IoT device access capability information of the terminal, including: The first network-side device receives a first message from the terminal, wherein the first message carries the access capability information of the IoT device, and the first message includes one of the following: a registration message and a session establishment request message.

19. The method according to any one of claims 13 to 18, characterized in that The first network-side device obtains the first IoT device group policy, including: The first network side device receives the first IoT device group policy from a unified data management (UDM) and / or a policy control function (PCF).

20. A method for establishing a session of an Internet of Things device, characterized in that: include: The second network side device receives the IoT device group policy acquisition request from the first network side device; The second network side device sends a first IoT device group policy to the first network side device, wherein the first IoT device group policy indicates establishing a session channel based on an IoT device group; The first IoT device group policy is used to describe: establishing a session channel for IoT devices of the same type accessing the same terminal, where the type includes at least one of the following: IoT service type and IoT device type.

21. The method according to claim 20, characterized in that The IoT service type includes at least one of the following: environmental measurement, tag tracking, and material management.

22. The method according to claim 20, characterized in that The IoT device type includes at least one of the following: sensor, tag.

23. The method according to claim 20, characterized in that The IoT device group policy also includes session channel establishment parameters.

24. The method according to claim 23, wherein The session channel establishment parameters include at least one of the following: First indication information, wherein the first indication information is used to indicate that the session channel is of IP type; Second indication information, wherein the second indication information is used to indicate that the session channel is of Ethernet type; third indication information, wherein the third indication information is used to indicate a service continuity mode of the session channel; Fourth indication information, wherein the fourth indication information is used to indicate that the session channel is a control plane channel; Fifth indication information, wherein the fifth indication information is used to indicate that the session channel is a user plane channel.

25. The method according to any one of claims 20 to 24, characterized in that The IoT device group policy acquisition request includes IoT device access capability information, wherein the IoT device access capability information is used to indicate that the terminal can access the IoT device to the communication network.

26. A session establishment device for an Internet of Things device, applied to a terminal, characterized in that: The device comprises: A first acquisition module is configured to acquire an IoT device group policy, wherein the IoT device group policy instructs the terminal to establish a session channel based on an IoT device group; An establishing module, configured to establish a target session channel for a target IoT device connected to the terminal based on the IoT device group policy; The IoT device group policy is used to describe that the terminal establishes a session channel for IoT devices of the same type connected to the terminal, where the type includes an IoT service type and an IoT device type.

27. The device according to claim 26, characterized in that The establishing module establishes a target session channel for a target IoT device connected to the terminal based on the IoT device group policy, including: Obtaining a target type of the target IoT device; Based on the IoT device group policy, a target session channel is established for the target IoT device.

28. The device according to claim 27, characterized in that The establishing module establishes a target session channel corresponding to the target type for establishing the target IoT device based on the IoT device group policy, including: If a target session channel corresponding to the target type is not established, a target session channel is established for the target Internet of Things device.

29. The device according to claim 26, characterized in that The first acquisition module acquires the IoT device group policy, including: Obtain the IoT device group policy from the network side device.

30. The device according to any one of claims 26 to 29, characterized in that The device further comprises: The first sending module is used to send the Internet of Things device access capability information to the network side device, wherein the Internet of Things device access capability information is used to indicate that the terminal can access the Internet of Things device to the communication network.

31. A session establishment device for an Internet of Things device, applied to a first network side device, characterized in that: The device comprises: A second acquisition module is configured to acquire a first IoT device group policy, wherein the first IoT device group policy indicates establishing a session channel based on an IoT device group; A second sending module is configured to send a second IoT device group policy to a terminal based on the first IoT device group policy, wherein the terminal has IoT device access capability, and the second IoT device group policy instructs the terminal to establish a target session channel for a target IoT device accessing the terminal based on an IoT device group; The second IoT device group policy is used to describe: establishing a target session channel for IoT devices of the same type accessing the terminal; the type includes at least one of the following: IoT service type and IoT device type.

32. The device according to claim 31, characterized in that The second acquisition module is further used to obtain the Internet of Things device access capability information of the terminal, wherein the Internet of Things device access capability information is used to indicate that the Internet of Things device can access the terminal.

33. The device according to claim 32, characterized in that The second acquisition module acquires the IoT device access capability information of the terminal, including: A first message is received from the terminal, wherein the first message carries the access capability information of the Internet of Things device, and the first message includes one of the following: a registration message and a session establishment request message.

34. The device according to claim 31, characterized in that The second acquisition module acquires the first IoT device group policy, including: Receive the first IoT device group policy from a unified data management entity UDM or a policy control function entity PCF.

35. A session establishment device for an Internet of Things device, applied to a second network side device, characterized in that: The device comprises: A receiving module, configured to receive an IoT device group policy acquisition request from a first network-side device; A third sending module is configured to send a first IoT device group policy to the first network-side device, wherein the first IoT device group policy indicates establishing a session channel based on an IoT device group; The first IoT device group policy is used to describe: establishing a session channel for IoT devices of the same type accessing the same terminal, where the type includes at least one of the following: IoT service type and IoT device type.

36. A terminal, characterized in that: The method comprises a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the session establishment method of the Internet of Things device according to any one of claims 1 to 12 are implemented.

37. A network side device, characterized in that: The method comprises a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the session establishment method of the Internet of Things device according to any one of claims 13 to 25 are implemented.

38. 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 the processor, it implements the steps of the session establishment method of the Internet of Things device as described in any one of claims 1 to 12, or implements the steps of the session establishment method of the Internet of Things device as described in any one of claims 13 to 25.

Images