Management method and equipment

Abstract

The embodiment of the invention provides a management method and equipment, and the management method comprises the steps that first equipment releases or establishes communication resources occupied by a network and / or second equipment according to a network validity period and / or an equipment validity period. According to the embodiment of the invention, the method can achieve the management of the network and equipment, and reduces the service time delay in a management process.

Description

Management methods and equipment Technical Field

[0001] The present application relates to the field of communications, and more particularly, to a management method and device. Background Art

[0002] Related technologies typically manage network / device validity periods in a relatively simple manner. For example, when a network / device expires, the communication system resources occupied by the network / device are released and the network / device configuration information is deleted. At the beginning of the network / device validity period, communication system resources are re-requested and communication configuration is performed. This approach requires cumbersome operations and results in significant service latency.

[0003] Summary of the Invention

[0004] The embodiments of the present application provide a management method and device that can manage the validity period of a network / device.

[0005] An embodiment of the present application provides a management method, including: a first device releasing or establishing communication resources occupied by a network and / or a second device according to a network validity period and / or a device validity period.

[0006] An embodiment of the present application provides a management method, including: a third device triggering the release or establishment of communication resources occupied by the network and / or the second device according to the network validity period and / or the device validity period.

[0007] An embodiment of the present application provides a first device, including: a first management module, configured to release or establish communication resources occupied by a network and / or a second device according to a network validity period and / or a device validity period.

[0008] An embodiment of the present application provides a third device, including: a second management module, used to trigger the release or establishment of communication resources occupied by the network and / or the second device according to the network validity period and / or the device validity period.

[0009] An embodiment of the present application provides a communication device, including a processor, a memory and a transceiver, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory and control the transceiver to execute any method of the embodiment of the present application.

[0010] An embodiment of the present application provides a chip, including: a processor, configured to call and execute a computer program from a memory, so that a device equipped with the chip executes any method of the embodiment of the present application.

[0011] An embodiment of the present application provides a computer-readable storage medium for storing a computer program, which enables a computer to execute any method of the embodiment of the present application.

[0012] An embodiment of the present application provides a computer program product, including computer program instructions, which enable a computer to execute any method of the embodiment of the present application.

[0013] An embodiment of the present application provides a computer program, which enables a computer to execute any method of the embodiment of the present application.

[0014] In an embodiment of the present application, the first device releases or establishes communication resources occupied by the network and / or the second device according to the network validity period and / or the device validity period, thereby achieving management of the network / device and reducing service delays during the management process. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] FIG1 exemplarily shows a communication system 100 .

[0016] FIG2 is a schematic diagram of a PIN structure.

[0017] FIG3 is a schematic flowchart of a management method 300 according to an embodiment of the present application.

[0018] FIG4A is a schematic diagram showing a PDU session used for only one group of devices.

[0019] FIG4B is a schematic diagram of a PDU session for multiple groups of devices.

[0020] FIG5A is a schematic flowchart of AF-triggered PIN deactivation according to an embodiment of the present application.

[0021] FIG5B is a schematic flowchart of AF-triggered PIN reactivation according to an embodiment of the present application.

[0022] FIG5C is a schematic flowchart of AF-triggered PINE deactivation according to an embodiment of the present application.

[0023] FIG5D is a schematic flowchart of AF-triggered PINE reactivation according to an embodiment of the present application.

[0024] FIG5E is a schematic flowchart of PEMC-triggered PIN deactivation according to an embodiment of the present application.

[0025] FIG5F is a schematic flowchart of PEMC-triggered PIN reactivation according to an embodiment of the present application.

[0026] FIG5G is a schematic flowchart of PEMC-triggered PINE deactivation according to an embodiment of the present application.

[0027] FIG5H is a schematic flowchart of PEMC-triggered PINE reactivation according to an embodiment of the present application.

[0028] FIG5I is a schematic flowchart of PEGC-triggered PIN deactivation according to an embodiment of the present application.

[0029] FIG5J is a schematic flowchart of PEGC-triggered PIN reactivation according to an embodiment of the present application.

[0030] FIG5K is a schematic flowchart of PEGC-triggered PINE deactivation according to an embodiment of the present application.

[0031] FIG5L is a schematic flowchart of PEGC-triggered PINE reactivation according to an embodiment of the present application.

[0032] FIG6 is a schematic flowchart of a management method 600 according to an embodiment of the present application.

[0033] FIG7 is a schematic block diagram of a first device 700 according to an embodiment of the present application.

[0034] FIG8 is a schematic block diagram of a first device 800 according to an embodiment of the present application.

[0035] FIG9 is a schematic block diagram of a third device 900 according to an embodiment of the present application.

[0036] FIG10 is a schematic structural diagram of a communication device 1000 according to an embodiment of the present application.

[0037] FIG11 is a schematic structural diagram of a chip 1100 according to an embodiment of the present application. DETAILED DESCRIPTION

[0038] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0039] It should be noted that the terms "first," "second," and the like in the description and claims of the embodiments of this application and the accompanying drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or precedence. The objects described by the terms "first" and "second" may be the same or different.

[0040] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-U) system, NR on unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (Wireless Fidelity) system. Fidelity, WiFi), fifth-generation communication (5th-Generation, 5G) system or other communication systems, etc.

[0041] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, or vehicle-to-everything (V2X) communication, etc. The embodiments of the present application can also be applied to these communication systems.

[0042] In one embodiment, the communication system in the embodiment of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, and a standalone (SA) networking scenario.

[0043] In one embodiment, the communication system in the embodiment of the present application can be applied to an unlicensed spectrum, wherein the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to an authorized spectrum, wherein the authorized spectrum can also be considered as an unshared spectrum.

[0044] The embodiments of the present application describe various embodiments in conjunction with network devices and terminal devices, wherein the terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.

[0045] The terminal device can be a station (STAION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a next-generation communication system such as an NR network, or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.

[0046] In an embodiment of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons and satellites, etc.).

[0047] In an embodiment of the present application, the terminal device may be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc.

