WO2020211837A1 - 一种终端设备的管理方法及装置 - Google Patents

一种终端设备的管理方法及装置 Download PDF

Info

Publication number
WO2020211837A1
WO2020211837A1 PCT/CN2020/085331 CN2020085331W WO2020211837A1 WO 2020211837 A1 WO2020211837 A1 WO 2020211837A1 CN 2020085331 W CN2020085331 W CN 2020085331W WO 2020211837 A1 WO2020211837 A1 WO 2020211837A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
context
network
time
arrive
Prior art date
Application number
PCT/CN2020/085331
Other languages
English (en)
French (fr)
Inventor
马景旺
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to AU2020259560A priority Critical patent/AU2020259560A1/en
Priority to EP20791167.8A priority patent/EP3952598A4/en
Publication of WO2020211837A1 publication Critical patent/WO2020211837A1/zh
Priority to US17/503,992 priority patent/US20220039018A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0248—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal dependent on the time of the day, e.g. according to expected transmission activity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/53—Allocation or scheduling criteria for wireless resources based on regulatory allocation policies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave
    • H04W52/0216—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave using a pre-established activity schedule, e.g. traffic indication frame
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0229—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • This application relates to the field of mobile communication technology, and in particular to a method and device for managing terminal equipment.
  • terminal devices In the future vertical industry factories will be equipped with a large number of terminal devices. According to business needs, a large number of terminal devices will be divided into different types, such as production equipment for production lines (such as robotic arms, etc.), cameras for monitoring, or It is an Automated Guided Vehicle (AGV) that conveys materials.
  • AGV Automated Guided Vehicle
  • Each type of terminal device has a fixed working time period, such as the time period of 07:00-23:00, the terminal device is in the wake-up state, and will work, and the time period of 23:00-07:00, the terminal The device will shut down and be in a sleep state.
  • the above solution has the following problems: When a large number of terminal devices enter the awake state at the same time and report the context of the terminal device, it will cause a signaling storm, which will cause network congestion, which may cause some terminal devices to fail to report the context, and further cause the PDU session to fail. Affect the communication efficiency of terminal equipment.
  • the present application provides a management method and device for terminal equipment, which are used to improve the success rate of terminal equipment access, thereby improving the communication efficiency of the terminal equipment.
  • this application provides a method for managing a terminal device.
  • the method includes: the network device obtains the wake-up time of the terminal device, and obtains the context of the terminal device according to the wake-up time; The context of the terminal device establishes a session of the terminal device. Based on this solution, when the network device determines that the wake-up time of the terminal device is about to arrive (or arrives), it obtains the context of the terminal device, and then when the terminal device initiates the establishment of a PDU session, it does not need to report the context of the terminal device again, which can save The signaling overhead helps to avoid signaling storms, and further improves the success rate of the terminal equipment in the wake-up state.
  • the obtaining the context of the terminal device according to the wake-up time includes: the network device determines that the wake-up time of the terminal device is about to arrive, then obtaining the terminal device The context.
  • the network device determining that the wake-up time of the terminal device is about to arrive includes: the network device determines that the local timer expires, then determining that the wake-up time of the terminal device is about to arrive; or The network device receives indication information from a data management network element, where the indication information is used to indicate that the wake-up time of the terminal device is about to arrive, and the indication information is sent after a timer on the data management network element expires.
  • acquiring the wake-up time of the terminal device by the network device includes: the network device receives notification information from an external industry center, and the notification information includes the wake-up time of the terminal device.
  • the notification information is used to instruct to acquire the context of the terminal device when the wake-up time of the terminal device is about to arrive; Acquiring the context information of the terminal device when the wake-up time of the terminal device is about to arrive.
  • the notification information further includes an identifier of the terminal device and/or an identifier of a terminal group, and the terminal group indicated by the identifier of the terminal group includes the terminal device.
  • the network device increases the capacity of the network device according to the context of the terminal device.
  • acquiring the context of the terminal device by the network device includes: the network device acquiring the context of the terminal device from a local database or a data management network element.
  • the network device is an access network device; the method further includes: the network device adjusts the deployment of the network device according to a positional relationship with the terminal device.
  • the network device adjusting the deployment of the network device includes: the network device adjusting the antenna direction and/or coverage of the network device.
  • the network device includes an access network device, a mobility management network element, a session management network element, and a user plane network element.
  • this application provides a method for managing a terminal device.
  • the method includes: a network device obtains the sleep time of the terminal device, and stores the context of the terminal device according to the sleep time; and the network device releases the The session of the terminal device.
  • the network device determines that the sleep time of the terminal device is about to arrive (or arrives), it stores the context of the terminal device.
  • the terminal device subsequently needs to initiate the establishment of a PDU session, the terminal device does not need to re-report the context of the terminal device. Instead, the context of the terminal device is directly obtained from the storage space in advance, which can save signaling overhead, help avoid signaling storms, and improve the success rate of the terminal device in the wake-up state.
  • the network device storing the context of the terminal device according to the sleep time includes: the network device determines that the sleep time of the terminal device is about to arrive, then storing the The context of the terminal device.
  • the network device determining that the sleep time of the terminal device is about to arrive includes: the network device determines that the local timer expires, and then determining that the sleep time of the terminal device is about to arrive; or The network device receives indication information from a data management network element, the indication information is used to indicate that the sleep time of the terminal device is about to arrive, and the indication information is sent after a timer on the data management network element expires.
  • acquiring the sleep time of the terminal device by the network device includes: the network device receives notification information from an external industry center, and the notification information includes the sleep time of the terminal device.
  • the notification information is used to instruct to store the context of the terminal device when the sleep time of the terminal device is about to arrive; or, the notification information further includes the Storing the context information of the terminal device when the sleep time of the terminal device is about to arrive.
  • the notification information further includes an identifier of the terminal device and/or an identifier of a terminal group, and the terminal group indicated by the identifier of the terminal group includes the terminal device.
  • the network device reduces the capacity of the network device according to the context of the terminal device.
  • storing the context of the terminal device by the network device includes: the network device stores the context of the terminal device in a local database; and/or,
  • the network device stores the context of the terminal device in a data management network element.
  • the network device is an access network device; the method further includes: the network device adjusts the deployment of the network device according to a positional relationship with the terminal device.
  • the network device adjusting the deployment of the network device includes: the network device adjusting the antenna direction and/or coverage of the network device.
  • the network device includes an access network device, a mobility management network element, a session management network element, and a user plane network element.
  • this application provides a method for managing a terminal device.
  • the method includes: a data management network element determines that the wake-up time of the terminal device is about to arrive; the data management network element sends instruction information to the network device, and the instruction information is used It indicates that the wake-up time of the terminal device is about to arrive.
  • the determining that the wake-up time of the terminal device is about to arrive includes: the data management network element determines that a local timer expires, and then determines that the wake-up time of the terminal device is about to arrive.
  • the data management network element receives a request message from the network device, and the request message is used to request to obtain the context of the terminal device;
  • the device sends the context of the terminal device.
  • this application provides a method for managing a terminal device.
  • the method includes: a data management network element determines that the sleep time of the terminal device is about to arrive; the data management network element sends instruction information to the network device, and the instruction information uses To indicate that the sleep time of the terminal device is about to arrive.
  • the data management network element determining that the sleep time of the terminal device is about to arrive includes: the data management network element determines that the local timer expires, and then determining that the sleep time of the terminal device is about to arrive .
  • the data management network element receives a request message from the network device, the request message includes the context of the terminal device; the data management network element stores the context of the terminal device .
  • the present application provides a terminal device management device, which may be a network device or a chip for the network device.
  • the device has the function of implementing the embodiments of the first aspect or the embodiments of the second aspect. This function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the present application provides a terminal device management device, which may be a data management network element, or a chip for a data management network element.
  • the device has the function of implementing the embodiments of the third aspect or the embodiments of the fourth aspect. This function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the present application provides a terminal device management device, including: a processor and a memory; the memory is used to store computer execution instructions, and when the device is running, the processor executes the computer execution instructions stored in the memory, So that the device executes the methods described in the above aspects.
  • the present application provides a terminal device management apparatus, including: including units or means for executing each step of the above-mentioned aspects.
  • the present application provides a management device for terminal equipment, including a processor and an interface circuit, the processor is configured to communicate with other devices through the interface circuit and execute the methods described in the foregoing aspects.
  • the processor includes one or more.
  • the present application provides a management apparatus for terminal equipment, including a processor, configured to be connected to a memory, and configured to call a program stored in the memory to execute the methods described in the foregoing aspects.
  • the memory can be located inside the device or outside the device.
  • the processor includes one or more.
  • the present application also provides a computer-readable storage medium having instructions stored in the computer-readable storage medium, which when run on a computer, cause a processor to execute the methods described in the foregoing aspects.
  • this application also provides a computer program product including instructions, which when run on a computer, causes the computer to execute the methods described in the above aspects.
  • this application also provides a chip system, including a processor, configured to execute the methods described in the foregoing aspects.
  • the present application also provides a communication system, including: a network device for executing any of the methods described in the first aspect and a data management network element for executing any of the methods described in the third aspect.
  • this application also provides a communication system, including: a network device for executing any of the methods described in the second aspect and a data management network element for executing any of the methods in the fourth aspect.
  • Figure 1 is a schematic diagram of a possible network architecture provided by this application.
  • FIG. 2 is a schematic flowchart of a method for managing terminal equipment provided by this application;
  • FIG. 3 is a schematic flowchart of another terminal device management method provided by this application.
  • FIG. 4 is a schematic flowchart of another terminal device management method provided by this application.
  • FIG. 5 is a schematic flowchart of another terminal device management method provided by this application.
  • FIG. 6 is a schematic flowchart of another terminal device management method provided by this application.
  • FIG. 7 is a schematic flow diagram of another terminal device management method provided by this application.
  • FIG. 8 is a schematic diagram of a terminal device management apparatus provided by this application.
  • FIG. 9 is a schematic diagram of another terminal device management apparatus provided by this application.
  • FIG. 10 is a schematic diagram of another terminal device management apparatus provided by this application.
  • FIG. 1 it is a schematic diagram of the fifth generation (5G) network architecture based on a service-oriented architecture.
  • the 5G network architecture shown in FIG. 1 may include three parts, namely a terminal equipment part, a data network (DN), and an operator network part.
  • DN data network
  • the operator's network may include network exposure function (NEF) network elements, network storage function (network function repository function, NRF) network elements, policy control function (PCF) network elements, and unified data management (unified data management, UDM) network element, application function (AF) network element, unstructured data storage function (UDSF) network element, access and mobility management function (access and mobility management function) , AMF) network elements, session management function (SMF) network elements, (radio) access network ((radio) access network, (R)AN), and user plane function (UPF) network elements Wait.
  • NEF network exposure function
  • NRF network storage function repository function
  • PCF policy control function
  • UDM unified data management
  • UDM unified data management
  • AF application function
  • UDSF unstructured data storage function
  • AMF access and mobility management function
  • SMF session management function
  • R radio access network
  • R user plane function
  • UPF user plane function
  • the terminal equipment of the present application (also referred to as user equipment (UE)) is a device with wireless transceiver function, which can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; or on the water (Such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons, and satellites, etc.).
  • UE user equipment
  • the terminal may be a mobile phone (mobile phone), a tablet computer (pad), a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, and an industrial control (industrial control) Wireless terminals in, self-driving (self-driving), wireless terminals in remote medical, wireless terminals in smart grid, wireless terminals in transportation safety, Wireless terminals in a smart city, wireless terminals in a smart home, etc.
  • the above-mentioned terminal equipment can establish a connection with the operator's network through an interface (such as N1, etc.) provided by the operator's network, and use the data and/or voice services provided by the operator's network.
  • the terminal device can also access the DN through the operator's network, and use the operator's service deployed on the DN and/or the service provided by a third party.
  • the aforementioned third party may be a service party other than the operator's network and terminal equipment, and may provide other services such as data and/or voice for the terminal equipment.
  • the specific form of expression of the aforementioned third party can be determined according to actual application scenarios, and is not limited here.
  • Access network equipment is a device that provides wireless communication functions for terminals.
  • the access network equipment includes, but is not limited to: next-generation base stations (gnodeB, gNB) in 5G, evolved node B (evolved node B, eNB), radio network controller (RNC), node B ( node B, NB), base station controller (BSC), base transceiver station (BTS), home base station (for example, home evolved nodeB, or home node B, HNB), baseband unit (baseBand unit) , BBU), transmission point (transmitting and receiving point, TRP), transmission point (transmitting point, TP), mobile switching center, etc.
  • next-generation base stations evolved node B, eNB
  • RNC radio network controller
  • node B node B
  • BSC base station controller
  • BTS base transceiver station
  • home base station for example, home evolved nodeB, or home node B, HNB
  • baseband unit baseBand unit
  • BBU transmission point
  • the mobility management network element is the control plane network element provided by the operator network, and is responsible for the access control and mobility management of terminal equipment accessing the operator’s network, including, for example, mobility status management and allocating user temporary identities. Functions such as authentication and authorization of users.
  • mobility management network elements can be AMF network elements.
  • future communications such as the 6th generation (6G)
  • mobility management network elements can still be AMF network elements, or have other names. The application is not limited.
  • the session management network element is a control plane network element provided by an operator network, and is responsible for managing a protocol data unit (PDU) session of a terminal device.
  • the PDU session is a channel used to transmit PDUs, and terminal devices need to transmit PDUs to each other through the PDU session and the DN.
  • the PDU session is established, maintained, and deleted by the SMF network element.
  • SMF network elements include session management (such as session establishment, modification, and release, including tunnel maintenance between UPF and RAN), UPF network element selection and control, service and session continuity (Service and Session Continuity, SSC) mode selection, Session-related functions such as roaming.
  • the session management network element may be an SMF network element.
  • future communications such as 6G, the session management network element may still be an SMF network element or have other names, which is not limited in this application.
  • the network visual perception network element can save the environmental information of the corresponding vertical industry (such as the map data where the vertical industry is located, the layout information of the factory area, etc., which can be obtained from the vertical industry control center), the corresponding area of the vertical industry Communication network deployment information (such as access website points, network cell coverage areas, etc.), as well as information such as the movement path of terminal equipment can be obtained from the vertical industry control center.
  • the network visual perception network element may be an NVAF network element.
  • future communications such as 6G, the network visual perception network element may still be an NVAF network element or have other names, which is not limited by this application.
  • the user plane network element is a gateway provided by an operator, and a gateway for communication between the operator's network and the DN.
  • UPF network elements include user plane-related functions such as data packet routing and transmission, packet inspection, service usage reporting, quality of service (QoS) processing, lawful monitoring, upstream packet inspection, and downstream packet storage.
  • QoS quality of service
  • the user plane network element may be a UPF network element.
  • future communications such as 6G, the user plane network element may still be a UPF network element or have other names, which is not limited in this application.
  • DN also called packet data network (PDN)
  • PDN packet data network
  • the operator’s network can be connected to multiple DNs, and multiple services can be deployed on the DN to provide terminal equipment. Services such as data and/or voice.
  • DN is the private network of a smart factory.
  • the sensors installed in the workshop of the smart factory can be terminal devices.
  • the control server of the sensor is deployed in the DN, and the control server can provide services for the sensors.
  • the sensor can communicate with the control server, obtain instructions from the control server, and transmit the collected sensor data to the control server according to the instructions.
  • a DN is an internal office network of a company.
  • the mobile phones or computers of employees of the company can be terminal devices, and the mobile phones or computers of employees can access information and data resources on the company's internal office network.
  • the data management network element is the control plane network element provided by the operator, and is responsible for storing the subscriber permanent identifier (SUPI), credential, and security context of the subscribers in the operator’s network. context), contract data and other information.
  • the information stored in UDM network elements can be used for authentication and authorization of terminal equipment accessing the operator's network.
  • the contracted users of the above-mentioned operator's network may specifically be users who use the services provided by the operator's network, such as users who use China Telecom's mobile phone core card, or users who use China Mobile's mobile phone core card.
  • the permanent subscription identifier (Subscription Permanent Identifier, SUPI) of the aforementioned subscriber may be the number of the mobile phone core card, etc.
  • the credential and security context of the aforementioned subscriber may be a small file stored such as the encryption key of the mobile phone core card or information related to the encryption of the mobile phone core card for authentication and/or authorization.
  • the aforementioned security context may be data (cookie) or token (token) stored on the user's local terminal (for example, mobile phone).
  • the contract data of the aforementioned subscriber may be the supporting service of the mobile phone core card, such as the data package of the mobile phone core card or the use of the network. It should be noted that permanent identifiers, credentials, security contexts, authentication data (cookies), and tokens are equivalent to information related to authentication and authorization. In this application file of the present invention, no distinction or restriction is made for the convenience of description.
  • the data management network element may be a UDM network element.
  • the data management network element may still be a UDM network element or have other names, which is not limited in this application.
  • the network open network element is the control plane network element provided by the operator.
  • NEF network elements open the external interface of the operator's network to third parties in a safe manner.
  • the SMF network element needs to communicate with a third-party network element
  • the NEF network element can serve as a relay for the communication between the SMF network element and the third-party network element.
  • the NEF network element can be used as the translation of the identification information of the subscriber and the translation of the identification information of the third-party network element. For example, when NEF sends the SUPI of the subscriber from the operator network to the third party, it can translate the SUPI into its corresponding external identity (identity, ID).
  • the NEF network element when it sends the external ID (third-party network element ID) to the operator's network, it can be translated into SUPI.
  • the network open network element may be a NEF network element.
  • future communications such as 6G, the network open network element may still be a NEF network element or have other names, which is not limited by this application.
  • the policy control network element is a control plane function provided by the operator for providing a PDU session policy to the SMF network element.
  • Policies can include charging-related policies, QoS-related policies, and authorization-related policies.
  • the policy control network element may be a PCF network element.
  • future communications such as 6G, the policy control network element may still be a PCF network element or have other names, which is not limited in this application.
  • Nnef, Nudsf, Nnrf, Npcf, Nudm, Naf, Namf, Nnvaf, Nsmf, N1, N2, N3, N4, and N6 are interface serial numbers.
  • the meaning of these interface serial numbers can refer to the meaning defined in the 3GPP standard protocol, which is not limited here.
  • the network visual perception network element in this application may be the NVAF network element shown in FIG. 1, or may be a network element having the function of the above-mentioned NVAF network element in a future communication system.
  • the access network device in this application may be the RAN device in FIG. 1, or may be a network element having the function of the above-mentioned RAN device in a future communication system.
  • the AMF network element is referred to as AMF
  • the NVAF network element is referred to as NVAF
  • the RAN device is referred to as RAN
  • the terminal device is referred to as UE.
  • the foregoing network elements or functions may be network elements in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (for example, a cloud platform).
  • a platform for example, a cloud platform.
  • the foregoing network element or function may be implemented by one device, or jointly implemented by multiple devices, or may be a functional module in one device, which is not specifically limited in the embodiment of the present application.
  • the present application provides a method for UE management, which is used for the UE to enter the wake-up state (or wake-up mode) from the dormant state (or sleep mode).
  • the method includes the following steps:
  • the network device determines that the UE's wake-up time is about to arrive, and then acquires the UE's context.
  • the network device is locally configured with a timer, and when the network device determines that the local timer expires, it is determined that the UE wake-up time is about to arrive.
  • obtaining the wake-up time of the UE in step 201 may be, for example, that the network device receives notification information from an external industry center, and the notification information includes the wake-up time of the UE.
  • the notification information is used to indicate that the UE context is obtained when the UE's wake-up time is about to arrive, or the notification information further includes information used to indicate that the UE's context is obtained when the UE's wake-up time is about to arrive.
  • the notification information may also include the identity of the UE or the identity of the terminal group, and the terminal group indicated by the identity of the terminal group includes the aforementioned UE.
  • the network device can set a timer according to the wake-up time, and when the timer expires, it can acquire the context of the UE according to the wake-up time.
  • the notification information sent by the external industry center to the network device includes a wake-up time of 7 am, and instructs the network device to obtain the UE context when it is about to arrive at 7 am, then the network device can be defined or pre-configured according to the protocol Method, set a certain time before 7 am, for example, 6:59 am is divided into the time of timer timeout. Therefore, whenever 6:59 am arrives, the timer of the network device times out, which triggers the network device to acquire the context of the UE.
  • the network device receives indication information from the data management network element, the indication information is used to indicate that the wake-up time of the UE is about to arrive, and the indication information is sent after the timer on the data management network element expires.
  • the acquisition of the wake-up time in step 201 may be, for example, that the data management network element receives notification information from an external industry center, and the notification information includes the wake-up time of the UE.
  • the notification information is used to indicate to notify the network device when the UE's wake-up time is about to arrive, or the notification information further includes information used to indicate that the network device is notified when the UE's wake-up time is about to arrive.
  • the notification information may also include the identity of the UE or the identity of the terminal group, and the terminal group indicated by the identity of the terminal group includes the aforementioned UE.
  • the data management network element can set a timer according to the wake-up time, and then when the timer expires, send indication information to the network device, and then the network device can obtain the context of the UE according to the wake-up time.
  • the notification information sent by the external industry center to the data management network element includes a wake-up time of 7 am, and instructs the network device to notify the network device when it is about to arrive at 7 am
  • the data management network element can be defined according to the protocol Or the pre-configuration method, set a certain time before 7 am, such as 6:59 am as the time for the timer to expire. Therefore, whenever 6:59 am arrives, the timer of the network device times out, which triggers the data management network element to send the above-mentioned instruction information to the network device.
  • the network device determines that the UE's wake-up time is reached, and then obtains the UE's context.
  • the network device is locally configured with a timer, and when the network device determines that the local timer expires, it determines that the wake-up time of the UE has arrived.
  • obtaining the wake-up time of the UE in step 201 may be, for example, that the network device receives notification information from an external industry center, and the notification information includes the wake-up time of the UE.
  • the notification information is used to indicate that the UE context is obtained when the UE's wake-up time arrives, or the notification information further includes information used to indicate that the UE's context is obtained when the UE's wake-up time arrives.
  • the notification information may also include the identity of the UE or the identity of the terminal group, and the terminal group indicated by the identity of the terminal group includes the aforementioned UE.
  • the network device can set a timer according to the wake-up time, and when the timer expires, it can acquire the context of the UE according to the wake-up time.
  • the notification information sent by the external industry center to the network device includes a wake-up time of 7 am, and instructs the network device to obtain the context of the UE when it arrives at 7 am, the network device can be defined or pre-configured according to the protocol , Set 7 am as the time for the timer to expire. Therefore, whenever 7 am arrives, the timer of the network device times out, which triggers the network device to acquire the context of the UE.
  • the network device receives indication information from the data management network element, the indication information is used to indicate that the wake-up time of the UE is reached, and the indication information is sent after the timer on the data management network element expires.
  • the acquisition of the wake-up time in step 201 may be, for example, that the data management network element receives notification information from an external industry center, and the notification information includes the wake-up time of the UE.
  • the notification information is used to indicate to notify the network device when the UE's wake-up time arrives, or the notification information further includes information used to indicate to notify the network device when the UE's wake-up time arrives.
  • the notification information may also include the identity of the UE or the identity of the terminal group, and the terminal group indicated by the identity of the terminal group includes the aforementioned UE.
  • the data management network element can set a timer according to the wake-up time, and then send indication information to the network device when the timer expires, and the network device can obtain the context of the UE according to the wake-up time.
  • the notification information sent by the external industry center to the data management network element includes a wake-up time of 7 am, and instructs the network device to notify the network device when it arrives at 7 am
  • the data management network element can be defined by the protocol or Pre-configuration method, set 7 am as the time for the timer to expire. Therefore, whenever 7 am arrives, the timer of the network device times out, which triggers the data management network element to send the above-mentioned instruction information to the network device.
  • the network device obtains the context of the UE, for example, it may obtain the context of the UE from a local database, or it may also obtain the context of the UE from a data management network element.
  • the network device sends a request message to the data management network element to request The message is used to request to obtain the context of the UE, and the data management network element sends the context of the UE to the network device.
  • the specific implementation method of storing the context of the UE in the local database of the network device or the database management network element refer to the description of Embodiment 3.
  • the UE After the session of the UE is established, the UE enters the awake state.
  • the network device determines that the UE's wake-up time is about to arrive (or arrive), it acquires the UE context, and then when the UE initiates the establishment of a PDU session, it does not need to report the UE context again, which can save signaling overhead. It helps to avoid the occurrence of signaling storms, and thus can improve the success rate of the UE in the wake state.
  • the capacity of the network device can be increased according to the context of the UE. If multiple UEs enter the awake state, the capacity of the network device can also be increased according to the number of UEs. In this way, the capacity of network equipment can be dynamically adjusted, which helps to flexibly adjust the capacity of network equipment according to business requirements.
  • the RAN device can also adjust the deployment of the network device according to the position relationship with the RAN device UE. For example, adjust the antenna direction and/or coverage of the network device.
  • this application provides yet another method for UE management, which is used for the UE to enter the sleep state (or sleep mode) from the awake state (or wake mode).
  • the method includes the following steps:
  • Step 301 The network device obtains the sleep time of the UE, and stores the context of the UE according to the sleep time.
  • the network device determines that the sleep time of the UE is about to arrive, and stores the context of the UE.
  • the network device is locally configured with a timer, and when the network device determines that the local timer expires, it determines that the sleep time of the UE is about to arrive.
  • obtaining the sleep time of the UE in step 301 may be, for example, that the network device receives notification information from an external industry center, and the notification information includes the sleep time of the UE.
  • the notification information is used to indicate to store the context of the UE when the sleep time of the UE is about to arrive, or the notification information further includes information used to indicate that the context of the UE is stored when the sleep time of the UE is about to arrive.
  • the notification information may also include the identity of the UE or the identity of the terminal group, and the terminal group indicated by the identity of the terminal group includes the aforementioned UE.
  • the network device can set a timer according to the sleep time, and then when the timer expires, store the context of the UE according to the sleep time.
  • the notification information sent by the external industry center to the network device includes the sleep time of 23:00, and instructs the network device to store the UE context when it is about to arrive at 23:00
  • the network device can be defined or pre-configured according to the protocol Method, set a certain time before 23 o'clock in the afternoon, such as 22:59 in the afternoon divided into the timer timeout time. Therefore, whenever 22:59 pm arrives, the timer of the network device times out, which triggers the network device to store the context of the UE.
  • the network device receives indication information from the data management network element, the indication information is used to indicate that the sleep time of the UE is about to arrive, and the indication information is sent after the timer on the data management network element expires.
  • obtaining the sleep time of the UE in step 301 may be, for example, that the data management network element receives notification information from an external industry center.
  • the notification information includes the sleep time of the UE.
  • the notification information is used to indicate Notify the network device when the UE’s sleep time is about to arrive, or the notification information may also include information for indicating that the UE’s sleep time is about to arrive, and the notification information may also include the UE’s identity or terminal group
  • the terminal group indicated by the terminal group identifier includes the aforementioned UE.
  • the data management network element can set a timer according to the sleep time, and then send indication information to the network device when the timer expires, and the network device can store the context of the UE according to the sleep time.
  • the network device determines that the sleep time of the UE is reached, and then stores the context of the UE.
  • the network device is locally configured with a timer, and when the network device determines that the local timer expires, it determines that the sleep time of the UE has arrived.
  • obtaining the sleep time of the UE in step 301 may be, for example, that the network device receives notification information from an external industry center, and the notification information includes the sleep time of the UE.
  • the notification information is used to indicate to store the context of the UE when the sleep time of the UE arrives, or the notification information further includes information used to indicate that the context of the UE is stored when the sleep time of the UE arrives.
  • the notification information may also include the identity of the UE or the identity of the terminal group, and the terminal group indicated by the identity of the terminal group includes the aforementioned UE.
  • the network device can set a timer according to the sleep time, and then when the timer expires, store the context of the UE according to the sleep time.
  • the notification information sent by the external industry center to the network device includes the sleep time of 23:00 PM, and instructs the network device to store the UE context when it arrives at 23:00 PM, then the network device can be defined or pre-configured according to the protocol , Set 23:00 pm as the time for the timer to expire. Therefore, whenever it arrives at 23:00 in the afternoon, the timer of the network device times out, which triggers the network device to store the context of the UE.
  • the notification information is used to indicate Notify the network device when the sleep time of the UE arrives, or the notification information further includes information for indicating that the network device is notified when the sleep time of the UE arrives, and the notification information may also include the identity of the UE or the identity of the terminal group
  • the terminal group indicated by the identifier of the terminal group includes the aforementioned UE.
  • the data management network element can set a timer according to the sleep time, and then send indication information to the network device when the timer expires, and the network device can store the context of the UE according to the sleep time.
  • the notification information sent by the external industry center to the data management network element includes a wake-up time of 23:00, and instructs the network device to notify the network device when it arrives at 23:00, then the data management network element can be defined or Pre-configuration method, set 23 o'clock in the afternoon as the time for the timer to expire. Therefore, whenever 23:00 in the afternoon arrives, the timer of the network device times out, which triggers the data management network element to send the above-mentioned instruction information to the network device.
  • the network device stores the context of the UE, for example, it can be stored in a local database or stored in a data management network element.
  • the network device sends a request message to the data management network element, and the request message includes the context of the UE.
  • the request message is used to request storage of the context of the UE, and the data management network element stores the context of the UE.
  • Step 302 The network device releases the UE's session.
  • the network device releases the session of the UE, and then the UE enters the dormant state.
  • the network device may also delete the context of the UE stored on the network device.
  • the network device determines that the sleep time of the UE is about to arrive (or arrives), it stores the context of the UE, and then when the UE needs to initiate the establishment of a PDU session subsequently, the UE does not need to report the context of the UE again, but directly from The context of the UE is acquired in the storage space in advance, which can save signaling overhead and help avoid signaling storms, thereby increasing the success rate of the UE in the wake-up state.
  • the capacity of the network device can also be reduced according to the context of the UE. If multiple UEs enter the dormant state, the capacity of the network device can also be reduced according to the number of UEs. In this way, the capacity of network equipment can be dynamically adjusted, which helps to flexibly adjust the capacity of network equipment according to business requirements.
  • FIG. 2 and the embodiment shown in FIG. 3 can be implemented separately or in combination, that is, the operation of the UE from the sleep state to the awake state is performed through the embodiment shown in FIG. 2 , The operation of the UE from the awake state to the sleep state is performed through the embodiment shown in FIG. 3.
  • FIG. 2 and FIG. 3 will be described in detail below with reference to specific examples.
  • FIG. 4 it is a schematic flowchart of another UE management method provided by this application.
  • This embodiment describes that the network side obtains the working time period information (sleep and wake-up time period) of the UE from an external industry center through the NEF, and the operation description information that the network side needs to perform when the UE enters the dormant or awake state.
  • Step 401 The external industry center sends a request message to NEF.
  • the request message is used to request the network to monitor the UE's communication time period (for example, 08:00-23:00).
  • the request information includes the UE ID or group ID (Group ID), and also includes indication information.
  • the indication information Used to indicate when the UE is about to enter the dormant state (that is, the dormant time is about to arrive), the network element in the RAN or core network needs to store the corresponding UE context in the data management network element (such as UDSF, etc.), and to indicate when the UE is about to enter
  • the network element in the RAN or the core network extracts the corresponding UE context from the data management network element or instructs the data management network element to actively send the corresponding UE context to the RAN or core network Network element.
  • Step 402-Step 403 NEF sends a request message to AMF, and AMF sends a request message to RAN, that is, NEF requests RAN to monitor the communication time period of the UE through AMF.
  • the function and content of the request message are the same as the request message in step 401.
  • Step 404-Step 405 NEF requests SMF and UPF to monitor the communication time period of the UE.
  • the function and content of the request message are the same as the request message in step 401.
  • request messages in the above steps 401 to 405 may be the same request message or different request messages, but these request messages have the same function and contain the same content.
  • the core network side and the RAN side can grasp the UE dormancy and wake-up time period information.
  • some action description information is configured for the network side and the RAN side to indicate that the core network side and the RAN side are about to be on the UE.
  • make corresponding changes when sleeping or waking up That is, when the UE is sleeping, the RAN needs to store the corresponding UE context in the RAN local database or data management network element.
  • the RAN side can also perform capacity reduction processing on the configured capacity, and at the same time, the NF in the core network needs to store the corresponding UE context in the data management network element, and the network element in the core network can also perform the configured capacity Shrink processing.
  • the network elements on the RAN side and the core network need to extract the corresponding UE context from the corresponding database, and can also perform capacity expansion processing on the configured capacity respectively.
  • an indication function is provided for the network side to perform related preparations when the subsequent UE enters the dormant and awake states.
  • the external industry center only informs the UE of the working time period, and does not instruct the network side and RAN side to make corresponding changes according to the sleep and awakening state of the UE, which causes the subsequent UE to enter the awake state and need to report again
  • the UE context causes unnecessary signaling storms, and the configuration capacity of the network side does not make corresponding dynamic expansion and contraction processing for the number of UEs in the awake state, resulting in low network resource utilization.
  • FIG. 5 it is a schematic flowchart of another UE management method provided by this application.
  • This embodiment describes the related operation procedures performed by the RAN side and the core network side when the UE is about to enter the dormant state.
  • the data management network element is UDSF as an example.
  • step 500 the sleep time set by the external industry center arrives, triggering the network side and the RAN side to enter the sleep mode.
  • Step 501 The RAN stores the context of the UE in a local database.
  • the RAN can also store the UE context in the UDSF.
  • the RAN sends a request message to the UDSF.
  • the request message includes the context of the UE and the corresponding UE ID or Group ID, so that the UDSR stores the context of the UE on the RAN.
  • Steps 502-504 AMF, SMF and UPF send a request message to the UDSF.
  • the request message includes the context of the UE and the corresponding UE ID or Group ID.
  • step 502 step 503, and step 504, only some of the steps may be executed, or all of the steps may be executed.
  • the AMF stores the context of the UE locally, there is no need to perform step 502, but the AMF directly stores the context of the UE locally.
  • the SMF stores the context of the UE locally, there is no need to perform step 503, but the SMF directly stores the context of the UE locally.
  • the UPF stores the context of the UE locally
  • step 504 does not need to be performed, but the UPF directly stores the context of the UE locally.
  • Step 505 Release the PDU session, release idle network resources, and reduce virtual capacity configuration of related network elements (such as AMF, SMF, UPF, etc.).
  • related network elements such as AMF, SMF, UPF, etc.
  • AMF, SMF and UPF can also delete the UE context stored on AMF, SMF and UPF respectively.
  • Step 506 The RAN side can adjust the deployment of the RAN side according to the relative positions of the UEs in the dormant state and the awake state, such as antenna direction, coverage size, etc., and the RAN side can also adjust the RAN side according to the number of UEs in the dormant state. Virtual capacity configuration.
  • the network side and the RAN will actively save the corresponding UE context when the PDU session is released, which provides a way for the network side and the RAN side to perform subsequent operations when the UE re-enters the wake-up mode. Data support.
  • the RAN side and the core network side will reduce the virtual capacity configuration of the provided network resources, reducing the redundancy of network resource usage.
  • FIG. 6 a schematic flow diagram of another UE management method provided by this application.
  • This embodiment describes related operations performed by the RAN side and the core network side when the UE is about to enter the awakening state (the triggering of the awakening state is completed by the timers configured in each network element in the core network and the RAN local).
  • step 600 the wake-up time set by the external industry center arrives, triggering the network side and the RAN side to perform the wake-up mode.
  • Step 601 The RAN extracts the UE context from the local database.
  • the context of the UE on the RAN is stored on the UDSF, and in this step, the RAN obtains the context of the UE from the UDSF.
  • Step 602-Step 604 AMF, SMF and UPF obtain UE context from UDSF respectively.
  • AMF, SMF, and UPF respectively initiate a request message to the UDSF, and the request message includes the UE ID or Group ID, and the request message is used to obtain the context of the UE. Then the UDSF sends the UE context to AMF, SMF and UPF respectively.
  • step 602 step 603, and step 604, only some of the steps can be executed, or all of the steps can be executed.
  • step 602 if the AMF stores the context of the UE locally, step 602 does not need to be performed, and the AMF obtains the context of the UE locally.
  • step 603 if the SMF stores the context of the UE locally, step 603 does not need to be performed, and the SMF obtains the context of the UE locally.
  • step 604 does not need to be performed, and the UPF obtains the context of the UE locally.
  • step 605 the PDU session is established, the communication connection is restored, and the core network side increases the capacity configuration of the relevant network.
  • the RAN side may adjust the deployment of the RAN side according to the relative positions of the UE in the dormant state and the awake state, such as the antenna direction, the size of the coverage area, and so on. At the same time, the RAN side can also adjust the configuration of the virtual capacity on the RAN side according to the number of UEs in the awake state.
  • the UE when the UE enters the wake-up mode to reestablish the PDU session, the UE does not need to report the UE context, and the network elements on the RAN side and the core network side will actively extract the previously stored UE context from the database, thereby The signaling interaction between the UE and the network side is reduced, and the possibility of signaling storms is reduced.
  • the RAN side and the core network side will increase the virtual capacity configuration of the network resources provided to implement a dynamic resource provision strategy and improve the use efficiency of network resources.
  • FIG. 7 it is a schematic flow chart of another UE management method provided by this application.
  • This embodiment describes related operations performed by the RAN side and the core network side when the UE is about to enter the awake state (the triggering of the awake state is completed by the RAN and the data management network element).
  • the data management network element is UDSF as an example.
  • step 700 the wake-up time set by the external industry center arrives, and the UDSF triggers the wake-up mode.
  • Step 701 The RAN extracts the UE context from the local database.
  • the context of the UE on the RAN is stored on the UDSF.
  • the UDSF sends a notification message to the RAN.
  • the notification information includes the context of the UE and the corresponding UE ID or Group ID.
  • the UDSF sends notification information to AMF, SMF and UPF.
  • the notification information includes the context of the UE and the corresponding UE ID or Group ID.
  • step 702 step 703, and step 704
  • the notification information of some of the steps may carry the UE context, or the notification information of all steps may carry the UE context.
  • the notification message in step 702 does not carry the context of the UE, and the function of the notification information is to notify the AMF to obtain the context of the UE locally.
  • the notification message in step 703 does not carry the context of the UE, and the function of the notification information is to notify the SMF to obtain the context of the UE locally.
  • the notification message in step 704 does not carry the context of the UE, and the function of the notification information is to notify the UPF to obtain the context of the UE locally.
  • Step 705 Establish a PDU session, restore the communication connection, and at the same time increase the capacity configuration of the relevant network on the core network side.
  • the RAN side may adjust the deployment of the RAN side according to the relative positions of the UE in the dormant state and the awake state, such as the antenna direction, the size of the coverage area, and so on. At the same time, the RAN side can also adjust the configuration of the virtual capacity on the RAN side according to the number of UEs in the awake state.
  • the UE when the UE enters the wake-up mode and reestablishes the PDU session, the UE does not need to report the UE context.
  • the UDSF will actively send the previously stored UE context to the network element in the core network, thereby reducing the UE and the network side. Signaling interaction reduces the possibility of signaling storms.
  • the RAN side and the core network side will increase the virtual capacity configuration of the network resources provided, realize a dynamic resource provision strategy, and improve the use efficiency of network resources.
  • FIG. 6 or FIG. 7 is a specific implementation of the embodiment shown in FIG. 2, and the specific implementation details can refer to related descriptions in the embodiment shown in FIG. 2.
  • the embodiment shown in FIG. 5 is a specific implementation of the embodiment shown in FIG. 2, and for specific implementation details, reference may be made to related descriptions in the embodiment shown in FIG. 3.
  • FIG. 5 and FIG. 6 may be combined with each other, or the embodiments shown in FIG. 5 and FIG. 7 may be combined with each other.
  • each network element described above includes hardware structures and/or software modules corresponding to each function.
  • the present invention can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered as going beyond the scope of the present invention.
  • the apparatus 800 may exist in the form of software or hardware.
  • the communication device 800 may include: a processing unit 802 and a communication unit 803.
  • the communication unit 803 may include a receiving unit and a sending unit.
  • the processing unit 802 is used to control and manage the actions of the communication device 800.
  • the communication unit 803 is used to support communication between the communication device 800 and other network entities.
  • the communication device 800 may further include a storage unit 801 for storing program codes and data of the communication device 800.
  • the processing unit 802 may be a processor or a controller, for example, a general-purpose central processing unit (central processing unit, CPU), a general-purpose processor, a digital signal processing (digital signal processing, DSP), and an application specific integrated circuit (application specific integrated circuit). circuits, ASIC), field programmable gate array (FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It can implement or execute various exemplary logical blocks, modules and circuits described in conjunction with the disclosure of this application.
  • the processor may also be a combination for realizing computing functions, for example, including a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and so on.
  • the storage unit 801 may be a memory.
  • the communication unit 803 is an interface circuit of the device for receiving signals from other devices.
  • the communication unit 803 is an interface circuit for the chip to receive signals from other chips or devices, or an interface circuit for the chip to send signals to other chips or devices.
  • the communication device 800 may be the network device in any of the above embodiments, and may also be a chip for the network device.
  • the processing unit 802 may be, for example, a processor
  • the communication unit 803 may be, for example, a transceiver.
  • the transceiver may include a radio frequency circuit
  • the storage unit may be, for example, a memory.
  • the processing unit 802 may be a processor, for example, and the communication unit 803 may be an input/output interface, a pin or a circuit, for example.
  • the processing unit 802 can execute computer-executable instructions stored in the storage unit.
  • the storage unit is a storage unit in the chip, such as a register, a cache, etc., and the storage unit may also be a network device located outside the chip.
  • the storage unit such as read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM), etc.
  • the communication device 800 is a network device
  • the processing unit 802 is configured to obtain the wake-up time of the terminal device, and obtain the context of the terminal device according to the wake-up time; and, according to the terminal device The context of the device establishes a session of the terminal device.
  • the processing unit 802 is specifically configured to determine that the wake-up time of the terminal device is about to arrive, and then acquire the context of the terminal device.
  • the processing unit 802 is specifically configured to determine that the local timer expires, and then determine that the wake-up time of the terminal device is about to arrive; or, through the communication unit 803, receive indication information from the data management network element The indication information is used to indicate that the wake-up time of the terminal device is about to arrive, and the indication information is sent after a timer on the data management network element expires.
  • the processing unit 802 is specifically configured to receive notification information from an external industry center, where the notification information includes the wake-up time of the terminal device.
  • the notification information is used to instruct to acquire the context of the terminal device when the wake-up time of the terminal device is about to arrive; Acquiring the context information of the terminal device when the wake-up time of the terminal device is about to arrive.
  • the notification information further includes an identifier of the terminal device and/or an identifier of a terminal group, and the terminal group indicated by the identifier of the terminal group includes the terminal device.
  • the processing unit 802 is further configured to increase the capacity of the network device according to the context of the terminal device.
  • the network device is an access network device; the processing unit 802 is further configured to adjust the deployment of the network device according to the position relationship with the terminal device.
  • the processing unit 802 is specifically configured to adjust the antenna direction and/or coverage of the network device.
  • the network device includes an access network device, a mobility management network element, a session management network element, and a user plane network element.
  • the communication device 800 is a network device
  • the processing unit 802 is configured to obtain the sleep time of the terminal device, and store the context of the terminal device according to the sleep time; and release the terminal device Conversation.
  • the processing unit 802 is specifically configured to determine that the sleep time of the terminal device is about to arrive, and then store the context of the terminal device.
  • the processing unit 802 is specifically configured to determine that the local timer expires, and then determine that the sleep time of the terminal device is about to arrive; or, through the communication unit 803, receive indication information from the data management network element The indication information is used to indicate that the sleep time of the terminal device is about to arrive, and the indication information is sent after a timer on the data management network element expires.
  • the processing unit 802 is specifically configured to receive notification information from an external industry center through the communication unit 803, where the notification information includes the sleep time of the terminal device.
  • the notification information is used to instruct to store the context of the terminal device when the sleep time of the terminal device is about to arrive; or, the notification information further includes the Storing the context information of the terminal device when the sleep time of the terminal device is about to arrive.
  • the notification information further includes an identifier of the terminal device and/or an identifier of a terminal group, and the terminal group indicated by the identifier of the terminal group includes the terminal device.
  • the processing unit 802 is further configured to reduce the capacity of the network device according to the context of the terminal device.
  • the processing unit 802 is specifically configured to store the context of the terminal device in a local database; and/or store the context of the terminal device in a data management network element.
  • the network device is an access network device; the processing unit 802 is further configured to adjust the deployment of the network device according to the position relationship with the terminal device.
  • the processing unit 802 is specifically configured to adjust the antenna direction and/or coverage of the network device.
  • the network device includes an access network device, a mobility management network element, a session management network element, and a user plane network element.
  • the communication apparatus 900 may exist in the form of software or hardware.
  • the communication device 900 may include: a processing unit 902 and a communication unit 903.
  • the communication unit 903 may include a receiving unit and a sending unit.
  • the processing unit 902 is used to control and manage the actions of the communication device 900.
  • the communication unit 903 is used to support communication between the communication device 900 and other network entities.
  • the communication device 900 may further include a storage unit 901 for storing program codes and data of the communication device 900.
  • the processing unit 902 may be a processor or a controller, for example, a CPU, a general-purpose processor, a DSP, an ASIC, an FPGA, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logical blocks, modules and circuits described in conjunction with the disclosure of this application.
  • the processor may also be a combination for realizing computing functions, for example, including a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and so on.
  • the storage unit 901 may be a memory.
  • the communication unit 903 is an interface circuit of the device for receiving signals from other devices. For example, when the device is implemented as a chip, the communication unit 903 is an interface circuit for the chip to receive signals from other chips or devices, or an interface circuit for the chip to send signals to other chips or devices.
  • the communication device 900 may be a data management network element in any of the foregoing embodiments, and may also be a chip used for a data management network element.
  • the processing unit 902 may be, for example, a processor
  • the communication unit 903 may be, for example, a transceiver.
  • the transceiver may include a radio frequency circuit
  • the storage unit may be, for example, a memory.
  • the processing unit 902 may be, for example, a processor
  • the communication unit 903 may be, for example, an input/output interface, a pin, or a circuit.
  • the processing unit 902 can execute computer-executable instructions stored in the storage unit.
  • the storage unit is a storage unit in the chip, such as a register, a cache, etc., and the storage unit may also be a storage unit located in the data management network element.
  • a storage unit outside the chip such as ROM or other types of static storage devices that can store static information and instructions, RAM, etc.
  • the communication device 900 is a data management network element, and the processing unit 902 is configured to determine that the wake-up time of the terminal device is about to arrive; the communication unit 903 is configured to send instruction information to the network device, the instruction information Used to indicate that the wake-up time of the terminal device is about to arrive.
  • the processing unit 902 is specifically configured to determine that the local timer expires, and then determines that the wake-up time of the terminal device is about to arrive.
  • the communication unit 903 is further configured to receive a request message from the network device, where the request message is used to request to obtain the context of the terminal device; and, to send all information to the network device The context of the terminal device.
  • the communication device 900 is a data management network element, and the processing unit 902 is configured to determine that the sleep time of the terminal device is about to arrive; the communication unit 903 is configured to send instruction information to the network device, the instruction information Used to indicate that the sleep time of the terminal device is about to arrive.
  • the processing unit 902 is specifically configured to determine that the local timer expires, and then determines that the sleep time of the terminal device is about to arrive.
  • the communication unit 903 is further configured to receive a request message from the network device, where the request message includes the context of the terminal device; the processing unit 902 is further configured to store the terminal device The context.
  • the communication apparatus may be the network equipment or the data management network element in the foregoing embodiment.
  • the communication device 1000 includes a processor 1002, a communication interface 1003, and a memory 1001.
  • the communication device 1000 may further include a communication line 1004.
  • the communication interface 1003, the processor 1002, and the memory 1001 may be connected to each other through a communication line 1004;
  • the communication line 1004 may be a peripheral component interconnection standard (peripheral component interconnect, PCI for short) bus or an extended industry standard architecture (extended industry standard architecture) , Referred to as EISA) bus and so on.
  • the communication line 1004 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is used to represent in FIG. 10, but it does not mean that there is only one bus or one type of bus.
  • the processor 1002 may be a CPU, a microprocessor, an ASIC, or one or more integrated circuits used to control the execution of the programs of the present application.
  • the communication interface 1003 uses any device such as a transceiver to communicate with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), Wired access network, etc.
  • RAN radio access network
  • WLAN wireless local area networks
  • Wired access network etc.
  • the memory 1001 may be ROM or other types of static storage devices that can store static information and instructions, RAM or other types of dynamic storage devices that can store information and instructions, or may be an electrically erasable programmable read-only memory (electrically erasable programmable read-only memory).
  • read-only memory EEPROM
  • compact disc read-only memory, CD-ROM
  • optical disc storage including compact discs, laser discs, optical discs, digital universal discs, Blu-ray discs, etc.
  • magnetic disks A storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program codes in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto.
  • the memory can exist independently and is connected to the processor through the communication line 1004. The memory can also be integrated with the processor.
  • the memory 1001 is used to store computer execution instructions for executing the solution of the present application, and the processor 1002 controls the execution.
  • the processor 1002 is configured to execute computer-executable instructions stored in the memory 1001, so as to implement the UE management method provided in the foregoing embodiment of the present application.
  • the computer-executable instructions in the embodiments of the present application may also be referred to as application program code, which is not specifically limited in the embodiments of the present application.
  • At least one (piece, species) of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or Multiple.
  • Multiple refers to two or more, and other measure words are similar.
  • "a device” means to one or more such devices.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or a data center integrated with one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)), etc.
  • the various illustrative logic units and circuits described in the embodiments of this application can be implemented by general-purpose processors, digital signal processors, application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, Discrete gates or transistor logic, discrete hardware components, or any combination of the above are designed to implement or operate the described functions.
  • the general-purpose processor may be a microprocessor, and optionally, the general-purpose processor may also be any traditional processor, controller, microcontroller, or state machine.
  • the processor can also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors combined with a digital signal processor core, or any other similar configuration achieve.
  • the steps of the method or algorithm described in the embodiments of the present application can be directly embedded in hardware, a software unit executed by a processor, or a combination of the two.
  • the software unit can be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM or any other storage medium in the field.
  • the storage medium may be connected to the processor, so that the processor can read information from the storage medium, and can store and write information to the storage medium.
  • the storage medium may also be integrated into the processor.
  • the processor and the storage medium can be arranged in the ASIC.
  • These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment.
  • the instructions provide steps for implementing functions specified in a flow or multiple flows in the flowchart and/or a block or multiple blocks in the block diagram.

