[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

WO2024124413A1 - 管理方法和设备 - Google Patents

管理方法和设备 Download PDF

Info

Publication number
WO2024124413A1
WO2024124413A1 PCT/CN2022/138831 CN2022138831W WO2024124413A1 WO 2024124413 A1 WO2024124413 A1 WO 2024124413A1 CN 2022138831 W CN2022138831 W CN 2022138831W WO 2024124413 A1 WO2024124413 A1 WO 2024124413A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
identifier
pdu session
validity period
pin
Prior art date
Application number
PCT/CN2022/138831
Other languages
English (en)
French (fr)
Inventor
郭伯仁
Original Assignee
Oppo广东移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to PCT/CN2022/138831 priority Critical patent/WO2024124413A1/zh
Publication of WO2024124413A1 publication Critical patent/WO2024124413A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems

Definitions

  • the present application relates to the field of communications, and more particularly, to management methods and devices.
  • 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.
  • 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.
  • 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.
  • 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.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • LTE-A Advanced long term evolution
  • NR New Radio
  • LTE-based access to unlicensed spectrum (LTE-U) systems LTE-based access to unlicensed spectrum (LTE-U) systems
  • NR-based access to unlicensed spectrum (NR-U) systems NTN-based access to unlicensed spectrum (NR-U) systems
  • NTN non-terrestrial communication networks
  • UMTS universal mobile telecommunication systems
  • WLAN wireless local area networks
  • WiFi wireless fidelity
  • 5G fifth-generation communication
  • D2D Device to Device
  • M2M Machine to Machine
  • MTC Machine Type Communication
  • V2V vehicle to vehicle
  • V2X vehicle to everything
  • 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.
  • CA carrier aggregation
  • DC dual connectivity
  • SA standalone
  • 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.
  • UE user equipment
  • 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.
  • STAION, ST in a WLAN
  • a cellular phone a cordless phone
  • Session Initiation Protocol (SIP) phone Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • PDA Personal Digital Assistant
  • 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.).
  • 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.
  • VR virtual reality
  • AR augmented reality
  • 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.
  • 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.
  • 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.
  • the network device may have a mobile feature, for example, the network device may be a mobile device.
  • the network device may be a satellite or a balloon station.
  • 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.
  • the network device may also be a base station set up in a location such as land or water.
  • 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.
  • 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.
  • 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.
  • MME Mobility Management Entity
  • AMF Access and Mobility Management Function
  • 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.
  • eNB evolutionary base station
  • AP access point
  • TP transmission point
  • gNodeB new generation Node B
  • LTE long-term evolution
  • NR next-generation
  • LAA-LTE authorized auxiliary access long-term evolution
  • the device with communication function in the network/system in the embodiment of the present application can be called a communication device.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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
  • office or factory equipment e.g., printers, meters, sensors
  • FIG. 2 is a schematic diagram of the PIN structure.
  • the personal IoT PIN, Personal IoT Network
  • PINE personal IoT Element
  • 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).
  • 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.
  • 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.
  • the management granularity of the PIN validity period is relatively coarse, and discrete validity period configuration is not supported.
  • the validity period is multiple discrete time periods, for example, 2:00-3:00 every day.
  • the corresponding PIN network will be deactivated after the first time period ends, and the stored PIN configuration information will be released.
  • 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.
  • 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.
  • the network validity period represents the active time of a network composed of a group of devices.
  • the network validity period ends, the network is released or switched to an inactive state.
  • 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);
  • 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.
  • the device validity period indicates the active time of the device in the network.
  • 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).
  • the AF can trigger the PIN/PINE deactivation and reactivation after the validity period timer expires.
  • 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.
  • 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 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.
  • the first device includes a SMF or a PEGC.
  • the third device comprises an AF or a PEMC.
  • the network includes a PIN
  • the second device includes a PINE.
  • 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.
  • the first device releases the communication resources occupied by the network according to the network validity period:
  • 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.
  • the first device releases the communication resources occupied by the network according to the network validity period, which may include:
  • 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.
  • 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.
  • the first device can be a network side device, such as SMF.
  • the first device initiates a PDU session release process to release user plane resources allocated to the network.
  • 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.
  • QoS Quality of Service
  • 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.
  • 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.
  • the third network device can be an AF or a PEMC.
  • the third network device can be an AF.
  • the third device can be a PEMC.
  • the third device can be a PEMC.
  • the first device receives a network deactivation request, which is sent by the third device when the network validity period of the network ends.
  • 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.
  • the network deactivation request may carry at least one of the following:
  • the identification of the management device in the network is the identification of the management device in the network
  • the identification of the gateway device in the network is the identification of the gateway device in the network
  • the PDU session identifier and QoS flow identifier that carries the network service flow.
  • the management device in the network may be PEMC, and the gateway device in the network may be PEGC.
  • the first device may release the communication resources occupied by the network.
  • the first device may release communication resources occupied by the network based on configuration information of the network.
  • the first device may obtain the network configuration information from the fourth device.
  • 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:
  • 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 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.
  • 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).
  • PIN management entity such as PEMC and/or AF.
  • 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.
  • the first device establishes (or rebuilds) the communication resources occupied by the network according to the network validity period:
  • the first device establishes communication resources occupied by the network according to the network validity period, which may include:
  • 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.
  • 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.
  • the first device initiates a PDU session modification process to establish a QoS flow corresponding to the network in the PDU session.
  • 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.
  • 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.
  • the third network device can be an AF or a PEMC.
  • the third network device can be an AF.
  • the third device can be a PEMC.
  • the third device can be a PEMC.
  • 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.
  • 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.
  • the network activation request may carry at least one of the following:
  • the identification of the management device in the network is the identification of the management device in the network
  • the identification of the gateway device in the network is the identification of the gateway device in the network
  • the PDU session identifier and/or QoS flow identifier that carries the network service flow.
  • the management device in the network may be PEMC, and the gateway device in the network may be PEGC.
  • the first device may establish (or re-establish) the communication resources occupied by the network.
  • the first device may establish communication resources occupied by the network based on configuration information of the network.
  • the first device may obtain the network configuration information from the fourth device.
  • 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:
  • 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 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.
  • 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.
  • 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.
  • the first device releasing the communication resources occupied by the second device according to the network validity period may include:
  • the first device initiates a PDU session modification process to release the communication resources occupied by the second device.
  • the first device initiates a PDU session modification process to delete the QoS flow corresponding to the second device in the PDU session.
  • 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.
  • 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.
  • the third network device can be an AF or a PEMC.
  • the third network device can be an AF.
  • the third device can be a PEMC.
  • the third device can be a PEMC.
  • 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.
  • 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.
  • the device deactivation request carries at least one of the following:
  • a PDU session identifier and/or a QoS flow identifier that carries the service flow of the second device are described.
  • the second device is PINE
  • the management device associated with the second device may be PEMC associated with the PINE
  • the gateway device associated with the second device may be PEGC associated with the PINE.
  • the first device may release the communication resources occupied by the second device.
  • the first device may release the communication resources occupied by the second device based on the configuration information of the second device.
  • the first device may obtain the configuration information of the second device from the fourth device.
  • 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.
  • the device configuration query request carries at least one of the following:
  • An identifier of a network to which the second device belongs is an identifier of a network to which the second device belongs
  • An identification of a gateway device associated with the second device is an identification of a gateway device associated with the second device.
  • 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.
  • the configuration information of the second device includes at least one of the following:
  • the PDU session identifier and/or QoS flow identifier that carries the service flow of the second device.
  • 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.
  • 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.
  • 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.
  • the second device such as the PINE
  • the first device establishes (or reconstructs) the communication resources occupied by the second device according to the network validity period:
  • the first device establishing the communication resources occupied by the second device according to the network validity period may include:
  • the first device initiates a PDU session modification process to establish communication resources occupied by the second device.
  • the first device initiates a PDU session modification process to establish a QoS flow corresponding to the second device in the PDU session.
  • 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.
  • 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.
  • the third network device can be an AF or a PEMC.
  • the third network device can be an AF.
  • the third device can be a PEMC.
  • the third device can be a PEMC.
  • 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.
  • 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.
  • the device activation request carries at least one of the following:
  • a PDU session identifier and/or a QoS flow identifier that carries the service flow of the second device are described.
  • the second device is PINE
  • the management device associated with the second device may be PEMC associated with the PINE
  • the gateway device associated with the second device may be PEGC associated with the PINE.
  • the first device may establish communication resources occupied by the second device.
  • the first device may establish communication resources occupied by the second device based on configuration information of the second device.
  • the first device may obtain the configuration information of the second device from the fourth device.
  • 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.
  • the device configuration query request carries at least one of the following:
  • An identifier of a network to which the second device belongs is an identifier of a network to which the second device belongs
  • An identification of a gateway device associated with the second device is an identification of a gateway device associated with the second device.
  • 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.
  • the configuration information of the second device includes at least one of the following:
  • the PDU session identifier and/or QoS flow identifier that carries the service flow of the second device.
  • 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.
  • 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.
  • 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.
  • the second device eg, PINE
  • 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 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • Example 1 PIN deactivation triggered by AF
  • 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:
  • 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.
  • PCF forwards the PIN deactivation request to SMF, which carries the PIN deactivation instruction and PIN ID.
  • 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.
  • SMF 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.
  • the above user plane deactivation process and PDU session modification process will additionally carry the PIN deactivation indication and PIN ID.
  • 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.
  • 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:
  • AF sends a PIN reactivation request to PCF through NEF.
  • the message includes PIN reactivation indication and PIN ID.
  • PCF forwards the PIN reactivation request to SMF, which carries the PIN reactivation instruction and PIN ID.
  • 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.
  • 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.
  • the above service request process and PDU session modification process can additionally carry a PIN reactivation indication and a PIN ID.
  • 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.
  • 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:
  • 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.
  • 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.
  • 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.
  • PDU session ID i.e., QFI
  • SMSF 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.
  • 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.
  • 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:
  • 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.
  • 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.
  • 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.
  • PDU session ID and QoS flow ID i.e., QFI
  • 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.
  • the above PDU session modification process will additionally carry PINE activation indication, PIN ID, and PINE ID.
  • 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.
  • 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:
  • 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.
  • 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.
  • SMF 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.
  • the above user plane deactivation process and PDU session modification process will additionally carry the PIN deactivation indication and PIN ID.
  • 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.
  • 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:
  • PEMC sends a PIN activation request to AMF through RAN.
  • the message includes PIN activation indication and PIN ID.
  • AMF forwards the PIN activation request to SMF, which carries the PIN activation instruction and PIN ID.
  • 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.
  • 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.
  • the above service request process and PDU session modification process can additionally carry a PIN reactivation indication and a PIN ID.
  • 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.
  • PEMC 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:
  • 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.
  • 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.
  • 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.
  • 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.
  • PDU session ID i.e., QFI
  • SMSF 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.
  • 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.
  • PEMC 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:
  • 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.
  • 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.
  • 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.
  • 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.
  • PDU session ID and QoS flow ID i.e., QFI
  • 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.
  • the above PDU session modification process will additionally carry PINE activation indication, PIN ID, and PINE ID.
  • 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.
  • PEMC 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:
  • 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.
  • PEGC 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.
  • 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.
  • PEMC 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:
  • 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.
  • PEGC 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.
  • PEGC 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.
  • the above service request process and PDU session modification process will additionally carry a PIN reactivation indication and a PIN ID.
  • 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.
  • PEMC 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:
  • 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.
  • 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.
  • 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.
  • PEMC 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:
  • 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.
  • 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.
  • the above PDU session modification process will additionally carry PINE activation indication, PIN ID, and PINE ID.
  • 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.
  • 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.
  • 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.
  • this solution provides a specific PIN/PINE activation and deactivation process, filling the gap in the existing technology.
  • 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.
  • 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 third device triggers the release or establishment of communication resources occupied by the network according to the network validity period, including:
  • 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.
  • the third device triggers the release or establishment of communication resources occupied by the network according to the network validity period, including:
  • a network activation request is sent.
  • 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.
  • the third device triggers the release or establishment of communication resources occupied by the second device according to the device validity period, including:
  • 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.
  • the third device triggers the release or establishment of communication resources occupied by the second device according to the device validity period, including:
  • a device activation request is sent.
  • 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.
  • the third device comprises an AF or a PEMC.
  • the network includes a PIN.
  • the second device comprises a PINE.
  • 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.
  • 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.
  • 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.
  • the first management module 710 is configured to initiate a PDU session release process to release user plane resources allocated to the network.
  • 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.
  • 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.
  • 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.
  • the first management module 710 is configured to initiate a service request process to activate a PDU session established for the network.
  • the first management module 710 is used to initiate a PDU session establishment process to establish a PDU session for the network.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 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.
  • the first device includes a session management function SMF or a personal Internet of Things device PEGC with gateway capabilities.
  • the third device includes an application function AF or a personal Internet of Things device PEMC with management capabilities.
  • the fourth device includes a unified data management function UDM.
  • the network includes a personal IoT PIN.
  • the second device includes a personal Internet of Things device PINE.
  • 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.
  • the second management module 910 is configured to send a network deactivation request when the network validity period ends.
  • 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.
  • the PDU session identifier and QoS flow identifier that carries the network service flow.
  • the second management module 910 is configured to send a network activation request when the network validity period begins.
  • 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.
  • the second management module 910 is configured to send a device deactivation request when the validity period of the device expires.
  • 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.
  • the second management module 910 is configured to send a device activation request when the validity period of the device begins.
  • 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.
  • the third device comprises an AF or a PEMC.
  • the network includes a PIN.
  • the second device comprises a PINE.
  • 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.).
  • 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.
  • 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.
  • 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 .
  • 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.
  • 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.
  • 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 .
  • 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.
  • 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.
  • 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.
  • 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.
  • DSP digital signal processor
  • FPGA field programmable gate array
  • ASIC application specific integrated circuit
  • 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.
  • 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).
  • 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.
  • the computer program product includes one or more computer instructions.
  • 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.
  • 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.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例提出管理方法和设备，其中管理方法包括，第一设备根据网络有效期和/或设备有效期，释放或建立网络和/或第二设备占用的通信资源。本申请实施例能够实现对网络/设备的管理，降低管理过程中的服务时延。