[0048] As an example and not a limitation, in the embodiment of the present application, the terminal device may also be a wearable device. Wearable devices may also be called wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are fully functional, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0049] In an embodiment of the present application, the network device may be a device for communicating with a mobile device. The network device may be an access point (AP) in WLAN, a base station (BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and a network device (gNB) in an NR network, or a network device in a future evolved PLMN network or a network device in an NTN network, etc.

[0050] As an example and not a limitation, in an embodiment of the present application, the network device may have a mobile feature, for example, the network device may be a mobile device. Alternatively, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. Optionally, the network device may also be a base station set up in a location such as land or water.

[0051] In an embodiment of the present application, the network device can provide services for a cell, and the terminal device communicates with the network device through the transmission resources used by the cell (for example, frequency domain resources, or spectrum resources). The cell can be a cell corresponding to the network device (for example, a base station). The cell can belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

[0052] FIG1 exemplarily illustrates a communication system 100. The communication system includes a network device 110 and two terminal devices 120. In one embodiment, the communication system 100 may include multiple network devices 110, and each network device 110 may include a different number of terminal devices 120 within its coverage area, which is not limited in this embodiment of the present application.

[0053] In one embodiment, the communication system 100 may further include other network entities such as a Mobility Management Entity (MME) and an Access and Mobility Management Function (AMF), which is not limited in this embodiment of the present application.

[0054] Among them, the network equipment may include access network equipment and core network equipment. That is, the wireless communication system also includes multiple core networks for communicating with the access network equipment. The access network equipment can be an evolutionary base station (evolutional node B, abbreviated as eNB or e-NodeB) macro base station, micro base station (also called "small base station"), pico base station, access point (AP), transmission point (TP) or new generation base station (new generation Node B, gNodeB), etc. in a long-term evolution (LTE) system, a next-generation (mobile communication system) (next radio, NR) system or an authorized auxiliary access long-term evolution (LAA-LTE) system.

[0055] It should be understood that in the embodiments of the present application, a device having a communication function in a network / system may be referred to as a communication device. Taking the communication system shown in Figure 1 as an example, the communication device may include a network device and a terminal device having a communication function. The network device and the terminal device may be specific devices in the embodiments of the present application and will not be described in detail here. The communication device may also include other devices in the communication system, such as a network controller, a mobility management entity, and other network entities, which are not limited in the embodiments of the present application.

[0056] It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and / or" is simply a description of an association between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " generally indicates that the related objects are in an "or" relationship.

[0057] It should be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B.

[0058] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and being indicated, configuration and being configured, etc.

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

[0060] IoT devices can be categorized into wearable devices (e.g., cameras, earphones, watches, headphones, health monitors), home lifestyle devices (e.g., smart lights, cameras, thermostats, door sensors, voice assistants, speakers, refrigerators, washing machines, lawn mowers, robots), and office or factory equipment (e.g., printers, meters, sensors). Users can use these IoT devices to create (e.g., plan, change topology) personal networks in their homes, offices, factories, or around their bodies.

[0061] Currently, with the exception of some wearable devices, other types of IoT devices can only access the internet through relay devices and gateways or mobile networks through mobile phones. In both cases, the core network is unaware that the IoT device is connected to the mobile network. However, to fully utilize the 5G system to assist in the management and service support of IoT devices, enabling the 5G system to participate in the Personal IoT is essential. Figure 2 is a schematic diagram of the PIN structure. As shown in Figure 2, a user-created Personal IoT Network (PIN) consists of a group of Personal IoT Elements / Personal IoT Devices (PINEs), which can be configured and managed. These IoT devices can communicate with each other directly or through PIN elements with gateway capabilities, or communicate with the 5G network through at least one PEGC and are managed by at least one PIN element with management capabilities. An IoT device can be a UE capable of accessing the 5G system or a non-3GPP device that can only communicate via WiFi, Bluetooth, or other methods. A PINE that can provide other PINEs with connectivity to the 5G network or relay communication between PINEs is called an IoT device with gateway capability (PEGC). The PINE that can manage PINs is called an IoT device with management capability (PEMC, PIN Element with Management Capability).

[0062] After a PIN is created, the PEMC can add a PINE or PEGC to the PIN, remove a PINE or PEGC from the PIN, or associate a PINE with a PEGC that has already joined the network. In addition, the PEMC can set the duration of the PIN network by starting a timer. The duration of the PIN network depends on the operator's policy or third-party policy. At the end of the PIN duration, the PEMC will deactivate the PIN, delete all its PIN-related repositories, and broadcast information about the PIN deactivation to the PIN device. Once the PIN is deactivated, the PEMC will notify the 5GC and the PINE in the network that the device has been deactivated.

[0063] The management method proposed in the embodiment of the present application can be applied to PIN networks, or to other networks such as local area networks. In the related technical solutions, the management granularity of the PIN validity period is relatively coarse, and discrete validity period configuration is not supported. When the validity period is multiple discrete time periods, for example, 2:00-3:00 every day. According to the existing technology, the corresponding PIN network will be deactivated after the end of the first time period, and the stored PIN configuration information will be released. When the second validity period arrives, it is necessary to re-initiate the PIN network establishment process and PIN communication configuration, such as PINE ID allocation and address allocation, PIN parameter configuration, traffic routing management and other tedious operations. This greatly increases service latency and affects user experience. In addition, the existing technology is not clear about how to support PIN validity period management, and does not involve detailed descriptions of processes such as validity period execution.

[0064] The management method proposed in the embodiment of the present application manages the network / device based on the validity period. Specifically, the embodiment of the present application divides the validity period into two dimensions: network validity period and device validity period, and performs management operations such as establishment / release, activation / deactivation, etc. on the network and device based on the validity period.

[0065] In some examples, the network validity period represents the active time of a network composed of a group of devices. When the network validity period ends, the network is released or switched to an inactive state. Specifically, if the network validity period is a fixed duration, the network is released when the network validity period ends, for example, the 5G system (5GS) resources allocated to the network are released and the configuration information stored in the Unified Data Management (UDM) is deleted; if the validity period is a discontinuous period, the network is switched to inactive when the network validity period ends, for example, the 5GS resources allocated to the network are released, and the stored network configuration information is retained until the next validity period arrives to reactivate the network.

[0066] In some examples, the device lifetime represents the duration of a device's activity on the network. When the device lifetime expires, the device is removed from the network or switched to an inactive state. Specifically, if the device lifetime is a fixed duration, the device is removed from the network when the lifetime expires. If the device lifetime is a discrete period, the device is switched to an inactive state when the lifetime expires, releasing the network resources allocated to the device while retaining the device's configuration information on the network.

[0067] The network validity period and / or device validity period parameter configuration can be statically configured in the device or in 5G core network elements such as UDM, or dynamically configured by the application function (AF). When the validity period information is configured in the AF, the AF can trigger PIN / PINE deactivation and reactivation based on the expiration of the validity period timer. When the validity period information is configured in the PEMC / PEGC of the IoT device, the PEMC triggers the PIN / PINE deactivation and reactivation after the validity period timer expires.

[0068] FIG3 is a schematic flow chart of a management method 300 according to an embodiment of the present application, which can be applied to the system shown in FIG1 or 2, but is not limited thereto. The method includes at least part of the following contents.

[0069] S310: The first device releases or establishes communication resources occupied by the network and / or the second device according to the network validity period and / or the device validity period.

[0070] In the following, the management method proposed in the embodiment of the present application is applied to PIN as an example. The management method proposed in the embodiment of the present application is not only applicable to PIN, but also to other networks and devices that need to use 5GS resources.

[0071] In some embodiments, the first device comprises a SMF or a PEGC.

[0072] In some embodiments, the third device comprises an AF or a PEMC.

[0073] In some embodiments, the network includes a PIN and the second device includes a PINE. Accordingly, the network validity period may include a PIN validity period, which is used to manage the PIN, such as releasing or establishing communication resources occupied by the PIN based on the PIN validity period; and the device validity period may include a PINE validity period, which is used to manage the PINE, such as releasing or establishing communication resources occupied by the PINE based on the PINE validity period.

[0074] (1) The first device releases the communication resources occupied by the network according to the network validity period:

[0075] In related technologies, a PDU session can be used for only one group of devices (e.g., one PIN) or for multiple groups of devices (e.g., multiple PINs), as shown in Figures 4A and 4B. Regarding the above two situations, in some embodiments, the first device releases the communication resources occupied by the network according to the network validity period, which may include:

[0076] At the end of the network validity period, the first device initiates a user plane deactivation process, a PDU session release process, or a PDU session modification process to release communication resources occupied by the network.

[0077] For example, in the case where a PDU session is only used for one PIN, the first device can initiate a user plane deactivation process to release the radio resources and / or channels of the PDU session that carries the service of the network. In this case, the first device can be a network-side device, such as an SMF.

[0078] For another example, in the case where a PDU session is only used for one PIN, the first device initiates a PDU session release process to release user plane resources allocated to the network.

[0079] Alternatively, in the case where one PDU session is used for multiple PINs, the first device initiates a PDU session modification process to delete the Quality of Service (QoS) flow corresponding to the network in the PDU session.

[0080] If the network validity period is configured in the first device, the first device can actively initiate a user plane deactivation process, a PDU session release process, or a PDU session modification process at the end of the network validity period to release the communication resources occupied by the network. If the network validity period is configured in other devices (such as a third device), the first device can initiate a user plane deactivation process, a PDU session release process, or a PDU session modification process based on the triggering of other devices (such as the third device) to release the communication resources occupied by the network. In the case where the first network device is an SMF, the third network device can be an AF or a PEMC. In the case where the first network device is a PEMC, the third network device can be an AF. When the first device is a PEGC, the third device can be a PEMC.

[0081] In some embodiments, the first device receives a network deactivation request, which is sent by a third device at the end of a network validity period of the network. For example, the third device stores a network validity period configuration, and at the end of the network validity period of the network, the third device sends the network deactivation request to the first device.

[0082] Exemplarily, the network deactivation request may carry at least one of the following:

[0083] Network deactivation indication;

[0084] the network's identity;

[0085] The identification of the management device in the network;

[0086] The identifier of the gateway device in the network;

[0087] The PDU session identifier and QoS flow identifier that carry the network service flow.

[0088] Taking the network as PIN as an example, the management device in the network may be PEMC, and the gateway device in the network may be PEGC.

[0089] After receiving the network deactivation request, the first device may release the communication resources occupied by the network.

[0090] In some implementations, the first device may release communication resources occupied by the network based on configuration information of the network.

[0091] Exemplarily, the first device may obtain network configuration information from the fourth device, for example, in the following manner:

[0092] The first device sends a network configuration query request to the fourth device;

[0093] The first device receives network configuration information from the fourth device.

[0094] The network configuration query request may carry identification information of the network, such as a PIN ID.

[0095] The fourth device may include a UDM.

[0096] The network configuration information may include at least one of the following:

[0097] Network topology information;

[0098] the network's identity;

[0099] Identification of management devices in the network;

[0100] Identification of devices in the network;

[0101] The PDU session identifier and / or QoS flow identifier that carries the network service flow.

[0102] The network topology information may include at least one of the following:

[0103] The relationship between devices in the network and management devices;

[0104] The relationship between devices and gateway devices in the network;

[0105] The relationship between a device and other devices in the network.

[0106] Taking PIN as an example, the topology information of the PIN may include the association relationship between the PINE in the PIN and the PEMC, the association relationship between the PINE in the PIN and the PEGC, and the association relationship between the PINE in the PIN and other PINEs.

[0107] Based on the configuration information of the network, the first device can release the communication resources occupied by the network without deleting the configuration information of the network. For example, there is no need to delete the PIN configuration information stored in the network and in the PIN management entity (such as PEMC and / or AF). This improves the utilization of communication resources while avoiding repeated network establishment and configuration of the network and the device during reactivation, as well as tedious operations such as PINE ID allocation and address allocation, PIN parameter configuration, and traffic routing management. Especially for scenarios with discontinuous validity periods, it can reduce the network reconstruction and device activation delays, speed up the response of the network and the device to continue to provide services, thereby improving the user experience and reducing the signaling load caused by repeated network establishment / release and repeated addition and deletion of devices to a certain extent.

[0108] The PEGC or PEMC may release communication resources such as WiFi and Bluetooth allocated to the network (such as a PIN), and send a notification to the PINE in the PIN to inform that the PIN in which it is located has been deactivated.

[0109] (2) The first device establishes (or reconstructs) the communication resources occupied by the network according to the network validity period:

[0110] In some implementations, the first device establishing communication resources occupied by the network according to the network validity period may include:

[0111] At the beginning of the network validity period, the first device initiates a service request process, a PDU session establishment process, or a PDU session modification process to establish (or re-establish) the communication resources occupied by the network.

[0112] For example, in the case where a PDU session is only used for one PIN, the first device can initiate a service request process to activate the PDU session established for the network; or, the first device can initiate a PDU session establishment process to establish a PDU session for the network.

[0113] For another example, in the case where one PDU session is used for multiple PINs, the first device initiates a PDU session modification process to establish a QoS flow corresponding to the network in the PDU session.

[0114] If the network validity period is configured in the first device, the first device can actively initiate a service request process, a PDU session establishment process, or a PDU session modification process at the beginning of the network validity period to establish (or rebuild) the communication resources occupied by the network. If the network validity period is configured in other devices (such as a third device), the first device can initiate a service request process, a PDU session establishment process, or a PDU session modification process based on the triggering of other devices (such as a third device) to establish (or rebuild) the communication resources occupied by the network. In the case where the first network device is an SMF, the third network device can be an AF or a PEMC. In the case where the first network device is a PEMC, the third network device can be an AF. When the first device is a PEGC, the third device can be a PEMC.

[0115] In some embodiments, the first device receives a network activation (or reactivation) request, which is sent by a third device at the beginning of a network validity period for the network. For example, the third device stores a network validity period configuration, and at the beginning of the network validity period, the third device sends the network activation request to the first device.

[0116] Exemplarily, the network activation request may carry at least one of the following:

[0117] Network activation instructions;

[0118] the network's identity;

[0119] The identification of the management device in the network;

[0120] The identifier of the gateway device in the network;

[0121] The PDU session identifier and / or QoS flow identifier that carries the network service flow.

[0122] Taking the network as PIN as an example, the management device in the network may be PEMC, and the gateway device in the network may be PEGC.

[0123] After receiving the network deactivation request, the first device may establish (or re-establish) the communication resources occupied by the network.

[0124] In some implementations, the first device may establish communication resources occupied by the network based on configuration information of the network.

[0125] Exemplarily, the first device may obtain network configuration information from the fourth device, for example, in the following manner:

[0126] The first device sends a network configuration query request to the fourth device;

[0127] The first device receives network configuration information from the fourth device.

[0128] The network configuration query request may carry identification information of the network, such as a PIN ID.

[0129] The fourth device may include a UDM.

[0130] The network configuration information may include at least one of the following:

[0131] Network topology information;

[0132] the network's identity;

[0133] Identification of management devices in the network;

[0134] Identification of devices in the network;

[0135] The PDU session identifier and / or QoS flow identifier that carries the network service flow.

[0136] The network topology information may include at least one of the following:

[0137] The relationship between devices in the network and management devices;

[0138] The relationship between devices and gateway devices in the network;

[0139] The relationship between a device and other devices in the network.

[0140] Taking PIN as an example, the topology information of the PIN may include the association relationship between the PINE in the PIN and the PEMC, the association relationship between the PINE in the PIN and the PEGC, and the association relationship between the PINE in the PIN and other PINEs.

[0141] Based on the configuration information of the network, the first device can establish (or rebuild) the communication resources occupied by the network without reconfiguring the configuration information of the network, for example, without reconfiguring the PIN configuration information. This improves the utilization of communication resources while avoiding repeated network establishment and configuration of the network and the device during reactivation, as well as tedious operations such as PINE ID allocation and address allocation, PIN parameter configuration, and traffic routing management. In particular, for scenarios with discontinuous validity periods, it can reduce network reconstruction and device activation delays, speed up the response of the network and the device to continue providing services, thereby improving user experience and, to a certain extent, reducing the signaling load caused by repeated network establishment / release and repeated addition and deletion of devices.

[0142] The PEGC or PEMC can reallocate communication resources such as WiFi and Bluetooth to the PINE in the network (such as the PIN); and send a notification to the PINE in the PIN to inform that the PIN in which it is located has been activated.

[0143] (3) The first device releases the communication resources occupied by the second device according to the network validity period:

[0144] In some implementations, the first device releasing the communication resources occupied by the second device according to the network validity period may include:

[0145] When the validity period of the second device ends, the first device initiates a PDU session modification process to release the communication resources occupied by the second device.

[0146] For example, the first device initiates a PDU session modification process to delete the QoS flow corresponding to the second device in the PDU session.

[0147] If the device validity period is configured in the first device, the first device can actively initiate a PDU session modification process at the end of the device validity period to delete the QoS flow corresponding to the second device in the PDU session. If the device validity period is configured in other devices (such as a third device), the first device can initiate a PDU session modification process based on the triggering of other devices (such as the third device) to delete the QoS flow corresponding to the second device in the PDU session. In the case where the first network device is an SMF, the third network device can be an AF or a PEMC. In the case where the first network device is a PEMC, the third network device can be an AF. When the first device is a PEGC, the third device can be a PEMC.

[0148] In some embodiments, the first device receives a device deactivation request, which is sent by the third device at the end of a device validity period of the second device.

[0149] For example, the third device stores the network validity period configuration, and when the device validity period of the second device ends, the third device sends a device deactivation request to the first device.

[0150] Exemplarily, the device deactivation request carries at least one of the following:

[0151] Device deactivation indication;

[0152] an identifier of the second device;

[0153] an identifier of the network to which the second device belongs;

[0154] an identifier of a management device associated with the second device;

[0155] an identifier of a gateway device associated with the second device;

[0156] The PDU session identifier and / or QoS flow identifier that carries the service flow of the second device.

[0157] Taking the network as PIN as an example, the second device is PINE, the management device associated with the second device may be PEMC associated with the PINE, and the gateway device associated with the second device may be PEGC associated with the PINE.

[0158] After receiving the device deactivation request, the first device may release the communication resources occupied by the second device.

[0159] In some implementations, the first device may release communication resources occupied by the second device based on the configuration information of the second device.

[0160] Exemplarily, the first device may obtain the configuration information of the second device from the fourth device. For example, the acquisition is performed in the following manner:

[0161] The first device sends a device configuration query request to the fourth device;

[0162] The first device receives configuration information of the second device from the fourth device.

[0163] The fourth device may include a UDM.

[0164] In some implementations, the device configuration query request carries at least one of the following:

[0165] an identifier of the second device;

[0166] an identifier of the network to which the second device belongs;

[0167] an identifier of a management device associated with the second device;

[0168] An identifier of a gateway device associated with the second device.

[0169] Taking PIN as an example, the device configuration query request may carry at least one of the PINE ID, the PIN ID of the PIN to which the PINE belongs, the ID of the PEMC associated with the PINE, and the ID of the PEGC associated with the PINE.

[0170] In some embodiments, the configuration information of the second device includes at least one of the following:

[0171] an identifier of the second device;

[0172] an identifier of a management device associated with the second device;

[0173] an identifier of a gateway device associated with the second device;

[0174] The PDU session identifier and / or QoS flow identifier that carries the service flow of the second device.

[0175] Taking PIN as an example, the configuration information of the second device may include at least one of the PINE ID, the ID of the PEMC associated with the PINE, the ID of the PEGC associated with the PINE, the PDU session identifier carrying the PINE service flow, and / or the QoS flow identifier.

[0176] Based on the configuration information of the second device, the first device can release the communication resources occupied by the second device without having to reconfigure the configuration information of the second device, for example, without having to reconfigure the PINE configuration information. This improves the utilization of communication resources while avoiding repeated network establishment and configuration, as well as PINE communication configuration, such as PINE ID allocation and address allocation, PIN parameter configuration, traffic routing management, and other tedious operations when the device is reactivated. In particular, for scenarios with discontinuous validity periods, it can reduce network reconstruction and device activation delays, speed up the response of the network and devices to continue providing services, thereby improving user experience and, to a certain extent, reducing the signaling load caused by repeated network establishment / release and repeated addition and deletion of devices.

[0177] The PEGC or PEMC may release the communication resources such as WiFi and Bluetooth allocated to the second device (such as PINE), and notify the associated target PINE that it has been switched to a deactivated state in the target PIN.

[0178] (4) The first device establishes (or re-establishes) the communication resources occupied by the second device according to the network validity period:

[0179] In some implementations, the first device establishing, based on the network validity period, communication resources occupied by the second device may include:

[0180] When the validity period of the second device begins, the first device initiates a PDU session modification process to establish communication resources occupied by the second device.

[0181] For example, the first device initiates a PDU session modification process to establish a QoS flow corresponding to the second device in the PDU session.

[0182] If the device validity period is configured in the first device, the first device can actively initiate the PDU session modification process at the beginning of the device validity period to establish the QoS flow corresponding to the second device in the PDU session. If the device validity period is configured in other devices (such as a third device), the first device can initiate the PDU session modification process based on the triggering of other devices (such as the third device) to establish the QoS flow corresponding to the second device in the PDU session. In the case where the first network device is an SMF, the third network device can be an AF or a PEMC. In the case where the first network device is a PEMC, the third network device can be an AF. When the first device is a PEGC, the third device can be a PEMC.

[0183] In some implementations, the first device receives a device activation request sent by a third device at the beginning of a device validity period of the second device.

[0184] For example, the third device stores the network validity period configuration, and when the device validity period of the second device begins, the third device sends a device activation request to the first device.

[0185] Illustratively, the device activation request carries at least one of the following:

[0186] Device activation instructions;

[0187] an identifier of the second device;

[0188] an identifier of the network to which the second device belongs;

[0189] an identifier of a management device associated with the second device;

[0190] an identifier of a gateway device associated with the second device;

[0191] The PDU session identifier and / or QoS flow identifier that carries the service flow of the second device.

[0192] Taking the network as PIN as an example, the second device is PINE, the management device associated with the second device may be PEMC associated with the PINE, and the gateway device associated with the second device may be PEGC associated with the PINE.

[0193] After receiving the device activation request, the first device may establish the communication resources occupied by the second device.

[0194] In some implementations, the first device may establish communication resources occupied by the second device based on configuration information of the second device.

[0195] Exemplarily, the first device may obtain the configuration information of the second device from the fourth device. For example, the acquisition is performed in the following manner:

[0196] The first device sends a device configuration query request to the fourth device;

[0197] The first device receives configuration information of the second device from the fourth device.

[0198] The fourth device may include a UDM.

[0199] In some implementations, the device configuration query request carries at least one of the following:

[0200] an identifier of the second device;

[0201] an identifier of the network to which the second device belongs;

[0202] an identifier of a management device associated with the second device;

[0203] An identifier of a gateway device associated with the second device.

[0204] Taking PIN as an example, the device configuration query request may carry at least one of the PINE ID, the PIN ID of the PIN to which the PINE belongs, the ID of the PEMC associated with the PINE, and the ID of the PEGC associated with the PINE.

[0205] In some embodiments, the configuration information of the second device includes at least one of the following:

[0206] an identifier of the second device;

[0207] an identifier of a management device associated with the second device;

[0208] an identifier of a gateway device associated with the second device;

[0209] The PDU session identifier and / or QoS flow identifier that carries the service flow of the second device.

[0210] Taking PIN as an example, the configuration information of the second device may include at least one of the PINE ID, the ID of the PEMC associated with the PINE, the ID of the PEGC associated with the PINE, the PDU session identifier carrying the PINE service flow, and / or the QoS flow identifier.

[0211] Based on the configuration information of the second device, the first device can establish (or rebuild) the communication resources occupied by the second device without reconfiguring the configuration information of the second device, for example, without reconfiguring the PINE configuration information. This improves the utilization of communication resources while avoiding repeated network establishment and configuration when the device is reactivated, as well as tedious operations such as PINE communication configuration, such as PINE ID allocation and address allocation, PIN parameter configuration, and traffic routing management. In particular, for scenarios with discontinuous validity periods, it can reduce network reconstruction and device activation delays, speed up the response of the network and devices to continue to provide services, thereby improving user experience and, to a certain extent, reducing the signaling load caused by repeated network establishment / release and repeated addition and deletion of devices.

[0212] The PEGC or PEMC may reallocate communication resources such as WiFi and Bluetooth to the second device (eg, PINE), and notify the associated target PINE that it has been switched to an active state in the target PIN.

[0213] In addition to the above four methods, the first device releases or establishes the communication resources occupied by the network and / or the second device according to the network validity period and / or the device validity period. For example, the first device releases the communication resources occupied by the network at the end of the network validity period; and releases the communication resources occupied by the second device at the end of the device validity period. For another example, the first device releases the communication resources occupied by the network at the end of the network validity period; and establishes the communication resources occupied by the second device at the beginning of the device validity period. For another example, the first device establishes the communication resources occupied by the network at the beginning of the network validity period; and releases the communication resources occupied by the second device at the end of the device validity period. For another example, the first device establishes the communication resources occupied by the network at the beginning of the network validity period; and establishes the communication resources occupied by the second device at the beginning of the device validity period.

[0214] For example, the network is a PIN and the second device is a PINE. The first device may release the communication resources occupied by PIN 1 at the end of the validity period of PIN 1, and release the communication resources occupied by PINE 1 at the end of the validity period of PINE 1. Alternatively, the first device may release the communication resources occupied by PIN 1 at the end of the validity period of PIN 1, and establish the communication resources occupied by PINE 1 at the beginning of the validity period of PINE 1. Alternatively, the first device may establish the communication resources occupied by PIN 1 at the beginning of the validity period of PIN 1, and release the communication resources occupied by PINE 1 at the end of the validity period of PINE 1. Alternatively, the first device may establish the communication resources occupied by PIN 1 at the beginning of the validity period of PIN 1, and establish the communication resources occupied by PINE 1 at the beginning of the validity period of PINE 1. PINE 1 in the above example may not be PIN 1.

[0215] The following describes specific implementation methods in conjunction with the accompanying drawings.

[0216] Example 1: AF-triggered PIN deactivation

[0217] As shown in Figure 5A, the AF can trigger the deactivation of the PIN according to the validity period setting, releasing the 5GS resources allocated to the PIN. The specific steps are as follows:

[0218] 1. When the PIN is valid for an expiration date, the AF sends a PIN deactivation request to the PCF via the Network Exposure Function (NEF). The message includes a PIN deactivation instruction and a PIN ID.

[0219] 2. PCF forwards the PIN deactivation request to SMF, which carries the PIN deactivation instruction and PIN ID.

[0220] 3.SMF initiates a PIN configuration information query request to UDM, and the message carries the PIN ID.

[0221] 4. The UDM returns the PIN configuration information to the SMF. The PIN configuration information may include the PIN network topology information, the PIN ID, the PEGC ID in the PIN, the PEMC ID in the PIN, the PDU session ID and / or QoS ID that carries the PIN service flow. The PIN network topology information may include the association between each PINE in the PIN and the PEGC, the association between each PINE in the PIN and the PEMC, and the association between different PINEs in the PIN.

[0222] 5. When a PDU session is used for only one PIN (as shown in Figure 4A), the SMF will initiate a user plane deactivation process to release the radio resources (such as DRBs) and N3 tunnels of the PDU session that carries the PIN service established by all PEGCs and PEMCs in the PIN network. When a PDU session is used for multiple PINs (as shown in Figure 4B), the SMF will initiate a PDU session modification process to delete the QoS flow corresponding to the target PIN. In addition, the above user plane deactivation process and PDU session modification process will additionally carry a PIN deactivation indication and a PIN ID.

[0223] 6. PEGC releases the WiFi, Bluetooth and other communication resources allocated to the target PIN and notifies the associated PINE belonging to the target PIN that the target PIN has been deactivated.

[0224] Example 2: AF-triggered PIN activation (reactivation)

[0225] As shown in Figure 5B, the AF can trigger the reactivation of the PIN according to the validity period setting, re-allocate 5GS resources to the PIN, and restore the communication resources between the PINE and the PEGC. The specific steps are as follows:

[0226] 1. When the PIN validity period begins, the AF sends a PIN reactivation request to the PCF through the NEF. The message includes a PIN reactivation indication and a PIN ID.

[0227] 2. PCF forwards the PIN reactivation request to SMF, which carries the PIN reactivation indication and PIN ID.

[0228] 3.SMF initiates a PIN configuration information query request to UDM, and the message carries the PIN ID.

[0229] 4. The UDM returns the PIN configuration information to the SMF. The PIN configuration information may include the PIN network topology information, the PIN ID, the PEGC ID in the PIN, the PEMC ID in the PIN, the PDU session ID and / or QoS ID that carries the PIN service flow. The PIN network topology information may include the association between each PINE in the PIN and the PEGC, the association between each PINE in the PIN and the PEMC, and the association between different PINEs in the PIN.

[0230] 5. When a PDU session is used for only one PIN (as shown in Figure 4A), the SMF initiates a service request process to reactivate the PDU session in the PIN network based on the PEGC ID, PIN ID, PDU session ID, and other information obtained in step 4. When a PDU session is used for multiple PINs (as shown in Figure 4B), the SMF will initiate a PDU session modification process to reestablish the QoS flow based on the traffic routing relationship between the PINE and the PEGC in the target PIN. In addition, the above service request process and PDU session modification process can additionally carry a PIN reactivation indication and a PIN ID.

[0231] 6. PEGC re-allocates WiFi, Bluetooth and other communication resources to the PINE in the target PIN, and notifies the associated target PIN where the PINE belonging to the target PIN is located that it has been reactivated.

[0232] Example 3: Deactivation of PINE triggered by AF

[0233] As shown in Figure 5C, the AF can trigger the deactivation of the PINE according to the validity period setting, releasing the 5GS resources allocated to the PINE. The specific steps are as follows:

[0234] 1. When the PINE validity period expires, the AF sends a PINE deactivation request to the PCF via the Network Exposure Function (NEF). The message includes at least one of the PINE deactivation indication, PIN ID, PINE ID, PEGC ID associated with the target PINE, and PEMC ID associated with the target PINE.

[0235] 2. The PCF forwards the PINE deactivation request to the SMF. The message carries at least one of the PINE deactivation indication, PIN ID, PINE ID, PEGC ID associated with the target PINE, and PEMC ID associated with the target PINE.

[0236] 3.SMF initiates a PINE configuration information query request to UDM. The message carries the PIN ID, PINE ID, and the PEGC ID associated with the target PINE.

[0237] 4. UDM returns PINE configuration information to SMF, including the PEGC ID associated with the target PINE in the target PIN, as well as the PDU session ID and QoS flow ID (QFI) established by PEGC to carry the target PINE service traffic.

[0238] 5. The SMF will initiate the PDU session modification process and release the QoS flow corresponding to the target PINE based on the PEGC ID, PINE ID, PDU session ID, QFI and other information obtained in step 4. The above PDU session modification process will additionally carry the PINE deactivation indication, PIN ID and PINE ID.

[0239] 6. PEGC releases the communication resources such as WiFi and Bluetooth allocated to the target PINE, and notifies the associated target PINE that it has been switched to the deactivated state in the target PINE.

[0240] Example 4: AF-triggered activation (reactivation) of PINE

[0241] As shown in Figure 5D, the AF can trigger the activation of the PINE according to the validity period setting and reallocate 5GS resources to the PINE. The specific steps are as follows:

[0242] 1. The AF sends a PINE activation request to the PCF through the NEF. The message includes at least one of a PINE activation indication, a PIN ID, a PINE ID, a PEGC ID associated with the target PINE, and a PEMC ID associated with the target PINE.

[0243] 2. The PCF forwards the PINE activation request to the SMF. The message carries at least one of the PINE activation indication, PIN ID, PINE ID, PEGC ID associated with the target PINE, and PEMC ID associated with the target PINE.

[0244] 3. The SMF initiates a PIN configuration information query request to the UDM. The message carries at least one of the PIN ID, PINE ID, PEGC ID associated with the target PINE, and PEMC ID associated with the target PINE.

[0245] 4. UDM returns PIN configuration information to SMF, including the PEGC ID associated with the target PINE in the target PIN, as well as the PDU session ID and QoS flow ID (QFI) established by PEGC to carry the target PINE service traffic.

[0246] 5. The SMF will initiate a PDU session modification process to re-establish the QoS flow based on the traffic routing relationship between the PINE and PEGC in the target PIN. In addition, the above PDU session modification process will additionally carry the PINE activation indication, PIN ID, and PINE ID.

[0247] 6. PEGC reallocates the WiFi, Bluetooth and other communication resources to the target PINE and notifies the associated target PINE that it has been switched to the active state in the target PIN.

[0248] Example 5: PEMC-triggered PIN deactivation

[0249] As shown in Figure 5E, when PEMC and PEGC are deployed in different locations, PEMC can trigger the deactivation of the PIN through the network side according to the validity period setting, releasing the 5GS resources allocated to the PIN. The specific steps are as follows:

[0250] 1. When the PIN expires, the PEMC sends a PIN deactivation request to the AMF through the Radio Access Network (RAN). The message includes a PIN deactivation indication and a PIN ID.

[0251] 2.AMF forwards the PIN deactivation request to SMF, which carries the PIN deactivation indication and PIN ID.

[0252] 3.SMF initiates a PIN configuration information query request to UDM, and the message carries the PIN ID.

[0253] 4. The UDM returns the PIN configuration information to the SMF. The PIN configuration information may include the PIN network topology information, the PIN ID, the PEGC ID in the PIN, the PEMC ID in the PIN, the PDU session ID and / or QoS ID that carries the PIN service flow. The PIN network topology information may include the association between each PINE in the PIN and the PEGC, the association between each PINE in the PIN and the PEMC, and the association between different PINEs in the PIN.

[0254] 5. When a PDU session is used for only one PIN (as shown in Figure 4A), the SMF will initiate a user plane deactivation process to release the radio resources (such as DRBs) and N3 tunnels of the PDU session that carries the PIN service established by all PEGCs and PEMCs in the PIN network. When a PDU session is used for multiple PINs (as shown in Figure 4B), the SMF will initiate a PDU session modification process to delete the QoS flow corresponding to the target PIN. In addition, the above user plane deactivation process and PDU session modification process will additionally carry a PIN deactivation indication and a PIN ID.

[0255] 6. PEGC releases the WiFi, Bluetooth and other communication resources allocated to the target PIN and notifies the associated PINE belonging to the target PIN that the target PIN has been deactivated.

[0256] Example 6: PEMC-triggered PIN reactivation

[0257] As shown in Figure 5F, when PEMC and PEGC are deployed in different locations, PEMC can trigger the reactivation of the PIN through the network side according to the validity period setting, re-allocate 5GS resources to the PIN, and restore the communication resources between the PIN and PEGC. The specific steps are as follows:

[0258] 1. PEMC sends a PIN activation request to AMF via RAN. The message includes a PIN activation indication and a PIN ID.

[0259] 2.AMF forwards the PIN activation request to SMF, which carries the PIN activation indication and PIN ID.

[0260] 3.SMF initiates a PIN configuration information query request to UDM, and the message carries the PIN ID.

[0261] 4. The UDM returns the PIN configuration information to the SMF. The PIN configuration information may include the PIN network topology information, the PIN ID, the PEGC ID in the PIN, the PEMC ID in the PIN, the PDU session ID and / or QoS ID that carries the PIN service flow. The PIN network topology information may include the association between each PINE in the PIN and the PEGC, the association between each PINE in the PIN and the PEMC, and the association between different PINEs in the PIN.

[0262] 5. When a PDU session is used for only one PIN (as shown in Figure 4A), the SMF initiates a service request process to reactivate the PDU session in the PIN network based on the PEGC ID, PIN ID, PDU session ID, and other information obtained in step 4. When a PDU session is used for multiple PINs (as shown in Figure 4B), the SMF will initiate a PDU session modification process to reestablish the QoS flow based on the traffic routing relationship between the PINE and the PEGC in the target PIN. In addition, the above service request process and PDU session modification process can additionally carry a PIN reactivation indication and a PIN ID.

[0263] 6. PEGC re-allocates WiFi, Bluetooth and other communication resources to the PINE in the target PIN, and notifies the associated target PIN where the PINE belonging to the target PIN is located that it has been reactivated.

[0264] Example 7: Deactivation of PINE triggered by PEMC

[0265] As shown in Figure 5G, when the PEMC is deployed remotely from the target PINE and the PEGC associated with the target PINE, the PEMC can trigger the deactivation of the PINE through the network side according to the validity period setting, releasing the 5GS resources allocated to the PINE. The specific steps are as follows:

[0266] 1. When the PINE validity period expires, the PEMC sends a PINE deactivation request to the AMF through the RAN. The message includes at least one of the PINE deactivation indication, PIN ID, PINE ID, PEGC ID associated with the target PINE, and PEMC ID associated with the target PINE.

[0267] 2. The AMF forwards the PINE deactivation request to the SMF. The message includes at least one of the PINE deactivation indication, PIN ID, PINE ID, PEGC ID associated with the target PINE, and PEMC ID associated with the target PINE.

[0268] 3.SMF initiates a PINE configuration information query request to UDM. The message carries the PIN ID, PINE ID, and the PEGC ID associated with the target PINE.

[0269] 4. UDM returns PINE configuration information to SMF, including the PEGC ID associated with the target PINE in the target PIN, as well as the PDU session ID and QoS flow ID (QFI) established by PEGC to carry the target PINE service traffic.

[0270] 5. The SMF will initiate the PDU session modification process and release the QoS flow corresponding to the target PINE based on the PEGC ID, PINE ID, PDU session ID, QFI and other information obtained in step 4. The above PDU session modification process will additionally carry the PINE deactivation indication, PIN ID and PINE ID.

[0271] 6. PEGC releases the communication resources such as WiFi and Bluetooth allocated to the target PINE, and notifies the associated target PINE that it has been switched to the deactivated state in the target PINE.

[0272] Example 8: PEMC-triggered reactivation of PINE

[0273] As shown in Figure 5H, when the PEMC, the target PINE, and the PEGC associated with the target PINE are deployed remotely, the PEMC can trigger the reactivation of the PINE through the network side according to the validity period setting and re-allocate 5GS resources to the PINE. The specific steps are as follows:

[0274] 1. PEMC sends a PINE activation request to AMF via RAN. The message includes at least one of the PINE activation indication, PIN ID, PINE ID, PEGC ID associated with the target PINE, and PEMC ID associated with the target PINE.

[0275] 2. The AMF forwards the PINE activation request to the SMF. The message carries at least one of the PINE activation indication, PIN ID, PINE ID, PEGC ID associated with the target PINE, and PEMC ID associated with the target PINE.

[0276] 3. The SMF initiates a PIN configuration information query request to the UDM. The message carries at least one of the PIN ID, PINE ID, PEGC ID associated with the target PINE, and PEMC ID associated with the target PINE.

[0277] 4. UDM returns PIN configuration information to SMF, including the PEGC ID associated with the target PINE in the target PIN, as well as the PDU session ID and QoS flow ID (QFI) established by PEGC to carry the target PINE service traffic.

[0278] 5. The SMF will initiate a PDU session modification process to re-establish the QoS flow based on the traffic routing relationship between the PINE and PEGC in the target PIN. In addition, the above PDU session modification process will additionally carry the PINE activation indication, PIN ID, and PINE ID.

[0279] 6. PEGC reallocates the WiFi, Bluetooth and other communication resources to the target PINE and notifies the associated target PINE that it has been switched to the active state in the target PIN.

[0280] Example 9: Deactivation of PIN triggered by PEGC

[0281] As shown in Figure 5I, when direct communication is possible between PEMC and PEGC, PEMC can directly trigger PEGC to initiate the release of 5GS resources based on the validity period configuration, thereby achieving target PIN deactivation. The specific process is as follows:

[0282] 1. When the PIN validity period ends (expires), the PEMC sends a PIN deactivation request to each PEGC in the target PIN. The request message contains PIN deactivation indication, PIN ID, PEGC ID, PEMC ID, PDU session ID, QFI and other information.

[0283] 2. When a PDU session is used for only one PIN (as shown in Figure 4A), the PEGC initiates a PDU session release process to release the user plane resources allocated to the target PIN. When a PDU session is used for multiple PINs (as shown in Figure 4B), the PEGC initiates a PDU session modification process to delete the QoS flow corresponding to the target PIN. In addition, the above user plane deactivation process and PDU session modification process will additionally carry a PIN deactivation indication and PIN ID.

[0284] 3. The PEGC releases the communication resources such as WiFi and Bluetooth allocated to the target PINE, and notifies the associated target PINE that it has been switched to the deactivated state in the target PIN.

[0285] Example 10: PIN activation (reactivation) triggered by PEGC

[0286] As shown in Figure 5J, when direct communication is possible between PEMC and PEGC, PEMC can directly trigger PEGC to initiate target PIN activation based on the validity period configuration and reallocate 5GS resources to the target PIN. The specific process is as follows:

[0287] 1. PEMC sends a PIN activation request to each PEGC in the target PIN. The request message contains PIN activation indication, PIN ID, PEGC ID, PEMC ID, PDU session ID, QFI and other information.

[0288] 2. When a PDU session is only used for one PIN (as shown in Figure 4A), if PEGC has not established a PDU session for the target PIN, PEGC initiates a PDU session establishment process to allocate user plane resources for the target PIN; if the PDU session established by PEGC for the target PIN is in a deactivated state, a service request process is initiated to activate the above PDU session. When a PDU session is used for multiple PINs (as shown in Figure 4B), PEGC will initiate a PDU session modification process to re-establish the QoS flow based on the traffic routing relationship between the PINE and PEGC in the target PIN. In addition, the above service request process and PDU session modification process will additionally carry a PIN reactivation indication and a PIN ID.

[0289] 3. PEGC re-allocates WiFi, Bluetooth and other communication resources to the PINE in the target PIN, and notifies the associated target PIN where the PINE belonging to the target PIN is located that it has been reactivated.

[0290] Example 11: Deactivation of PINE Triggered by PEGC

[0291] As shown in Figure 5K, when direct communication is possible between PEMC and PEGC, PEMC can directly trigger PEGC to initiate the release of 5GS resources based on the validity period configuration, thereby achieving the target PINE deactivation. The specific process is as follows:

[0292] 1. When the PINE validity period expires, the PEMC sends a PINE deactivation request to the PEGC associated with the target PINE in the target PIN. The request message contains the PINE deactivation indication, PIN ID, PINE ID, PEGC ID associated with the target PINE, PDU session ID, QFI and other information.

[0293] 2. PEGC releases the QoS flow corresponding to the target PINE based on the PEGC ID, PINE ID, PDU session ID, QFI, and other information obtained in the first step. The above PDU session modification process will additionally carry the PINE deactivation indication, PIN ID, and PINE ID.

[0294] 3. PEGC releases the communication resources such as WiFi and Bluetooth allocated to the target PINE, and notifies the associated target PINE that it has been switched to the deactivated state in the target PIN.

[0295] Example 12: PEGC-triggered activation (reactivation) of PINE

[0296] As shown in Figure 5L, when direct communication is possible between PEMC and PEGC, PEMC can directly trigger PEGC to initiate target PINE activation based on the validity period configuration and reallocate 5GS resources to the target PINE. The specific process is as follows:

[0297] 1. PEMC sends a PINE activation request to the PEGC associated with the target PINE in the target PIN. The request message contains PINE activation indication, PIN ID, PINE ID, PEGC ID associated with the target PINE, PEMC ID associated with the target PINE, PDU session ID, QFI and other information.

[0298] 2. Based on the PEGC ID, PINE ID, PDU session ID, and QFI information obtained in the first step, the PEGC re-establishes the QoS flow according to the traffic routing relationship between the PINE and the PEGC in the target PIN. In addition, the above PDU session modification process will also carry the PINE activation indication, PIN ID, and PINE ID.

[0299] 3. PEGC reallocates communication resources such as WiFi and Bluetooth to the target PINE and notifies the associated target PINE that it has been switched to an active state in the target PIN.

[0300] The embodiments of the present application provide AF-triggered PIN / PINE activation and deactivation, PEMC-triggered PIN / PINE activation and deactivation, and PEGC-triggered PIN / PINE activation and deactivation methods to support network validity period and device validity period management. In the above-mentioned PIN / PINE activation and deactivation methods, there is no need to delete the PIN configuration information stored in the network and the PIN management entity (such as PEMC and / or AF). Instead, the 5GS resources occupied by the network and the device can be released and reallocated based on the network validity period and the device validity period. Thus, while improving the utilization of communication resources, it avoids the repeated network establishment and configuration of the network and the device during reactivation, as well as tedious operations such as PINE ID allocation and address allocation, PIN parameter configuration, and traffic routing management. Especially for scenarios where the validity period is discontinuous, this solution can reduce the network reconstruction and device activation delay, speed up the response of the network and the device to continue to provide services, thereby improving the user experience, and to a certain extent reducing the signaling load caused by repeated network establishment / release and repeated addition and deletion of devices. In addition, this solution provides a specific PIN / PINE activation and deactivation process, filling the gap in the existing technology.

[0301] The present application also provides a management method. FIG6 is a schematic flow chart of a management method 600 according to an embodiment of the present application. The method can be applied to the system shown in FIG1 or 2, but is not limited thereto. The method includes at least part of the following contents.

[0302] S610: The third device triggers the release or establishment of communication resources occupied by the network and / or the second device according to the network validity period and / or the device validity period.

[0303] In some implementations, the third device triggers the release or establishment of communication resources occupied by the network according to the network validity period, including:

[0304] When the network validity period ends, a network deactivation request is sent.

[0305] In some embodiments, the network deactivation request carries at least one of the following: a network deactivation indication; an identifier of the network; an identifier of a management device in the network; an identifier of a gateway device in the network; a PDU session identifier and a QoS flow identifier that carry the network service flow.

[0306] In some implementations, the third device triggers the release or establishment of communication resources occupied by the network according to the network validity period, including:

[0307] At the beginning of the network validity period, a network activation request is sent.

[0308] In some embodiments, the network activation request carries at least one of the following: a network activation indication; an identifier of the network; an identifier of a management device in the network; an identifier of a gateway device in the network; a PDU session identifier and a QoS flow identifier that carry the network service flow.

[0309] In some implementations, the third device triggers, based on the device validity period, the release or establishment of communication resources occupied by the second device, including:

[0310] When the validity period of the device ends, a device deactivation request is sent.

[0311] In some embodiments, the device deactivation request carries at least one of the following: a device deactivation indication; an identifier of the second device; an identifier of the network to which the second device belongs; an identifier of a management device associated with the second device; an identifier of a gateway device associated with the second device; and a PDU session identifier and a QoS flow identifier that carry the service flow of the second device.

[0312] In some implementations, the third device triggers, based on the device validity period, the release or establishment of communication resources occupied by the second device, including:

[0313] At the beginning of the device's validity period, a device activation request is sent.

[0314] In some embodiments, the device activation request carries at least one of the following: a device activation indication; an identifier of the second device; an identifier of the network to which the second device belongs; an identifier of a management device associated with the second device; an identifier of a gateway device associated with the second device; and a PDU session identifier and a QoS flow identifier that carry the service flow of the second device.

[0315] In some embodiments, the third device comprises an AF or a PEMC.

[0316] In some embodiments, the network includes a PIN.

[0317] In some embodiments, the second device comprises a PINE.

[0318] The present application also provides a first device. FIG7 is a schematic block diagram of a first device 700 according to an embodiment of the present application. The first device 700 may include:

[0319] The first management module 710 is configured to release or establish communication resources occupied by the network and / or the second device according to the network validity period and / or the device validity period.

[0320] In some embodiments, the first management module 710 is configured to initiate, when the validity period of the network ends, a user plane deactivation process, a protocol data unit (PDU) session release process, or a PDU session modification process by the first device to release communication resources occupied by the network.

[0321] In some implementations, the first management module 710 is configured to initiate a user plane deactivation process to release radio resources and / or channels of a PDU session that carries services of the network.

[0322] In some implementations, the first management module 710 is configured to initiate a PDU session release process to release user plane resources allocated to the network.

[0323] In some implementations, the first management module 710 is configured to initiate a PDU session modification process to delete a Quality of Service (QoS) flow corresponding to the network in the PDU session.

[0324] FIG8 is a schematic block diagram of a first device 800 according to an embodiment of the present application, wherein the first device 800 includes one or more features of the above-mentioned embodiment 710. In one possible implementation, in the embodiment of the present application, the device further includes:

[0325] The first receiving module 820 is configured to receive a network deactivation request, where the network deactivation request is sent by a third device when the network validity period of the network ends.

[0326] In some embodiments, the network deactivation request carries at least one of the following: a network deactivation indication; an identifier of the network; an identifier of a management device in the network; an identifier of a gateway device in the network; a PDU session identifier and a QoS flow identifier that carry the network service flow.

[0327] In some implementations, the first management module 710 is configured to initiate a service request process, a PDU session establishment process, or a PDU session modification process at the beginning of the network validity period to establish communication resources occupied by the network.

[0328] In some implementations, the first management module 710 is configured to initiate a service request process to activate a PDU session established for the network.

[0329] In some implementations, the first management module 710 is configured to initiate a PDU session establishment process to establish a PDU session for the network.

[0330] In some implementations, the first management module 710 is configured to initiate a PDU session modification process to establish a QoS flow corresponding to the network in the PDU session.

[0331] In some embodiments, further comprising:

[0332] The second receiving module 830 is configured to receive a network activation request, where the network activation request is sent by a third device when the network validity period of the network begins.

[0333] In some embodiments, the network activation request carries at least one of the following: a network activation indication; an identifier of the network; an identifier of a management device in the network; an identifier of a gateway device in the network; a PDU session identifier and / or a QoS flow identifier that carries the network service flow.

[0334] In some implementations, the first management module 710 is configured to initiate a PDU session modification process when the validity period of the second device expires, so as to release communication resources occupied by the second device.

[0335] In some implementations, the first management module 710 is configured to initiate a PDU session modification process to delete the QoS flow corresponding to the second device in the PDU session.

[0336] In some embodiments, further comprising:

[0337] The third receiving module 840 is configured to receive a device deactivation request, where the device deactivation request is sent by the third device when the device validity period of the second device expires.

[0338] In some embodiments, the device deactivation request carries at least one of the following: a device deactivation indication; an identifier of the second device; an identifier of the network to which the second device belongs; an identifier of a management device associated with the second device; an identifier of a gateway device associated with the second device; a PDU session identifier and / or a QoS flow identifier that carries the service flow of the second device.

[0339] In some implementations, the first management module 710 is configured to initiate a PDU session modification process when the validity period of the second device begins, so as to establish communication resources occupied by the second device.

[0340] In some implementations, the first management module 710 is configured to initiate a PDU session modification process to establish a QoS flow corresponding to the second device in the PDU session.

[0341] In some embodiments, further comprising:

[0342] The fourth receiving module 850 is configured to receive a device activation request, where the device activation request is sent by the third device when the device validity period of the second device begins.

[0343] In some embodiments, the device activation request carries at least one of the following: a device activation indication; an identifier of the second device; an identifier of the network to which the second device belongs; an identifier of a management device associated with the second device; an identifier of a gateway device associated with the second device; and a PDU session identifier and a QoS flow identifier that carry the service flow of the second device.

[0344] In some embodiments, further comprising:

[0345] A sending module 860 sends a network configuration query request / device configuration query request to the fourth device;

[0346] The fifth receiving module 870 is configured to receive the configuration information of the network / the configuration information of the second device from the fourth device.

[0347] In some embodiments, the configuration information of the network includes at least one of the following: topology information of the network; identification of the network; identification of the management device in the network; identification of the device in the network; PDU session identification and QoS flow identification carrying the network service flow.

[0348] In some embodiments, the topology information of the network includes at least one of the following: an association relationship between a device in the network and a management device; an association relationship between a device in the network and a gateway device; and an association relationship between a device in the network and other devices.

[0349] In some embodiments, the device configuration query request carries at least one of the following: an identifier of the second device; an identifier of a network to which the second device belongs; an identifier of a management device associated with the second device; or an identifier of a gateway device associated with the second device.

[0350] In some embodiments, the configuration information of the second device includes at least one of the following: an identifier of the second device; an identifier of a management device associated with the second device; an identifier of a gateway device associated with the second device; a PDU session identifier and / or a QoS flow identifier that carries the service flow of the second device.

[0351] In some implementations, the first management module 710 is configured to release or establish communication resources occupied by the network and / or the second device based on the configuration information of the network / the configuration information of the second device.

[0352] In some embodiments, the first device includes a session management function SMF or a personal Internet of Things device PEGC with gateway capabilities.

[0353] In some embodiments, the third device includes an application function AF or a personal Internet of Things device with management capabilities PEMC.

[0354] In some embodiments, the fourth device includes a unified data management function UDM.

[0355] In some embodiments, the network includes a personal IoT PIN.

[0356] In some embodiments, the second device includes a personal Internet of Things device PINE.

[0357] It should be understood that the above and other operations and / or functions of the modules in the first device according to the embodiment of the present application are respectively for implementing the corresponding processes of the first device in method 300 of Figure 3. For the sake of brevity, they are not repeated here.

[0358] The present application also provides a third device. FIG9 is a schematic block diagram of a third device 900 according to an embodiment of the present application. The third device 900 may include:

[0359] The second management module 910 is configured to trigger the release or establishment of communication resources occupied by the network and / or the second device according to the network validity period and / or the device validity period.

[0360] In some implementations, the second management module 910 is configured to send a network deactivation request when the network validity period ends.

[0361] In some implementations, the network deactivation request carries at least one of the following: a network deactivation indication; an identifier of the network; an identifier of a management device in the network; or an identifier of a gateway device in the network.

[0362] The PDU session identifier and QoS flow identifier that carry the network service flow.

[0363] In some implementations, the second management module 910 is configured to send a network activation request when the network validity period begins.

[0364] In some embodiments, the network activation request carries at least one of the following: a network activation indication; an identifier of the network; an identifier of a management device in the network; an identifier of a gateway device in the network; a PDU session identifier and a QoS flow identifier that carry the network service flow.

[0365] In some implementations, the second management module 910 is configured to send a device deactivation request when the validity period of the device expires.

[0366] In some embodiments, the device deactivation request carries at least one of the following: a device deactivation indication; an identifier of the second device; an identifier of the network to which the second device belongs; an identifier of a management device associated with the second device; an identifier of a gateway device associated with the second device; and a PDU session identifier and a QoS flow identifier that carry the service flow of the second device.

[0367] In some implementations, the second management module 910 is configured to send a device activation request when the validity period of the device begins.

[0368] In some embodiments, the device activation request carries at least one of the following: a device activation indication; an identifier of the second device; an identifier of the network to which the second device belongs; an identifier of a management device associated with the second device; an identifier of a gateway device associated with the second device; and a PDU session identifier and a QoS flow identifier that carry the service flow of the second device.

[0369] In some embodiments, the third device comprises an AF or a PEMC.

[0370] In some embodiments, the network includes a PIN.

[0371] In some embodiments, the second device comprises a PINE.

[0372] It should be understood that the above and other operations and / or functions of the modules in the third device according to the embodiment of the present application are respectively for implementing the corresponding processes of the third device in method 600 of Figure 6. For the sake of brevity, they are not repeated here.

[0373] It should be noted that the functions described in the various modules (submodules, units, or components, etc.) in the communication device of the embodiment of the present application can be implemented by different modules (submodules, units, or components, etc.) or by the same module (submodule, unit, or component, etc.). For example, the first receiving module and the second receiving module can be different modules or the same module, and both can implement their corresponding functions in the embodiment of the present application. In addition, the sending module and the receiving module in the embodiment of the present application can be implemented by the transceiver of the device, and some or all of the other modules can be implemented by the processor of the device.

[0374] Figure 10 is a schematic structural diagram of a communication device 1000 according to an embodiment of the present application. The communication device 1000 shown in Figure 10 includes a processor 1010, which can call and execute a computer program from a memory to implement the method in the embodiment of the present application.

[0375] In some implementations, as shown in FIG10 , the communication device 1000 may further include a memory 1020. The processor 1010 may call and execute a computer program from the memory 1020 to implement the communication device in the embodiment of the present application.

[0376] The memory 1020 may be a separate device independent of the processor 1010 , or may be integrated into the processor 1010 .

[0377] In some embodiments, as shown in FIG10 , the communication device 1000 may further include a transceiver 1030 , and the processor 1010 may control the transceiver 1030 to communicate with other devices. Specifically, the transceiver 1030 may send information or data to other devices, or receive information or data sent by other devices.

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

[0379] In some embodiments, the communication device 1000 may be the communication device of an embodiment of the present application, and the communication device 1000 may implement the corresponding processes implemented by the communication device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0380] Figure 11 is a schematic structural diagram of a chip 1100 according to an embodiment of the present application. The chip 1100 shown in Figure 11 includes a processor 1110, which can call and execute a computer program from a memory to implement the method in the embodiment of the present application.