Landscapes

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

Abstract

本申请提供一种终端设备的管理方法及装置。该方法包括：网络设备在确定终端设备的唤醒时间即将到达(或到达)时，则获取终端设备的上下文，网络设备在确定终端设备的休眠时间即将到达(或到达)时，则存储终端设备的上下文，进而当终端设备后续发起建立PDU会话时，不需要UE重新上报终端设备的上下文，如此可以节约信令开销，有助于避免发生信令风暴，进而可以提升终端设备进行唤醒态的成功率。

Description

一种终端设备的管理方法及装置
相关申请的交叉引用
本申请要求在2019年04月18日提交中国专利局、申请号为201910312419.3、申请名称为“一种终端设备的管理方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及移动通信技术领域，尤其涉及一种终端设备的管理方法及装置。
背景技术
未来的垂直行业工厂中会配置大量的终端设备，根据业务需求，大量的终端设备又会被分成不同类型，如用于生产线的生产设备(如机械臂等)，用于监控的摄像头，或者用于传送物质的是自动导引运输车(Automated Guided Vehicle，AGV)。每一种类型的终端设备都有固定的工作时间段，如07:00-23:00这个时间段,终端设备处于唤醒态，会进行工作，而23:00-07:00这个时间段，终端设备就会停机，处于休眠态。
当终端设备进入休眠态时，目前技术的处理流程是网络侧让终端设备进入空闲态(idle)，并且网络侧释放协议数据单元(protocol data unit，PDU)会话(session)，同时释放掉终端设备的上下文，而当终端设备第二天进入唤醒态准备工作时，网络侧会让终端设备重新上报终端设备的上下文,从而为终端设备重新建立PDU session。
上述方案存在以下问题：当有大量终端设备同时进入唤醒态并且上报终端设备的上下文时,会造成信令风暴，从而造成网络拥塞，有可能导致部分终端设备上报上下文失败，进一步造成PDU session失败，影响终端设备的通信效率。
发明内容
本申请提供一种终端设备的管理方法及装置，用以提升终端设备接入的成功率，进而提升终端设备的通信效率。
第一方面，本申请提供一种终端设备的管理方法，该方法包括：网络设备获取终端设备的唤醒时间，并根据所述唤醒时间，获取所述终端设备的上下文；所述网络设备根据所述终端设备的上下文，建立所述终端设备的会话。基于该方案，网络设备在确定终端设备的唤醒时间即将到达(或到达)时，则获取终端设备的上下文，进而当终端设备发起建立PDU会话时，不需要重新上报终端设备的上下文，如此可以节约信令开销，有助于避免发生信令风暴，进而可以提升终端设备进行唤醒态的成功率。
在一种可能的实现方法中，所述根据所述唤醒时间，获取所述终端设备的上下文，包括：所述网络设备确定所述终端设备的所述唤醒时间即将到达，则获取所述终端设备的上下文。
在一种可能的实现方法中，所述网络设备确定终端设备的唤醒时间即将到达，包括：所述网络设备确定本地的定时器超时，则确定所述终端设备的唤醒时间即将到达；或者， 所述网络设备接收来自数据管理网元的指示信息，所述指示信息用于指示所述终端设备的唤醒时间即将到达，所述指示信息是所述数据管理网元上的定时器超时后发送的。
在一种可能的实现方法中，所述网络设备获取终端设备的唤醒时间，包括：所述网络设备接收来自外部行业中心的通知信息，所述通知信息包括所述终端设备的所述唤醒时间。
在一种可能的实现方法中，所述通知信息用于指示在所述终端设备的所述唤醒时间即将到达时获取所述终端设备的上下文；或者，所述通知信息还包括用于指示在所述终端设备的所述唤醒时间即将到达时获取所述终端设备的上下文的信息。
在一种可能的实现方法中，所述通知信息还包括所述终端设备的标识和/或终端群组的标识，所述终端群组的标识指示的终端群组包括所述终端设备。
在一种可能的实现方法中，所述网络设备根据所述终端设备的上下文，增加所述网络设备的容量。
在一种可能的实现方法中，所述网络设备获取所述终端设备的上下文，包括：所述网络设备从本地数据库或数据管理网元获取所述终端设备的上下文。
在一种可能的实现方法中，所述网络设备为接入网设备；所述方法还包括：所述网络设备根据与所述终端设备之间的位置关系，调整所述网络设备的部署。
在一种可能的实现方法中，所述网络设备调整所述网络设备的部署，包括：所述网络设备调整所述网络设备的天线方向和/或覆盖范围。
在一种可能的实现方法中，所述网络设备包括接入网设备、移动性管理网元、会话管理网元、用户面网元。
第二方面，本申请提供一种终端设备的管理方法，该方法包括：网络设备获取终端设备的休眠时间，并根据所述休眠时间，存储所述终端设备的上下文；所述网络设备释放所述终端设备的会话。基于上述方案，网络设备在确定终端设备的休眠时间即将到达(或到达)时，则存储终端设备的上下文，进而当终端设备后续需要发起建立PDU会话时，不需要终端设备重新上报终端设备的上下文，而是直接从存储空间中提前获取终端设备的上下文，如此可以节约信令开销，有助于避免发生信令风暴，进而可以提升终端设备进行唤醒态的成功率。
在一种可能的实现方法中，所述网络设备根据所述休眠时间，存储所述终端设备的上下文，包括：所述网络设备确定所述终端设备的所述休眠时间即将到达，则存储所述终端设备的上下文。
在一种可能的实现方法中，所述网络设备确定终端设备的休眠时间即将到达，包括：所述网络设备确定本地的定时器超时，则确定所述终端设备的休眠时间即将到达；或者，所述网络设备接收来自数据管理网元的指示信息，所述指示信息用于指示所述终端设备的休眠时间即将到达，所述指示信息是所述数据管理网元上的定时器超时后发送的。
在一种可能的实现方法中，所述网络设备获取终端设备的休眠时间，包括：所述网络设备接收来自外部行业中心的通知信息，所述通知信息包括所述终端设备的所述休眠时间。
在一种可能的实现方法中，所述通知信息用于指示在所述终端设备的所述休眠时间即将到达时存储所述终端设备的上下文；或者，所述通知信息还包括用于指示在所述终端设备的所述休眠时间即将到达时存储所述终端设备的上下文的信息。
在一种可能的实现方法中，所述通知信息还包括所述终端设备的标识和/或终端群组的标识，所述终端群组的标识指示的终端群组包括所述终端设备。
在一种可能的实现方法中，所述网络设备根据所述终端设备的上下文，减少所述网络设备的容量。
在一种可能的实现方法中，所述网络设备存储所述终端设备的上下文，包括：所述网络设备将所述终端设备的上下文存储在本地数据库；和/或，
所述网络设备将所述终端设备的上下文存储至数据管理网元。
在一种可能的实现方法中，所述网络设备为接入网设备；所述方法还包括：所述网络设备根据与所述终端设备之间的位置关系，调整所述网络设备的部署。
在一种可能的实现方法中，所述网络设备调整所述网络设备的部署，包括：所述网络设备调整所述网络设备的天线方向和/或覆盖范围。
在一种可能的实现方法中，所述网络设备包括接入网设备、移动性管理网元、会话管理网元、用户面网元。
第三方面，本申请提供一种终端设备的管理方法，该方法包括：数据管理网元确定终端设备的唤醒时间即将到达；所述数据管理网元向网络设备发送指示信息，所述指示信息用于指示所述终端设备的唤醒时间即将到达。
在一种可能的实现方法中，所述确定终端设备的唤醒时间即将到达，包括：所述数据管理网元确定本地的定时器超时，则确定所述终端设备的唤醒时间即将到达。
在一种可能的实现方法中，所述数据管理网元接收来自所述网络设备的请求消息，所述请求消息用于请求获取所述终端设备的上下文；所述数据管理网元向所述网络设备发送所述终端设备的上下文。
第四方面，本申请提供一种终端设备的管理方法，该方法包括：数据管理网元确定终端设备的休眠时间即将到达；所述数据管理网元向网络设备发送指示信息，所述指示信息用于指示所述终端设备的休眠时间即将到达。
在一种可能的实现方法中，所述数据管理网元确定终端设备的休眠时间即将到达，包括：所述数据管理网元确定本地的定时器超时，则确定所述终端设备的休眠时间即将到达。
在一种可能的实现方法中，所述数据管理网元接收来自所述网络设备的请求消息，所述请求消息包括所述终端设备的上下文；所述数据管理网元存储所述终端设备的上下文。
第五方面，本申请提供一种终端设备的管理装置，该装置可以是网络设备，还可以是用于网络设备的芯片。该装置具有实现上述第一方面的各实施例、或第二方面的各实施例的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第六方面，本申请提供一种终端设备的管理装置，该装置可以是数据管理网元，还可以是用于数据管理网元的芯片。该装置具有实现上述第三方面的各实施例或第四方面的各实施例的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第七方面，本申请提供一种终端设备的管理装置，包括：处理器和存储器；该存储器用于存储计算机执行指令，当该装置运行时，该处理器执行该存储器存储的该计算机执行指令，以使该装置执行如上述各方面所述的方法。
第八方面，本申请提供一种终端设备的管理装置，包括：包括用于执行上述各方面的各个步骤的单元或手段(means)。
第九方面，本申请提供一种终端设备的管理装置，包括处理器和接口电路，所述处理 器用于通过接口电路与其它装置通信，并执行上述各方面所述的方法。该处理器包括一个或多个。
第十方面，本申请提供一种终端设备的管理装置，包括处理器，用于与存储器相连，用于调用所述存储器中存储的程序，以执行上述各方面所述的方法。该存储器可以位于该装置之内，也可以位于该装置之外。且该处理器包括一个或多个。
第十一方面，本申请还提供一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得处理器执行上述各方面所述的方法。
第十二方面，本申请还提供一种包括指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
第十三方面，本申请还提供一种芯片系统，包括：处理器，用于执行上述各方面所述的方法。
第十四方面，本申请还提供一种通信系统，包括：用于执行上述第一方面任意所述的方法的网络设备和用于执行上述第三方面任意所述的方法的数据管理网元。
第十五方面，本申请还提供一种通信系统，包括：用于执行上述第二方面任意所述的方法的网络设备和用于执行上述第四方面任意所述的方法的数据管理网元。
附图说明
图1为本申请提供的一种可能的网络架构示意图；
图2为本申请提供的一种终端设备的管理方法流程示意图；
图3为本申请提供的又一种终端设备的管理方法流程示意图；
图4为本申请提供的又一种终端设备的管理方法流程示意图；
图5为本申请提供的又一种终端设备的管理方法流程示意图；
图6为本申请提供的又一种终端设备的管理方法流程示意图；
图7为本申请提供的又一种终端设备的管理方法流程示意图；
图8为本申请提供的一种终端设备的管理装置示意图；
图9为本申请提供的又一种终端设备的管理装置示意图；
图10为本申请提供的又一种终端设备的管理装置示意图。
具体实施方式
为了使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请作进一步地详细描述。方法实施例中的具体操作方法也可以应用于装置实施例或系统实施例中。其中，在本申请的描述中，除非另有说明，“多个”的含义是两个或两个以上。
如图1所示，为基于服务化架构的第五代(the 5th generation，5G)网络架构示意图。图1所示的5G网络架构中可包括三部分，分别是终端设备部分、数据网络(data network，DN)和运营商网络部分。
其中，运营商网络可包括网络开放功能(network exposure function，NEF)网元、网络存储功能(network function repository function，NRF)网元、策略控制功能(policy control function，PCF)网元、统一数据管理(unified data management，UDM)网元、应用功能(application function，AF)网元、非结构数据储存功能(Unstructured Data Storage Function， UDSF)网元、接入与移动性管理功能(access and mobility management function，AMF)网元、会话管理功能(session management function，SMF)网元、(无线)接入网((radio)access network，(R)AN)以及用户面功能(user plane function，UPF)网元等。上述运营商网络中，除(无线)接入网部分之外的部分可以称为核心网络部分。为方便说明，后续以(R)AN称为RAN为例进行说明。
本申请的终端设备(也可以称为用户设备(user equipment，UE))是一种具有无线收发功能的设备，可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。所述终端可以是手机(mobile phone)、平板电脑(pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端、增强现实(augmented reality，AR)终端、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等。
上述终端设备可通过运营商网络提供的接口(例如N1等)与运营商网络建立连接，使用运营商网络提供的数据和/或语音等服务。终端设备还可通过运营商网络访问DN，使用DN上部署的运营商业务，和/或第三方提供的业务。其中，上述第三方可为运营商网络和终端设备之外的服务方，可为终端设备提供他数据和/或语音等服务。其中，上述第三方的具体表现形式，具体可根据实际应用场景确定，在此不做限制。
接入网设备，是一种为终端提供无线通信功能的设备。接入网设备例如包括但不限于：5G中的下一代基站(g nodeB，gNB)、演进型节点B(evolved node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved nodeB，或home node B，HNB)、基带单元(baseBand unit，BBU)、传输点(transmitting and receiving point，TRP)、发射点(transmitting point，TP)、移动交换中心等。
本申请中，移动性管理网元是由运营商网络提供的控制面网元，负责终端设备接入运营商网络的接入控制和移动性管理，例如包括移动状态管理，分配用户临时身份标识，认证和授权用户等功能。在5G中，移动性管理网元可以是AMF网元，在未来通信如第六代(the 6th generation，6G)中，移动性管理网元仍可以是AMF网元，或有其它的名称，本申请不做限定。
本申请中，会话管理网元是由运营商网络提供的控制面网元，负责管理终端设备的协议数据单元(protocol data unit，PDU)会话。PDU会话是一个用于传输PDU的通道，终端设备需要通过PDU会话与DN互相传送PDU。PDU会话由SMF网元负责建立、维护和删除等。SMF网元包括会话管理(如会话建立、修改和释放，包含UPF和RAN之间的隧道维护)、UPF网元的选择和控制、业务和会话连续性(Service and Session Continuity，SSC)模式选择、漫游等会话相关的功能。在5G中，会话管理网元可以是SMF网元，在未来通信如6G中，会话管理网元仍可以是SMF网元，或有其它的名称，本申请不做限定。
本申请中，网络视觉感知网元，可保存对应的垂直行业的环境信息(如垂直行业所在的地图数据、工厂区域的layout信息等，该信息可以从垂直行业控制中心获取)、垂直行业对应区域的通信网络部署信息(如接入网站点、网络小区的覆盖区域等)，以及还可以从垂直行业控制中心获取终端设备的移动路径等信息。在5G中，网络视觉感知网元可以 是NVAF网元，在未来通信如6G中，网络视觉感知网元仍可以是NVAF网元，或有其它的名称，本申请不做限定。
本申请中，用户面网元是由运营商提供的网关，是运营商网络与DN通信的网关。UPF网元包括数据包路由和传输、包检测、业务用量上报、服务质量(Quality of Service,QoS)处理、合法监听、上行包检测、下行数据包存储等用户面相关的功能。在5G中，用户面网元可以是UPF网元，在未来通信如6G中，用户面网元仍可以是UPF网元，或有其它的名称，本申请不做限定。
DN，也可以称为分组数据网络(packet data network，PDN)，是位于运营商网络之外的网络，运营商网络可以接入多个DN，DN上可部署多种业务，可为终端设备提供数据和/或语音等服务。例如，DN是某智能工厂的私有网络，智能工厂安装在车间的传感器可为终端设备，DN中部署了传感器的控制服务器，控制服务器可为传感器提供服务。传感器可与控制服务器通信，获取控制服务器的指令，根据指令将采集的传感器数据传送给控制服务器等。又例如，DN是某公司的内部办公网络，该公司员工的手机或者电脑可为终端设备，员工的手机或者电脑可以访问公司内部办公网络上的信息、数据资源等。
本申请中，数据管理网元是由运营商提供的控制面网元，负责存储运营商网络中签约用户的用户永久标识符(subscriber permanent identifier，SUPI)、信任状(credential)、安全上下文(security context)、签约数据等信息。UDM网元所存储的这些信息可用于终端设备接入运营商网络的认证和授权。其中，上述运营商网络的签约用户具体可为使用运营商网络提供的业务的用户，例如使用中国电信的手机芯卡的用户，或者使用中国移动的手机芯卡的用户等。上述签约用户的永久签约标识(Subscription Permanent Identifier，SUPI)可为该手机芯卡的号码等。上述签约用户的信任状、安全上下文可为该手机芯卡的加密密钥或者跟该手机芯卡加密相关的信息等存储的小文件，用于认证和/或授权。上述安全上下文可为存储在用户本地终端(例如手机)上的数据(cookie)或者令牌(token)等。上述签约用户的签约数据可为该手机芯卡的配套业务，例如该手机芯卡的流量套餐或者使用网络等。需要说明的是，永久标识符、信任状、安全上下文、认证数据(cookie)、以及令牌等同认证、授权相关的信息，在本发明本申请文件中，为了描述方便起见不做区分、限制。如果不做特殊说明，本申请实施例将以用安全上下文为例进行来描述，但本申请实施例同样适用于其他表述方式的认证、和/或授权信息。在5G中，数据管理网元可以是UDM网元，在未来通信如6G中，数据管理网元仍可以是UDM网元，或有其它的名称，本申请不做限定。
本申请中，网络开放网元是由运营商提供控制面网元。NEF网元以安全的方式对第三方开放运营商网络的对外接口。在SMF网元需要与第三方的网元通信时，NEF网元可作为SMF网元与第三方的网元通信的中继。NEF网元作为中继时，可作为签约用户的标识信息的翻译，以及第三方的网元的标识信息的翻译。比如，NEF将签约用户的SUPI从运营商网络发送到第三方时，可以将SUPI翻译成其对应的外部身份标识(identity，ID)。反之，NEF网元将外部ID(第三方的网元ID)发送到运营商网络时，可将其翻译成SUPI。在5G中，网络开放网元可以是NEF网元，在未来通信如6G中，网络开放网元仍可以是NEF网元，或有其它的名称，本申请不做限定。
本申请中，策略控制网元是由运营商提供的控制面功能，用于向SMF网元提供PDU会话的策略。策略可以包括计费相关策略、QoS相关策略和授权相关策略等。在5G中， 策略控制网元可以是PCF网元，在未来通信如6G中，策略控制网元仍可以是PCF网元，或有其它的名称，本申请不做限定。
图1中Nnef、Nudsf、Nnrf、Npcf、Nudm、Naf、Namf、Nnvaf、Nsmf、N1、N2、N3、N4，以及N6为接口序列号。这些接口序列号的含义可参见3GPP标准协议中定义的含义，在此不做限制。
本申请中的网络视觉感知网元可以是图1所示的NVAF网元，也可以是未来通信系统中的具有上述NVAF网元的功能的网元。本申请中的接入网设备可以是图1中的RAN设备，也可以是未来通信系统中具有上述RAN设备的功能的网元。
为方便说明，本申请后续，将AMF网元简称为AMF，将NVAF网元简称为NVAF，将RAN设备简称为RAN，以及将终端设备称为UE。
可以理解的是，上述网元或者功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。可选的,上述网元或者功能可以由一个设备实现，也可以由多个设备共同实现，还可以是一个设备内的一个功能模块，本申请实施例对此不作具体限定。
为解决背景技术中提到的问题，基于图1所示的架构。如图2所示，本申请提供一种UE的管理方法，该方法用于UE从休眠态(或休眠模式)进入唤醒态(或唤醒模式)。
该方法包括以下步骤：
步骤201，网络设备获取UE的唤醒时间，并根据所述唤醒时间，获取UE的上下文。
在第一种实现方法中，网络设备确定UE的唤醒时间即将到达，则获取UE的上下文。
比如，网络设备本地配置有定时器，当网络设备确定本地的定时器超时，则确定UE的唤醒时间即将到达。在具体实现中，步骤201中的获取UE的唤醒时间，例如可以是：网络设备接收来自外部行业中心的通知信息，通知信息包括UE的唤醒时间。可选的，该通知信息用于指示在UE的唤醒时间即将到达时获取UE的上下文，或者，该通知信息还包括用于指示在UE的唤醒时间即将到达时获取UE的上下文的信息。该通知信息还可以包括该UE的标识或终端群组的标识，该终端群组的标识指示的终端群组包括上述UE。如此，网络设备可根据该唤醒时间，设定定时器，进而当定时器超时后，则根据所述唤醒时间，获取UE的上下文。作为一个具体示例，外部行业中心向网络设备发送的通知信息包括的唤醒时间为上午7点，并指示网络设备在上午7点即将到达时获取UE的上下文，则网络设备可以根据协议定义或预配置方法，设定上午7点之前的某个时刻，如上午6点59分为定时器超时的时间。因而每当上午6点59分到来时，则网络设备的定时器超时，因而触发网络设备获取UE的上下文。
再比如，网络设备接收来自数据管理网元的指示信息，该指示信息用于指示UE的唤醒时间即将到达，指示信息是数据管理网元上的定时器超时后发送的。在具体实现中，该步骤201中的获取唤醒时间，例如可以是：数据管理网元接收来自外部行业中心的通知信息，通知信息包括UE的唤醒时间。可选的，该通知信息用于指示在UE的唤醒时间即将到达时通知网络设备，或者，该通知信息还包括用于指示在UE的唤醒时间即将到达时通知网络设备的信息。该通知信息还可以包括该UE的标识或终端群组的标识，该终端群组的标识指示的终端群组包括上述UE。如此，数据管理网元可根据该唤醒时间，设定定时器，进而当定时器超时后，则向网络设备发送指示信息，进而网络设备可以根据所述唤醒 时间，获取UE的上下文。作为一个具体示例，外部行业中心向数据管理网元发送的通知信息包括的唤醒时间为上午7点，并指示网络设备在上午7点即将到达时通知网络设备，则数据管理网元可以根据协议定义或预配置方法，设定上午7点之前的某个时刻，如上午6点59分为定时器超时的时间。因而每当上午6点59分到来时，则网络设备的定时器超时，因而触发数据管理网元向网络设备发送上述指示信息。
在第二种实现方法中，网络设备确定UE的唤醒时间到达，则获取UE的上下文。
比如，网络设备本地配置有定时器，当网络设备确定本地的定时器超时，则确定UE的唤醒时间到达。在具体实现中，步骤201中的获取UE的唤醒时间，例如可以是：网络设备接收来自外部行业中心的通知信息，通知信息包括UE的唤醒时间。可选的，该通知信息用于指示在UE的唤醒时间到达时获取UE的上下文，或者，该通知信息还包括用于指示在UE的唤醒时间到达时获取UE的上下文的信息。该通知信息还可以包括该UE的标识或终端群组的标识，该终端群组的标识指示的终端群组包括上述UE。如此，网络设备可根据该唤醒时间，设定定时器，进而当定时器超时后，则根据所述唤醒时间，获取UE的上下文。作为一个具体示例，外部行业中心向网络设备发送的通知信息包括的唤醒时间为上午7点，并指示网络设备在上午7点到达时获取UE的上下文，则网络设备可以根据协议定义或预配置方法，设定上午7点为定时器超时的时间。因而每当上午7点到来时，则网络设备的定时器超时，因而触发网络设备获取UE的上下文。
再比如，网络设备接收来自数据管理网元的指示信息，该指示信息用于指示UE的唤醒时间到达，指示信息是数据管理网元上的定时器超时后发送的。在具体实现中，该步骤201中的获取唤醒时间，例如可以是：数据管理网元接收来自外部行业中心的通知信息，通知信息包括UE的唤醒时间。可选的，该通知信息用于指示在UE的唤醒时间到达时通知网络设备，或者，该通知信息还包括用于指示在UE的唤醒时间到达时通知网络设备的信息。该通知信息还可以包括该UE的标识或终端群组的标识，该终端群组的标识指示的终端群组包括上述UE。如此，数据管理网元可根据该唤醒时间，设定定时器，进而当定时器超时后，则向网络设备发送指示信息，进而网络设备可以根据所述唤醒时间，获取UE的上下文。作为一个具体示例，外部行业中心向数据管理网元发送的通知信息包括的唤醒时间为上午7点，并指示网络设备在上午7点到达时通知网络设备，则数据管理网元可以根据协议定义或预配置方法，设定上午7点为定时器超时的时间。因而每当上午7点到来时，则网络设备的定时器超时，因而触发数据管理网元向网络设备发送上述指示信息。
该步骤中，网络设备获取UE的上下文，例如可以是从本地数据库获取UE的上下文，或者还可以是从数据管理网元获取UE的上下文，比如，网络设备向数据管理网元发送请求消息，请求消息用于请求获取UE的上下文，则数据管理网元向网络设备发送UE的上下文。其中，网络设备的本地数据库或数据库管理网元存储UE的上下文的具体实现方法，可以参考实施例3的描述。
步骤202，网络设备根据UE的上下文，建立UE的会话。
如此，在建立了UE的会话之后，则UE进入唤醒态。
基于上述方案，网络设备在确定UE的唤醒时间即将到达(或到达)时，则获取UE的上下文，进而当UE发起建立PDU会话时，不需要重新上报UE的上下文，如此可以节约信令开销，有助于避免发生信令风暴，进而可以提升UE进行唤醒态的成功率。
进一步地，在图2所示的实施例中，在UE进入唤醒态之后，还可以根据该UE的上 下文，增加网络设备的容量。若有多个UE均进入唤醒态，则还可以根据该UE的数量，增加网络设备的容量。如此可以实现动态调整网络设备的容量，有助于根据业务需求灵活调整网络设备的容量。
进一步地，若上述网络设备为RAN设备，则RAN设备还可以根据与RAN设备UE之间的位置关系，调整网络设备的部署。比如调整网络设备的天线方向和/或覆盖范围等。
如图3所示，本申请提供又一种UE的管理方法，该方法用于UE从唤醒态(或唤醒模式)进入休眠态(或休眠模式)。
该方法包括以下步骤：
步骤301，网络设备获取UE的休眠时间，并根据所述休眠时间，存储UE的上下文。
在第一个实现方法中，网络设备确定UE的休眠时间即将到达，则存储UE的上下文。
比如，网络设备本地配置有定时器，当网络设备确定本地的定时器超时，则确定UE的休眠时间即将到达。在具体实现中，步骤301中的获取UE的休眠时间，例如可以是：网络设备接收来自外部行业中心的通知信息，通知信息包括UE的休眠时间。可选的，该通知信息用于指示在UE的休眠时间即将到达时存储UE的上下文，或者，该通知信息还包括用于指示在UE的休眠时间即将到达时存储UE的上下文的信息。该通知信息还可以包括该UE的标识或终端群组的标识，该终端群组的标识指示的终端群组包括上述UE。如此，网络设备可根据该休眠时间，设定定时器，进而当定时器超时后，则根据所述休眠时间，存储UE的上下文。作为一个具体示例，外部行业中心向网络设备发送的通知信息包括的休眠时间为下午23点，并指示网络设备在下午23点即将到达时存储UE的上下文，则网络设备可以根据协议定义或预配置方法，设定下午23点之前的某个时刻，如下午22点59分为定时器超时的时间。因而每当下午22点59分到来时，则网络设备的定时器超时，因而触发网络设备存储UE的上下文。
再比如，网络设备接收来自数据管理网元的指示信息，该指示信息用于指示UE的休眠时间即将到达，指示信息是数据管理网元上的定时器超时后发送的。在具体实现中，步骤301中的获取UE的休眠时间，例如可以是：数据管理网元接收来自外部行业中心的通知信息，通知信息包括UE的休眠时间，可选的，该通知信息用于指示在UE的休眠时间即将到达时通知网络设备，或者，该通知信息还包括用于指示在UE的休眠时间即将到达时通知网络设备的信息，该通知信息还可以包括该UE的标识或终端群组的标识，该终端群组的标识指示的终端群组包括上述UE。如此，数据管理网元可根据该休眠时间，设定定时器，进而当定时器超时后，则向网络设备发送指示信息，进而网络设备可以根据所述休眠时间，存储UE的上下文。作为一个具体示例，外部行业中心向数据管理网元发送的通知信息包括的唤醒时间为下午23点，并指示网络设备在下午23点即将到达时通知网络设备，则数据管理网元可以根据协议定义或预配置方法，设定下午23点之前的某个时刻，如下午22点59分为定时器超时的时间。因而每当下午22点59分到来时，则网络设备的定时器超时，因而触发数据管理网元向网络设备发送上述指示信息。
在第二个实现方法中，网络设备确定UE的休眠时间到达，则存储UE的上下文。
比如，网络设备本地配置有定时器，当网络设备确定本地的定时器超时，则确定UE的休眠时间到达。在具体实现中，步骤301中的获取UE的休眠时间，例如可以是：网络设备接收来自外部行业中心的通知信息，通知信息包括UE的休眠时间。可选的，该通知 信息用于指示在UE的休眠时间到达时存储UE的上下文，或者，该通知信息还包括用于指示在UE的休眠时间到达时存储UE的上下文的信息。该通知信息还可以包括该UE的标识或终端群组的标识，该终端群组的标识指示的终端群组包括上述UE。如此，网络设备可根据该休眠时间，设定定时器，进而当定时器超时后，则根据所述休眠时间，存储UE的上下文。作为一个具体示例，外部行业中心向网络设备发送的通知信息包括的休眠时间为下午23点，并指示网络设备在下午23点到达时存储UE的上下文，则网络设备可以根据协议定义或预配置方法，设定下午23点为定时器超时的时间。因而每当下午23点到来时，则网络设备的定时器超时，因而触发网络设备存储UE的上下文。
再比如，网络设备接收来自数据管理网元的指示信息，该指示信息用于指示UE的休眠时间到达，指示信息是数据管理网元上的定时器超时后发送的。在具体实现中，步骤301中的获取UE的休眠时间，例如可以是：数据管理网元接收来自外部行业中心的通知信息，通知信息包括UE的休眠时间，可选的，该通知信息用于指示在UE的休眠时间到达时通知网络设备，或者，该通知信息还包括用于指示在UE的休眠时间到达时通知网络设备的信息，该通知信息还可以包括该UE的标识或终端群组的标识，该终端群组的标识指示的终端群组包括上述UE。如此，数据管理网元可根据该休眠时间，设定定时器，进而当定时器超时后，则向网络设备发送指示信息，进而网络设备可以根据所述休眠时间，存储UE的上下文。作为一个具体示例，外部行业中心向数据管理网元发送的通知信息包括的唤醒时间为下午23点，并指示网络设备在下午23点到达时通知网络设备，则数据管理网元可以根据协议定义或预配置方法，设定下午23点为定时器超时的时间。因而每当下午23点到来时，则网络设备的定时器超时，因而触发数据管理网元向网络设备发送上述指示信息。
该步骤中，网络设备存储UE的上下文，例如可以是从存储于本地数据库，或者还可以是存储于数据管理网元，比如，网络设备向数据管理网元发送请求消息，请求消息包括UE的上下文，请求消息用于请求存储UE的上下文，则数据管理网元存储UE的上下文。
步骤302，网络设备释放UE的会话。
网络设备释放UE的会话，之后UE则进入休眠态。
需要说明的是，若网络设备将UE的上下文存储至数据管理网元，则该步骤302中，网络设备还可以删除网络设备上存储的UE的上下文。
基于上述方案，网络设备在确定UE的休眠时间即将到达(或到达)时，则存储UE的上下文，进而当UE后续需要发起建立PDU会话时，不需要UE重新上报UE的上下文，而是直接从存储空间中提前获取UE的上下文，如此可以节约信令开销，有助于避免发生信令风暴，进而可以提升UE进行唤醒态的成功率。
进一步地，在图3所示的实施例中，在UE进入休眠态之后，还可以根据该UE的上下文，减少网络设备的容量。若有多个UE均进入休眠态，则还可以根据该UE的数量，减少网络设备的容量。如此可以实现动态调整网络设备的容量，有助于根据业务需求灵活调整网络设备的容量。
进一步地，若上述网络设备为RAN设备，则RAN设备还可以根据与RAN设备UE之间的位置关系，调整网络设备的部署。比如调整网络设备的天线方向和/或覆盖范围等。
需要说明的是，上述图2所示的实施例和图3所示的实施例可以单独实施，也可以相结合实施，即通过图2所示的实施例执行UE从休眠态到唤醒态的操作，通过图3所示的实施例执行UE从唤醒态进入休眠态的操作。
下面结合具体示例，对上述图2和图3所示的实施例进行详细说明。
如图4所示，为本申请提供的又一种UE的管理方法流程示意图。该实施例描述网络侧通过NEF由外部行业中心获得UE的工作时间段信息(休眠、唤醒时间段)，以及当UE进入休眠或者唤醒态时，网络侧需要进行的操作描述信息。
步骤401，外部行业中心向NEF发送请求消息。
该请求消息用于请求网络端监控UE的通信时间段(比如08:00-23:00)，该请求信息中包括UE ID或群组标识(Group ID)，以及还包括指示信息，该指示信息用于指示当UE即将进入休眠态(即休眠时间即将到达)时，RAN或核心网内的网元需将对应的UE上下文存入数据管理网元(如UDSF等)，以及指示当UE即将进入唤醒态(即唤醒时间即将到达)时，RAN或核心网内的网元从数据管理网元中提取对应的UE上下文或者指示数据管理网元主动将对应的UE上下文发给RAN或核心网内的网元。
步骤402-步骤403，NEF向AMF发送请求消息，AMF向RAN发送请求消息，即NEF通过AMF请求RAN监控UE的通信时间段。
该请求消息的作用及包含的内容与上述步骤401的请求消息相同。
步骤404-步骤405，NEF请求SMF和UPF监控UE的通信时间段。
该请求消息的作用及包含的内容与上述步骤401的请求消息相同。
需要说明的是，上述步骤401-步骤405的各个请求消息可以是相同的请求消息，也可以是不同的请求消息，但这些请求消息具有相同的作用，包含相同的内容。
需要说明的是，上述步骤402-步骤404之间没有严格的执行顺序。
该实施例，首先可以让核心网侧和RAN侧掌握UE休眠和唤醒的时间段信息，同时还给网络侧和RAN侧配置了一些动作描述信息，用于指示核心网侧和RAN侧在UE即将休眠或唤醒时做出相应的变化。即UE休眠时，RAN需将对应的UE的上下文存入RAN本地数据库或数据管理网元。进一步地，RAN侧还可以对配置的容量进行缩容处理，同时核心网内的NF需将对应的UE的上下文存入数据管理网元，并且核心网内的网元也可以对配置的容量进行缩容处理。而当UE即将进入唤醒态开始工作时，RAN侧和核心网内的网元则需要从相应的数据库中提取对应的UE的上下文，并且还可以各自对配置的容量进行扩容处理。通过这个实施例的配置信息过程，为后续UE进入休眠和唤醒态时网络侧进行相关准备工作提供指示功能。而现有技术中，外部行业中心只是告知UE的工作时间段，并不指示网络侧和RAN侧根据UE的休眠和唤醒态时做出相应变化，从而造成后续UE进入唤醒态时，需要重新上报UE上下文，造成不必要的信令风暴，并且网络侧的配置容量并不会针对处于唤醒态的UE的数量做出相应的动态扩缩容处理，造成网络资源利用率低下。
如图5所示，为本申请提供的又一种UE的管理方法流程示意图。该实施例描述当UE即将进入休眠态时，RAN侧和核心网侧所进行的相关操作流程。该实施例中以数据管理网元为UDSF为例。
步骤500，外部行业中心设置的休眠时间到达，引发网络侧和RAN侧进行休眠模式。
步骤501，RAN将UE的上下文存储在本地数据库。
作为一种可替代的实现方法，RAN也可以将UE的上下文存储至UDSF。比如RAN 向UDSF发送请求消息，该请求消息包括UE的上下文以及对应的UE ID或Group ID，从而UDSR存储RAN上的UE的上下文。
步骤502-步骤504，AMF、SMF和UPF向UDSF发送请求消息，该请求消息中包括UE的上下文以及对应的UE ID或Group ID。
需要说明的是，步骤502、步骤503、步骤504中，可以只执行其中的部分步骤，也可以执行全部步骤。比如，若AMF是将UE的上下文存储于本地，则不需要执行步骤502，而是AMF直接将UE的上下文存储于本地。再比如，若SMF是将UE的上下文存储于本地，则不需要执行步骤503，而是SMF直接将UE的上下文存储于本地。再比如，若UPF是将UE的上下文存储于本地，则不需要执行步骤504，而是UPF直接将UE的上下文存储于本地。
步骤505，释放PDU会话,释放出空闲态的网络资源，以及减少相关网元(如AMF、SMF、UPF等)的虚拟容量配置。
该步骤中，AMF、SMF和UPF还可以分别删除AMF、SMF和UPF上存储的UE的上下文。
步骤506，RAN侧可以根据处于休眠态和唤醒态的UE的相对位置调整RAN侧的部署，如天线方向，覆盖范围大小等等，同时RAN侧也可以根据处于休眠态的UE的数量调整RAN侧的虚拟容量配置。
通过该实施例的操作，当UE进入休眠态时，网络侧和RAN在进行PDU会话释放时会主动保存对应的UE的上下文，为UE重新进入唤醒模式时网络侧和RAN侧进行后续操作提供了数据支撑。同时，当UE进入休眠态时，RAN侧和核心网侧会减少提供的网络资源的虚拟容量配置，减少了网络资源使用冗余。
如图6所示，为本申请提供的又一种UE的管理方法流程示意图。该实施例描述当UE即将进入唤醒态时(此唤醒态的触发是由配置在核心网内各网元和RAN本地的定时器完成的)，RAN侧和核心网侧所进行的相关操作。
步骤600，外部行业中心设置的唤醒时间到达，引发网络侧和RAN侧进行唤醒模式。
步骤601，RAN从本地数据库中提取UE的上下文。
作为一种可替代的实现方法，RAN上的UE的上下文是存储在UDSF上的，则该步骤中RAN从UDSF获取UE的上下文。
步骤602-步骤604，AMF、SMF和UPF分别从UDSF获取UE的上下文。
比如，AMF、SMF和UPF分别向UDSF发起请求消息，请求消息中包括UE ID或Group ID，该请求消息用于获取UE的上下文。然后UDSF分别向AMF、SMF和UPF发送UE的上下文。
需要说明的是，步骤602、步骤603、步骤604中，可以只执行其中的部分步骤，也可以执行全部步骤。比如，若AMF是将UE的上下文存储于本地的，则不需要执行步骤602，AMF从本地获取UE的上下文。再比如，若SMF是将UE的上下文存储于本地的，则不需要执行步骤603，SMF从本地获取UE的上下文。再比如，若UPF是将UE的上下文存储于本地的，则不需要执行步骤604，UPF从本地获取UE的上下文。
步骤605，建立PDU会话,恢复通信连接，同时核心网侧增加相关网络的容量配置。
步骤606，RAN侧可以根据处于休眠态和唤醒态的UE相对位置调整RAN侧的部署， 如天线方向，覆盖范围大小等等。同时RAN侧也可以根据处于唤醒态的UE的数量调整RAN侧的虚拟容量的配置。
通过该实施例的操作，当UE进入唤醒模式重建PDU会话时，UE不用再上报UE的上下文，RAN侧和核心网侧内的网元会主动从数据库中提取先前已经储存的UE的上下文，从而减少了UE与网络侧的信令交互，降低了信令风暴发生的可能性。同时当大量UE重新进入唤醒态时，RAN侧和核心网侧会增加提供的网络资源虚拟容量配置，实现动态的资源提供策略，提高了网络资源的使用效率。
如图7所示，为本申请提供的又一种UE的管理方法流程示意图。该实施例描述当UE即将进入唤醒态时(此唤醒态的触发是由RAN和数据管理网元完成的)，RAN侧和核心网侧所进行的相关操作。该实施例以数据管理网元为UDSF为例。
步骤700，外部行业中心设置的唤醒时间到达，UDSF触发进行唤醒模式。
步骤701，RAN从本地数据库中提取UE的上下文。
作为一种可替代的实现方法，RAN上的UE的上下文是存储在UDSF上的，则该步骤中UDSF向RAN发送通知消息，该通知信息包含UE的上下文以及对应的UE ID或Group ID。
步骤702-步骤704，UDSF向AMF、SMF和UPF发送通知信息，该通知信息包含UE的上下文以及对应的UE ID或Group ID。
需要说明的是，步骤702、步骤703、步骤704中，可以是其中的部分步骤的通知信息携带UE的上下文，也可以是全部步骤的通知信息均携带UE的上下文。比如，若AMF是将UE的上下文存储于本地，则上述步骤702的通知消息不携带UE的上下文，该通知信息的作用是为了通知AMF从本地获取UE的上下文。再比如，若SMF是将UE的上下文存储于本地，则上述步骤703的通知消息不携带UE的上下文，该通知信息的作用是为了通知SMF从本地获取UE的上下文。再比如，若UPF是将UE的上下文存储于本地，则上述步骤704的通知消息不携带UE的上下文，该通知信息的作用是为了通知UPF从本地获取UE的上下文。
步骤705，建立PDU会话,恢复通信连接，同时核心网侧增加相关网络的容量配置。
步骤706，RAN侧可以根据处于休眠态和唤醒态的UE相对位置调整RAN侧的部署，如天线方向，覆盖范围大小等等。同时RAN侧也可以根据处于唤醒态的UE的数量调整RAN侧的虚拟容量的配置。
通过该实施例的操作，当UE进入唤醒模式重建PDU会话时，UE不用再上报UE的上下文，UDSF会主动向核心网内的网元发送先前储存的UE上下文，从而减少了UE与网络侧的信令交互，降低了信令风暴发生的可能性。同时当大量UE重新进入唤醒工作态时，RAN侧和核心网侧会增加提供的网络资源虚拟容量配置，实现动态的资源提供策略，提高了网络资源的使用效率。
需要说明的是，上述图6或图7所示的实施例是图2所示的实施例的一个具体实现方式，其具体实现细节可以参考图2所示的实施例中的相关描述。上述图5所示的实施例是图2所示的实施例的一个具体实现方式，其具体实现细节可以参考图3所示的实施例中的相关描述。
需要说明的是，上述图5与图6所示的实施例之间可以相互结合实施例，或者是，上 述图5与图7所示的实施例之间可以相互结合实施例。
上述主要从各个网元之间交互的角度对本申请提供的方案进行了介绍。可以理解的是，上述实现各网元为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本发明能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
如图8所示，为本申请所涉及的终端设备的管理装置的一种可能的示例性框图，该装置800可以以软件或硬件的形式存在。通信装置800可以包括：处理单元802和通信单元803。作为一种实现方式，该通信单元803可以包括接收单元和发送单元。处理单元802用于对通信装置800的动作进行控制管理。通信单元803用于支持通信装置800与其他网络实体的通信。通信装置800还可以包括存储单元801，用于存储通信装置800的程序代码和数据。
其中，处理单元802可以是处理器或控制器，例如可以是通用中央处理器(central processing unit，CPU)，通用处理器，数字信号处理(digital signal processing，DSP)，专用集成电路(application specific integrated circuits，ASIC)，现场可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包括一个或多个微处理器组合，DSP和微处理器的组合等等。存储单元801可以是存储器。通信单元803是一种该装置的接口电路，用于从其它装置接收信号。例如，当该装置以芯片的方式实现时，该通信单元803是该芯片用于从其它芯片或装置接收信号的接口电路，或者，是该芯片用于向其它芯片或装置发送信号的接口电路。
该通信装置800可以为上述任一实施例中的网络设备，还可以为用于网络设备的芯片。例如，当通信装置800为网络设备时，该处理单元802例如可以是处理器，该通信单元803例如可以是收发器。可选的，该收发器可以包括射频电路，该存储单元例如可以是存储器。例如，当通信装置800为用于网络设备的芯片时，该处理单元802例如可以是处理器，该通信单元803例如可以是输入/输出接口、管脚或电路等。该处理单元802可执行存储单元存储的计算机执行指令，可选地，该存储单元为该芯片内的存储单元，如寄存器、缓存等，该存储单元还可以是该网络设备内的位于该芯片外部的存储单元，如只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)等。
在第一个实施例中，该通信装置800为网络设备，处理单元802，用于获取终端设备的唤醒时间，并根据所述唤醒时间，获取所述终端设备的上下文；以及，根据所述终端设备的上下文，建立所述终端设备的会话。
在一种可能的实现方法中，处理单元802，具体用于确定所述终端设备的所述唤醒时间即将到达，则获取所述终端设备的上下文。
在一种可能的实现方法中，处理单元802，具体用于确定本地的定时器超时，则确定 所述终端设备的唤醒时间即将到达；或者，通过通信单元803接收来自数据管理网元的指示信息，所述指示信息用于指示所述终端设备的唤醒时间即将到达，所述指示信息是所述数据管理网元上的定时器超时后发送的。
在一种可能的实现方法中，处理单元802，具体用于接收来自外部行业中心的通知信息，所述通知信息包括所述终端设备的所述唤醒时间。
在一种可能的实现方法中，所述通知信息用于指示在所述终端设备的所述唤醒时间即将到达时获取所述终端设备的上下文；或者，所述通知信息还包括用于指示在所述终端设备的所述唤醒时间即将到达时获取所述终端设备的上下文的信息。
在一种可能的实现方法中，所述通知信息还包括所述终端设备的标识和/或终端群组的标识，所述终端群组的标识指示的终端群组包括所述终端设备。
在一种可能的实现方法中，处理单元802，还用于根据所述终端设备的上下文，增加所述网络设备的容量。
在一种可能的实现方法中，处理单元802，具体用于从本地数据库或数据管理网元获取所述终端设备的上下文。
在一种可能的实现方法中，网络设备为接入网设备；处理单元802，还用于根据与所述终端设备之间的位置关系，调整所述网络设备的部署。
在一种可能的实现方法中，处理单元802，具体用于调整所述网络设备的天线方向和/或覆盖范围。
在一种可能的实现方法中，网络设备包括接入网设备、移动性管理网元、会话管理网元、用户面网元。
在第二个实施例中，该通信装置800为网络设备，处理单元802，用于获取终端设备的休眠时间，并根据所述休眠时间，存储所述终端设备的上下文；以及释放所述终端设备的会话。
在一种可能的实现方法中，处理单元802，具体用于确定所述终端设备的所述休眠时间即将到达，则存储所述终端设备的上下文。
在一种可能的实现方法中，处理单元802，具体用于确定本地的定时器超时，则确定所述终端设备的休眠时间即将到达；或者，通过通信单元803接收来自数据管理网元的指示信息，所述指示信息用于指示所述终端设备的休眠时间即将到达，所述指示信息是所述数据管理网元上的定时器超时后发送的。
在一种可能的实现方法中，处理单元802，具体用于通过通信单元803接收来自外部行业中心的通知信息，所述通知信息包括所述终端设备的所述休眠时间。
在一种可能的实现方法中，所述通知信息用于指示在所述终端设备的所述休眠时间即将到达时存储所述终端设备的上下文；或者，所述通知信息还包括用于指示在所述终端设备的所述休眠时间即将到达时存储所述终端设备的上下文的信息。
在一种可能的实现方法中，所述通知信息还包括所述终端设备的标识和/或终端群组的标识，所述终端群组的标识指示的终端群组包括所述终端设备。
在一种可能的实现方法中，处理单元802，还用于根据所述终端设备的上下文，减少所述网络设备的容量。
在一种可能的实现方法中，处理单元802，具体用于将所述终端设备的上下文存储在本地数据库；和/或，将所述终端设备的上下文存储至数据管理网元。
在一种可能的实现方法中，网络设备为接入网设备；处理单元802，还用于根据与所述终端设备之间的位置关系，调整所述网络设备的部署。
在一种可能的实现方法中，处理单元802，具体用于调整所述网络设备的天线方向和/或覆盖范围。
在一种可能的实现方法中，网络设备包括接入网设备、移动性管理网元、会话管理网元、用户面网元。
可以理解的是，该通信装置用于上述UE的管理方法时的具体实现过程以及相应的有益效果，可以参考前述方法实施例中的相关描述，这里不再赘述。
如图9所示，为本申请所涉及的终端设备的管理装置的一种可能的示例性框图，该通信装置900可以以软件或硬件的形式存在。通信装置900可以包括：处理单元902和通信单元903。作为一种实现方式，该通信单元903可以包括接收单元和发送单元。处理单元902用于对通信装置900的动作进行控制管理。通信单元903用于支持通信装置900与其他网络实体的通信。通信装置900还可以包括存储单元901，用于存储通信装置900的程序代码和数据。
其中，处理单元902可以是处理器或控制器，例如可以是CPU，通用处理器，DSP，ASIC，FPGA或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包括一个或多个微处理器组合，DSP和微处理器的组合等等。存储单元901可以是存储器。通信单元903是一种该装置的接口电路，用于从其它装置接收信号。例如，当该装置以芯片的方式实现时，该通信单元903是该芯片用于从其它芯片或装置接收信号的接口电路，或者，是该芯片用于向其它芯片或装置发送信号的接口电路。
该通信装置900可以为上述任一实施例中的数据管理网元，还可以为用于数据管理网元的芯片。例如，当通信装置900为数据管理网元时，该处理单元902例如可以是处理器，该通信单元903例如可以是收发器。可选的，该收发器可以包括射频电路，该存储单元例如可以是存储器。例如，当通信装置900为用于数据管理网元的芯片时，该处理单元902例如可以是处理器，该通信单元903例如可以是输入/输出接口、管脚或电路等。该处理单元902可执行存储单元存储的计算机执行指令，可选地，该存储单元为该芯片内的存储单元，如寄存器、缓存等，该存储单元还可以是该数据管理网元内的位于该芯片外部的存储单元，如ROM或可存储静态信息和指令的其他类型的静态存储设备，RAM等。
在第一个实施例中，该通信装置900为数据管理网元，处理单元902，用于确定终端设备的唤醒时间即将到达；通信单元903，用于向网络设备发送指示信息，所述指示信息用于指示所述终端设备的唤醒时间即将到达。
在一种可能的实现方法中，处理单元902，具体用于确定本地的定时器超时，则确定所述终端设备的唤醒时间即将到达。
在一种可能的实现方法中，通信单元903，还用于接收来自所述网络设备的请求消息，所述请求消息用于请求获取所述终端设备的上下文；以及，向所述网络设备发送所述终端设备的上下文。
在第二个实施例中，该通信装置900为数据管理网元，处理单元902，用于确定终端 设备的休眠时间即将到达；通信单元903，用于向网络设备发送指示信息，所述指示信息用于指示所述终端设备的休眠时间即将到达。
在一种可能的实现方法中，处理单元902，具体用于确定本地的定时器超时，则确定所述终端设备的休眠时间即将到达。
在一种可能的实现方法中，通信单元903，还用于接收来自所述网络设备的请求消息，所述请求消息包括所述终端设备的上下文；处理单元902，还用于存储所述终端设备的上下文。
可以理解的是，该通信装置用于上述UE的管理方法时的具体实现过程以及相应的有益效果，可以参考前述方法实施例中的相关描述，这里不再赘述。
参阅图10所示，为本申请提供的一种终端设备的管理装置示意图，该通信装置可以是上述实施例中的网络设备、或数据管理网元。该通信装置1000包括：处理器1002、通信接口1003、存储器1001。可选的，通信装置1000还可以包括通信线路1004。其中，通信接口1003、处理器1002以及存储器1001可以通过通信线路1004相互连接；通信线路1004可以是外设部件互连标准(peripheral component interconnect，简称PCI)总线或扩展工业标准结构(extended industry standard architecture，简称EISA)总线等。所述通信线路1004可以分为地址总线、数据总线、控制总线等。为便于表示，图10中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
处理器1002可以是一个CPU，微处理器，ASIC，或一个或多个用于控制本申请方案程序执行的集成电路。
通信接口1003，使用任何收发器一类的装置，用于与其他设备或通信网络通信，如以太网，无线接入网(radio access network，RAN)，无线局域网(wireless local area networks，WLAN)，有线接入网等。
存储器1001可以是ROM或可存储静态信息和指令的其他类型的静态存储设备，RAM或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过通信线路1004与处理器相连接。存储器也可以和处理器集成在一起。
其中，存储器1001用于存储执行本申请方案的计算机执行指令，并由处理器1002来控制执行。处理器1002用于执行存储器1001中存储的计算机执行指令，从而实现本申请上述实施例提供的UE的管理方法。
可选的，本申请实施例中的计算机执行指令也可以称之为应用程序代码，本申请实施例对此不作具体限定。
本领域普通技术人员可以理解：本申请中涉及的第一、第二等各种数字编号仅为描述方便进行的区分，并不用来限制本申请实施例的范围，也表示先后顺序。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或” 的关系。“至少一个”是指一个或者多个。至少两个是指两个或者多个。“至少一个”、“任意一个”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a,b,或c中的至少一项(个、种)，可以表示：a,b,c,a-b,a-c,b-c,或a-b-c，其中a,b,c可以是单个，也可以是多个。“多个”是指两个或两个以上，其它量词与之类似。此外，对于单数形式“a”，“an”和“the”出现的元素(element)，除非上下文另有明确规定，否则其不意味着“一个或仅一个”，而是意味着“一个或多于一个”。例如，“a device”意味着对一个或多个这样的device。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包括一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(Solid State Disk，SSD))等。
本申请实施例中所描述的各种说明性的逻辑单元和电路可以通过通用处理器，数字信号处理器，专用集成电路(ASIC)，现场可编程门阵列(FPGA)或其它可编程逻辑装置，离散门或晶体管逻辑，离散硬件部件，或上述任何组合的设计来实现或操作所描述的功能。通用处理器可以为微处理器，可选地，该通用处理器也可以为任何传统的处理器、控制器、微控制器或状态机。处理器也可以通过计算装置的组合来实现，例如数字信号处理器和微处理器，多个微处理器，一个或多个微处理器联合一个数字信号处理器核，或任何其它类似的配置来实现。
本申请实施例中所描述的方法或算法的步骤可以直接嵌入硬件、处理器执行的软件单元、或者这两者的结合。软件单元可以存储于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、可移动磁盘、CD-ROM或本领域中其它任意形式的存储媒介中。示例性地，存储媒介可以与处理器连接，以使得处理器可以从存储媒介中读取信息，并可以向存储媒介存写信息。可选地，存储媒介还可以集成到处理器中。处理器和存储媒介可以设置于ASIC中。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管结合具体特征及其实施例对本申请进行了描述，显而易见的，在不脱离本申请的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明，且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱 离本申请的范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包括这些改动和变型在内。