Description

管理方法和设备 技术领域
本申请涉及通信领域，并且更具体地，涉及管理方法和设备。
背景技术
相关技术中，针对网络/设备的有效期管理较为简单，例如，在网络/设备的有效期结束时，释放网络/设备占用的通信系统资源，并删除该网络/设备的配置信息；在网络/设备的有效期开始时，重新请求通信系统资源并进行通信配置。这种方式需要繁琐的操作，服务时延较大。
发明内容
本申请实施例提供管理方法和设备，能够对网络/设备进行有效期管理。
本申请实施例提供一种管理方法，包括：第一设备根据网络有效期和/或设备有效期，释放或建立网络和/或第二设备占用的通信资源。
本申请实施例提供一种管理方法，包括：第三设备根据网络有效期和/或设备有效期，触发对网络和/或第二设备占用的通信资源的释放或建立。
本申请实施例提供一种第一设备，包括：第一管理模块，用于根据网络有效期和/或设备有效期，释放或建立网络和/或第二设备占用的通信资源。
本申请实施例提供一种第三设备，包括：第二管理模块，用于根据网络有效期和/或设备有效期，触发对网络和/或第二设备占用的通信资源的释放或建立。
本申请实施例提供一种通信设备，包括处理器、存储器和收发器，该存储器用于存储计算机程序，该处理器用于调用并运行该存储器中存储的计算机程序、并控制该收发器，执行本申请实施例的任一方法。
本申请实施例提供一种芯片，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有该芯片的设备执行本申请实施例的任一方法。
本申请实施例提供一种计算机可读存储介质，用于存储计算机程序，该计算机程序使得计算机执行本申请实施例的任一方法。
本申请实施例提供一种计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行本申请实施例的任一方法。
本申请实施例提供一种计算机程序，该计算机程序使得计算机执行本申请实施例的任一方法。
本申请实施例，通过第一设备根据网络有效期和/或设备有效期，释放或建立网络和/或第二设备占用的通信资源，能够实现对网络/设备的管理，降低管理过程中的服务时延。
附图说明
图1示例性地示出了一种通信系统100。
图2是一种PIN结构示意图。
图3是根据本申请实施例的一种管理方法300的示意性流程图。
图4A是一个PDU会话只用于一组设备的示意图。
图4B是一个PDU会话用于多组设备的示意图。
图5A是根据本申请实施例的AF触发的PIN去激活的示意性流程图。
图5B是根据本申请实施例的AF触发的PIN重激活的示意性流程图。
图5C是根据本申请实施例的AF触发的PINE的去激活的示意性流程图。
图5D是根据本申请实施例的AF触发的PINE的重激活的示意性流程图。
图5E是根据本申请实施例的PEMC触发的PIN的去激活的示意性流程图。
图5F是根据本申请实施例的PEMC触发的PIN的重激活的示意性流程图。
图5G是根据本申请实施例的PEMC触发的PINE的去激活的示意性流程图。
图5H是根据本申请实施例的PEMC触发的PINE的重激活的示意性流程图。
图5I是根据本申请实施例的PEGC触发的PIN的去激活的示意性流程图。
图5J是根据本申请实施例的PEGC触发的PIN的重激活的示意性流程图。
图5K是根据本申请实施例的PEGC触发的PINE的去激活的示意性流程图。
图5L是根据本申请实施例的PEGC触发的PINE的重激活的示意性流程图。
图6是根据本申请一实施例的管理方法600的示意性流程图。
图7是根据本申请一实施例的第一设备700的示意性框图。
图8是根据本申请一实施例的第一设备800的示意性框图。
图9是根据本申请一实施例的第三设备900的示意性框图。
图10是根据本申请实施例的通信设备1000示意性结构图。
图11是根据本申请实施例的芯片1100的示意性结构图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。
需要说明的是，本申请实施例的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。同时描述的“第一”、“第二”描述的对象可以相同，也可以不同。
本申请实施例的技术方案可以应用于各种通信系统，例如：全球移动通讯(Global System of Mobile communication，GSM)系统、码分多址(Code Division Multiple Access，CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统、通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution，LTE)系统、先进的长期演进(Advanced long term evolution，LTE-A)系统、新无线(New Radio，NR)系统、NR系统的演进系统、非授权频谱上的LTE(LTE-based access to unlicensed spectrum，LTE-U)系统、非授权频谱上的NR(NR-based access to unlicensed spectrum，NR-U)系统、非地面通信网络(Non-Terrestrial Networks，NTN)系统、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、无线局域网(Wireless Local Area Networks，WLAN)、无线保真(Wireless Fidelity，WiFi)、第五代通信(5th-Generation，5G)系统或其它通信系统等。
通常来说，传统的通信系统支持的连接数有限，也易于实现，然而，随着通信技术的发展，移动通信系统将不仅支持传统的通信，还将支持例如，设备到设备(Device to Device，D2D)通信，机器到机器(Machine to Machine，M2M)通信，机器类型通信(Machine Type Communication，MTC)，车辆间(Vehicle to Vehicle，V2V)通信，或车联网(Vehicle to everything，V2X)通信等，本申请实施例也可以应用于这些通信系统。
在一种实施方式中，本申请实施例中的通信系统可以应用于载波聚合(Carrier Aggregation，CA)场景，也可以应用于双连接(Dual Connectivity，DC)场景，还可以应用于独立(Standalone，SA)布网场景。
在一种实施方式中，本申请实施例中的通信系统可以应用于非授权频谱，其中，非授权频谱也可以认为是共享频谱；或者，本申请实施例中的通信系统也可以应用于授权频谱，其中，授权频谱也可以认为是非共享频谱。
本申请实施例结合网络设备和终端设备描述了各个实施例，其中，终端设备也可以称为用户设备(User Equipment，UE)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置等。
终端设备可以是WLAN中的站点(STAION，ST)，可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)设备、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、下一代通信系统例如NR网络中的终端设备，或者未来演进的公共陆地移动网络(Public Land Mobile Network，PLMN)网络中的终端设备等。
在本申请实施例中，终端设备可以部署在陆地上，包括室内或室外、手持、穿戴或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。
在本申请实施例中，终端设备可以是手机(Mobile Phone)、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(Virtual Reality，VR)终端设备、增强现实(Augmented Reality，AR)终端设备、工业控制(industrial control)中的无线终端设备、无人驾驶(self driving)中的无线终端设备、远程医疗(remote medical)中的无线终端设备、智能电网(smart grid)中的无线终端设备、运输安全(transportation safety)中的无线终端设备、智慧城市(smart city)中的无线终端设备或智慧家庭(smart home)中的无线终端设备等。
作为示例而非限定，在本申请实施例中，该终端设备还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的 功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
在本申请实施例中，网络设备可以是用于与移动设备通信的设备，网络设备可以是WLAN中的接入点(Access Point，AP)，GSM或CDMA中的基站(Base Transceiver Station，BTS)，也可以是WCDMA中的基站(NodeB，NB)，还可以是LTE中的演进型基站(Evolutional Node B，eNB或eNodeB)，或者中继站或接入点，或者车载设备、可穿戴设备以及NR网络中的网络设备(gNB)或者未来演进的PLMN网络中的网络设备或者NTN网络中的网络设备等。
作为示例而非限定，在本申请实施例中，网络设备可以具有移动特性，例如网络设备可以为移动的设备。可选地，网络设备可以为卫星、气球站。例如，卫星可以为低地球轨道(low earth orbit，LEO)卫星、中地球轨道(medium earth orbit，MEO)卫星、地球同步轨道(geostationary earth orbit，GEO)卫星、高椭圆轨道(High Elliptical Orbit，HEO)卫星等。可选地，网络设备还可以为设置在陆地、水域等位置的基站。
在本申请实施例中，网络设备可以为小区提供服务，终端设备通过该小区使用的传输资源(例如，频域资源，或者说，频谱资源)与网络设备进行通信，该小区可以是网络设备(例如基站)对应的小区，小区可以属于宏基站，也可以属于小小区(Small cell)对应的基站，这里的小小区可以包括：城市小区(Metro cell)、微小区(Micro cell)、微微小区(Pico cell)、毫微微小区(Femto cell)等，这些小小区具有覆盖范围小、发射功率低的特点，适用于提供高速率的数据传输服务。
图1示例性地示出了一种通信系统100。该通信系统包括一个网络设备110和两个终端设备120。在一种实施方式中，该通信系统100可以包括多个网络设备110，并且每个网络设备110的覆盖范围内可以包括其它数量的终端设备120，本申请实施例对此不做限定。
在一种实施方式中，该通信系统100还可以包括移动性管理实体(Mobility Management Entity，MME)、接入与移动性管理功能(Access and Mobility Management Function，AMF)等其它网络实体，本申请实施例对此不作限定。
其中，网络设备又可以包括接入网设备和核心网设备。即无线通信系统还包括用于与接入网设备进行通信的多个核心网。接入网设备可以是长期演进(long-term evolution，LTE)系统、下一代(移动通信系统)(next radio，NR)系统或者授权辅助接入长期演进(authorized auxiliary access long-term evolution，LAA-LTE)系统中的演进型基站(evolutional node B，简称可以为eNB或e-NodeB)宏基站、微基站(也称为“小基站”)、微微基站、接入站点(access point，AP)、传输站点(transmission point，TP)或新一代基站(new generation Node B，gNodeB)等。
应理解，本申请实施例中网络/系统中具有通信功能的设备可称为通信设备。以图1示出的通信系统为例，通信设备可包括具有通信功能的网络设备和终端设备，网络设备和终端设备可以为本申请实施例中的具体设备，此处不再赘述；通信设备还可包括通信系统中的其它设备，例如网络控制器、移动管理实体等其它网络实体，本申请实施例中对此不做限定。
应理解，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
应理解，在本申请的实施例中提到的“指示”可以是直接指示，也可以是间接指示，还可以是表示具有关联关系。举例说明，A指示B，可以表示A直接指示B，例如B可以通过A获取；也可以表示A间接指示B，例如A指示C，B可以通过C获取；还可以表示A和B之间具有关联关系。
在本申请实施例的描述中，术语“对应”可表示两者之间具有直接对应或间接对应的关系，也可以表示两者之间具有关联关系，也可以是指示与被指示、配置与被配置等关系。
为便于理解本申请实施例的技术方案，以下对本申请实施例的相关技术进行说明，以下相关技术作为可选方案与本申请实施例的技术方案可以进行任意结合，其均属于本申请实施例的保护范围。
物联网设备可以分为可穿戴设备，(如相机、耳机、手表、耳机、健康监视器)，家居生活设备(如智能灯、相机、恒温器、门传感器、语音助手、扬声器、冰箱、洗衣机、割草机、机器人)，办公或者工厂设备(例如打印机、仪表、传感器)。用户可以在他们的家中、办公室、工厂或者他们的身体周围使用这些物联网设备创建(例如，规划、更改拓扑)个人的网络。
目前除了一些可穿戴设备，其他类型的物联网设备只能通过中继设备、网关接入互联网或者通过移动手机接入移动网络。在这两种情况下，核心网是无法意识到物联网设备接入到了移动网络中。然而，为了充分利用5G系统来对物联网设备进行辅助管理与业务支持，赋能5G系统参与个人物联网是不可 或缺的。图2是一种PIN结构示意图，如图2所示，用户创建的个人物联网(PIN，Personal IoT Network)包含一组个人物联网元素/个人物联网设备(PINE，PIN Element)，并可以对这组物联网设备进行配置和管理。这些物联网设备之间能够直接或通过具有网关能力的PIN元素相互通信，或者通过至少一个PEGC与5G网络通信，并由至少一个具有管理能力的PIN元素管理。物联网设备可以是一个具有接入5G系统能力的UE，也可以是一个仅能通过WiFi、蓝牙等方式进行通信的非3GPP设备。一个能够为其他PINE提供与5G网络的连接，或为PINE之间的通信提供中继的PINE被称为具有网关功能的物联网设备(PEGC，PIN Element with Gateway Capability)。而能够对PIN进行管理的PINE被称为具有管理功能的物联网设备(PEMC，PIN Element with Management Capability)。
在一个PIN被创建后，PEMC可以将一个PINE或者PEGC加入PIN，或者从PIN中移除一个PINE或者PEGC，也可以将某个PINE关联到已加入网络中的PEGC上。此外，PEMC可以通过启动一个计时器来设置PIN网络的持续时间，PIN网络的持续时间取决于运营商的策略或第三方策略。在PIN持续时间结束时，PEMC将停用PIN，并删除其所有与PIN相关的存储库，并向PIN设备广播有关PIN停用的信息。一旦PIN被停用，PEMC将会通知5GC和网络中的PINE，该设备已经被停用。
本申请实施例提出的管理方法，可以适用于PIN网络、或者适用于其他局域网等网络。在相关技术方案中，PIN有效期的管理粒度较为粗糙，并且不支持离散的有效期配置。当有效期为多个离散的时间段时，例如每日2:00-3:00。按照现有技术将在第一个时间段结束后就停用了相应的PIN网络，并释放存储的PIN配置信息。而到了第二段有效期时，就需要重新发起PIN网络的建立流程以及PIN通信配置，例如PINE ID分配和地址分配，PIN参数配置，流量路由管理等繁琐的操作。这大大增加了服务时延，影响用户体验。此外，现有技术中对如何支持PIN有效期管理尚不明确，并未涉及有效期执行等流程的细节描述。
本申请实施例提出的管理方法基于有效期对网络/设备进行管理。具体地，本申请实施例将有效期分为网络有效期、设备有效期两个维度，并且基于有效期对网络和设备进行建立/释放、激活/去激活等管理操作。
在一些示例中，网络有效期表示一组设备所组成的网络的活跃时间。当网络有效期结束时，该网络被释放或者切换到不活跃状态。具体地，如果网络有效期为固定的时长，则当网络有效期结束时释放该网络，例如释放分配给该网络的5G系统(5GS，5G System)资源、删除存储在统一数据管理(UDM，Unified Data Management)中的配置信息；如果有效期为不连续时段，则当网络有效期结束时将该网络切换为不活跃，例如释放分配给该网络的5GS资源，保留存储的网络配置信息，以待下一个有效期时段到来后重新激活网络。
在一些示例中，设备有效期表示设备在网络中的活跃时间。当设备有效期结束时，该设备被网络移除，或者被切换到不活跃状态。具体地，如果设备有效期为固定的时长，则当设备有效期结束时，将该设备从网络中移除；如果设备有效期为不连续的时段，则当设备有效期结束时，将该设备切换为不活跃状态，即释放该网络分配给该设备的资源，但保留该设备在网络中的配置信息。
网络有效期和/或设备有效期的参数配置可以被静态地配置在设备中、或者UDM等5G核心网(5GC，5G core)网元中，也可以由应用功能(AF，Application function)动态配置。当有效期信息配置在AF中时，AF可以根据有效期定时器(timer)到期后，触发PIN/PINE去激活和重激活。而当有效期信息配置在物联网设备PEMC/PEGC中时，PEMC在有效期定时器(timer)到期后，触发PIN/PINE去激活和重激活。
图3是根据本申请实施例的一种管理方法300的示意性流程图，该方法可以应用于图1或2所示的系统，但并不仅限于此。该方法包括以下内容的至少部分内容。
S310：第一设备根据网络有效期和/或设备有效期，释放或建立网络和/或第二设备占用的通信资源。
在以下内容中，以本申请实施例提出的管理方法应用于PIN为例进行介绍。本申请实施例提出的管理方法不仅适用于PIN，也适用于其他需要使用5GS资源的网络及设备。
在一些实施方式中，第一设备包括SMF或PEGC。
在一些实施方式中，第三设备包括AF或PEMC。
在一些实施方式中，网络包括PIN，第二设备包括PINE。相应地，网络有效期可以包括PIN有效期，用于对PIN进行管理，如根据PIN有效期释放或建立PIN占用的通信资源；设备有效期可以包括PINE有效期，用于对PINE进行管理，如根据PINE有效期释放或建立PINE占用的通信资源。
(一)、第一设备根据网络有效期，释放网络占用的通信资源：
相关技术中，一个PDU会话可以只用于一组设备(如一个PIN)、或者用于多组设备(如多个PIN)，如图4A和4B所示。针对前述两种情况，在一些实施方式中，第一设备根据网络有效期，释放网络占用的通信资源，可以包括：
在网络有效期结束时，第一设备发起用户面去激活流程、PDU会话释放流程或PDU会话修改流程，以释放网络占用的通信资源。
例如，针对一个PDU会话只用于一个PIN的情况，第一设备可以发起用户面去激活流程，以释放承载该网络的业务的PDU会话的无线资源和/或通道。这种情况下，第一设备可以是网络侧设备，如SMF。
又如，针对一个PDU会话只用于一个PIN的情况，第一设备发起PDU会话释放流程，以释放为网络分配的用户面资源。
或者，针对一个PDU会话用于多个PIN的情况，第一设备发起PDU会话修改流程，以删除PDU会话中对应该网络的服务质量(QoS，Quality of Service)流。
如果网络有效期配置在第一设备中，则第一设备可以在网络有效期结束时，主动发起用户面去激活流程、PDU会话释放流程或PDU会话修改流程，以释放网络占用的通信资源。如果网络有效期配置在其他设备(如第三设备)中，则第一设备可以基于其他设备(如第三设备)的触发，发起用户面去激活流程、PDU会话释放流程或PDU会话修改流程，以释放网络占用的通信资源。在第一网络设备是SMF的情况下，第三网络设备可以为AF或PEMC。在第一网络设备是PEMC的情况下，第三网络设备可以为AF。当第一设备是PEGC时，第三设备可以是PEMC。
在一些实施方式中，第一设备接收网络去激活请求，该网络去激活请求由第三设备在该网络的网络有效期结束时发送。例如，第三设备中保存网络有效期配置，在网络的网络有效期结束时，第三设备向第一设备发送网络去激活请求。
示例性地，该网络去激活请求中可以携带以下至少之一：
网络去激活指示；
该网络的标识；
该网络中的管理设备的标识；
该网络中的网关设备的标识；
承载该网络业务流的PDU会话标识和QoS流标识。
以该网络为PIN为例，该网络中的管理设备可以为PEMC，该网络中的网关设备可以为PEGC。
第一设备接收到网络去激活请求后，可以释放该网络占用的通信资源。
在一些实施方式中，第一设备可以基于网络的配置信息，释放网络占用的通信资源。
示例性地，第一设备可以从第四设备获取网络的配置信息。例如，采用以下方式获取：
第一设备向第四设备发送网络配置查询请求；
第一设备从第四设备接收网络的配置信息。
网络配置查询请求中可以携带该网络的标识信息，如PIN ID。
第四设备可以包括UDM。
网络的配置信息可以包括以下至少之一：
网络的拓扑信息；
网络的标识；
网络中的管理设备的标识；
网络中的设备的标识；
承载网络业务流的PDU会话标识和/或QoS流标识。
其中，网络的拓扑信息可以包括以下至少之一：
网络中设备与管理设备之间的关联关系；
网络中设备与网关设备之间的关联关系；
网络中设备与其他设备之间的关联关系。
以PIN为例，PIN的拓扑信息可以包括PIN中的PINE与PEMC之间的关联关系、PIN中的PINE与PEGC之间的关联关系、PIN中的PINE与其他PINE之间的关联关系。
基于网络的配置信息，第一设备可以释放该网络占用的通信资源，无需删除网络的配置信息，例如，无需删除存储网络中及PIN管理实体(例如PEMC和/或AF)中的PIN配置信息。从而在提高通信资源利用率的同时，避免了网络和设备在重激活时进行重复的网络建立与配置，以及PIN通信配置，例如PINE ID分配和地址分配，PIN参数配置，流量路由管理等繁琐的操作。尤其是对于有效期为不连续的时段的场景，能够降低网络重建、设备激活时延，加快网络、设备继续提供服务的响应适度，从而提高用户体验，并一定程度上减少了网络重复建立/释放、设备重复添加删除所带来地信令负载。
PEGC或PEMC可以释放分配给该网络(如PIN)的WiFi，蓝牙等通信资源，并向该PIN内的PINE发出通知，以通知其所在的PIN已经被去激活。
(二)、第一设备根据网络有效期，建立(或重建)网络占用的通信资源：
在一些实施方式中，第一设备根据网络有效期，建立网络占用的通信资源，可以包括：
在网络有效期开始时，第一设备发起服务请求流程、PDU会话建立流程或PDU会话修改流程，以建立(或重建)该网络占用的通信资源。
例如，针对一个PDU会话只用于一个PIN的情况，第一设备可以发起服务请求流程，以激活为该网络建立的PDU会话；或者，第一设备可以发起PDU会话建立流程，为该网络建立PDU会话。
又如，针对一个PDU会话用于多个PIN的情况，第一设备发起PDU会话修改流程，以建立PDU会话中对应所述网络的QoS流。
如果网络有效期配置在第一设备中，则第一设备可以在网络有效期开始时，主动发起服务请求流程、PDU会话建立流程或PDU会话修改流程，以建立(或重建)该网络占用的通信资源。如果网络有效期配置在其他设备(如第三设备)中，则第一设备可以基于其他设备(如第三设备)的触发，发起服务请求流程、PDU会话建立流程或PDU会话修改流程，以建立(或重建)该网络占用的通信资源。在第一网络设备是SMF的情况下，第三网络设备可以为AF或PEMC。在第一网络设备是PEMC的情况下，第三网络设备可以为AF。当第一设备是PEGC时，第三设备可以是PEMC。
在一些实施方式中，第一设备接收网络激活(或重激活)请求，该网络激活请求由第三设备在该网络的网络有效期开始时发送。例如，第三设备中保存网络有效期配置，在网络的网络有效期开始时，第三设备向第一设备发送网络激活请求。
示例性地，该网络激活请求中可以携带以下至少之一：
网络激活指示；
该网络的标识；
该网络中的管理设备的标识；
该网络中的网关设备的标识；
承载该网络业务流的PDU会话标识和/或QoS流标识。
以该网络为PIN为例，该网络中的管理设备可以为PEMC，该网络中的网关设备可以为PEGC。
第一设备接收到网络去激活请求后，可以建立(或重建)该网络占用的通信资源。
在一些实施方式中，第一设备可以基于网络的配置信息，建立网络占用的通信资源。
示例性地，第一设备可以从第四设备获取网络的配置信息。例如，采用以下方式获取：
第一设备向第四设备发送网络配置查询请求；
第一设备从第四设备接收网络的配置信息。
网络配置查询请求中可以携带该网络的标识信息，如PIN ID。
第四设备可以包括UDM。
网络的配置信息可以包括以下至少之一：
网络的拓扑信息；
网络的标识；
网络中的管理设备的标识；
网络中的设备的标识；
承载网络业务流的PDU会话标识和/或QoS流标识。
其中，网络的拓扑信息可以包括以下至少之一：
网络中设备与管理设备之间的关联关系；
网络中设备与网关设备之间的关联关系；
网络中设备与其他设备之间的关联关系。
以PIN为例，PIN的拓扑信息可以包括PIN中的PINE与PEMC之间的关联关系、PIN中的PINE与PEGC之间的关联关系、PIN中的PINE与其他PINE之间的关联关系。
基于网络的配置信息，第一设备可以建立(或重建)该网络占用的通信资源，无需重新配置网络的配置信息，例如，无需重新配置PIN配置信息。从而在提高通信资源利用率的同时，避免了网络和设备在重激活时进行重复的网络建立与配置，以及PIN通信配置，例如PINE ID分配和地址分配，PIN参数配置，流量路由管理等繁琐的操作。尤其是对于有效期为不连续的时段的场景，能够降低网络重建、设备激活时延，加快网络、设备继续提供服务的响应适度，从而提高用户体验，并一定程度上减少了网络重复建立/释放、设备重复添加删除所带来地信令负载。
PEGC或PEMC可以重新为该该网络(如PIN)中的PINE分配WiFi，蓝牙等通信资源；并向该PIN中的PINE发出通知，以通知其所在的PIN已经被激活。
(三)、第一设备根据网络有效期，释放第二设备占用的通信资源：
在一些实施方式中，第一设备根据网络有效期，释放第二设备占用的通信资源，可以包括：
在第二设备有效期结束时，第一设备发起PDU会话修改流程，以释放第二设备占用的通信资源。
例如，第一设备发起PDU会话修改流程，以删除PDU会话中对应该第二设备的QoS流。
如果设备有效期配置在第一设备中，则第一设备可以在设备有效期结束时，主动发起PDU会话修改流程，以删除PDU会话中对应该第二设备的QoS流。如果设备有效期配置在其他设备(如第三设备)中，则第一设备可以基于其他设备(如第三设备)的触发，发起PDU会话修改流程，以删除PDU会话中对应该第二设备的QoS流。在第一网络设备是SMF的情况下，第三网络设备可以为AF或PEMC。在第一网络设备是PEMC的情况下，第三网络设备可以为AF。当第一设备是PEGC时，第三设备可以是PEMC。
在一些实施方式中，第一设备接收设备去激活请求，该设备去激活请求由第三设备在第二设备的设备有效期结束时发送。
例如，第三设备中保存网络有效期配置，在第二设备的设备有效期结束时，第三设备向第一设备发送设备去激活请求。
示例性地，设备去激活请求中携带以下至少之一：
设备去激活指示；
所述第二设备的标识；
所述第二设备所属网络的标识；
与所述第二设备关联的管理设备的标识；
与所述第二设备关联的网关设备的标识；
承载所述第二设备业务流的PDU会话标识和/或QoS流标识。
以该网络为PIN为例，第二设备为PINE，与第二设备关联的管理设备可以为与该PINE关联的PEMC，与第二设备关联的网关设备可以为与该PINE关联的PEGC。
第一设备接收到设备去激活请求后，可以释放该第二设备占用的通信资源。
在一些实施方式中，第一设备可以基于第二设备的配置信息，释放第二设备占用的通信资源。
示例性地，第一设备可以从第四设备获取第二设备的配置信息。例如，采用以下方式获取：
第一设备向第四设备发送设备配置查询请求；
第一设备从第四设备接收第二设备的配置信息。
第四设备可以包括UDM。
在一些实施方式中，设备配置查询请求中携带以下至少之一：
第二设备的标识；
第二设备所属网络的标识；
与第二设备关联的管理设备的标识；
与第二设备关联的网关设备的标识。
以PIN为例，设备配置查询请求中可以携带PINE ID、该PINE所属PIN的PIN ID、与该PINE关联的PEMC的ID、与该PINE关联的PEGC的ID中的至少之一。
在一些实施方式中，第二设备的配置信息包括以下至少之一：
第二设备的标识；
与第二设备关联的管理设备的标识；
与第二设备关联的网关设备的标识；
承载第二设备业务流的PDU会话标识和/或QoS流标识。
以PIN为例，第二设备的配置信息可以包括PINE ID、与该PINE关联的PEMC的ID、与该PINE关联的PEGC的ID、承载该PINE业务流的中的PDU会话标识和/或QoS流标识中的至少之一。
基于第二设备的配置信息，第一设备可以释放该第二设备占用的通信资源，无需重新配置第二设备的配置信息，例如，无需重新配置PINE配置信息。从而在提高通信资源利用率的同时，避免了设备在重激活时进行重复的网络建立与配置，以及PINE通信配置，例如PINE ID分配和地址分配，PIN参数配置，流量路由管理等繁琐的操作。尤其是对于有效期为不连续的时段的场景，能够降低网络重建、设备激活时延，加快网络、设备继续提供服务的响应适度，从而提高用户体验，并一定程度上减少了网络重复建立/释放、设备重复添加删除所带来地信令负载。
PEGC或PEMC可以释放分配给该第二设备(如PINE)的WiFi，蓝牙等通信资源，并通知所关联的目标PINE在目标PIN中已经被切换至去激活状态。
(四)、第一设备根据网络有效期，建立(或重建)第二设备占用的通信资源：
在一些实施方式中，第一设备根据网络有效期，建立第二设备占用的通信资源，可以包括：
在第二设备有效期开始时，第一设备发起PDU会话修改流程，以建立第二设备占用的通信资源。
例如，第一设备发起PDU会话修改流程，以建立PDU会话中对应该第二设备的QoS流。
如果设备有效期配置在第一设备中，则第一设备可以在设备有效期开始时，主动发起PDU会话修改流程，以建立PDU会话中对应该第二设备的QoS流。如果设备有效期配置在其他设备(如第三设备)中，则第一设备可以基于其他设备(如第三设备)的触发，发起PDU会话修改流程，以建立PDU会话中对应该第二设备的QoS流。在第一网络设备是SMF的情况下，第三网络设备可以为AF或PEMC。在第一网络设备是PEMC的情况下，第三网络设备可以为AF。当第一设备是PEGC时，第三设备可以是PEMC。
在一些实施方式中，第一设备接收设备激活请求，该设备激活请求由第三设备在第二设备的设备有效期开始时发送。
例如，第三设备中保存网络有效期配置，在第二设备的设备有效期开始时，第三设备向第一设备发送设备激活请求。
示例性地，设备激活请求中携带以下至少之一：
设备激活指示；
所述第二设备的标识；
所述第二设备所属网络的标识；
与所述第二设备关联的管理设备的标识；
与所述第二设备关联的网关设备的标识；
承载所述第二设备业务流的PDU会话标识和/或QoS流标识。
以该网络为PIN为例，第二设备为PINE，与第二设备关联的管理设备可以为与该PINE关联的PEMC，与第二设备关联的网关设备可以为与该PINE关联的PEGC。
第一设备接收到设备激活请求后，可以建立该第二设备占用的通信资源。
在一些实施方式中，第一设备可以基于第二设备的配置信息，建立第二设备占用的通信资源。
示例性地，第一设备可以从第四设备获取第二设备的配置信息。例如，采用以下方式获取：
第一设备向第四设备发送设备配置查询请求；
第一设备从第四设备接收第二设备的配置信息。
第四设备可以包括UDM。
在一些实施方式中，设备配置查询请求中携带以下至少之一：
第二设备的标识；
第二设备所属网络的标识；
与第二设备关联的管理设备的标识；
与第二设备关联的网关设备的标识。
以PIN为例，设备配置查询请求中可以携带PINE ID、该PINE所属PIN的PIN ID、与该PINE关联的PEMC的ID、与该PINE关联的PEGC的ID中的至少之一。
在一些实施方式中，第二设备的配置信息包括以下至少之一：
第二设备的标识；
与第二设备关联的管理设备的标识；
与第二设备关联的网关设备的标识；
承载第二设备业务流的PDU会话标识和/或QoS流标识。
以PIN为例，第二设备的配置信息可以包括PINE ID、与该PINE关联的PEMC的ID、与该PINE关联的PEGC的ID、承载该PINE业务流的中的PDU会话标识和/或QoS流标识中的至少之一。
基于第二设备的配置信息，第一设备可以建立(或重建)该第二设备占用的通信资源，无需重新配置第二设备的配置信息，例如，无需重新配置PINE配置信息。从而在提高通信资源利用率的同时，避免了设备在重激活时进行重复的网络建立与配置，以及PINE通信配置，例如PINE ID分配和地址分配，PIN参数配置，流量路由管理等繁琐的操作。尤其是对于有效期为不连续的时段的场景，能够降低网络重建、设备激活时延，加快网络、设备继续提供服务的响应适度，从而提高用户体验，并一定程度上减少了网络重复建立/释放、设备重复添加删除所带来地信令负载。
PEGC或PEMC可以重新为该第二设备(如PINE)分配WiFi、蓝牙等通信资源，并通知所关联的目标PINE在目标PIN中已经被切换至激活状态。
除上述四种方式之外，第一设备根据网络有效期和/或设备有效期，释放或建立网络和/或第二设备占用的通信资源。如，第一设备在网络有效期结束时，释放网络占用的通信资源；并且在设备有效期结束时，释放第二设备占用的通信资源。又如，第一设备在网络有效期结束时，释放网络占用的通信资源； 并且在设备有效期开始时，建立第二设备占用的通信资源。又如，第一设备在网络有效期开始时，建立网络占用的通信资源；并且在设备有效期结束时，释放第二设备占用的通信资源。又如，第一设备在网络有效期开始时，建立网络占用的通信资源；并且在设备有效期开始时，建立第二设备占用的通信资源。
以网络为PIN、第二设备为PINE为例。第一设备可以在PIN 1的有效期结束时，释放该PIN 1占用的通信资源；并且在PINE 1的有效期结束时，释放该PINE 1占用的通信资源。或者，第一设备可以在PIN 1的有效期结束时，释放该PIN 1占用的通信资源；并且在PINE 1的有效期开始时，建立该PINE1占用的通信资源。或者，第一设备可以在PIN 1的有效期开始时，建立该PIN 1占用的通信资源；并且在PINE 1的有效期结束时，释放该PINE 1占用的通信资源。或者，第一设备可以在PIN 1的有效期开始时，建立该PIN 1占用的通信资源；并且在PINE 1的有效期开始时，建立该PINE 1占用的通信资源。上述示例中的PINE 1可以不属于PIN 1。
以下结合附图，介绍具体的实施方式。
实施例一：AF触发的PIN去激活
如图5A所示，AF根据有效期设置可以触发PIN的去激活，释放分配给该PIN的5GS资源，具体步骤如下：
1.当PIN有效期结束(到期)时，AF通过网络开放功能(NEF，Network Exposure Function)向PCF发送PIN去激活请求，该消息中包括PIN去激活指示，PIN ID。
2.PCF将PIN去激活请求转发给SMF，该消息中携带PIN去激活指示，PIN ID。
3.SMF向UDM发起PIN配置信息查询请求，该消息携带PIN ID。
4.UDM向SMF返回PIN配置信息，PIN配置信息可以包括PIN网络的拓扑信息、PIN ID、PIN中PEGC的ID，PIN中PEMC的ID，承载PIN业务流的PDU会话ID和/或QoS ID。PIN网络的拓扑信息可以包括PIN中各个PINE与PEGC之间的关联关系、PIN中各个PINE与PEMC之间的关联关系、PIN中不同PINE之间的关联关系等。
5.当一个PDU会话只用于一个PIN时(如图4A所示)，SMF将会发起用户面去激活过程，释放该PIN网络中所有PEGC、PEMC所建立的承载该PIN业务的PDU会话的无线资源(如DRB)与N3通道(N3 tunnel)；当一个PDU会话被用于多个PIN时(如图4B所示)，SMF将会发起PDU会话修改流程，删除目标PIN对应的QoS流。此外，上述用户面去激活过程、PDU会话修改流程会额外携带PIN去激活指示以及PIN ID。
6.PEGC释放分配给目标PIN的WiFi，蓝牙等通信资源，并通知所关联的属于目标PIN的PINE所在的目标PIN已经被去激活。
实施例二：AF触发的PIN激活(重激活)
如图5B所示，AF根据有效期设置可以触发PIN的重激活，重新为该PIN分配5GS资源，并恢复PINE与PEGC之间的通信资源，具体步骤如下：
1.当PIN有效期开始时，AF通过NEF向PCF发送PIN重激活请求，该消息中包括PIN重激活指示，PIN ID。
2.PCF将PIN重激活请求转发给SMF，该消息中携带PIN重激活指示，PIN ID。
3.SMF向UDM发起PIN配置信息查询请求，该消息携带PIN ID。
4.UDM向SMF返回PIN配置信息，PIN配置信息可以包括PIN网络的拓扑信息、PIN ID、PIN中PEGC的ID，PIN中PEMC的ID，承载PIN业务流的PDU会话ID和/或QoS ID。PIN网络的拓扑信息可以包括PIN中各个PINE与PEGC之间的关联关系、PIN中各个PINE与PEMC之间的关联关系、PIN中不同PINE之间的关联关系等。
5.当一个PDU会话只用于一个PIN时(如图4A所示)，SMF发起服务请求过程，基于第四步中获取的PEGC ID、PIN ID、PDU会话ID等信息重新激活PIN网络中PDU会话；当一个PDU会话被用于多个PIN时(如图4B所示)，SMF将会发起PDU会话修改流程，根据目标PIN中PINE与PEGC之间的流量路由关系重新建立QoS流。此外，上述服务请求过程、PDU会话修改流程可以额外携带PIN重激活指示以及PIN ID。
6.PEGC重新为目标PIN中的PINE分配WiFi，蓝牙等通信资源，并通知所关联的属于目标PIN的PINE所在的目标PIN已经被重新激活。
实施例三：AF触发的PINE的去激活
如图5C所示，AF根据有效期设置可以触发PINE的去激活，释放为该PINE分配的5GS资源，具体步骤如下：
1.当PINE有效期到期时，AF通过(NEF，Network Exposure Function)向PCF发送PINE去激活请求，该消息中包括PINE去激活指示，PIN ID，PINE ID，与目标PINE关联的PEGC ID，与目标PINE 关联的PEMC ID中的至少之一。
2.PCF将PINE去激活请求转发给SMF，该消息中携带PINE去激活指示，PIN ID，PINE ID，与目标PINE关联的PEGC ID，与目标PINE关联的PEMC ID中的至少之一。
3.SMF向UDM发起PINE配置信息查询请求，该消息携带PIN ID，PINE ID，与目标PINE关联的PEGC ID。
4.UDM向SMF返回PINE配置信息，包括目标PIN中和目标PINE相关联的PEGC ID，以及PEGC为其建立的承载目标PINE业务流量的PDU会话ID、QoS流标识(QoS flow ID)(即QFI)。
5.SMF将会发起PDU会话修改流程，基于第四步中获取的PEGC ID，PINE ID，PDU会话ID、QFI等信息，释放目标PINE对应的QoS流。上述PDU会话修改流程会额外携带PINE去激活指示、PIN ID、PINE ID。
6.PEGC释放分配给目标PINE的WiFi、蓝牙等通信资源，并通知所关联的目标PINE在目标PINE中已经被切换至去激活状态。
实施例四：AF触发的PINE的激活(重激活)
如图5D所示，AF根据有效期设置可以触发PINE的激活，重新为该PINE分配5GS资源，具体步骤如下：
1.AF通过NEF向PCF发送PINE激活请求，该消息中包括PINE激活指示，PIN ID，PINE ID，与目标PINE关联的PEGC ID，与目标PINE关联的PEMC ID中的至少之一。
2.PCF将PINE激活请求转发给SMF，该消息中携带PINE激活指示，PIN ID，PINE ID，与目标PINE关联的PEGC ID，与目标PINE关联的PEMC ID中的至少之一。
3.SMF向UDM发起PIN配置信息查询请求，该消息携带PIN ID，PINE ID，与目标PINE关联的PEGC ID，与目标PINE关联的PEMC ID中的至少之一。
4.UDM向SMF返回PIN配置信息，包括目标PIN中和目标PINE相关联的PEGC ID，以及PEGC为其建立的承载目标PINE业务流量的PDU会话ID、QoS flow ID(即QFI)。
5.SMF将会发起PDU会话修改流程，根据目标PIN中PINE与PEGC之间的流量路由关系重新建立QoS流。此外，上述PDU会话修改流程会额外携带PINE激活指示、PIN ID、PINE ID。
6.PEGC重新分配给目标PINE的WiFi、蓝牙等通信资源，并通知所关联的目标PINE在目标PIN中已经被切换至激活状态。
实施例五：PEMC触发的PIN的去激活
如图5E所示，当PEMC与PEGC异地部署时，PEMC可以根据有效期设置通过网络侧触发PIN的去激活，释放为该PIN分配5GS资源，具体步骤如下：
1.当PIN有效期到期时，PEMC通过无线接入网(RAN，Radio Access Network)向AMF发送PIN去激活请求，该消息中包括PIN去激活指示，PIN ID。
2.AMF将PIN去激活请求转发给SMF，该消息中携带PIN去激活指示，PIN ID。
3.SMF向UDM发起PIN配置信息查询请求，该消息携带PIN ID。
4.UDM向SMF返回PIN配置信息，PIN配置信息可以包括PIN网络的拓扑信息、PIN ID、PIN中PEGC的ID，PIN中PEMC的ID，承载PIN业务流的PDU会话ID和/或QoS ID。PIN网络的拓扑信息可以包括PIN中各个PINE与PEGC之间的关联关系、PIN中各个PINE与PEMC之间的关联关系、PIN中不同PINE之间的关联关系等。
5.当一个PDU会话只用于一个PIN时(如图4A所示)，SMF将会发起用户面去激活过程，释放该PIN网络中所有PEGC、PEMC所建立的承载该PIN业务的PDU会话的无线资源(如DRB)与N3通道(N3 tunnel)；当一个PDU会话被用于多个PIN时(如图4B所示)，SMF将会发起PDU会话修改流程，删除目标PIN对应的QoS流。此外，上述用户面去激活过程、PDU会话修改流程会额外携带PIN去激活指示以及PIN ID。
6.PEGC释放分配给目标PIN的WiFi，蓝牙等通信资源，并通知所关联的属于目标PIN的PINE所在的目标PIN已经被去激活。
实施例六：PEMC触发的PIN的重激活
如图5F所示，当PEMC与PEGC异地部署时，PEMC可以根据有效期设置通过网络侧触发PIN的重激活，重新为该PIN分配5GS资源，并恢复PINE与PEGC之间的通信资源，具体步骤如下：
1.PEMC通过RAN向AMF发送PIN激活请求，该消息中包括PIN激活指示，PIN ID。
2.AMF将PIN激活请求转发给SMF，该消息中携带PIN激活指示，PIN ID。
3.SMF向UDM发起PIN配置信息查询请求，该消息携带PIN ID。
4.UDM向SMF返回PIN配置信息，PIN配置信息可以包括PIN网络的拓扑信息、PIN ID、PIN中 PEGC的ID，PIN中PEMC的ID，承载PIN业务流的PDU会话ID和/或QoS ID。PIN网络的拓扑信息可以包括PIN中各个PINE与PEGC之间的关联关系、PIN中各个PINE与PEMC之间的关联关系、PIN中不同PINE之间的关联关系等。
5.当一个PDU会话只用于一个PIN时(如图4A所示)，SMF发起服务请求过程，基于第四步中获取的PEGC ID、PIN ID、PDU会话ID等信息重新激活PIN网络中PDU会话；当一个PDU会话被用于多个PIN时(如图4B所示)，SMF将会发起PDU会话修改流程，根据目标PIN中PINE与PEGC之间的流量路由关系重新建立QoS流。此外，上述服务请求过程、PDU会话修改流程可以额外携带PIN重激活指示以及PIN ID。
6.PEGC重新为目标PIN中的PINE分配WiFi，蓝牙等通信资源，并通知所关联的属于目标PIN的PINE所在的目标PIN已经被重新激活。
实施例七：PEMC触发的PINE的去激活
如图5G所示，当PEMC与目标PINE以及目标PINE关联的PEGC异地部署时，PEMC根据有效期设置可以通过网络侧触发PINE的去激活，释放为该PINE分配5GS资源，具体步骤如下：
1.当PINE有效期到期时，PEMC通过RAN向AMF发送PINE去激活请求，该消息中包括PINE去激活指示，PIN ID，PINE ID，与目标PINE关联的PEGC ID，与目标PINE关联的PEMC ID中的至少之一。
2.AMF将PINE去激活请求转发给SMF，该消息中包括PINE去激活指示，PIN ID，PINE ID，与目标PINE关联的PEGC ID，与目标PINE关联的PEMC ID中的至少之一。
3.SMF向UDM发起PINE配置信息查询请求，该消息携带PIN ID，PINE ID，与目标PINE关联的PEGC ID。
4.UDM向SMF返回PINE配置信息，包括目标PIN中和目标PINE相关联的PEGC ID，以及PEGC为其建立的承载目标PINE业务流量的PDU会话ID、QoS流标识(QoS flow ID)(即QFI)。
5.SMF将会发起PDU会话修改流程，基于第四步中获取的PEGC ID，PINE ID，PDU会话ID、QFI等信息，释放目标PINE对应的QoS流。上述PDU会话修改流程会额外携带PINE去激活指示、PIN ID、PINE ID。
6.PEGC释放分配给目标PINE的WiFi、蓝牙等通信资源，并通知所关联的目标PINE在目标PINE中已经被切换至去激活状态。
实施例八：PEMC触发的PINE的重激活
如图5H所示，当PEMC与目标PINE以及目标PINE关联的PEGC异地部署时，PEMC根据有效期设置可以通过网络侧触发PINE的重激活，重新为该PINE分配5GS资源，具体步骤如下：
1.PEMC通过RAN向AMF发送PINE激活请求，该消息中包括PINE激活指示，PIN ID，PINE ID，与目标PINE关联的PEGC ID，与目标PINE关联的PEMC ID中的至少之一。
2.AMF将PINE激活请求转发给SMF，该消息中携带PINE激活指示，PIN ID，PINE ID，与目标PINE关联的PEGC ID，与目标PINE关联的PEMC ID中的至少之一。
3.SMF向UDM发起PIN配置信息查询请求，该消息携带PIN ID，PINE ID，与目标PINE关联的PEGC ID，与目标PINE关联的PEMC ID中的至少之一。
4.UDM向SMF返回PIN配置信息，包括目标PIN中和目标PINE相关联的PEGC ID，以及PEGC为其建立的承载目标PINE业务流量的PDU会话ID、QoS flow ID(即QFI)。
5.SMF将会发起PDU会话修改流程，根据目标PIN中PINE与PEGC之间的流量路由关系重新建立QoS流。此外，上述PDU会话修改流程会额外携带PINE激活指示、PIN ID、PINE ID。
6.PEGC重新分配给目标PINE的WiFi、蓝牙等通信资源，并通知所关联的目标PINE在目标PIN中已经被切换至激活状态。
实施例九：PEGC触发的PIN的去激活
如图5I所示，当PEMC和PEGC之间可以进行直连通信时，PEMC可以直接根据有效期配置来触发PEGC发起5GS资源的释放，从而实现目标PIN去激活，具体流程如下：
1.当PIN有效期结束(到期)时，PEMC向目标PIN内每一个PEGC发送PIN去激活请求，该请求消息包含PIN去激活指示，PIN ID，PEGC ID，PEMC ID，PDU会话ID，QFI等信息。
2.当一个PDU会话只用于一个PIN时(如图4A所示)，PEGC发起PDU会话释放流程，释放为目标PIN分配的用户面资源。当一个PDU会话被用于多个PIN时(如图4B所示)，PEGC将会发起PDU会话修改流程，删除目标PIN对应的QoS流。此外，上述用户面去激活过程、PDU会话修改流程会额外携带PIN去激活指示以及PIN ID。
3.PEGC释放分配给目标PINE的WiFi、蓝牙等通信资源，并通知所关联的目标PINE在目标PIN 中已经被切换至去激活状态。
实施例十：PEGC触发的PIN的激活(重激活)
如图5J所示，当PEMC和PEGC之间可以进行直连通信时，PEMC可以直接根据有效期配置来触发PEGC发起目标PIN激活，重新为目标PIN分配5GS资源，具体流程如下：
1.PEMC向目标PIN内每一个PEGC发送PIN激活请求，该请求消息包含PIN激活指示，PIN ID，PEGC ID，PEMC ID，PDU会话ID，QFI等信息。
2.当一个PDU会话只用于一个PIN时(如图4A所示)，若PEGC没有为目标PIN建立的PDU会话，PEGC发起PDU会话建立流程为目标PIN分配的用户面资源；若PEGC为目标PIN建立的PDU会话处于去激活状态，则发起服务请求流程来激活上述PDU会话。当一个PDU会话被用于多个PIN时(如图4B所示)，PEGC将会发起PDU会话修改流程，根据目标PIN中PINE与PEGC之间的流量路由关系重新建立QoS流。此外，上述服务请求过程、PDU会话修改流程会额外携带PIN重激活指示以及PIN ID。
3.PEGC重新为目标PIN中的PINE分配WiFi，蓝牙等通信资源，并通知所关联的属于目标PIN的PINE所在的目标PIN已经被重新激活。
实施例十一：PEGC触发的PINE的去激活
如图5K所示，当PEMC和PEGC之间可以进行直连通信时，PEMC可以直接根据有效期配置来触发PEGC发起5GS资源的释放，从而实现目标PINE去激活，具体流程如下：
1.当PINE有效期到期时，PEMC向目标PIN内与目标PINE所关联的PEGC发送PINE去激活请求，该请求消息包含PINE去激活指示，PIN ID，PINE ID,与目标PINE关联的PEGC ID，PDU会话ID，QFI等信息。
2.PEGC基于第一步中获取的PEGC ID，PINE ID，PDU会话ID、QFI等信息，释放目标PINE对应的QoS流。上述PDU会话修改流程会额外携带PINE去激活指示、PIN ID、PINE ID。
3.PEGC释放分配给目标PINE的WiFi、蓝牙等通信资源，并通知所关联的目标PINE在目标PIN中已经被切换至去激活状态。
实施例十二：PEGC触发的PINE的激活(重激活)
如图5L所示，当PEMC和PEGC之间可以进行直连通信时，PEMC可以直接根据有效期配置来触发PEGC发起目标PINE激活，重新为目标PINE分配5GS资源，具体流程如下：
1.PEMC向目标PIN内与目标PINE所关联的PEGC发送PINE激活请求，该请求消息包含PINE激活指示，PIN ID，PINE ID，与目标PINE关联的PEGC ID，与目标PINE关联的PEMC ID，PDU会话ID，QFI等信息。
2.PEGC基于第一步中获取的PEGC ID，PINE ID，PDU会话ID、QFI等信息，根据目标PIN中PINE与PEGC之间的流量路由关系重新建立QoS流。此外，上述PDU会话修改流程会额外携带PINE激活指示、PIN ID、PINE ID。
3.PEGC重新分配给目标PINE的WiFi、蓝牙等通信资源，并通知所关联的目标PINE在目标PIN中已经被切换至激活状态。
本申请实施例给出了AF触发的PIN/PINE激活与去激活、PEMC触发的PIN/PINE激活与去激活、PEGC触发的PIN/PINE激活与去激活方式，来支持网络有效期与设备有效期管理。在上述PIN/PINE激活与去激活方式中，无需删除存储网络中及PIN管理实体(例如PEMC和/或AF)中的PIN配置信息，而是可以基于网络有效期与设备有效期对网络和设备占用的5GS资源进行释放与重分配。从而在提高通信资源利用率的同时，避免了网络和设备在重激活时进行重复的网络建立与配置，以及PIN通信配置，例如PINE ID分配和地址分配，PIN参数配置，流量路由管理等繁琐的操作。尤其是对于有效期为不连续的时段的场景，本方案能够降低网络重建、设备激活时延，加快网络、设备继续提供服务的响应适度，从而提高用户体验，并一定程度上减少了网络重复建立/释放、设备重复添加删除所带来地信令负载。此外，本方案给出了具体的PIN/PINE激活与去激活流程，弥补了现有技术上的空白。
本申请实施例还提出一种管理方法，图6是根据本申请一实施例的管理方法600的示意性流程图，该方法可以应用于图1或2所示的系统，但并不仅限于此。该方法包括以下内容的至少部分内容。
S610：第三设备根据网络有效期和/或设备有效期，触发对网络和/或第二设备占用的通信资源的释放或建立。
在一些实施方式中，该第三设备根据网络有效期，触发对网络占用的通信资源的释放或建立，包括：
在该网络有效期结束时，发送网络去激活请求。
在一些实施方式中，该网络去激活请求中携带以下至少之一：网络去激活指示；该网络的标识；该网络中的管理设备的标识；该网络中的网关设备的标识；承载该网络业务流的PDU会话标识和QoS流 标识。
在一些实施方式中，该第三设备根据网络有效期，触发对网络占用的通信资源的释放或建立，包括：
在该网络有效期开始时，发送网络激活请求。
在一些实施方式中，该网络激活请求中携带以下至少之一：网络激活指示；该网络的标识；该网络中的管理设备的标识；该网络中的网关设备的标识；承载该网络业务流的PDU会话标识和QoS流标识。
在一些实施方式中，该第三设备根据设备有效期，触发对第二设备占用的通信资源的释放或建立，包括：
在该设备有效期结束时，发送设备去激活请求。
在一些实施方式中，该设备去激活请求中携带以下至少之一：设备去激活指示；该第二设备的标识；该第二设备所属网络的标识；与该第二设备关联的管理设备的标识；与该第二设备关联的网关设备的标识；承载该第二设备业务流的PDU会话标识和QoS流标识。
在一些实施方式中，该第三设备根据设备有效期，触发对第二设备占用的通信资源的释放或建立，包括：
在该设备有效期开始时，发送设备激活请求。
在一些实施方式中，该设备激活请求中携带以下至少之一：设备激活指示；该第二设备的标识；该第二设备所属网络的标识；与该第二设备关联的管理设备的标识；与该第二设备关联的网关设备的标识；承载该第二设备业务流的PDU会话标识和QoS流标识。
在一些实施方式中，该第三设备包括AF或PEMC。
在一些实施方式中，该网络包括PIN。
在一些实施方式中，该第二设备包括PINE。
本申请实施例还提出一种第一设备，图7是根据本申请一实施例的第一设备700的示意性框图。该第一设备700，可以包括：
第一管理模块710，用于根据网络有效期和/或设备有效期，释放或建立网络和/或第二设备占用的通信资源。
在一些实施方式中，该第一管理模块710，用于在该网络有效期结束时，该第一设备发起用户面去激活流程、协议数据单元PDU会话释放流程或PDU会话修改流程，以释放该网络占用的通信资源。
在一些实施方式中，该第一管理模块710，用于发起用户面去激活流程，以释放承载该网络的业务的PDU会话的无线资源和/或通道。
在一些实施方式中，该第一管理模块710，用于发起PDU会话释放流程，以释放为该网络分配的用户面资源。
在一些实施方式中，该第一管理模块710，用于发起PDU会话修改流程，以删除PDU会话中对应该网络的服务质量QoS流。
图8是根据本申请一实施例的第一设备800的示意性框图，该第一设备800包括上述710实施例的一个或多个特征。在一种可能的实现方式中，在本申请实施例中，还包括：
第一接收模块820，用于接收网络去激活请求，该网络去激活请求由第三设备在该网络的网络有效期结束时发送。
在一些实施方式中，该网络去激活请求中携带以下至少之一：网络去激活指示；该网络的标识；该网络中的管理设备的标识；该网络中的网关设备的标识；承载该网络业务流的PDU会话标识和QoS流标识。
在一些实施方式中，该第一管理模块710，用于在该网络有效期开始时，发起服务请求流程、PDU会话建立流程或PDU会话修改流程，以建立该网络占用的通信资源。
在一些实施方式中，该第一管理模块710，用于发起服务请求流程，以激活为该网络建立的PDU会话。
在一些实施方式中，该第一管理模块710，用于发起PDU会话建立流程，为该网络建立PDU会话。
在一些实施方式中，该第一管理模块710，用于发起PDU会话修改流程，以建立PDU会话中对应该网络的QoS流。
在一些实施方式中，还包括：
第二接收模块830，用于接收网络激活请求，该网络激活请求由第三设备在该网络的网络有效期开始时发送。
在一些实施方式中，该网络激活请求中携带以下至少之一：网络激活指示；该网络的标识；该网络中的管理设备的标识；该网络中的网关设备的标识；承载该网络业务流的PDU会话标识和/或QoS流标识。
在一些实施方式中，该第一管理模块710，用于在该第二设备有效期结束时，发起PDU会话修改流程，以释放该第二设备占用的通信资源。
在一些实施方式中，该第一管理模块710，用于发起PDU会话修改流程，以删除PDU会话中对应该第二设备的QoS流。
在一些实施方式中，还包括：
第三接收模块840，用于接收设备去激活请求，该设备去激活请求由第三设备在该第二设备的设备有效期结束时发送。
在一些实施方式中，该设备去激活请求中携带以下至少之一：设备去激活指示；该第二设备的标识；该第二设备所属网络的标识；与该第二设备关联的管理设备的标识；与该第二设备关联的网关设备的标识；承载该第二设备业务流的PDU会话标识和/或QoS流标识。
在一些实施方式中，该第一管理模块710，用于在该第二设备有效期开始时，发起PDU会话修改流程，以建立该第二设备占用的通信资源。
在一些实施方式中，该第一管理模块710，用于发起PDU会话修改流程，以建立PDU会话中对应该第二设备的QoS流。
在一些实施方式中，还包括：
第四接收模块850，用于接收设备激活请求，该设备激活请求由第三设备在该第二设备的设备有效期开始时发送。
在一些实施方式中，该设备激活请求中携带以下至少之一：设备激活指示；该第二设备的标识；该第二设备所属网络的标识；与该第二设备关联的管理设备的标识；与该第二设备关联的网关设备的标识；承载该第二设备业务流的PDU会话标识和QoS流标识。
在一些实施方式中，还包括：
发送模块860，向第四设备发送网络配置查询请求/设备配置查询请求；
第五接收模块870，用于从该第四设备接收该网络的配置信息/该第二设备的配置信息。
在一些实施方式中，该网络的配置信息包括以下至少之一：该网络的拓扑信息；该网络的标识；该网络中的管理设备的标识；该网络中的设备的标识；承载该网络业务流的PDU会话标识和QoS流标识。
在一些实施方式中，该网络的拓扑信息包括以下至少之一：网络中设备与管理设备之间的关联关系；网络中设备与网关设备之间的关联关系；网络中设备与其他设备之间的关联关系。
在一些实施方式中，该设备配置查询请求中携带以下至少之一：该第二设备的标识；该第二设备所属网络的标识；与该第二设备关联的管理设备的标识；与该第二设备关联的网关设备的标识。
在一些实施方式中，该第二设备的配置信息包括以下至少之一：该第二设备的标识；与该第二设备关联的管理设备的标识；与该第二设备关联的网关设备的标识；承载该第二设备业务流的PDU会话标识和/或QoS流标识。
在一些实施方式中，该第一管理模块710，用于基于该网络的配置信息/该第二设备的配置信息，释放或建立该网络和/或第二设备占用的通信资源。
在一些实施方式中，该第一设备包括会话管理功能SMF或具有网关能力的个人物联网设备PEGC。
在一些实施方式中，该第三设备包括应用功能AF或具有管理能力的个人物联网设备PEMC。
在一些实施方式中，该第四设备包括统一数据管理功能UDM。
在一些实施方式中，该网络包括个人物联网PIN。
在一些实施方式中，该第二设备包括个人物联网设备PINE。
应理解，根据本申请实施例的第一设备中的模块的上述及其他操作和/或功能分别为了实现图3的方法300中的第一设备的相应流程，为了简洁，在此不再赘述。
本申请实施例还提出一种第三设备，图9是根据本申请一实施例的第三设备900的示意性框图。该第三设备900，可以包括：
第二管理模块910，用于根据网络有效期和/或设备有效期，触发对网络和/或第二设备占用的通信资源的释放或建立。
在一些实施方式中，该第二管理模块910，用于在该网络有效期结束时，发送网络去激活请求。
在一些实施方式中，该网络去激活请求中携带以下至少之一：网络去激活指示；该网络的标识；该网络中的管理设备的标识；该网络中的网关设备的标识。
承载该网络业务流的PDU会话标识和QoS流标识。
在一些实施方式中，该第二管理模块910，用于在该网络有效期开始时，发送网络激活请求。
在一些实施方式中，该网络激活请求中携带以下至少之一：网络激活指示；该网络的标识；该网络中的管理设备的标识；该网络中的网关设备的标识；承载该网络业务流的PDU会话标识和QoS流标识。
在一些实施方式中，该第二管理模块910，用于在该设备有效期结束时，发送设备去激活请求。
在一些实施方式中，该设备去激活请求中携带以下至少之一：设备去激活指示；该第二设备的标识；该第二设备所属网络的标识；与该第二设备关联的管理设备的标识；与该第二设备关联的网关设备的标识；承载该第二设备业务流的PDU会话标识和QoS流标识。
在一些实施方式中，该第二管理模块910，用于在该设备有效期开始时，发送设备激活请求。
在一些实施方式中，该设备激活请求中携带以下至少之一：设备激活指示；该第二设备的标识；该第二设备所属网络的标识；与该第二设备关联的管理设备的标识；与该第二设备关联的网关设备的标识；承载该第二设备业务流的PDU会话标识和QoS流标识。
在一些实施方式中，该第三设备包括AF或PEMC。
在一些实施方式中，该网络包括PIN。
在一些实施方式中，该第二设备包括PINE。
应理解，根据本申请实施例的第三设备中的模块的上述及其他操作和/或功能分别为了实现图6的方法600中的第三设备的相应流程，为了简洁，在此不再赘述。
需要说明，关于本申请实施例的通信设备中的各个模块(子模块、单元或组件等)所描述的功能，可以由不同的模块(子模块、单元或组件等)实现，也可以由同一个模块(子模块、单元或组件等)实现，举例来说，第一接收模块与第二接收模块可以是不同的模块，也可以是同一个模块，均能够实现其在本申请实施例中的相应功能。此外，本申请实施例中的发送模块和接收模块，可通过设备的收发机实现，其余各模块中的部分或全部可通过设备的处理器实现。
图10是根据本申请实施例的通信设备1000示意性结构图。图10所示的通信设备1000包括处理器1010，处理器1010可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
在一些实施方式中，如图10所示，通信设备1000还可以包括存储器1020。其中，处理器1010可以从存储器1020中调用并运行计算机程序，以实现本申请实施例中的通信设备。
其中，存储器1020可以是独立于处理器1010的一个单独的器件，也可以集成在处理器1010中。
在一些实施方式中，如图10所示，通信设备1000还可以包括收发器1030，处理器1010可以控制该收发器1030与其他设备进行通信，具体地，可以向其他设备发送信息或数据，或接收其他设备发送的信息或数据。
其中，收发器1030可以包括发射机和接收机。收发器1030还可以进一步包括天线，天线的数量可以为一个或多个。
在一些实施方式中，该通信设备1000可为本申请实施例的通信设备，并且该通信设备1000可以实现本申请实施例的各个方法中由通信设备实现的相应流程，为了简洁，在此不再赘述。
图11是根据本申请实施例的芯片1100的示意性结构图。图11所示的芯片1100包括处理器1110，处理器1110可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
在一些实施方式中，如图11所示，芯片1100还可以包括存储器1120。其中，处理器1110可以从存储器1120中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器1120可以是独立于处理器1110的一个单独的器件，也可以集成在处理器1110中。
在一些实施方式中，该芯片1100还可以包括输入接口1130。其中，处理器1110可以控制该输入接口1130与其他设备或芯片进行通信，具体地，可以获取其他设备或芯片发送的信息或数据。
在一些实施方式中，该芯片1100还可以包括输出接口1140。其中，处理器1110可以控制该输出接口1140与其他设备或芯片进行通信，具体地，可以向其他设备或芯片输出信息或数据。
在一些实施方式中，该芯片可应用于本申请实施例中的通信设备，并且该芯片可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
上述提及的处理器可以是通用处理器、数字信号处理器(digital signal processor，DSP)、现成可编程门阵列(field programmable gate array，FPGA)、专用集成电路(application specific integrated circuit，ASIC)或者其他可编程逻辑器件、晶体管逻辑器件、分立硬件组件等。其中，上述提到的通用处理器可以是微处理器或者也可以是任何常规的处理器等。
上述提及的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)。
应理解，上述存储器为示例性但不是限制性说明，例如，本申请实施例中的存储器还可以是静态随 机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synch link DRAM，SLDRAM)以及直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)等等。也就是说，本申请实施例中的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行该计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。该计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。该计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，该计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(Digital Subscriber Line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。该计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。该可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(Solid State Disk，SSD))等。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
以上所述仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以该权利要求的保护范围为准。