[0381] In some embodiments, as shown in FIG11 , the chip 1100 may further include a memory 1120. The processor 1110 may call and execute a computer program from the memory 1120 to implement the method in the embodiment of the present application.

[0382] The memory 1120 may be a separate device independent of the processor 1110 , or may be integrated into the processor 1110 .

[0383] In some embodiments, the chip 1100 may further include an input interface 1130. The processor 1110 may control the input interface 1130 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0384] In some embodiments, the chip 1100 may further include an output interface 1140. The processor 1110 may control the output interface 1140 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0385] In some embodiments, the chip can be applied to the communication equipment in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the network equipment in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

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

[0387] The processor mentioned above may be a general-purpose processor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or other programmable logic devices, transistor logic devices, discrete hardware components, etc. The general-purpose processor mentioned above may be a microprocessor or any conventional processor, etc.

[0388] The memory mentioned above may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. 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).

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

[0390] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instruction is loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network or other programmable devices. The computer instruction can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instruction can be transmitted from a website, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode to another website, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).

[0391] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

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

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

Claims

1. A management method comprising: The first device releases or establishes communication resources occupied by the network and / or the second device according to the network validity period and / or the device validity period.

2. The method according to claim 1, wherein The first device releases communication resources occupied by the network according to the network validity period, including: At the end of the validity period of the network, the first device initiates a user plane deactivation process, a protocol data unit PDU session release process or a PDU session modification process to release the communication resources occupied by the network.