Claims (40)

  1. 一种终端设备的管理方法，其特征在于，包括：
    网络设备获取终端设备的唤醒时间，并根据所述唤醒时间，获取所述终端设备的上下文；
    所述网络设备根据所述终端设备的上下文，建立所述终端设备的会话。
  2. 如权利要求1所述的方法，其特征在于，所述根据所述唤醒时间，获取所述终端设备的上下文，包括：
    所述网络设备确定所述终端设备的所述唤醒时间即将到达，则获取所述终端设备的上下文。
  3. 如权利要求2所述的方法，其特征在于，所述网络设备确定终端设备的唤醒时间即将到达，包括：
    所述网络设备确定本地的定时器超时，则确定所述终端设备的唤醒时间即将到达；或者，
    所述网络设备接收来自数据管理网元的指示信息，所述指示信息用于指示所述终端设备的唤醒时间即将到达，所述指示信息是所述数据管理网元上的定时器超时后发送的。
  4. 如权利要求1-3任一所述的方法，其特征在于，所述网络设备获取终端设备的唤醒时间，包括：
    所述网络设备接收来自外部行业中心的通知信息，所述通知信息包括所述终端设备的所述唤醒时间。
  5. 如权利要求4所述的方法，其特征在于，所述通知信息用于指示在所述终端设备的所述唤醒时间即将到达时获取所述终端设备的上下文；或者，
    所述通知信息还包括用于指示在所述终端设备的所述唤醒时间即将到达时获取所述终端设备的上下文的信息。
  6. 如权利要求1-5任一所述的方法，其特征在于，所述网络设备获取所述终端设备的上下文，包括：
    所述网络设备从本地数据库或数据管理网元获取所述终端设备的上下文。
  7. 一种终端设备的管理方法，其特征在于，包括：
    网络设备获取终端设备的休眠时间，并根据所述休眠时间，存储所述终端设备的上下文；
    所述网络设备释放所述终端设备的会话。
  8. 如权利要求7所述的方法，其特征在于，所述网络设备根据所述休眠时间，存储所述终端设备的上下文，包括：
    所述网络设备确定所述终端设备的所述休眠时间即将到达，则存储所述终端设备的上下文。
  9. 如权利要求8所述的方法，其特征在于，所述网络设备确定终端设备的休眠时间即将到达，包括：
    所述网络设备确定本地的定时器超时，则确定所述终端设备的休眠时间即将到达；或者，
    所述网络设备接收来自数据管理网元的指示信息，所述指示信息用于指示所述终端设 备的休眠时间即将到达，所述指示信息是所述数据管理网元上的定时器超时后发送的。
  10. 如权利要求7-9任一所述的方法，其特征在于，所述网络设备获取终端设备的休眠时间，包括：
    所述网络设备接收来自外部行业中心的通知信息，所述通知信息包括所述终端设备的所述休眠时间。
  11. 如权利要求10所述的方法，其特征在于，所述通知信息用于指示在所述终端设备的所述休眠时间即将到达时存储所述终端设备的上下文；或者，
    所述通知信息还包括用于指示在所述终端设备的所述休眠时间即将到达时存储所述终端设备的上下文的信息。
  12. 如权利要求7-11任一所述的方法，其特征在于，所述网络设备存储所述终端设备的上下文，包括：
    所述网络设备将所述终端设备的上下文存储在本地数据库；和/或，
    所述网络设备将所述终端设备的上下文存储至数据管理网元。
  13. 如权利要求1-12任一所述的方法，其特征在于，所述网络设备为接入网设备；所述方法还包括：
    所述网络设备根据与所述终端设备之间的位置关系，调整所述网络设备的部署。
  14. 如权利要求13所述的方法，其特征在于，所述网络设备调整所述网络设备的部署，包括：
    所述网络设备调整所述网络设备的天线方向和/或覆盖范围。
  15. 如权利要求1-12任一所述的方法，其特征在于，所述网络设备包括接入网设备、移动性管理网元、会话管理网元、用户面网元。
  16. 一种终端设备的管理装置，其特征在于，包括：
    处理单元，用于获取终端设备的唤醒时间，并根据所述唤醒时间，获取所述终端设备的上下文；以及，根据所述终端设备的上下文，建立所述终端设备的会话。
  17. 如权利要求16所述的装置，其特征在于，所述处理单元，具体用于：
    确定所述终端设备的所述唤醒时间即将到达，则获取所述终端设备的上下文。
  18. 如权利要求17所述的装置，其特征在于，所述处理单元，具体用于：
    确定本地的定时器超时，则确定所述终端设备的唤醒时间即将到达；或者，
    所述装置还包括通信单元；通过所述通信单元接收来自数据管理网元的指示信息，所述指示信息用于指示所述终端设备的唤醒时间即将到达，所述指示信息是所述数据管理网元上的定时器超时后发送的。
  19. 如权利要求16-18任一所述的装置，其特征在于，所述装置还包括通信单元；所述处理单元，具体用于：
    通过所述通信单元接收来自外部行业中心的通知信息，所述通知信息包括所述终端设备的所述唤醒时间。
  20. 如权利要求19所述的装置，其特征在于，所述通知信息用于指示在所述终端设备的所述唤醒时间即将到达时获取所述终端设备的上下文；或者，
    所述通知信息还包括用于指示在所述终端设备的所述唤醒时间即将到达时获取所述终端设备的上下文的信息。
  21. 如权利要求16-20任一所述的装置，其特征在于，所述处理单元，具体用于：
    从本地数据库或数据管理网元获取所述终端设备的上下文。
  22. 一种终端设备的管理装置，其特征在于，包括：
    处理单元，用于获取终端设备的休眠时间，并根据所述休眠时间，存储所述终端设备的上下文；以及，释放所述终端设备的会话。
  23. 如权利要求22所述的装置，其特征在于，所述网络设备根据所述休眠时间，存储所述终端设备的上下文，包括：
    所述网络设备确定所述终端设备的所述休眠时间即将到达，则存储所述终端设备的上下文。
  24. 如权利要求23所述的装置，其特征在于，所述处理单元，具体用于：
    确定本地的定时器超时，则确定所述终端设备的休眠时间即将到达；或者，
    所述装置还包括通信单元；通过所述通信单元接收来自数据管理网元的指示信息，所述指示信息用于指示所述终端设备的休眠时间即将到达，所述指示信息是所述数据管理网元上的定时器超时后发送的。
  25. 如权利要求22-24任一所述的装置，其特征在于，所述装置还包括通信单元；所述处理单元，具体用于：
    通过所述通信单元接收来自外部行业中心的通知信息，所述通知信息包括所述终端设备的所述休眠时间。
  26. 如权利要求25所述的装置，其特征在于，所述通知信息用于指示在所述终端设备的所述休眠时间即将到达时存储所述终端设备的上下文；或者，
    所述通知信息还包括用于指示在所述终端设备的所述休眠时间即将到达时存储所述终端设备的上下文的信息。
  27. 如权利要求22-26任一所述的装置，其特征在于，所述处理单元，具体用于：
    将所述终端设备的上下文存储在本地数据库；和/或，
    将所述终端设备的上下文存储至数据管理网元。
  28. 如权利要求16-27任一所述的装置，其特征在于，所述装置为接入网设备；所述处理单元，还用于根据与所述终端设备之间的位置关系，调整所述网络设备的部署。
  29. 如权利要求28所述的装置，其特征在于，所述处理单元，具体用于调整所述网络设备的天线方向和/或覆盖范围。
  30. 如权利要求16-27任一所述的装置，其特征在于，所述装置包括接入网设备、移动性管理网元、会话管理网元、用户面网元。
  31. 一种通信装置，其特征在于，包括：通信接口和至少一个处理器，所述通信接口和所述至少一个处理器通过线路互联，所述通信接口用于执行权利要求1到6任一项所述的方法中，在所述装置侧进行消息接收和发送的操作；
    所述至少一个处理器调用指令，执行权利要求1到6任一项所述的方法中，在所述装置进行的消息处理或控制操作。
  32. 一种通信装置，其特征在于，包括：通信接口和至少一个处理器，所述通信接口和所述至少一个处理器通过线路互联，所述通信接口用于执行权利要求7到15任一项所述的方法中，在所述装置侧进行消息接收和发送的操作；
    所述至少一个处理器调用指令，执行权利要求7到15任一项所述的方法中，在所述装置进行的消息处理或控制操作。
  33. 一种芯片系统，其特征在于，包括：所述芯片系统包括至少一个处理器，和接口电路，所述接口电路和所述至少一个处理器通过线路互联，所述处理器通过运行指令，以执行权利要求1到6任一项所述的方法。
  34. 一种芯片系统，其特征在于，包括：所述芯片系统包括至少一个处理器，和接口电路，所述接口电路和所述至少一个处理器通过线路互联，所述处理器通过运行指令，以执行权利要求7到15任一项所述的方法。
  35. 一种通信装置，其特征在于，用于执行权利要求1到6任一项所述的方法。
  36. 一种通信装置，其特征在于，用于执行权利要求7到15任一项所述的方法。
  37. 一种包含指令的计算机程序产品，其特征在于，当其在计算机上运行时，使得计算机执行上述权利要求1到6任一项所述的方法。
  38. 一种包含指令的计算机程序产品，其特征在于，当其在计算机上运行时，使得计算机执行上述权利要求7到15任一项所述的方法。
  39. 一种计算机可读存储介质，其特征在于，包括指令，当其在计算机上运行时，使得计算机执行如权利要求1到6任一项所述的方法。
  40. 一种计算机可读存储介质，其特征在于，包括指令，当其在计算机上运行时，使得计算机执行如权利要求7到15任一项所述的方法。