Claims (51)

  1. 一种管理方法，包括：
    第一设备根据网络有效期和/或设备有效期，释放或建立网络和/或第二设备占用的通信资源。
  2. 根据权利要求1所述的方法，其中，所述第一设备根据网络有效期，释放网络占用的通信资源，包括：
    在所述网络有效期结束时，所述第一设备发起用户面去激活流程、协议数据单元PDU会话释放流程或PDU会话修改流程，以释放所述网络占用的通信资源。
  3. 根据权利要求2所述的方法，其中，所述第一设备发起用户面去激活流程，以释放所述网络占用的通信资源，包括：
    所述第一设备发起用户面去激活流程，以释放承载所述网络的业务的PDU会话的无线资源和/或通道。
  4. 根据权利要求2所述的方法，其中，所述第一设备发起PDU会话释放流程，以释放所述网络占用的通信资源，包括：
    所述第一设备发起PDU会话释放流程，以释放为所述网络分配的用户面资源。
  5. 根据权利要求2所述的方法，其中，所述第一设备发起PDU会话修改流程，以释放所述网络占用的通信资源，包括：
    所述第一设备发起PDU会话修改流程，以删除PDU会话中对应所述网络的服务质量QoS流。
  6. 根据权利要求2-5中任一所述的方法，还包括：
    所述第一设备接收网络去激活请求，所述网络去激活请求由第三设备在所述网络的网络有效期结束时发送。
  7. 根据权利要求6所述的方法，其中，所述网络去激活请求中携带以下至少之一：
    网络去激活指示；
    所述网络的标识；
    所述网络中的管理设备的标识；
    所述网络中的网关设备的标识；
    承载所述网络业务流的PDU会话标识和QoS流标识。
  8. 根据权利要求1所述的方法，其中，所述第一设备根据网络有效期，建立网络占用的通信资源，包括：
    在所述网络有效期开始时，所述第一设备发起服务请求流程、PDU会话建立流程或PDU会话修改流程，以建立所述网络占用的通信资源。
  9. 根据权利要求8所述的方法，其中，所述第一设备发起服务请求流程，以建立所述网络占用的通信资源，包括：
    所述第一设备发起服务请求流程，以激活为所述网络建立的PDU会话。
  10. 根据权利要求8所述的方法，其中，所述第一设备发起PDU会话建立流程，以建立所述网络占用的通信资源，包括：
    所述第一设备发起PDU会话建立流程，为所述网络建立PDU会话。
  11. 根据权利要求8所述的方法，其中，所述第一设备发起PDU会话修改流程，以建立所述网络占用的通信资源，包括：
    所述第一设备发起PDU会话修改流程，以建立PDU会话中对应所述网络的QoS流。
  12. 根据权利要求8-11中任一所述的方法，还包括：
    所述第一设备接收网络激活请求，所述网络激活请求由第三设备在所述网络的网络有效期开始时发送。
  13. 根据权利要求12所述的方法，其中，所述网络激活请求中携带以下至少之一：
    网络激活指示；
    所述网络的标识；
    所述网络中的管理设备的标识；
    所述网络中的网关设备的标识；
    承载所述网络业务流的PDU会话标识和/或QoS流标识。
  14. 根据权利要求1所述的方法，其中，所述第一设备根据设备有效期，释放第二设备占用的通信资源，包括：
    在所述第二设备有效期结束时，所述第一设备发起PDU会话修改流程，以释放所述第二设备占用的通信资源。
  15. 根据权利要求14所述的方法，其中，所述第一设备发起PDU会话修改流程，以释放所述第二设备占用的通信资源，包括：
    所述第一设备发起PDU会话修改流程，以删除PDU会话中对应所述第二设备的QoS流。
  16. 根据权利要求14或15所述的方法，还包括：
    所述第一设备接收设备去激活请求，所述设备去激活请求由第三设备在所述第二设备的设备有效期结束时发送。
  17. 根据权利要求16所述的方法，其中，所述设备去激活请求中携带以下至少之一：
    设备去激活指示；
    所述第二设备的标识；
    所述第二设备所属网络的标识；
    与所述第二设备关联的管理设备的标识；
    与所述第二设备关联的网关设备的标识；
    承载所述第二设备业务流的PDU会话标识和/或QoS流标识。
  18. 根据权利要求1所述的方法，其中，所述第一设备根据设备有效期，建立第二设备占用的通信资源，包括：
    在所述第二设备有效期开始时，所述第一设备发起PDU会话修改流程，以建立所述第二设备占用的通信资源。
  19. 根据权利要求18所述的方法，其中，所述第一设备发起PDU会话修改流程，以建立所述第二设备占用的通信资源，包括：
    所述第一设备发起PDU会话修改流程，以建立PDU会话中对应所述第二设备的QoS流。
  20. 根据权利要求18或19所述的方法，还包括：
    所述第一设备接收设备激活请求，所述设备激活请求由第三设备在所述第二设备的设备有效期开始时发送。
  21. 根据权利要求20所述的方法，其中，所述设备激活请求中携带以下至少之一：
    设备激活指示；
    所述第二设备的标识；
    所述第二设备所属网络的标识；
    与所述第二设备关联的管理设备的标识；
    与所述第二设备关联的网关设备的标识；
    承载所述第二设备业务流的PDU会话标识和QoS流标识。
  22. 根据权利要求1-21中任一所述的方法，还包括：
    所述第一设备向第四设备发送网络配置查询请求和/或设备配置查询请求；
    所述第一设备从所述第四设备接收所述网络的配置信息和/或所述第二设备的配置信息。
  23. 根据权利要求22所述的方法，其中，所述网络的配置信息包括以下至少之一：
    所述网络的拓扑信息；
    所述网络的标识；
    所述网络中的管理设备的标识；
    所述网络中的网关设备的标识；
    所述网络中的设备的标识；
    承载所述网络业务流的PDU会话标识和QoS流标识。
  24. 根据权利要求22所述的方法，其中，所述网络的拓扑信息包括以下至少之一：
    网络中设备与管理设备之间的关联关系；
    网络中设备与网关设备之间的关联关系；
    网络中设备与其他设备之间的关联关系。
  25. 根据权利要求22所述的方法，其中，所述设备配置查询请求中携带以下至少之一：
    所述第二设备的标识；
    所述第二设备所属网络的标识；
    与所述第二设备关联的管理设备的标识；
    与所述第二设备关联的网关设备的标识。
  26. 根据权利要求22所述的方法，其中，所述第二设备的配置信息包括以下至少之一：
    所述第二设备的标识；
    与所述第二设备关联的管理设备的标识；
    与所述第二设备关联的网关设备的标识；
    承载所述第二设备业务流的PDU会话标识和/或QoS流标识。
  27. 根据权利要求22-26中任一所述的方法，其中，所述第一设备释放或建立网络和/或第二设备占用的通信资源，包括：
    所述第一设备基于所述网络的配置信息和/或所述第二设备的配置信息，释放或建立所述网络和/或第二设备占用的通信资源。
  28. 根据权利要求1-27中任一所述的方法，其中，所述第一设备包括会话管理功能SMF或具有网关能力的个人物联网设备PEGC。
  29. 根据权利要求6、12、16或20所述的方法，其中，所述第三设备包括应用功能AF或具有管理能力的个人物联网设备PEMC。
  30. 根据权利要求22-27中任一所述的方法，其中，所述第四设备包括统一数据管理功能UDM。
  31. 根据权利要求1-30中任一所述的方法，其中，所述网络包括个人物联网PIN。
  32. 根据权利要求1-30中任一所述的方法，其中，所述第二设备包括个人物联网设备PINE。
  33. 一种管理方法，包括：
    第三设备根据网络有效期和/或设备有效期，触发对网络和/或第二设备占用的通信资源的释放或建立。
  34. 根据权利要求33所述的方法，其中，所述第三设备根据网络有效期，触发对网络占用的通信资源的释放或建立，包括：
    在所述网络有效期结束时，发送网络去激活请求。
  35. 根据权利要求34所述的方法，其中，所述网络去激活请求中携带以下至少之一：
    网络去激活指示；
    所述网络的标识；
    所述网络中的管理设备的标识；
    所述网络中的网关设备的标识。
    承载所述网络业务流的PDU会话标识和QoS流标识。
  36. 根据权利要求33所述的方法，其中，所述第三设备根据网络有效期，触发对网络占用的通信资源的释放或建立，包括：
    在所述网络有效期开始时，发送网络激活请求。
  37. 根据权利要求36所述的方法，其中，所述网络激活请求中携带以下至少之一：
    网络激活指示；
    所述网络的标识；
    所述网络中的管理设备的标识；
    所述网络中的网关设备的标识。
    承载所述网络业务流的PDU会话标识和QoS流标识。
  38. 根据权利要求33所述的方法，其中，所述第三设备根据设备有效期，触发对第二设备占用的通信资源的释放或建立，包括：
    在所述设备有效期结束时，发送设备去激活请求。
  39. 根据权利要求38所述的方法，其中，所述设备去激活请求中携带以下至少之一：
    设备去激活指示；
    所述第二设备的标识；
    所述第二设备所属网络的标识；
    与所述第二设备关联的管理设备的标识；
    与所述第二设备关联的网关设备的标识；
    承载所述第二设备业务流的PDU会话标识和QoS流标识。
  40. 根据权利要求33所述的方法，其中，所述第三设备根据设备有效期，触发对第二设备占用的通信资源的释放或建立，包括：
    在所述设备有效期开始时，发送设备激活请求。
  41. 根据权利要求40所述的方法，其中，所述设备激活请求中携带以下至少之一：
    设备激活指示；
    所述第二设备的标识；
    所述第二设备所属网络的标识；
    与所述第二设备关联的管理设备的标识；
    与所述第二设备关联的网关设备的标识；
    承载所述第二设备业务流的PDU会话标识和QoS流标识。
  42. 根据权利要求33-41中任一所述的方法，其中，所述第三设备包括AF或PEMC。
  43. 根据权利要求33-41中任一所述的方法，其中，所述网络包括PIN。
  44. 根据权利要求33-41中任一所述的方法，其中，所述第二设备包括PINE。
  45. 一种第一设备，包括：
    第一管理模块，用于根据网络有效期和/或设备有效期，释放或建立网络和/或第二设备占用的通信资源。
  46. 一种第三设备，包括：
    第二管理模块，用于根据网络有效期和/或设备有效期，触发对网络和/或第二设备占用的通信资源的释放或建立。
  47. 一种通信设备，包括：处理器、存储器和收发器，该存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，并控制所述收发器，执行如权利要求1至32或33至44中任一项所述的方法。
  48. 一种芯片，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如权利要求1至32或33至44中任一所述的方法。
  49. 一种计算机可读存储介质，用于存储计算机程序，所述计算机程序使得计算机执行如权利要求1至32或33至44中任一所述的方法。
  50. 一种计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行如权利要求1至32或33至44中任一所述的方法。
  51. 一种计算机程序，所述计算机程序使得计算机执行如权利要求1至32或33至44中任一所述的方法。
