WO2024124413A1

WO2024124413A1 - Management methods and devices

Info

Publication number: WO2024124413A1
Application number: PCT/CN2022/138831
Authority: WO
Inventors: 郭伯仁
Original assignee: Oppo广东移动通信有限公司
Priority date: 2022-12-13
Filing date: 2022-12-13
Publication date: 2024-06-20

Abstract

Provided in the embodiments of the present application are management methods and devices. A management method comprises: a first device releases or establishes a communication resource occupied by a network and/or a second device according to a network validity period and/or a device validity period. The embodiments of the present application can achieve network/device management, and reduce the service time delay during the management process.

Description

Management methods and equipment

Technical Field

The present application relates to the field of communications, and more particularly, to management methods and devices.

Background technique

In the related art, the validity period management of the network/device is relatively simple. For example, when the validity period of the network/device ends, the communication system resources occupied by the network/device are released and the configuration information of the network/device is deleted; when the validity period of the network/device begins, the communication system resources are requested again and the communication configuration is performed. This method requires cumbersome operations and has a large service delay.

Summary of the invention

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

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.

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

An embodiment of the present application provides a first device, including: a first management module, used 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.

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.

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.

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

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

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.

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.

In the 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

FIG. 1 exemplarily shows a communication system 100 .

FIG. 2 is a schematic diagram of a PIN structure.

FIG. 3 is a schematic flow chart of a management method 300 according to an embodiment of the present application.

FIG. 4A is a schematic diagram showing a PDU session for only one group of devices.

FIG. 4B is a schematic diagram of a PDU session for multiple groups of devices.

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

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

FIG5C is a schematic flowchart of deactivation of PINE triggered by AF according to an embodiment of the present application.

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

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

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

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

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

FIG5I is a schematic flowchart of deactivation of a PIN triggered by PEGC according to an embodiment of the present application.

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

FIG5K is a schematic flowchart of deactivation of a PINE triggered by PEGC according to an embodiment of the present application.

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

FIG. 6 is a schematic flowchart of a management method 600 according to an embodiment of the present application.

FIG. 7 is a schematic block diagram of a first device 700 according to an embodiment of the present application.

FIG. 8 is a schematic block diagram of a first device 800 according to an embodiment of the present application.

FIG. 9 is a schematic block diagram of a third device 900 according to an embodiment of the present application.

FIG. 10 is a schematic structural diagram of a communication device 1000 according to an embodiment of the present application.

FIG. 11 is a schematic structural diagram of a chip 1100 according to an embodiment of the present application.

Detailed ways

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.

It should be noted that the terms "first", "second", etc. in the description and claims of the embodiments of the present application and the above drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. The objects described by the "first" and "second" described at the same time may be the same or different.

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, and NR system. Evolved systems, LTE-based access to unlicensed spectrum (LTE-U) systems, NR-based access to unlicensed spectrum (NR-U) systems, non-terrestrial communication networks (NTN) systems, universal mobile telecommunication systems (UMTS), wireless local area networks (WLAN), wireless fidelity (WiFi), fifth-generation communication (5th-Generation, 5G) systems or other communication systems, etc.

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 (Device to Device, D2D) communication, machine to machine (Machine to Machine, M2M) communication, machine type 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.

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

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.

The embodiments of the present application describe various embodiments in conjunction with network equipment and terminal equipment, wherein the terminal equipment 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 equipment, user agent or user device, etc.

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 function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in the next generation communication system such as the NR network, or a terminal device in the future evolved Public Land Mobile Network (PLMN) network, etc.

In the embodiments 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 (for example, on airplanes, balloons and satellites, etc.).

In the embodiments 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 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.