3. The method according to claim 2, wherein: The first device initiating a user plane deactivation process to release communication resources occupied by the network includes: The first device initiates a user plane deactivation process to release radio resources and / or channels of the PDU session that carries the service of the network.

4. The method according to claim 2, wherein: The first device initiates a PDU session release process to release communication resources occupied by the network, including: The first device initiates a PDU session release process to release user plane resources allocated to the network.

5. The method according to claim 2, wherein: The first device initiates a PDU session modification process to release communication resources occupied by the network, including: The first device initiates a PDU session modification process to delete the quality of service QoS flow corresponding to the network in the PDU session.

6. The method according to any one of claims 2 to 5, further comprising: The first device receives a network deactivation request, which is sent by a third device when a network validity period of the network ends.

7. The method according to claim 6, wherein: The network deactivation request carries at least one of the following: Network deactivation indication; an identification of the network; An identifier of a management device in the network; An identifier of a gateway device in the network; The PDU session identifier and QoS flow identifier that carry the network service flow.

8. The method according to claim 1, wherein The first device establishes communication resources occupied by the network according to the network validity period, including: When the validity period of the network begins, the first device initiates a service request process, a PDU session establishment process or a PDU session modification process to establish communication resources occupied by the network.

9. The method according to claim 8, wherein The first device initiates a service request process to establish communication resources occupied by the network, including: The first device initiates a service request process to activate a PDU session established for the network.