PCT/CN2022/138831 2022-12-13 2022-12-13 管理方法和设备 WO2024124413A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/138831 WO2024124413A1 (zh) 2022-12-13 2022-12-13 管理方法和设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/138831 WO2024124413A1 (zh) 2022-12-13 2022-12-13 管理方法和设备

Publications (1)

Publication Number Publication Date
WO2024124413A1 true WO2024124413A1 (zh) 2024-06-20

Family

ID=91484221

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/138831 WO2024124413A1 (zh) 2022-12-13 2022-12-13 管理方法和设备

Country Status (1)

Country Link
WO (1) WO2024124413A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2020027578A (ja) * 2018-08-17 2020-02-20 株式会社クレディセゾン ポイント管理方法、プログラムおよびポイント管理システム
CN111787590A (zh) * 2018-07-20 2020-10-16 Oppo广东移动通信有限公司 会话管理方法、终端设备和网络设备
CN111788847A (zh) * 2019-01-11 2020-10-16 Oppo广东移动通信有限公司 用于资源建立的方法及设备
CN112351498A (zh) * 2019-08-09 2021-02-09 大唐移动通信设备有限公司 一种上行资源的配置方法、网络侧设备及用户设备
CN114071374A (zh) * 2020-08-07 2022-02-18 华为技术有限公司 通信方法、装置及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111787590A (zh) * 2018-07-20 2020-10-16 Oppo广东移动通信有限公司 会话管理方法、终端设备和网络设备
JP2020027578A (ja) * 2018-08-17 2020-02-20 株式会社クレディセゾン ポイント管理方法、プログラムおよびポイント管理システム
CN111788847A (zh) * 2019-01-11 2020-10-16 Oppo广东移动通信有限公司 用于资源建立的方法及设备
CN112351498A (zh) * 2019-08-09 2021-02-09 大唐移动通信设备有限公司 一种上行资源的配置方法、网络侧设备及用户设备
CN114071374A (zh) * 2020-08-07 2022-02-18 华为技术有限公司 通信方法、装置及系统