As an example but not limitation, in the embodiments of the present application, the terminal device may also be a wearable device. Wearable devices may also be referred to as 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 powerful functions achieved through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include full-featured, large-sized, and fully or partially independent of smartphones, such as smart watches or smart glasses, as well as devices 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 types of smart bracelets and smart jewelry for vital sign monitoring.

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 (Evolutional Node B, 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.

As an example but not 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. Optionally, 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.

In an embodiment of the present application, a network device can provide services for a cell, and a terminal device communicates with the network device through transmission resources used by the cell (for example, frequency domain resources, or spectrum resources). The cell can be a cell corresponding to a network device (for example, a base station), and 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.

Fig. 1 exemplarily shows 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 other number of terminal devices 120 within its coverage area, which is not limited in the embodiment of the present application.

In one implementation, the communication system 100 may also include other network entities such as a Mobility Management Entity (MME) and an Access and Mobility Management Function (AMF), but this is not limited to the embodiments of the present application.

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 may be an evolutionary base station (evolutional node B, referred to 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 Node B (gNodeB) 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.

It should be understood that the device with communication function in the network/system in the embodiment of the present application can be called 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 with communication function, and the network device and the terminal device may be specific devices in the embodiment of the present application, which will not be repeated here; the communication device may also include other devices in the communication system, such as other network entities such as a network controller and a mobile management entity, which is not limited in the embodiment of the present application.

It should be understood that the terms "system" and "network" are often used interchangeably in this article. The term "and/or" in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and/or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character "/" in this article generally indicates that the associated objects before and after are in an "or" relationship.

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

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

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 related technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all belong to the protection scope of the embodiments of the present application.

IoT devices can be divided into wearable devices (e.g., cameras, earphones, watches, headphones, health monitors), home life 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.

At present, except for some wearable devices, other types of IoT devices can only access the Internet through relay devices, gateways or mobile networks through mobile phones. In both cases, the core network cannot realize that the IoT device is connected to the mobile network. However, in order to make full use of the 5G system to assist in the management and business support of IoT devices, it is indispensable to enable the 5G system to participate in the personal IoT. Figure 2 is a schematic diagram of the PIN structure. As shown in Figure 2, the personal IoT (PIN, Personal IoT Network) created by the user contains a group of personal IoT elements/personal IoT devices (PINE, PIN Element), and this group of IoT devices 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. The IoT device can be a UE with the ability to access the 5G system, or it can be a non-3GPP device that can only communicate through WiFi, Bluetooth, etc. A PINE that can provide other PINEs with a connection to the 5G network or relay communications between PINEs is called an IoT device with gateway capabilities (PEGC, PIN Element with Gateway Capability). A PINE that can manage PINs is called an IoT device with management capabilities (PEMC, PIN Element with Management Capability).

After a PIN is created, 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, PEMC can set the duration of the PIN network by starting a timer, which depends on the operator's policy or third-party policy. At the end of the PIN duration, 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, PEMC will notify 5GC and the PINE in the network that the device has been deactivated.

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 scheme, 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 prior art, the corresponding PIN network will be deactivated after the first time period ends, 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 cumbersome operations. This greatly increases service latency and affects user experience. In addition, the prior art is not clear about how to support PIN validity period management, and does not involve detailed descriptions of processes such as validity period execution.

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 the device based on the validity period.

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, such as releasing the 5G system (5GS) resources allocated to the network and deleting the configuration information stored in the unified data management (UDM); if the validity period is a discontinuous period, the network is switched to inactive when the network validity period ends, such as releasing the 5GS resources allocated to the network and retaining the stored network configuration information until the next validity period arrives to reactivate the network.

In some examples, the device validity period indicates the active time of the device in the network. When the device validity period ends, the device is removed from the network or switched to an inactive state. Specifically, if the device validity period is a fixed duration, the device is removed from the network when the device validity period ends; if the device validity period is a discontinuous period, the device is switched to an inactive state when the device validity period ends, that is, the resources allocated to the device by the network are released, but the configuration information of the device in the network is retained.

The parameter configuration of the network validity period and/or device validity period can be statically configured in the device or in the 5G core network (5GC) network element 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 the PIN/PINE deactivation and reactivation after the validity period timer expires. 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.

Fig. 3 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 Fig. 1 or 2, but is not limited thereto. The method includes at least part of the following contents.

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.

In the following content, 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.

In some embodiments, the first device includes a SMF or a PEGC.

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

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 according to the PIN validity period; 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 according to the PINE validity period.

(I) The first device releases the communication resources occupied by the network according to the network validity period:

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

When the network validity period ends, 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.

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 SMF.

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.

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.

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 trigger 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.

In some implementations, the first device receives a network deactivation request, which is sent by the third device when the network validity period of the network ends. For example, the third device stores the network validity period configuration, and when the network validity period of the network ends, the third device sends the network deactivation request to the first device.

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

Network deactivation indication;

the identity of the network;

The identification of the management device in the network;

The identification of the gateway device in the network;

The PDU session identifier and QoS flow identifier that carries the network service flow.

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.

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

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

Exemplarily, the first device may obtain the network configuration information from the fourth device. For example, the method is as follows:

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

The first device receives configuration information of the network from the fourth device.

The network configuration query request can carry the network's identification information, such as a PIN ID.

The fourth device may include a UDM.

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

Network topology information;

The network's identity;

Identification of management equipment in the network;

Identification of devices in the network;

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

The network topology information may include 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.

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.

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 rate 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 PIN 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 the device to continue to provide services, thereby improving user experience and reducing the signaling load caused by repeated network establishment/release and repeated addition and deletion of devices to a certain extent.

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

(ii) The first device establishes (or rebuilds) the communication resources occupied by the network according to the network validity period:

In some implementations, the first device establishes communication resources occupied by the network according to the network validity period, which may include:

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 rebuild) the communication resources occupied by the network.

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.

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.

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 trigger 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.

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

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

Network activation instructions;

the identity of the network;

The identification of the management device in the network;

The identification of the gateway device in the network;

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

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

The fourth device may include a UDM.

Network topology information;

The network's identity;

Identification of management equipment in the network;

Identification of devices in the network;

The network topology information may include 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.

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 rate 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.

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.

(III) The first device releases the communication resources occupied by the second device according to the network validity period:

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

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.

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.

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 trigger 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.

In some implementations, 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.

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.

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

Device deactivation indication;

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;

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.

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.

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

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

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:

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

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

The fourth device may include a UDM.

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

an identification 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;

An identification of a gateway device associated with the second device.

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.

In some implementations, the configuration information of the second device includes at least one of the following:

an identification 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.

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.

Based on the configuration information of the second device, the first device can release 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 of the device when it is reactivated, as well as cumbersome 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 to provide services, thereby improving user experience and reducing the signaling load caused by repeated network establishment/release and repeated addition and deletion of devices to a certain extent.

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

(IV) The first device establishes (or reconstructs) the communication resources occupied by the second device according to the network validity period:

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

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.

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.

If the device validity period is configured in the first device, the first device can actively initiate a PDU session modification process at the beginning of the device validity period to establish a 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 trigger of other devices (such as a third device) to establish a 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.

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

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.

Exemplarily, the device activation request carries at least one of the following:

Device activation instructions;

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;

an identifier of a gateway device associated with the second device;

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

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

The fourth device may include a UDM.

an identification 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;

An identification of a gateway device associated with the second device.

an identification 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;

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 cumbersome 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 to provide services, thereby improving user experience and reducing the signaling load caused by repeated network establishment/release and repeated addition and deletion of devices to a certain extent.

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 activated state in the target PIN.

In addition to the above four methods, 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. 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.

Take the network as PIN and the second device as PINE as an example. 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 belong to PIN 1.

The specific implementation manner is introduced below in conjunction with the accompanying drawings.

Example 1: PIN deactivation triggered by AF

As shown in FIG5A , the AF can trigger the deactivation of the PIN according to the validity period setting and release the 5GS resources allocated to the PIN. The specific steps are as follows:

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

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

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

4. UDM returns PIN configuration information to SMF, which may include topology information of PIN network, PIN ID, ID of PEGC in PIN, ID of PEMC in PIN, PDU session ID and/or QoS ID carrying PIN service flow. Topology information of PIN network may include association relationship between each PINE and PEGC in PIN, association relationship between each PINE and PEMC in PIN, association relationship between different PINEs in PIN, etc.

5. When a PDU session is used for only one PIN (as shown in Figure 4A), SMF will initiate the user plane deactivation process to release the wireless resources (such as DRB) and N3 tunnel (N3 tunnel) 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), SMF will initiate the 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 the PIN deactivation indication and PIN ID.