10. The method according to claim 8, wherein The first device initiates a PDU session establishment process to establish communication resources occupied by the network, including: The first device initiates a PDU session establishment process to establish a PDU session for the network.

11. The method according to claim 8, wherein The first device initiates a PDU session modification process to establish communication resources occupied by the network, including: The first device initiates a PDU session modification process to establish a QoS flow corresponding to the network in the PDU session.

12. The method according to any one of claims 8 to 11, further comprising: The first device receives a network activation request, which is sent by a third device at the beginning of a network validity period of the network.

13. The method according to claim 12, wherein: The network activation request carries at least one of the following: Network activation instructions; an identification of the network; An identifier of a management device in the network; An identifier of a gateway device in the network; The PDU session identifier and / or QoS flow identifier that carries the network service flow.

14. The method according to claim 1, wherein The first device releasing the communication resources occupied by the second device according to the device validity period, including: When the validity period of the second device ends, the first device initiates a PDU session modification process to release the communication resources occupied by the second device.

15. The method according to claim 14, wherein The first device initiating a PDU session modification process to release communication resources occupied by the second device includes: The first device initiates a PDU session modification process to delete the QoS flow corresponding to the second device in the PDU session.

16. The method according to claim 14 or 15, further comprising: The first device receives a device deactivation request, which is sent by a third device when a device validity period of the second device ends.