Similar Documents

Publication Publication Date Title
JP7095942B2 (ja) 通信方法、通信装置、及び通信システム
WO2019080800A1 (zh) 一种信息传输方法和设备
EP4033799B1 (en) Relay transmission method, relay terminal and remote terminal
WO2020206582A1 (zh) 一种用于中继通信的方法和装置
US20240147489A1 (en) Sidelink relaying method, first electronic device, and non-transitory computer-readable storage medium
US20230224797A1 (en) Network access method, terminal device, and network device
WO2021258262A1 (zh) 无线通信方法、终端设备和网络设备
WO2024041288A1 (zh) 一种切片请求方法和终端设备
WO2024124413A1 (zh) 管理方法和设备
WO2022160205A1 (zh) 一种数据传输方法、终端设备和网络设备
WO2019218126A1 (zh) 控制网络拥塞的方法、终端设备和网络设备
WO2023056604A1 (zh) 无线通信的方法、终端设备和网络设备
WO2022155825A1 (zh) 用于建立通信连接的方法、通信设备和网络功能实体
WO2022160272A1 (zh) 无线通信的方法、终端设备和网络设备
WO2022006863A1 (zh) 无线通信方法、终端设备和网络设备
WO2022021165A1 (zh) 中继发现方法和终端
WO2021134601A1 (zh) 一种会话建立的方法及装置
WO2022198466A1 (zh) 发现方法和终端
WO2019232683A1 (zh) 小区建立的方法和装置
WO2024086996A1 (zh) 地址分配方法和设备
WO2022233011A1 (zh) 建立连接的方法和终端设备
CN115669211B (zh) 中继方法和终端
WO2024065137A1 (zh) 配置信息获取方法, 配置信息转发方法以及终端设备
WO2022217615A1 (zh) 进入连接态的方法和终端设备
TWI833316B (zh) 通信方法、裝置、電腦可讀存儲介質、電腦程式產品以及通信系統

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22968125

Country of ref document: EP

Kind code of ref document: A1