6. PEGC releases the WiFi, Bluetooth and other communication resources allocated to the target PIN, and notifies the target PIN where the associated PINE belonging to the target PIN is located that it has been deactivated.

Example 2: AF-triggered PIN activation (reactivation)

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

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

2. PCF forwards the PIN reactivation request to SMF, which carries the PIN reactivation instruction and PIN ID.

5. When a PDU session is used for only one PIN (as shown in Figure 4A), 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 the fourth step; when a PDU session is used for multiple PINs (as shown in Figure 4B), SMF will initiate a PDU session modification process to reestablish the QoS flow based on the traffic routing relationship between PINE and 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.

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.

Example 3: Deactivation of PINE triggered by AF

As shown in FIG5C , the AF can trigger the deactivation of the PINE according to the validity period setting, and release the 5GS resources allocated to the PINE. The specific steps are as follows:

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

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

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.

4. UDM returns the 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 (i.e., QFI) established by PEGC to carry the target PINE service traffic.

5.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 PINE deactivation indication, PIN ID, and PINE ID.

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.

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

As shown in FIG5D , 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:

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

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

3.SMF initiates a PIN configuration information query request to 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.

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

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

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 activated state in the target PIN.

Example 5: Deactivation of PIN triggered by PEMC

As shown in FIG5E , when PEMC and PEGC are deployed remotely, PEMC can trigger the deactivation of PIN through the network side according to the validity period setting, and release the 5GS resources allocated to the PIN. The specific steps are as follows:

1. When the PIN expires, PEMC sends a PIN deactivation request to AMF through the radio access network (RAN). The message includes a PIN deactivation indication and a PIN ID.

2.AMF forwards the PIN deactivation request to SMF, which carries the PIN deactivation instruction and PIN ID.

Example 6: PEMC-triggered PIN reactivation

As shown in FIG5F , when PEMC and PEGC are deployed remotely, PEMC can trigger the reactivation of PIN through the network side according to the validity period setting, re-allocate 5GS resources for the PIN, and restore the communication resources between PINE and PEGC. The specific steps are as follows:

1. PEMC sends a PIN activation request to AMF through RAN. The message includes PIN activation indication and PIN ID.

2.AMF forwards the PIN activation request to SMF, which carries the PIN activation instruction and PIN ID.

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

Example 7: Deactivation of PINE triggered by PEMC

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

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

2.AMF forwards the PINE deactivation request to SMF, which 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.

Example 8: PEMC-triggered reactivation of PINE

As shown in FIG5H , when PEMC is deployed remotely from the target PINE and the PEGC associated with the target PINE, 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:

1. PEMC sends a PINE activation request to AMF through 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.

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

Example 9: Deactivation of PIN triggered by PEGC

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

1. When the PIN validity period ends (expires), 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.

2. When a PDU session is used for only one PIN (as shown in Figure 4A), 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), PEGC will initiate a PDU session modification process to delete the QoS flow corresponding to the target PIN. In addition, the above-mentioned user plane deactivation process and PDU session modification process will additionally carry a PIN deactivation indication and a PIN ID.

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.

Example 10: Activation (reactivation) of PIN triggered by PEGC

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

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.

2. When a PDU session is used for only 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.

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.

Example 11: Deactivation of PINE Triggered by PEGC

As shown in Figure 5K, when PEMC and PEGC can communicate directly, PEMC can directly trigger PEGC to initiate the release of 5GS resources according to the validity period configuration, thereby achieving the target PINE deactivation. The specific process is as follows:

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

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 PINE deactivation indication, PIN ID and PINE ID.