17. The method according to claim 16, wherein: The device deactivation request carries at least one of the following: Device deactivation indication; an identifier of the second device; an identifier of the network to which the second device belongs; an identifier of a management device associated with the second device; an identifier of a gateway device associated with the second device; The PDU session identifier and / or QoS flow identifier that carries the service flow of the second device.

18. The method according to claim 1, wherein The first device establishes communication resources occupied by the second device according to the device validity period, including: When the validity period of the second device begins, the first device initiates a PDU session modification process to establish communication resources occupied by the second device.

19. The method according to claim 18, wherein The first device initiating a PDU session modification process to establish communication resources occupied by the second device, including: The first device initiates a PDU session modification process to establish a QoS flow corresponding to the second device in the PDU session.

20. The method according to claim 18 or 19, further comprising: The first device receives a device activation request, which is sent by a third device when a device validity period of the second device begins.

21. The method according to claim 20, wherein The device activation request carries at least one of the following: Device activation instructions; an identifier of the second device; an identifier of the network to which the second device belongs; an identifier of a management device associated with the second device; an identifier of a gateway device associated with the second device; The PDU session identifier and QoS flow identifier that carry the service flow of the second device.

22. The method according to any one of claims 1 to 21, further comprising: The first device sends a network configuration query request and / or a device configuration query request to the fourth device; The first device receives configuration information of the network and / or configuration information of the second device from the fourth device.