PCT/CN2020/085331 2019-04-18 2020-04-17 一种终端设备的管理方法及装置 WO2020211837A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
AU2020259560A AU2020259560A1 (en) 2019-04-18 2020-04-17 Management method and apparatus for terminal device
EP20791167.8A EP3952598A4 (en) 2019-04-18 2020-04-17 MANAGEMENT METHOD AND DEVICE FOR TERMINAL
US17/503,992 US20220039018A1 (en) 2019-04-18 2021-10-18 Terminal device management method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910312419.3A CN111836401A (zh) 2019-04-18 2019-04-18 一种终端设备的管理方法及装置
CN201910312419.3 2019-04-18

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/503,992 Continuation US20220039018A1 (en) 2019-04-18 2021-10-18 Terminal device management method and apparatus

Publications (1)

Publication Number Publication Date
WO2020211837A1 true WO2020211837A1 (zh) 2020-10-22

Family

ID=72838072

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/085331 WO2020211837A1 (zh) 2019-04-18 2020-04-17 一种终端设备的管理方法及装置

Country Status (5)

Country Link
US (1) US20220039018A1 (zh)
EP (1) EP3952598A4 (zh)
CN (1) CN111836401A (zh)
AU (1) AU2020259560A1 (zh)
WO (1) WO2020211837A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1941993A (zh) * 2005-10-01 2007-04-04 华为技术有限公司 一种移动终端上下文的控制方法
US20120214502A1 (en) * 2011-02-21 2012-08-23 Telefonaktiebolaget L M Ericsson (Publ) Offline device paging
US20130301611A1 (en) * 2012-05-10 2013-11-14 Samsung Electronics Co., Ltd. Method and system for connectionless transmission during uplink and downlink of data packets
WO2015021284A1 (en) * 2013-08-08 2015-02-12 Intel IP Corporation Power saving mode optimizations and related procedures
CN106792928A (zh) * 2015-11-23 2017-05-31 中国移动通信集团公司 一种终端接入网络的方法及装置

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110239011A1 (en) * 2010-03-26 2011-09-29 Nokia Corporation Method and apparatus for synchronizing wake-ups of offline mobile devices
CN103686955B (zh) * 2012-09-24 2018-10-16 中兴通讯股份有限公司 电能优化方法及系统
US9609632B2 (en) * 2012-11-01 2017-03-28 Lg Electronics Inc. Method and device for managing RAN resources in wireless communication system
EP2757856B1 (en) * 2013-01-17 2023-11-08 Alcatel Lucent Optimization of context and/or connection management in a mobile communication system

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1941993A (zh) * 2005-10-01 2007-04-04 华为技术有限公司 一种移动终端上下文的控制方法
US20120214502A1 (en) * 2011-02-21 2012-08-23 Telefonaktiebolaget L M Ericsson (Publ) Offline device paging
US20130301611A1 (en) * 2012-05-10 2013-11-14 Samsung Electronics Co., Ltd. Method and system for connectionless transmission during uplink and downlink of data packets
WO2015021284A1 (en) * 2013-08-08 2015-02-12 Intel IP Corporation Power saving mode optimizations and related procedures
CN106792928A (zh) * 2015-11-23 2017-05-31 中国移动通信集团公司 一种终端接入网络的方法及装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
CMCC: "Discussion on UE States in NR", 3GPP DRAFT; R2-165211, 26 August 2016 (2016-08-26), Göteborg , Sweden, pages 1 - 5, XP051126809 *
See also references of EP3952598A4 *