Example 12: Activation (reactivation) of PINE triggered by PEGC

As shown in FIG5L , when direct communication is possible between PEMC and PEGC, PEMC can directly trigger PEGC to initiate activation of the target PINE according to the validity period configuration and reallocate 5GS resources to the target PINE. The specific process is as follows:

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.

2. PEGC re-establishes the QoS flow based on the traffic routing relationship between PINE and PEGC in the target PIN based on the PEGC ID, PINE ID, PDU session ID, QFI and other information obtained in the first step. In addition, the above PDU session modification process will additionally carry PINE activation indication, PIN ID, and PINE ID.

3. 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 activated state in the target PIN.

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), but 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. Thereby, while improving the utilization rate 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 with discontinuous validity periods, this solution can reduce network reconstruction and device activation delays, speed up the response of the network and the device 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. In addition, this solution provides a specific PIN/PINE activation and deactivation process, filling the gap in the existing technology.

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.

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.

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:

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

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.

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

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.

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

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

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.

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

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.

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

In some embodiments, the network includes a PIN.

In some embodiments, the second device comprises a PINE.

The embodiment of the present application further proposes 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:

The first management module 710 is used 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.

In some embodiments, the first management module 710 is used 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.

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

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.

In some implementations, the first management module 710 is used to initiate a PDU session modification process to delete the quality of service QoS flow corresponding to the network in the PDU session.

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

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.

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

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.

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

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

In some embodiments, it further comprises:

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.

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.

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 to release communication resources occupied by the second device.

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

In some embodiments, it further comprises:

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 ends.

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.

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 to establish communication resources occupied by the second device.

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.

In some embodiments, it further comprises:

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.

In some embodiments, it further comprises:

A sending module 860 sends a network configuration query request/device configuration query request to a fourth device;

The fifth receiving module 870 is used to receive the configuration information of the network/the configuration information of the second device from the fourth device.

In some embodiments, the configuration information of the network includes at least one of the following: topology information of the network; an identifier of the network; an identifier of a management device in the network; an identifier of a device in the network; a PDU session identifier and a QoS flow identifier that carry the network service flow.

In some implementations, 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; an association relationship between a device in the network and other devices.

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.

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.

In some implementations, the first management module 710 is used 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.

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

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

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

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

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

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 the method 300 of Figure 3, and for the sake of brevity, they are not repeated here.

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:

The second management module 910 is 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.

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

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; an identifier of a gateway device in the network.

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

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

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

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

In some embodiments, the network includes a PIN.

In some embodiments, the second device comprises a PINE.

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, and for the sake of brevity, they are not repeated here.

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 (submodules, units or components, 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 remaining modules can be implemented by the processor of the device.

Fig. 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 Fig. 10 includes a processor 1010, and the processor 1010 can call and run a computer program from a memory to implement the method in the embodiment of the present application.

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

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

In some embodiments, as shown in FIG. 10 , 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, may send information or data to other devices, or receive information or data sent by other devices.

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.

In some implementations, 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, which will not be described in detail here for the sake of brevity.

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

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

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

In some implementations, 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.

In some implementations, 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.

In some embodiments, the chip can be applied to the communication device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

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.

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. Among them, the general-purpose processor mentioned above may be a microprocessor or any conventional processor, etc.

The memory mentioned above may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM).

It should be understood that the above-mentioned memory is exemplary but not restrictive. For example, the memory in the embodiment of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memory in the embodiment of the present application is intended to include but not limited to these and any other suitable types of memory.

In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (Digital Subscriber Line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, 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 integrated. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state drive (SSD)), etc.

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.

Those skilled in the art can 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.

The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

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.
The method according to claim 1, wherein the first device releases communication resources occupied by the network according to the network validity period, comprising:

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.
The method according to claim 2, wherein the first device initiates a user plane deactivation process to release communication resources occupied by the network, comprising:

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

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

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.
The method according to any one of claims 2 to 5, further comprising:

The first device receives a network deactivation request, where the network deactivation request is sent by a third device when a network validity period of the network ends.
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 identification of a management device in the network;

An identification of a gateway device in the network;

The PDU session identifier and QoS flow identifier that carry the network service flow.
The method according to claim 1, wherein the first device establishes communication resources occupied by the network according to the network validity period, comprising:

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.
The method according to claim 8, wherein the first device initiates a service request process to establish communication resources occupied by the network, comprising:

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

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

The first device initiates a PDU session modification process to establish a QoS flow corresponding to the network in the PDU session.
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.
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 identification of a management device in the network;

An identification of a gateway device in the network;

The PDU session identifier and/or QoS flow identifier that carries the network service flow.
The method according to claim 1, wherein the first device releases the communication resources occupied by the second device according to the device validity period, comprising:

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.
The method according to claim 14, wherein the first device initiates a PDU session modification process to release communication resources occupied by the second device, comprising:

The first device initiates a PDU session modification process to delete the QoS flow corresponding to the second device in the PDU session.
The method according to claim 14 or 15, further comprising:

The first device receives a device deactivation request, where the device deactivation request is sent by a third device when a device validity period of the second device ends.
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 a 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.
The method according to claim 1, wherein the first device establishes the communication resources occupied by the second device according to the device validity period, comprising:

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.
The method according to claim 18, wherein the first device initiates a PDU session modification process to establish communication resources occupied by the second device, comprising:

The first device initiates a PDU session modification process to establish a QoS flow corresponding to the second device in the PDU session.
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.
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 a 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.
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 a fourth device;

The first device receives configuration information of the network and/or configuration information of the second device from the fourth device.
The method according to claim 22, wherein the configuration information of the network includes at least one of the following:

Topology information of the network;

an identification of the network;

An identification of a management device in the network;

An identification 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.
The method according to claim 22, wherein the topology information of the network 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.
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 a 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 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;

A PDU session identifier and/or a QoS flow identifier that carries the service flow of the second device.
The method according to any one of claims 22 to 26, wherein the first device releases or establishes communication resources occupied by the network and/or the second device, comprising:

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.
The method according to any one of claims 1 to 27, wherein the first device comprises a session management function SMF or a personal Internet of Things device PEGC with gateway capabilities.
The method according to claim 6, 12, 16 or 20, wherein the third device includes an application function AF or a personal Internet of Things device with management capability PEMC.
The method according to any one of claims 22-27, wherein the fourth device comprises a unified data management function (UDM).
The method according to any one of claims 1-30, wherein the network includes a personal Internet of Things PIN.
The method according to any one of claims 1-30, wherein the second device comprises a personal Internet of Things device PINE.
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.
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, comprising:

When the network validity period ends, a network deactivation request is sent.
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 identification 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.
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, comprising:

At the beginning of the network validity period, a network activation request is sent.
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 identification 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.
The method according to claim 33, wherein the third device triggers the release or establishment of the communication resources occupied by the second device according to the device validity period, comprising:

When the validity period of the device ends, a device deactivation request is sent.
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 a 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.
The method according to claim 33, wherein the third device triggers the release or establishment of the communication resources occupied by the second device according to the device validity period, comprising:

When the validity period of the device begins, a device activation request is sent.
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 a 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.
The method according to any one of claims 33-41, wherein the third device comprises an AF or a PEMC.
A method according to any one of claims 33 to 41, wherein the network comprises a PIN.
The method according to any one of claims 33-41, wherein the second device comprises a PINE.
A first device includes:

The first management module is used 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.
A third device, comprising:

The second management module is 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.
A communication device comprises: 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 the method as described in any one of claims 1 to 32 or 33 to 44.
A chip, comprising: a processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as described in any one of claims 1 to 32 or 33 to 44.
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.
A computer program product comprising computer program instructions, the computer program instructions causing a computer to execute the method according to any one of claims 1 to 32 or 33 to 44.
A computer program, the computer program causing a computer to execute the method as claimed in any one of claims 1 to 32 or 33 to 44.