23. The method according to claim 22, wherein The network configuration information includes at least one of the following: Topology information of the network; an identification of the network; An identifier of a management device in the network; An identifier of a gateway device in the network; an identification of a device in the network; The PDU session identifier and QoS flow identifier that carry the network service flow.

24. The method according to claim 22, wherein The network topology information includes at least one of the following: The relationship between devices in the network and management devices; The relationship between devices and gateway devices in the network; The relationship between a device and other devices in the network.

25. The method according to claim 22, wherein The device configuration query request carries at least one of the following: an identifier of the second device; an identifier of the network to which the second device belongs; an identifier of a management device associated with the second device; An identifier of a gateway device associated with the second device.

26. The method according to claim 22, wherein The configuration information of the second device includes at least one of the following: an identifier of the second device; an identifier of a management device associated with the second device; an identifier of a gateway device associated with the second device; The PDU session identifier and / or QoS flow identifier that carries the service flow of the second device.

27. The method according to any one of claims 22 to 26, wherein: The first device releasing or establishing a network and / or communication resources occupied by the second device includes: The first device releases or establishes communication resources occupied by the network and / or the second device based on the configuration information of the network and / or the configuration information of the second device.

28. The method according to any one of claims 1 to 27, wherein: The first device includes a session management function SMF or a personal Internet of Things device PEGC with gateway capabilities.