Also Published As

Publication number Publication date
US20220039018A1 (en) 2022-02-03
EP3952598A1 (en) 2022-02-09
CN111836401A (zh) 2020-10-27
EP3952598A4 (en) 2022-05-25
AU2020259560A1 (en) 2021-11-11

Similar Documents

Publication Publication Date Title
WO2020220747A1 (zh) 一种tsn业务的处理方法、装置及系统
WO2020224463A1 (zh) 一种数据分析方法及装置
WO2020221266A1 (zh) 一种通信方法及装置
WO2022257549A1 (zh) 网络切片方法、设备及存储介质
JP2023085333A (ja) データ伝送の保証方法及び通信機器
EP3713372A1 (en) Method and device for creating user group
WO2021135187A1 (zh) 一种切片控制方法及装置
WO2019192546A1 (zh) 一种定位方法及装置
EP3780667A1 (en) Context management method and apparatus
WO2020103517A1 (zh) 终端的能力信息的获取方法、装置及系统
WO2020200254A1 (zh) 一种通信方法及装置
WO2020200319A1 (zh) 一种终端设备的网络接入管理方法及装置
WO2020220799A1 (zh) 一种通信方法、装置及系统
WO2019192445A1 (zh) 一种组播组创建、组播组加入方法及装置
WO2021000938A1 (zh) 一种同步pdu会话状态的方法、装置、系统及芯片
US11889568B2 (en) Systems and methods for paging over WiFi for mobile terminating calls
WO2020248709A1 (zh) 一种mdbv的确定方法、装置及系统
WO2022068771A1 (zh) 一种通信方法及通信装置
WO2023179238A1 (zh) 一种授时方法、通信装置及通信系统
WO2020211837A1 (zh) 一种终端设备的管理方法及装置
WO2022001753A1 (zh) 一种通信方法及装置
JP2024502890A (ja) 情報処理方法、端末、ネットワーク側機器及び可読記憶媒体
WO2021189496A1 (zh) 用于网络切片的数据传输方法及设备
US11956322B1 (en) Systems and methods for determining locations of emergency callers in standalone non-public networks
WO2023185062A1 (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: 20791167

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020259560

Country of ref document: AU

Date of ref document: 20200417

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2020791167

Country of ref document: EP

Effective date: 20211103