29. The method of claim 6, 12, 16 or 20, wherein The third device includes an application function AF or a personal Internet of Things device PEMC with management capabilities.

30. The method according to any one of claims 22 to 27, wherein: The fourth device includes a unified data management function UDM.

31. The method according to any one of claims 1 to 30, wherein: The network includes a personal IoT PIN.

32. The method according to any one of claims 1 to 30, wherein: The second device includes a personal Internet of Things device PINE.

33. A management method comprising: The third device triggers the release or establishment of communication resources occupied by the network and / or the second device according to the network validity period and / or the device validity period.

34. The method according to claim 33, wherein The third device triggers the release or establishment of communication resources occupied by the network according to the network validity period, including: When the network validity period ends, a network deactivation request is sent.

35. The method according to claim 34, wherein The network deactivation request carries at least one of the following: Network deactivation indication; an identification of the network; An identifier of a management device in the network; The identifier of a gateway device in the network. The PDU session identifier and QoS flow identifier that carry the network service flow.

36. The method of claim 33, wherein: The third device triggers the release or establishment of communication resources occupied by the network according to the network validity period, including: At the beginning of the network validity period, a network activation request is sent.

37. The method according to claim 36, wherein The network activation request carries at least one of the following: Network activation instructions; an identification of the network; An identifier of a management device in the network; The identifier of a gateway device in the network. The PDU session identifier and QoS flow identifier that carry the network service flow.

38. The method of claim 33, wherein: The third device triggers, according to the device validity period, the release or establishment of the communication resources occupied by the second device, including: When the validity period of the device ends, a device deactivation request is sent.

39. The method according to claim 38, wherein The device deactivation request carries at least one of the following: Device deactivation indication; an identifier of the second device; an identifier of the network to which the second device belongs; an identifier of a management device associated with the second device; an identifier of a gateway device associated with the second device; The PDU session identifier and QoS flow identifier that carry the service flow of the second device.

40. The method of claim 33, wherein The third device triggers, according to the device validity period, the release or establishment of the communication resources occupied by the second device, including: When the validity period of the device begins, a device activation request is sent.

41. The method according to claim 40, wherein The device activation request carries at least one of the following: Device activation instructions; an identifier of the second device; an identifier of the network to which the second device belongs; an identifier of a management device associated with the second device; an identifier of a gateway device associated with the second device; The PDU session identifier and QoS flow identifier that carry the service flow of the second device.

42. The method according to any one of claims 33 to 41, wherein: The third device includes AF or PEMC.

43. The method according to any one of claims 33 to 41, wherein: The network includes a PIN.

44. The method according to any one of claims 33 to 41, wherein: The second device includes a PINE.

45. A first device comprising: The first management module is configured to release or establish communication resources occupied by the network and / or the second device according to the network validity period and / or the device validity period.

46. ​​A third device comprising: The second management module is configured to trigger the release or establishment of communication resources occupied by the network and / or the second device according to the network validity period and / or the device validity period.

47. A communication device comprising: A processor, a memory and a transceiver, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory and control the transceiver to perform the method according to any one of claims 1 to 32 or 33 to 44.

48. A chip comprising: A processor, configured to call and execute a computer program from a memory, so that a device equipped with the chip executes the method according to any one of claims 1 to 32 or 33 to 44.

49. A computer-readable storage medium for storing a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 32 or 33 to 44.

50. A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 32 or 33 to 44.

51. A computer program causing a computer to perform the method of any one of claims 1 to 32 or 33 to 44.

Images