WO2019206322A1 - 能力开放方法、相关装置及系统 - Google Patents

能力开放方法、相关装置及系统 Download PDF

Info

Publication number
WO2019206322A1
WO2019206322A1 PCT/CN2019/084741 CN2019084741W WO2019206322A1 WO 2019206322 A1 WO2019206322 A1 WO 2019206322A1 CN 2019084741 W CN2019084741 W CN 2019084741W WO 2019206322 A1 WO2019206322 A1 WO 2019206322A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
time information
state
request message
application server
Prior art date
Application number
PCT/CN2019/084741
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 EP19792517.5A priority Critical patent/EP3761711A4/en
Publication of WO2019206322A1 publication Critical patent/WO2019206322A1/zh
Priority to US17/029,577 priority patent/US20210007172A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/53—Network services using third party service providers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • 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

Definitions

  • the present application relates to the field of wireless communication technologies, and in particular, to a capability opening method, related apparatus, and system.
  • the mobile communication network has limited network capabilities to third-party service providers, and cannot well support the business needs of new radio (NR) or third-party service providers in future communication systems.
  • NR new radio
  • the embodiments of the present application provide a capability opening method, a related device, and a system, which can enable a mobile communication network to open more network capabilities to a third-party service provider, and better support the service requirements of a third-party service provider.
  • the application provides a capability opening method, which is applied to an application server side, and the method may include: the application server sends a request message to the access network device, where the request message may include first time information and/or second Time information.
  • the application server receives a response message of the request message from the access network device.
  • the application provides a capability opening method, which is applied to an access network device side.
  • the method may include: the access network device acquires a request message from an application server, where the request message may include first time information and/or Or second time information. Then, the access network device sets the connection state of the terminal device according to the first time information and/or the second time information.
  • the request message from the application server refers to a series of request messages initiated from the application server, going through the core network device, and finally reaching the access network device, and the series of request messages are used together to request access.
  • the network device sets the connection state of the terminal device.
  • the core network element that the request message experiences may specifically include, but is not limited to, NEF, UDM, and AMF.
  • the access network device may receive the request message from the application server through the access management network element (AMF) or receive the request message from the application server via the terminal device.
  • AMF access management network element
  • the first time information may also refer to information for setting a transmission duration of the data packet, such as maximum response time information.
  • the second time information may also refer to information for setting a transmission delay of the data packet, such as maximum delay time information.
  • the first time information may be used to set a time when the terminal device is in the first state of the connected state
  • the second time information may be used to set the time when the terminal device is in the second state of the connected state.
  • the first state of the connected state may include, but is not limited to, an active state, such as an RRC CONNECTED state.
  • the second state of the connected state may include, but is not limited to, an inactive state, such as an RRC INACTIVE state.
  • the access network device may set the time when the terminal device is in the first state of the connected state according to the first time information, and/or set the time when the terminal device is in the second state of the connected state according to the second time information.
  • the network capability opened by the mobile communication operator may include: setting a duration in which the terminal device (UE) is in the RRC INACTIVE state.
  • the third-party service provider can request the network side to set the duration of the terminal device (UE) in the RRC INACTIVE state, which can facilitate the third-party service provider to transmit the downlink data packet to the terminal device.
  • the request message may further include identifier information of the application, where the connection state is a connection state of the terminal device corresponding application. This enables the connection state of the terminal device to be set for a specific application, providing differentiated network capabilities for different applications.
  • the application provides a capability opening method, which is applied to an application server side, and the method may include: the application server sends a request message to the access network device, where the request message may include first time information and/or second Time information.
  • the application server receives a response message of the request message from the access network device.
  • the application provides a capability opening method, which is applied to an access network device side.
  • the method may include: the access network device acquiring a request message from an application server, where the request message may include the first time information and/or Or second time information.
  • the access network device sets the state of the terminal device in the MICO mode according to the first time information and/or the second time information.
  • the request message from the application server refers to a series of request messages initiated from the application server, going through the core network device, and finally reaching the access network device, and the series of request messages are used together to request access.
  • the network device sets the connection state of the terminal device.
  • the core network element that the request message experiences may specifically include, but is not limited to, NEF, UDM, and AMF.
  • the access network device may receive the request message from the application server through the access management network element (AMF) or receive the request message from the application server via the terminal device.
  • AMF access management network element
  • the first time information may also refer to information for setting a transmission duration of the data packet, such as maximum response time information.
  • the second time information may also refer to information for setting a transmission delay of the data packet, such as maximum delay time information.
  • the first time information may be used to set a time when the terminal device is in the connected state in the mobile-initiated connection MICO mode, and/or a time in which the terminal device initiates uplink signaling or data in the idle state after the terminal device is in the MICO mode.
  • the access network device may set the time when the terminal device is in the connected state in the mobile-initiated connection MICO mode according to the first time information, and/or set the terminal device to initiate uplink signaling after the idle state in the MICO mode or The time of the data.
  • the network capability opened by the mobile communication carrier may include: setting a state of the terminal device (UE) in the MICO mode.
  • the third-party service provider can request the network side to set the state of the terminal device (UE) in the MICO mode, which can facilitate the third-party service provider to transmit the downlink data packet to the terminal device.
  • the request message may further include identifier information of the application, where the connection state is a connection state of the terminal device corresponding application.
  • the connection state is a connection state of the terminal device corresponding application.
  • the application provides a capability opening method, which is applied to an application server.
  • the method may include: the application server sends a request message to the core network device, where the request message includes identifier information and data volume information of the terminal device.
  • the application server receives a response message from the request message of the core network device.
  • the application provides a capability opening method, which is applied to a core network device side.
  • the method may include: the core network element acquires a request message request message from the application server, and includes identifier information and data volume information of the terminal device. Then, the core network device caches the data packet sent by the application server to the terminal device according to the data volume information.
  • the request message from the application server refers to a series of request messages initiated from the application server, experienced by a plurality of core network elements, and finally reaches a core network element for application data packet caching.
  • a series of request messages are used together to request a cached application packet.
  • the core network element for applying the data packet buffer may include: a UPF corresponding to a data network transmission access point identifier (DNAI) of an application server (SCS/AS), or an application server (SCS/AS).
  • DNN data network name
  • LADN local data network
  • the UPF corresponding to the DNAI of the application server may cache the data packet sent by the application server to the terminal device according to the data volume information.
  • the SMF corresponding to the terminal device may cache, according to the data volume information, a data packet sent by the application server to the terminal device.
  • the network capability opened by the mobile communication carrier may include: caching the application data packet, especially when the terminal device is unreachable.
  • a third-party service provider can request a cached application data packet from the network side, which facilitates the transmission of downlink data packets by the third-party service provider to the terminal device.
  • the request message may further include identification information of the application, where the data volume information is data amount information to be cached corresponding to the application.
  • the core network device may specifically detect the type of the data packet sent by the application server to the terminal device, determine whether the data packet is the corresponding data packet, and if so, cache the data packet. In this way, the core network device can process the application data packets from different third-party applications, and only the application data packets of the third-party applications indicated by the identification information of the application are cached, so as to better support the different service requirements of the third-party service providers. .
  • the application provides an application server, including a plurality of functional units, for respectively performing the method provided by any one of the first aspect or the third aspect or the fifth aspect possible embodiment.
  • the present application provides an access network device, including a plurality of functional units, for performing the method provided by any one of the second aspect or the possible implementation manner of the fourth aspect.
  • the present application provides a core network device, including a plurality of functional units, for performing the method provided by any one of the possible embodiments of the sixth aspect.
  • the application provides an application server for performing the capability opening method described in any one of the first aspect or the third aspect or the possible implementation manner of the fifth aspect.
  • the application server can include a memory and a processor, transceiver coupled to the memory, wherein the transceiver is for communicating with other communication devices, such as core network devices.
  • the memory is for storing the implementation code of the capability opening method described in any one of the first aspect or the third aspect or the fifth aspect
  • the processor is configured to execute the program code stored in the memory, that is, to perform the first aspect Or the method provided by any one of the third or fifth possible embodiments.
  • the application provides an access network device for performing the capability opening method described in any one of the second aspect or the possible implementation manner of the fourth aspect.
  • the application server can include a memory and a processor, transceiver coupled to the memory, wherein the transceiver is for communicating with other communication devices, such as core network devices.
  • the memory is for storing implementation code of the capability open method described in any one of the second aspect or the possible implementation of the fourth aspect
  • the processor is configured to execute the program code stored in the memory, that is, to perform the second aspect or the fourth aspect A method provided by any of the possible embodiments.
  • the present application provides a core network device for performing the capability opening method described in any one of the possible embodiments of the sixth aspect.
  • the application server can include a memory and a processor coupled to the memory, the transceiver, wherein: the transceiver is for communicating with other communication devices (eg, application servers, core network devices).
  • the memory is for storing implementation code of the capability opening method described in any one of the possible implementations of the sixth aspect
  • the processor is configured to execute the program code stored in the memory, that is, to perform any one of the possible embodiments of the sixth aspect The method provided.
  • the application provides a communication system, where the communication system includes: an application server and an access network device, wherein: the application server may be the application server described in the first aspect or the third aspect.
  • the access network device may be the access network device described in the second aspect or the fourth aspect.
  • the application provides a communication system, where the communication system includes: an application server and a core network device, wherein: the application server may be the application server described in the fifth aspect.
  • the access network device may be the core network device described in the sixth aspect.
  • the present application provides another computer readable storage medium having instructions stored on a readable storage medium, when executed on a computer, causing the computer to perform any of the above first to sixth aspects Describe the ability to open methods.
  • the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the capability opening method described in any one of the above first to sixth aspects.
  • FIG. 1 is a schematic structural diagram of a wireless communication system according to the present application.
  • FIG. 2 is a schematic flow chart of a capability opening method provided by the present application.
  • FIG. 3 is a schematic flow chart of still another capability opening method provided by the present application.
  • FIG. 5 is a schematic flowchart of still another capability opening method provided by the present application.
  • FIG. 6 is a schematic diagram of a network architecture of a UL CL according to the embodiment of FIG. 5;
  • FIG. 7 is a schematic structural diagram of an application server according to an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of an access network device according to an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a core network device according to an embodiment of the present application.
  • FIG. 10 is a functional block diagram of a communication system and related communication device provided by the present application.
  • FIG. 11 is a functional block diagram of still another communication system, related communication device, provided by the present application.
  • FIG. 1 illustrates the architecture of a communication system 100 to which the present application relates.
  • the communication system 100 shown in FIG. 1 includes a service capability server/applicant server (SCS/AS) 10 provided by a third party service provider and a mobile communication system provided by a mobile communication carrier.
  • the service capability server/application server 10 is an application server of a third-party service provider and/or a network operator, and can provide one or more application services, such as voice services, video services, location-based services, and the like.
  • the mobile communication system opens network capabilities to the application server 10.
  • the mobile communication system is not limited to a long term evolution (LTE) system, and may be a fifth generation mobile communication (the 5th Generation, 5G) system, a new air interface (NR) system, and machine-to-machine communication (machine). To machine, M2M) system, etc.
  • LTE long term evolution
  • 5G fifth generation mobile communication
  • NR new air interface
  • M2M machine-to-machine communication
  • the mobile communication system may include a terminal device 12, an access network device 13, and a core network device.
  • the terminal device 12 can be a user equipment (UE), a handheld terminal, a notebook computer, a subscriber unit, a cellular phone, a smart phone, a wireless data card, and a personal digital assistant.
  • UE user equipment
  • PDA personal digital assistant
  • tablet wireless modem
  • handheld laptop computer
  • cordless phone or wireless local loop (WLL) station machine type communication (machine type communication, MTC) terminal equipment or other equipment that can access the network.
  • MTC machine type communication
  • the terminal device 12 and the access network device 13 communicate with each other using some air interface technology.
  • R AN device 13 may include a RAN device or an AN device.
  • the RAN device is primarily a 3GPP wireless network device, such as a base station.
  • the AN device may be an access network device defined by non-3GPP, such as a Wi-Fi router.
  • the RAN device is mainly responsible for radio resource management, quality of service (QoS) management, data compression, and encryption on the air interface side.
  • the RAN device may include: a macro base station, a micro base station (also referred to as a small station), a relay station, and the like.
  • the name of a device having a base station function may be different, for example, in a 5th generation (5th generation, 5G) system, called gNB; in an LTE system, It is an evolved Node B (eNB or eNodeB); in a 3rd generation (3G) system, it is called a Node B or the like.
  • the AN device allows non-3GPP technology interconnection between the terminal device and the 3GPP core network, where non-3GPP technologies such as: wireless fidelity (Wi-Fi), and global interoperability for microwave access , WiMAX), code division multiple access (CDMA) network, and the like.
  • Wi-Fi wireless fidelity
  • WiMAX global interoperability for microwave access
  • CDMA code division multiple access
  • the core network device may include NEF 11, UPF 14, AF16, PCF 17, SMF 18, AMF 19, UDM 20, AUSF 21, etc. as shown in FIG. among them:
  • Network exposure function (NEF) network element 11 mainly supports the interaction between the 3GPP network and the third-party application security.
  • the NEF can securely open the mobile communication network capabilities and events to third parties to enhance or improve the application service quality.
  • the 3GPP network can also securely obtain relevant data from third parties to enhance the intelligent decision of the network; at the same time, the network element supports restoring structured data from the unified database or storing structured data in the unified database.
  • User plane function (UPF) network element 14 responsible for forwarding and receiving data packets.
  • the UPF network element can receive user data from the data network and transmit the data to the terminal device through the access network device.
  • the UPF network element can also receive user data from the terminal device through the access network device and forward the data to the data network.
  • the transmission resources and scheduling functions for the terminal devices in the UPF network element are managed and managed by the SMF network element.
  • the UPF network element can cache data packets.
  • Application function (AF) network element 16 an application server device that provides application services to a terminal device, etc., can interact with the 3GPP core network to provide services, such as affecting data routing decisions, policy control functions, or providing third parties to the network side. Some of the services.
  • Policy control function (PCF) network element 17 mainly supports providing a unified policy framework to control network behavior, providing policy rules to provide policy information to control layer devices and terminal devices, and is responsible for obtaining user subscriptions related to policy decisions. information.
  • Session management function (SMF) network element 18 responsible for user plane network element selection, user plane network element redirection, internet protocol (IP) address allocation, data transmission channel establishment, modification and release, and QoS control .
  • SMF network elements can cache data packets.
  • Access and mobility management function (AMF) network element 19 belongs to the core network element, and is mainly responsible for signaling processing parts, such as access control, mobility management, attach and detach, and gateway selection. And other functions.
  • AMF Access and mobility management function
  • the AMF network element provides a service for the session in the terminal device, the storage resource of the control plane is provided for the session, and the session identifier, the SMF network element identifier associated with the session identifier, and the like are stored.
  • Unified data management (UDM) network element 20 unified data management, consisting of two parts, one part is called application front stage (FE), and the other part is called user data warehouse (UDR).
  • the FE can access the subscription user information stored in the UDR and support authentication credit processing, user identification processing, access authorization, subscription management, short message management, and the like.
  • a UDR is a user subscription data storage server that provides a subscription data storage service.
  • Authentication server function (AUSF) network element 21 mainly provides authentication and authentication functions.
  • the communication system 100 further includes a data network (DN) 15 which is a network composed of application functions that provides an application data server to the terminal device.
  • DN data network
  • the network functions in FIG. 1 such as NEF 11, UPF 14, AF16, PCF 17, SMF18, AMF19, UDM 20, AUSF21, etc., belong to the core network device of the mobile communication system.
  • the mobile communication system of Figure 1 is a reference point based communication architecture.
  • the reference point based communication architecture embodies the interaction between peer-to-peer network functions, such as interaction between UDM 20 and SMF 18 based on reference point N10.
  • peer-to-peer network functions such as interaction between UDM 20 and SMF 18 based on reference point N10.
  • reference point N10 For the definition and description of each reference point in the figure, please refer to the related 3gpp protocol, such as TS23.501, TS23.502 and TS23.503, etc., which are not described here.
  • the NEF communicates with other network elements (such as PCF network elements and UDM network elements) through a service-based interface exhibiting by NEF (Nnef).
  • the application server 10 can implement an open application programming interface (API) provided by a mobile communication carrier to acquire an open network capability of a mobile communication carrier.
  • the network capabilities opened by mobile communication operators mainly include communication capabilities, context information, subscription information and control capabilities.
  • the communication capability refers to voice, short message, and multimedia message service;
  • the context information includes real-time user information, such as user location, terminal device capability, and data connection type;
  • the subscription information includes information such as subscription identifier and priority;
  • control capability refers to It is the control and monitoring of business quality, strategy and security.
  • third-party service providers can develop more new services that meet the actual needs of users by combining various existing network capabilities.
  • the current mobile communication network has limited network capabilities to third-party service providers, and cannot well support the business needs of third-party service providers under the new air interface (NR) or future communication systems.
  • NR new air interface
  • the present application provides a capability opening method, which can enable a mobile communication network to open more network capabilities to third-party service providers, and better support the business needs of third-party service providers.
  • the network capability opened by the mobile communication carrier may include: setting a duration in which the terminal device is in the RRC INACTIVE state.
  • the network capability opened by the mobile communication carrier may further include: setting the state of the terminal device in the MICO mode.
  • the communication system 100 shown in FIG. 1 is only for the purpose of more clearly explaining the technical solutions of the present application, and does not constitute a limitation of the present application. As those skilled in the art can understand, with the evolution of the network architecture and the emergence of new business scenarios, The technical solutions provided for the application are equally applicable to similar technical issues.
  • the present application provides a capability opening method, which can enable a mobile communication network to open more network capabilities to third-party service providers, and better support the business needs of third-party service providers.
  • RRC INACTIVE a new RRC state: RRC INACTIVE state. Both the RRC INACTIVE state and the RRC CONNECTED state are connected. In the RRC INACTIVE state, it still retains part of the RAN context (eg: security context, UE capability information, etc.), but the connection between the terminal device and the RAN device is released, and can be quickly transferred from the RRC INACTIVE state by a message similar to paging. Go to the RRC CONNECTED state and reduce the number of signaling.
  • RAN context eg: security context, UE capability information, etc.
  • the connection between the terminal device and the access network device needs to be established first. Specifically, when the downlink data packet arrives, the access network device initiates a paging process to the terminal device, thereby establishing a connection between the terminal device and the access device.
  • the support for the terminal device MICO mode is added to the 5G system, and the terminal device can be negotiated to be in the MICO mode during the initial registration or registration update of the terminal device. Moreover, when the terminal device is in the MICO mode, the AMF considers that the terminal device in the idle state is unreachable, and the AMF rejects any request for downlink data transmission to the terminal device. That is to say, when the state of the terminal device in the MICO mode is the idle state, the signaling process for transmitting data can only be initiated by the terminal device, and the signaling process for transmitting data cannot be initiated by the network side. When the state of the terminal device in the MICO mode is the connected state, both the network side and the terminal device can initiate a signaling process for transmitting data.
  • the network capability opened by the mobile communication carrier may include: setting a duration in which the terminal device is in the RRC INACTIVE state.
  • the third-party service provider can request the network side to set the duration in which the terminal device is in the RRC INACTIVE state.
  • the network side can respond to the request of the third-party service provider, and correspondingly set the duration of the terminal device in the RRC INACTIVE state, which can facilitate the third-party service provider to transmit the downlink data packet to the terminal device.
  • the network capability opened by the mobile communication carrier may further include: setting the state of the terminal device in the MICO mode.
  • third-party service providers can request the status of the terminal device in the MICO mode from the network side.
  • the network side can respond to the request of the third-party service provider, and correspondingly set the state of the terminal device in the MICO mode, so that the third-party service provider can facilitate the transmission of the downlink data packet to the terminal device.
  • the RRC INACTIVE state may be referred to as an inactive state of a connected state
  • the RRC CONNECTED state may be referred to as an activated state of a connected state.
  • the inactive state may also include other connection states similar to the RRC INACTIVE state.
  • the activation state may also include other connection states similar to the RRC CONNECTED state. Future communication standards may change the naming of the RRC INACTIVE state and the RRC CONNECTED state, and the technical solution provided by the present application is not affected by this.
  • the active state and the inactive state are only two specific example states included in the connection state applicable to the capability opening method provided by the present application.
  • the active state and the inactive state in the present application may be respectively summarized. It is the first state of the connected state and the second state of the connected state.
  • the network capability opened by the mobile communication carrier may include: setting a duration in which the terminal device is in the RRC INACTIVE state.
  • the capability opening method provided in Embodiment 1 may include:
  • the access network device acquires a request message from an application server, where the request message may include first time information and/or second time information.
  • the first time information can be used to set the time when the terminal device is in the first state of the connected state
  • the second time information can be used to set the time when the terminal device is in the second state of the connected state.
  • the first state of the connected state may be an activated state of the connected state, such as an RRC CONNECTED state.
  • the second state of the connected state may be an inactive state of the connected state, such as an RRC INACTIVE state.
  • the first time information may also refer to information for setting the transmission duration of the data packet, such as maximum response time information.
  • the second time information may also refer to information for setting a transmission delay of the data packet, such as maximum delay time information.
  • the request message from the application server refers to a series of request messages initiated from the application server, going through the core network, and finally reaching the access network device.
  • the series of request messages are used together to request the access network device to set the connection state of the terminal device.
  • the core network element that the request message is experienced may specifically include, but is not limited to, an NEF network element, a UDM network element, and an AMF network element.
  • the process of the access network device acquiring the request message from the application server may include, but is not limited to:
  • the application server sends a monitoring request to the NEF network element, where the monitoring request may include: first time information and/or second time information.
  • the monitoring request may further include the identifier information of the application server and/or the identifier information of the terminal device, where the identifier information of the terminal device may be an external identifier of the terminal device, or a Permanent Equipment Identifier (PEI).
  • the monitoring request may further include identifier information of the application, where the identifier information of the application is used to identify a third-party application that initiates the monitoring request process.
  • the monitoring request may further include a monitoring event type, where the monitoring event type is an event type for monitoring a connection status of the terminal device.
  • the NEF network element After receiving the monitoring request sent by the application server, the NEF network element may perform NEF processing.
  • NEF processing may include, but is not limited to, the following processes:
  • the NEF network element can save the identification information of the application.
  • the NEF network element may not save the identification information of the application, but obtain the information from the application server when the NEF network element needs the information.
  • the specific implementation process of the NEF network element acquiring the identification information of the application from the application server is not limited in this application.
  • the NEF network element may allocate an NEF reference identifier.
  • the NEF network element may determine, according to the policy of the operator, whether the monitoring request sent by the application server is legal. If not, send a response message to the SCS/AS, where the response message may include information such as the reason for the rejection.
  • the NEF network element sends a monitoring request to the UDM network element, where the monitoring request may include: first time information and/or second time information.
  • the monitoring request may further include the identifier information of the application server and the identifier information of the terminal device, where the identifier information of the terminal device may be an external identifier of the terminal device, or a permanent device identifier.
  • the monitoring request may further include identification information of the application.
  • the monitoring request may further include NEF related information, such as an NEF reference identifier.
  • the monitoring request may further include a monitoring event type, where the monitoring event type is an event type for monitoring a connection status of the terminal device.
  • the UDM network element may perform UDM processing.
  • the UDM processing may include, but is not limited to, the UDM network element checking whether the parameters in the monitoring request are legal according to the policy of the operator, and determining the AMF corresponding to the terminal device according to the representation information of the terminal device.
  • the UDM process may further include: determining, by the UDM network element, an in-network identifier of the terminal device according to an external identifier of the terminal device, such as a Subscriber Permanent Identifier (SUPI).
  • SUPI Subscriber Permanent Identifier
  • the UDM network element sends a message to the AMF network element, where the message may include first time information and/or second time information.
  • the message may be used to instruct the terminal device to request the RAN to set the connection state of the terminal device according to the first time information and/or the second time information.
  • the message may be a message that inserts subscription data.
  • the message may further include the identifier information of the application server and the identifier information of the terminal device, where the identifier information of the terminal device may be an external identifier of the terminal device, or a permanent device identifier.
  • the message may further include identification information of the application.
  • the message may further include NEF related information, such as an NEF reference identifier.
  • the message may further include a monitoring event type, where the monitoring event type is an event type for monitoring a connection status of the terminal device.
  • the AMF network element sends a request message to the access network device, where it is used to request to set a connection state of the terminal device.
  • the request message may be an RRC INACTIVE auxiliary information request message, and the request message may include first time information and/or second time information.
  • the request message may further include the identifier information of the application server, the identifier information of the terminal device, and the identifier information of the terminal device may be an external identifier of the terminal device, or a permanent device identifier.
  • the request message may further include identifier information of the application.
  • the request message may further include a monitoring event type, where the monitoring event type is an event type for monitoring a connection status of the terminal device.
  • the monitoring request sent by the application server to the NEF network element is different from the monitoring request sent by the NEF network element to the UDM network element, and the two are different in signaling implementation.
  • the monitoring request is only a message naming, and the application does not limit this, as long as the functions are the same.
  • the monitoring request mentioned in the subsequent embodiments is also applicable without restricting the message name.
  • the series of request messages corresponding to the request message from the application server may include: the monitoring request sent in S101, the monitoring request sent in S103, and the sending in S105.
  • the series of request messages corresponding to the request message from the application server may be implemented as other signaling, which is not limited to the S101-S106.
  • the access network device may set the connection state of the terminal device according to the first time information and/or the second time information. Specifically, the access network device may set the duration of the terminal device in the RRC CONNECTED state according to the first time information, and/or the access network device may set the duration of the terminal device in the RRC INACTIVE state according to the second time information.
  • connection state of the terminal device may be a connection state of the application indicated by the identifier information that should be applied by the terminal device, on the condition that the request message received by the access network device includes the identifier information of the application.
  • the connection state of the terminal device can be set for a specific application, and the service requirement of the third-party service provider can be better supported.
  • the access network device may set the duration of the terminal device in the RRC CONNECTED state to be greater than or equal to 10 ms. In this way, it is ensured that the terminal device maintains reachability, and the application server continuously transmits the application data packet to the terminal device.
  • the access network device may set the duration of the terminal device in the RRC INACTIVE state to be less than or equal to 5 ms. In this way, the terminal device can be ensured to be reachable in time, and the application server can continuously transmit the application data packet to the terminal device.
  • the access network device may set a periodic RAN Notification Area Update timer according to the maximum delay time to set a duration in which the terminal device is in the RRC INACTIVE state.
  • the AMF network element may return a monitoring indication to the application server by using the NEF network element, where the monitoring indication may include: the terminal device Connection status, access type, etc.
  • the AMF may determine, according to the identification information of the application, the access technology corresponding to the third-party application. If it is not the 3GPP access technology, the setting fails, and the monitoring indication is a message that the setting fails.
  • the application is not limited in terms of how to determine the access technology corresponding to the third-party application.
  • the AMF can determine whether the access network device is an access network device of the 3GPP. If it is not the access network device of the 3GPP, the setting fails, and the monitoring indication is a message that the setting fails.
  • the monitoring request sent in S101 may be not the first time information and/or the second time information, but may be the third time information and/or the fourth time information, where the third time information may be For determining the first time information, the fourth time information can be used to determine the second time information.
  • the third time information may be the maximum response time of the application server, and the core network device (such as the NEF network element or the UDM network element or the AMF network element) may determine that the first time information is greater than or equal to 10 ms according to the 10 ms. For example, 15ms to ensure that the terminal device can always reach the reachable state when the application server transmits the application data packet to the terminal device, thereby achieving continuous data transmission.
  • the core network device such as the NEF network element or the UDM network element or the AMF network element
  • the fourth time information may be a maximum delay time of 5 ms
  • the core network device such as a NEF network element or a UDM network element or an AMF network element
  • the core network device may determine that the first time information is greater than or equal to 5 ms according to the 5 ms.
  • the duration such as 4ms, ensures that the terminal device can be in a reachable state when the application server transmits the application data packet to the terminal device, thereby realizing effective data transmission.
  • the terminal device can be in the MICO mode.
  • the first time information can be used to set the time when the terminal device is in the connected state in the MICO mode
  • the second time information can be used to set the time when the terminal device initiates uplink signaling or data in the idle state after the terminal device is in the MICO mode.
  • the access network device may set the mode in the MICO according to the first time information and/or the second time information. Terminal device status. Specifically, the access network device may set the time when the terminal device is in the connected state in the MICO mode according to the first time information, and/or the access network device may set the terminal device to be in the idle state in the MICO mode according to the second time information. The time after which the uplink signaling or data is initiated.
  • the network capability opened by the mobile communication carrier may further include: setting the state of the terminal device in the MICO mode.
  • the third-party service provider can request the network side to set the state of the terminal device in the MICO mode.
  • the network side can respond to the request of the third-party service provider, and correspondingly set the state of the terminal device in the MICO mode, so that the third-party service provider can facilitate the transmission of the downlink data packet to the terminal device.
  • S201-S206 in FIG. 3 may refer to S101-S106 in FIG. 2, and S208-S209 in FIG. 3 may refer to S108-S109 in FIG. 2, and details are not described herein again.
  • the related extensions of Embodiment 1 and Embodiment 1 may be combined. Specifically, after receiving the request sent by the AMF network element, the access network device may determine whether the terminal device is in the MICO mode. If the terminal device is in the MICO mode, the capability opening method provided by the embodiment of FIG. 3 is adopted; otherwise, The capability opening method provided by the embodiment of Fig. 2 is employed.
  • the AMF network element receives the request message from the application server.
  • the access network device receives the request message from the application server via the terminal device.
  • the process of the access network device acquiring the request message from the application server may include the following two stages:
  • Phase 1 The terminal device receives a request message from the application server. Specifically, it may include:
  • the application server sends a monitoring request to the NEF network element, where the monitoring request may include: first time information and/or second time information.
  • the monitoring request may further include the identifier information of the application server and/or the identifier information of the terminal device, where the identifier information of the terminal device may be an external identifier of the terminal device, or a permanent device identifier.
  • the monitoring request may further include identifier information of the application, where the identifier information of the application is used to identify a third-party application that initiates the monitoring request process.
  • the monitoring request may further include a monitoring event type, where the monitoring event type is an event type for monitoring a connection status of the terminal device.
  • the NEF network element After receiving the monitoring request sent by the application server, the NEF network element may perform NEF processing.
  • NEF processing may include, but is not limited to, the following processes:
  • the NEF network element can save the identification information of the application.
  • the NEF network element may not save the identification information of the application, but obtain the information from the application server when the NEF network element needs the information.
  • the specific implementation process of the NEF network element acquiring the identification information of the application from the application server is not limited in this application.
  • the NEF network element may allocate an NEF reference identifier.
  • the NEF network element may determine, according to the policy of the operator, whether the monitoring request sent by the application server is legal. If not, send a response message to the SCS/AS, where the response message may include information such as the reason for the rejection.
  • the NEF network element sends a monitoring request to the UDM network element, where the monitoring request may include: first time information and/or second time information.
  • the monitoring request may further include the identifier information of the application server and/or the identifier information of the terminal device, where the identifier information of the terminal device may be an external identifier of the terminal device, or a permanent device identifier.
  • the monitoring request may further include identification information of the application.
  • the monitoring request may further include NEF related information, such as an NEF reference identifier.
  • the monitoring request may further include a monitoring event type, where the monitoring event type is an event type for monitoring a connection status of the terminal device.
  • the NEF network element sends a message to the PCF network element, where the message may include: first time information and/or second time information, and further, may further include identifier information of the terminal device and/or identifier of the server. Information, etc.
  • the PCF may send the information as a user routing selection policy (URSP) information to the terminal device, and the process of developing the URSP information to the terminal device is the same as the current.
  • URSP user routing selection policy
  • the UDM network element may perform UDM processing.
  • the UDM processing may include, but is not limited to, the UDM network element checking whether the parameters in the monitoring request are legal according to the policy of the operator, and determining the AMF corresponding to the terminal device according to the identification information of the terminal device.
  • the UDM process may further include: determining, by the UDM network element, an in-network identifier of the terminal device according to the external identifier of the terminal device, such as signing a permanent identifier.
  • the UDM network element sends a message to the AMF network element, where the message may include first time information and/or second time information.
  • the message may be used to instruct the terminal device to request the RAN to set the connection state of the terminal device according to the first time information and/or the second time information.
  • the message may be a message that inserts subscription data.
  • the message may further include the identifier information of the application server and the identifier information of the terminal device, where the identifier information of the terminal device may be an external identifier of the terminal device, or a permanent device identifier.
  • the message may further include identification information of the application.
  • the message may further include NEF related information, such as an NEF reference identifier.
  • the message may further include a monitoring event type, where the monitoring event type is an event type for monitoring a connection status of the terminal device.
  • the AMF network element sends a message to the terminal device, where the message may include the first time information and/or the second time information.
  • the message may be used to instruct the terminal device to request the RAN to set the connection state of the terminal device according to the first time information and/or the second time information.
  • the message may be a message that inserts subscription data.
  • the AMF may determine, according to the identification information of the application, an access technology corresponding to the third-party application, and if it is a 3GPP access technology, notify the terminal device of the first time information and/or the second time information.
  • the application is not limited in terms of how to determine the access technology corresponding to the third-party application.
  • the second stage the terminal device requests the access network device to set the connection state of the terminal device. Specifically, it may include:
  • the terminal device sends a request message to the access network device, where the access network device is configured to set a connection state of the terminal device.
  • the request message can include first time information and/or second time information.
  • the message may further include identification information of the application.
  • the message may further include a monitoring event type, where the monitoring event type is an event type for monitoring a connection status of the terminal device.
  • the access network device may set the duration of the terminal device in the RRC CONNECTED state according to the first time information, and/or the access network device may set the duration of the terminal device in the RRC INACTIVE state according to the second time information.
  • the access network device may set the duration of the terminal device in the RRC CONNECTED state to be greater than or equal to 10 ms. In this way, it is ensured that the terminal device maintains reachability, and the application server continuously transmits the application data packet to the terminal device.
  • the access network device may set the duration of the terminal device in the RRC INACTIVE state to be less than or equal to 5 ms. In this way, the terminal device can be ensured to be reachable in time, and the application server can continuously transmit the application data packet to the terminal device.
  • the access network device may set a periodic RAN notification area update timer according to the maximum delay time to set a duration in which the terminal device is in the RRC INACTIVE state.
  • the series of request messages corresponding to the request message from the application server may include: the monitoring request sent in S301, the monitoring request sent in S303, and the sending in S305.
  • the series of request messages corresponding to the request message from the application server may be implemented as other signaling, which is not limited to the S301-S307.
  • the same extension may be applied to the first embodiment.
  • the related extension 1 of the first embodiment and the related extension 2 of the first embodiment are not described herein again.
  • the present application also provides a capability opening method for caching application data packets, especially when the terminal device is unreachable. As shown in FIG. 5, the method can include:
  • the core network device acquires a request message from an application server.
  • the request message may include identification information of the terminal device and data volume information.
  • the core network device caches the data packet sent by the application server to the terminal device according to the data volume information.
  • the request message from the application server refers to a series of request messages initiated from the application server, going through a plurality of core network elements, and finally reaching a core network element for application data packet buffering, and the series of request messages are used together. Request to cache application packets.
  • the core network element for applying the data packet buffer may include: a UPF network element corresponding to a Data Network Access Identifier (DNAI) of the application server, or a local data network corresponding to the application server.
  • the UPF network element may cache, according to the data volume information, a data packet sent by the application server to the terminal device.
  • the SMF corresponding to the terminal device may cache, according to the data volume information, a data packet sent by the application server to the terminal device.
  • the process of the core network device acquiring the request message from the application server may include:
  • the application server sends a monitoring request to the NEF network element, where the monitoring request may include: data volume information and identifier information of the terminal device.
  • the identification information of the terminal device may be an external identifier of the terminal device, or a permanent device identifier, or an IP address information of the terminal device.
  • the monitoring request may further include identifier information of the application, where the identifier information of the application is used to identify a third-party application that initiates the monitoring request process.
  • the UPF network element or the SMF network element may detect the type of the application data packet, determine whether the application data packet is a data packet corresponding to the application identification information, and if yes, cache the application data packet.
  • the third-party service provider can request the core network device to cache the application data packet from the specified third application, and can implement the core network device to process the application data packet from different third-party applications, and only cache the identification information indication from the application.
  • the application package of the third-party application can better support the different business needs of the third-party service provider.
  • the NEF network element After receiving the monitoring request sent by the application server, the NEF network element may perform NEF processing.
  • the NEF network element may determine a data network access point identifier corresponding to the application server, where the DNAI refers to an application data packet transmission access point.
  • the DNAI may refer to the identity of the UPF. How to determine the DNAI is not limited in this patent.
  • the NEF network element requests the DNA element from the SM network element to which the PDU session of the application data flow identified by the application identifier belongs.
  • the NEF network element may determine, according to the identification information of the application, the DNN to which the application server belongs, and how to determine the application is not limited.
  • the method may include, but is not limited to, the following methods:
  • the A. NEF network element requests the correspondence between the application server and the DNN to the core network device (such as the SMF network element or the PCF network element, the OSS network management device, and the like).
  • the core network device such as the SMF network element or the PCF network element, the OSS network management device, and the like.
  • the core network device (such as the SMF network element or the PCF network element, the OSS network management device, etc.) sends the mapping relationship between the application server and the DNN to the NEF network element.
  • the NEF network element may determine, according to information such as an IP address of the terminal device, a PCF where the terminal device is located.
  • S403-S410 The core network element for applying the data packet buffer acquires the request message from the NEF network element.
  • the core network element for applying the data packet buffer can obtain the request message from the NEF network element by using, but not limited to, the following manners.
  • the NEF network element sends a monitoring request to the PCF network element, where the monitoring request may include data volume information and identifier information of the terminal device.
  • the monitoring request may further include a DNAI of the application server, or a DNN of the LADN corresponding to the application server.
  • the monitoring request may further include identification information of the application.
  • the PCF network element may determine, according to the identifier information of the terminal device, the SMF network element corresponding to the terminal device, and send a monitoring request to the SM network element F, where the monitoring request may include the data volume information and the identifier information of the terminal device.
  • the monitoring request may further include a DNAI of the application server, or a DNN of the LADN corresponding to the application server.
  • the monitoring request may further include identification information of the application.
  • the SMF network element may determine a corresponding UPF network element according to the DNAI of the application server, or determine a corresponding UPF network element according to the DNN of the LADN corresponding to the application server. Then, the SMF network element may send a monitoring request to the corresponding UPF network element, where the monitoring request may include data volume information and identification information of the terminal device.
  • the NEF network element may determine, according to the identifier information of the terminal device, the SMF network element corresponding to the terminal device, and send a monitoring request to the SMF network element, where the monitoring request may include the data volume information and the identifier information of the terminal device.
  • the monitoring request may further include a DNAI of the application server, or a DNN of the LADN corresponding to the application server.
  • the monitoring request may further include identification information of the application.
  • the SMF network element may determine a corresponding UPF network element according to the DNAI of the application server, or determine a corresponding UPF network element according to the DNN of the LADN corresponding to the application server. Then, the SMF network element may send a monitoring request to the corresponding UPF network element, where the monitoring request may include data volume information and identification information of the terminal device.
  • the NEF network element may send a monitoring request to the AMF network element, where the monitoring request may include data volume information and identifier information of the terminal device.
  • the monitoring request may further include a DNAI of the application server, or a DNN of the LADN corresponding to the application server.
  • the monitoring request may further include identification information of the application.
  • the NEF network element sending the monitoring request to the AMF network element is not limited to the NEF network element sending the monitoring request to the AMF network element directly, or the NEF network element sending the monitoring request to the AMF network element via other network equipment.
  • the NEF network element sends a monitoring request to the UDM network element, and then the UDM network element determines the corresponding AMF network element according to the identification information of the terminal device, and sends a monitoring request to the corresponding AMF network element, or the UDM network element determines After the corresponding AMF network element, the AMF identification information is sent to the NEF, and then the NEF network element sends a monitoring request to the AMF network element according to the identification information of the AMF network element.
  • the examples are merely illustrative of the application and should not be construed as limiting.
  • the AMF network element may determine, according to the identifier information of the terminal device, the SMF network element corresponding to the terminal device, and send a monitoring request to the SMF network element, where the monitoring request may include the data volume information and the identifier information of the terminal device.
  • the monitoring request may further include a DNAI of the application server, or a DNN of the LADN corresponding to the application server.
  • the monitoring request may further include identification information of the application.
  • the SMF network element may determine a corresponding UPF network element according to the DNAI of the application server, or determine a corresponding UPF network element according to the DNN of the LADN corresponding to the application server. Then, the SMF network element may send a monitoring request to the corresponding UPF network element, where the monitoring request may include data volume information and identification information of the terminal device.
  • the core network device can also obtain a request message from the Network Open Function (NEF) through other signaling processes.
  • NEF Network Open Function
  • the UPF network element may be an uplink classifier (UL CL) network element in FIG. 6.
  • the DNAI may be the identifier of the PDU session anchor 1 in FIG. 6, or the identifier of the PDU session anchor 2, or Is the identifier of the UPF network element with the UL CL function.
  • Figure 7 illustrates an application server 200 provided by some embodiments of the present application.
  • the application server 200 can include one or more processors 201, a memory 202, and a communication interface 203. These components can be connected by bus 204 or other means, and FIG. 7 is exemplified by a bus connection. among them:
  • Communication interface 203 can be used by application server 200 to communicate with other communication devices, such as core network devices.
  • the core network device may be the core network device 400 shown in FIG. 9.
  • the communication interface 203 may include a wired communication interface, such as a Wide Area Network (WAN) interface, a Local Access Network (LAN) interface, and the like.
  • the communication interface 203 may further include a wireless communication interface, such as a Wireless Local Area Networks (WLAN) interface or the like.
  • WLAN Wireless Local Area Networks
  • Memory 202 is coupled to processor 201 for storing various software programs and/or sets of instructions.
  • memory 202 can include high speed random access memory, and can also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid state storage devices.
  • the memory 202 can store an operating system (hereinafter referred to as a system) such as an embedded operating system such as uCOS, VxWorks, or RTLinux.
  • the memory 202 can also store a network communication program that can be used to communicate with one or more additional devices, one or more terminal devices, one or more network devices.
  • the memory 202 can be used to store an implementation program of the capability opening method provided by one or more embodiments of the present application on the application server 200 side.
  • the capability opening method provided by one or more embodiments of the present application please refer to the subsequent embodiments.
  • the processor 201 can be used to read and execute computer readable instructions. Specifically, the processor 201 can be used to invoke a program stored in the memory 212, such as the implementation method of the capability opening method provided by one or more embodiments of the present application on the application server 200 side, and execute the instructions included in the program.
  • a program stored in the memory 212 such as the implementation method of the capability opening method provided by one or more embodiments of the present application on the application server 200 side, and execute the instructions included in the program.
  • the application server 200 can be the business capability server/application server 10 in the communication system 100 shown in FIG.
  • the application server 200 shown in FIG. 7 is only one implementation of the embodiment of the present application. In an actual application, the application server 200 may further include more or fewer components, which are not limited herein.
  • FIG. 8 illustrates an access network device 300 provided by some embodiments of the present application.
  • access network device 300 can include one or more processors 301, memory 302, communication interface 303, transmitter 305, receiver 306, coupler 307, and antenna 308. These components can be connected via bus 304 or other means, and Figure 8 is exemplified by a bus connection. among them:
  • Transmitter 305 can be used to perform transmission processing, such as signal modulation, on signals output by processor 301.
  • Receiver 306 can be used to perform reception processing on signals received by antenna 308. For example, signal demodulation.
  • transmitter 305 and receiver 306 can be viewed as a wireless modem. In the access network device 300, the number of the transmitter 305 and the receiver 306 may each be one or more.
  • the antenna 308 can be used to convert electromagnetic energy in a transmission line into electromagnetic waves in free space, or to convert electromagnetic waves in free space into electromagnetic energy in a transmission line.
  • Coupler 307 can be used to divide the mobile pass signal into multiple channels and distribute it to multiple receivers 306.
  • Memory 302 is coupled to processor 301 for storing various software programs and/or sets of instructions.
  • memory 302 may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid state storage devices.
  • the memory 302 can store an operating system (hereinafter referred to as a system) such as an embedded operating system such as uCOS, VxWorks, or RTLinux.
  • the memory 302 can also store a network communication program that can be used to communicate with one or more additional devices, one or more terminal devices, one or more network devices.
  • the processor 301 can be used for performing wireless channel management, implementing call and communication link establishment and teardown, and providing cell handover control and the like for users in the control area.
  • the processor 301 may include: an Administration Module/Communication Module (AM/CM) (a center for voice exchange and information exchange), and a Basic Module (BM) (for completing a call) Processing, signaling processing, radio resource management, radio link management and circuit maintenance functions), code conversion and sub-multiplexer (TCSM) (for multiplexing demultiplexing and code conversion functions) Wait.
  • AM/CM Administration Module/Communication Module
  • BM Basic Module
  • TCSM code conversion and sub-multiplexer
  • the processor 301 can be used to read and execute computer readable instructions. Specifically, the processor 301 can be used to invoke a program stored in the memory 302, such as an implementation program of the capability opening method provided by one or more embodiments of the present application on the access network device 300 side, and execute instructions included in the program. .
  • the access network device 300 can be an access network device ((R)AN) 13 in the communication system 100 shown in FIG. 1 and can be implemented as a base transceiver station, a wireless transceiver, and a basic service set (BSS). ), an extended service set (ESS), NodeB, eNodeB, access point or TRP, and so on.
  • the access network device 300 shown in FIG. 8 is only one implementation of the embodiment of the present application. In an actual application, the access network device 300 may further include more or fewer components, which are not limited herein.
  • Figure 9 illustrates a core network device 400 provided by some embodiments of the present application.
  • the core network device 400 can include one or more processors 401, a memory 403, and a communication interface 405. These components can be connected by bus 404 or other means, and FIG. 9 is exemplified by a bus connection. among them:
  • Communication interface 405 can be used by core network device 400 to communicate with other communication devices, such as access network devices, application servers.
  • the application server may be the application server 200 shown in FIG. 7, and the access network device may be the access network device 300 shown in FIG.
  • communication interface 405 can include a wired communication interface, such as a wide area network (WAN) interface, a local area network (LAN) interface, and the like.
  • WAN wide area network
  • LAN local area network
  • communication interface 405 may also include a wireless communication interface, such as a wireless local area network (WLAN) interface or the like.
  • WLAN wireless local area network
  • Memory 403 is coupled to processor 401 for storing various software programs and/or sets of instructions.
  • memory 403 may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid state storage devices.
  • the memory 403 can store an operating system (hereinafter referred to as a system) such as an embedded operating system such as uCOS, VxWorks, or RTLinux.
  • the memory 403 can also store a network communication program that can be used to communicate with one or more additional devices, one or more terminal devices, one or more network devices.
  • the memory 403 can be used to store an implementation of the capability opening method provided by one or more embodiments of the present application on the core network device 400 side.
  • the capability opening method provided by one or more embodiments of the present application please refer to the subsequent embodiments.
  • the processor 401 can be used to read and execute computer readable instructions. Specifically, the processor 401 can be used to invoke a program stored in the memory 405, such as an implementation program of the capability opening method provided by one or more embodiments of the present application on the core network device 400 side, and execute instructions included in the program.
  • a program stored in the memory 405 such as an implementation program of the capability opening method provided by one or more embodiments of the present application on the core network device 400 side, and execute instructions included in the program.
  • the core network device 400 can be a core network device in the communication system 100 shown in FIG. 1, and can be implemented as NEF 11, AMF 19, SMF 18, PCF 17, UDM 20, UPF 14, and the like.
  • the core network device 400 shown in FIG. 9 is only one implementation of the embodiment of the present application. In actual applications, the core network device 400 may further include more or fewer components, which are not limited herein.
  • FIG. 10 illustrates a communication system and a communication device.
  • Communication system 30 may include communication devices such as application server 700, core network device 600, access network device 500, and terminal device 800.
  • the communication system 30 and the communication device therein can implement the capability opening method described in the embodiments corresponding to FIG. 2 to FIG. 4 respectively, that is, the core network device 600 (including but not limited to the following functions: NEF, UDM, PCF, AMF, SMF, UPF)
  • the open network capability of the mobile communication network where the access network device 500 is located may include: setting a duration in which the terminal device is in the RRC INACTIVE state; and/or setting a state of the terminal device in the MICO mode. The description is expanded below.
  • the application server 700 may include a receiving unit 701 and a transmitting unit 703. among them:
  • the receiving unit 701 can be configured to send a request message to the access network device 500, where the request message includes first time information and/or second time information.
  • the sending unit 703 can be configured to receive a response message of the request message from the access network device 500.
  • the first time information may also refer to information for setting the transmission duration of the data packet, such as maximum response time information.
  • the second time information may also refer to information for setting a transmission delay of the data packet, such as maximum delay time information.
  • the first time information can be used to set the time at which the terminal device 800 is in the first state of the connected state
  • the second time information can be used to set the time at which the terminal device 800 is in the second state of the connected state.
  • the first state of the connected state may include, but is not limited to, an active state, such as an RRC CONNECTED state.
  • the second state of the connected state may include, but is not limited to, an inactive state, such as an RRC INACTIVE state.
  • the first time information can be used to set the time when the terminal device 800 is in the connected state in the mobile-only initiated connection MICO mode
  • the second time information can be used to set the terminal device 800 to initiate the uplink after the idle state in the MICO mode. The time of signaling or data.
  • the request message may further include the identification information of the application, and the connection state may be specifically the connection state of the application corresponding to the terminal device 800.
  • the request message may also include identification information of the terminal device 800 and/or identification information of the application server.
  • the access network device 500 can include a receiving unit 501 and a processing unit 503. among them:
  • the receiving unit 501 is configured to obtain a request message from the application server 700, where the request message includes first time information and/or second time information.
  • the processing unit 503 is configured to set the connection state of the terminal device 800 according to the first time information and/or the second time information.
  • the request message from the application server 700 refers to a series of request messages initiated from the application server 700, going through the core network device 600, and finally reaching the access network device.
  • the series of request messages are used together to request the access network device to set the terminal.
  • the core network element that the request message experiences may specifically include, but is not limited to, NEF, UDM, and AMF.
  • the receiving unit 501 may be specifically configured to receive a request message from the application server 700 via an access management network element (AMF) or receive a request message from the application server 700 via the terminal device 800, which may be specifically implemented by referring to FIG. 5 or FIG. For example, I won't go into details here.
  • AMF access management network element
  • the first time information may also refer to information for setting the transmission duration of the data packet, such as maximum response time information.
  • the second time information may also refer to information for setting a transmission delay of the data packet, such as maximum delay time information.
  • the first time information can be used to set the time at which the terminal device 800 is in the first state of the connected state
  • the second time information can be used to set the time at which the terminal device 800 is in the second state of the connected state.
  • the first state of the connected state may include, but is not limited to, an active state, such as an RRC CONNECTED state.
  • the second state of the connected state may include, but is not limited to, an inactive state, such as an RRC INACTIVE state.
  • the processing unit 503 is specifically configured to set a time when the terminal device 800 is in the first state of the connected state according to the first time information, and/or set the second state of the terminal device 800 in the connected state according to the second time information. time.
  • the first time information can be used to set the time when the terminal device 800 is in the connected state in the mobile-only initiated connection MICO mode
  • the second time information can be used to set the terminal device 800 to initiate the uplink after the idle state in the MICO mode.
  • the time of signaling or data can be used.
  • the processing unit 503 is specifically configured to set, according to the first time information, a time when the terminal device 800 is in the connected state in the mobile only initiated connection MICO mode, and/or set the terminal device 800 in the MICO mode according to the second time information. The time at which uplink signaling or data is initiated after the idle state.
  • the request message may further include the identification information of the application, and the connection state may be specifically the connection state of the application corresponding to the terminal device 800.
  • the request message may also include identification information of the terminal device 800 and/or identification information of the application server 700.
  • the network capability opened by the mobile communication carrier may include: setting the duration of the terminal device in the RRC INACTIVE state, and/or setting the MICO mode.
  • the status of the terminal device By opening such a network capability, the third-party service provider can request the network side to set the duration of the terminal device in the RRC INACTIVE state, and/or set the state of the terminal device in the MICO mode, which can facilitate the third-party service provider to the terminal.
  • the device transmits downstream packets.
  • the communication system 30 illustrated in FIG. 10 can be implemented as the communication system 100 illustrated in FIG.
  • the application server 700 can be an SCS/AS 100.
  • the core network device 600 may include a network open function network element (NEF) 11, an access and mobility management function network element (AMF) 19, a session management function network element (SMF) 18, and a user plane function network element (UPF) 14.
  • a data network (DN) 15, an application function network element (AF) 16, a policy control function network element (PCF) 17, a unified data management network element (UDM) 20, and an authentication server function network element (AUSF) 21, and the like.
  • Access network device 500 can be (R) AN13.
  • the terminal device 800 can be the UE 12.
  • FIG 11 illustrates another communication system and communication device provided by the present application.
  • Communication system 40 may include communication devices such as application server 110, core network device 120, access network device 130, and terminal device 140.
  • the communication system 40 and the communication device therein can implement the capability opening method described in the embodiment of FIG. The description is expanded below.
  • the application server 110 may include a transmitting unit 111 and a receiving unit 113. among them:
  • the sending unit 111 is configured to send a request message to the core network device 120, where the request message includes identifier information and data volume information of the terminal device.
  • the receiving unit 113 is configured to receive a response message of the request message from the core network device 120.
  • the request message may further include the identification information of the application, and the data volume information may be specifically the data amount information to be cached corresponding to the application.
  • the core network device 120 may transmit a corresponding user plane function network element UPF for the data packet of the application server, or a UPF corresponding to the data network name of the local data network LADN corresponding to the application server, or the terminal.
  • the core network device 120 may include: a receiving unit 121 and a processing unit 123. among them:
  • the receiving unit 121 is configured to obtain the request message request message from the application server 110, including identifier information and data amount information of the terminal device.
  • the processing unit 123 is configured to cache, according to the data volume information, the data packet sent by the application server 110 to the terminal device.
  • the request message from the application server 110 refers to a series of request messages initiated from the application server 110, going through a plurality of core network elements, and finally reaching a core network element for application data packet caching. Used to request to cache application packets.
  • the core network element for applying the data packet buffer may include: a UPF corresponding to a data network access point identifier (DNAI) of the application server 110, or a local data network corresponding to the application server 110.
  • DNN data network name
  • LADN Local Area Data Network
  • the processing unit 123 may be specifically a processing unit in the UPF, and the UPF may cache the data packet sent by the application server 110 to the terminal device according to the data amount information.
  • the processing unit 123 may be specifically a processing unit in the SMF corresponding to the terminal device, and the SMF corresponding to the terminal device may cache the data packet sent by the application server 110 to the terminal device according to the data amount information.
  • the request message further includes identification information of the application, and the data volume information is data amount information to be cached corresponding to the application.
  • the processing unit 123 may be specifically configured to detect a type of the data packet sent by the application server 110 to the terminal device, determine whether the data packet is a data packet corresponding to the application, and if so, cache the data packet. In this way, the core network device 120 can process the application data packets from different third-party applications, and only the application data packets of the third-party applications indicated by the identification information of the application are cached, so as to better support the different services of the third-party service providers. demand.
  • the network capability opened by the mobile communication carrier can include: caching application data packets, especially when the terminal device is unreachable.
  • the communication system 40 illustrated in FIG. 11 can be implemented as the communication system 100 illustrated in FIG.
  • the application server 700 can be an SCS/AS 100.
  • the core network device 600 may include a network open function network element (NEF) 11, an access and mobility management function network element (AMF) 19, a session management function network element (SMF) 18, and a user plane function network element (UPF) 14.
  • a data network (DN) 15, an application function network element (AF) 16, a policy control function network element (PCF) 17, a unified data management network element (UDM) 20, and an authentication server function network element (AUSF) 21, and the like.
  • Access network device 500 can be (R) AN13.
  • the terminal device 800 can be the UE 12.
  • the implementation of the technical solution provided by the present application can realize that the mobile communication network can open more network capabilities to third-party service providers, and better support the business requirements of third-party service providers.
  • the program can be stored in a computer readable storage medium, when the program is executed
  • the flow of the method embodiments as described above may be included.
  • the foregoing storage medium includes various media that can store program codes, such as a ROM or a random access memory RAM, a magnetic disk, or an optical disk.

Landscapes

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

Abstract

本申请实施例公开了一种能力开放方法，所述方法可包括：接入网设备获取来自应用服务器的请求消息，所述请求消息包括第一时间信息和/或第二时间信息，所述第一时间信息用于设置所述终端设备处于连接态的第一状态的时间，所述第二时间信息用于设置所述终端设备处于连接态的第二状态的时间；所述接入网设备根据所述第一时间信息和/或所述第二时间信息设置所述终端设备的连接态。上述方案可实现移动通信网络向第三方业务提供商开放更多的网络能力，更好的支撑第三方业务提供商的业务需求。

Description

能力开放方法、相关装置及系统 技术领域
本申请涉及无线通信技术领域，尤其涉及能力开放方法、相关装置及系统。
背景技术
随着互联网各类应用的丰富，第三方业务提供商对网络运营商的信息交互及网络个性需求愈来愈强烈，网络能力开放逐渐成为未来网络技术的主流。
在未来的通信网络中，网络能力开放的场景可能会出现在车联网、工业网络、移动医疗探测、高清视频、紧急业务、网络金融等领域。
但是，目前移动通信网络向第三方业务提供商已经开放的网络能力有限，不能够很好的支撑新空口(new radio，NR)或未来通信系统下第三方业务提供商的业务需求。
发明内容
本申请实施例提供了能力开放方法、相关装置及系统，可实现移动通信网络向第三方业务提供商开放更多的网络能力，更好的支撑第三方业务提供商的业务需求。
第一方面，本申请提供了一种能力开放方法，应用于应用服务器侧，该方法可包括：应用服务器向接入网设备发送请求消息，该请求消息可包括第一时间信息和/或第二时间信息。应用服务器接收来自接入网设备的请求消息的响应消息。
第二方面，本申请提供了一种能力开放方法，应用于接入网设备侧，该方法可包括：接入网设备获取来自应用服务器的请求消息，该请求消息可包括第一时间信息和/或第二时间信息。然后，接入网设备根据第一时间信息和/或第二时间信息设置终端设备的连接态。
结合第一方面或第二方面，来自应用服务器的请求消息是指从应用服务器发起，经历核心网设备，最后到达接入网设备的一系列请求消息，这一系列请求消息共同用于请求接入网设备设置终端设备的连接态。这里，请求消息经历的核心网网元具体可包括但不限于：NEF、UDM、AMF。具体的，接入网设备可以具体经接入管理网元(AMF)接收来自应用服务器的请求消息或者经终端设备接收来自应用服务器的请求消息。
结合第一方面或第二方面，第一时间信息也可以是指用于设置数据包的传输时长的信息，例如最大响应时间信息。第二时间信息也可以是指用于设置数据包的传输时延的信息，例如最大延迟时间信息。
具体的，第一时间信息可用于设置终端设备处于连接态的第一状态的时间，第二时间信息可用于设置终端设备处于连接态的第二状态的时间。这里，连接态的第一状态可包括但不限于激活状态，如RRC CONNECTED状态。连接态的第二状态可包括但不限于非激活状态，如RRC INACTIVE状态。相应的，接入网设备可以根据第一时间信息设置终端设备处于连接态的第一状态的时间，和/或，根据第二时间信息设置终端设备处于连接态的第二状态的时间。
可以理解的，实施第一方面和第二方面描述的方法，移动通信运营商开放的网络能力可包括：设置终端设备(UE)处于RRC INACTIVE状态的时长。通过开放这种网络能力， 第三方服务提供商可以向网络侧请求设置终端设备(UE)处于RRC INACTIVE状态的时长，可便于第三方服务提供商向终端设备传输下行数据包。
结合第一方面或第二方面，在一些实施例中，请求消息还可以包括应用的标识信息，连接态为终端设备对应应用的连接态。这样可实现针对特定应用设置终端设备的连接态，为不同应用提供区别化的网络能力。
第三方面，本申请提供了一种能力开放方法，应用于应用服务器侧，该方法可包括：应用服务器向接入网设备发送请求消息，该请求消息可包括第一时间信息和/或第二时间信息。应用服务器接收来自接入网设备的请求消息的响应消息。
第四方面，本申请提供了一种能力开放方法，应用于接入网设备侧，该方法可包括：接入网设备获取来自应用服务器的请求消息，该请求消息可包括第一时间信息和/或第二时间信息。接入网设备根据第一时间信息和/或第二时间信息设置终端设备的在MICO模式下的状态。
结合第三方面或第四方面，来自应用服务器的请求消息是指从应用服务器发起，经历核心网设备，最后到达接入网设备的一系列请求消息，这一系列请求消息共同用于请求接入网设备设置终端设备的连接态。这里，请求消息经历的核心网网元具体可包括但不限于：NEF、UDM、AMF。具体的，接入网设备可以具体经接入管理网元(AMF)接收来自应用服务器的请求消息或者经终端设备接收来自应用服务器的请求消息。
结合第三方面或第四方面，第一时间信息也可以是指用于设置数据包的传输时长的信息，例如最大响应时间信息。第二时间信息也可以是指用于设置数据包的传输时延的信息，例如最大延迟时间信息。
具体的，第一时间信息可用于设置终端设备在仅移动发起连接MICO模式下处于连接态的时间，和/或，设置终端设备在MICO模式下在空闲态后发起上行信令或者数据的时间。相应的，接入网设备可以根据第一时间信息设置终端设备在仅移动发起连接MICO模式下处于连接态的时间，和/或，设置终端设备在MICO模式下在空闲态后发起上行信令或者数据的时间。
可以理解的，实施第三方面和第四方面描述的方法，移动通信运营商开放的网络能力可包括：设置MICO模式下的终端设备(UE)的状态。通过开放这种网络能力，第三方服务提供商可以向网络侧请求设置MICO模式下的终端设备(UE)的状态，可便于第三方服务提供商向终端设备传输下行数据包。
结合第三方面或第四方面，在一些实施例中，请求消息还可以包括应用的标识信息，连接态为终端设备对应应用的连接态。这样可实现针对特定应用设置终端设备在MICO模式下的状态，为不同应用提供区别化的网络能力。
第五方面，本申请提供了一种能力开放方法，应用于应用服务器侧，该方法可包括：应用服务器向核心网设备发送请求消息，请求消息包括终端设备的标识信息、数据量信息。应用服务器接收来自核心网设备的请求消息的响应消息。
第六方面，本申请提供了一种能力开放方法，应用于核心网设备侧，该方法可包括：核心网网元获取来自应用服务器的请求消息请求消息包括终端设备的标识信息、数据量信息。然后，核心网设备根据数据量信息缓存应用服务器向终端设备发送的数据包。
结合第五方面或第六方面，来自应用服务器的请求消息是指从应用服务器发起，经历多个核心网网元，最后到达用于应用数据包缓存的核心网网元的一系列请求消息，这一系列请求消息共同用于请求缓存应用数据包。
本申请中，用于应用数据包缓存的核心网网元可包括：应用服务器(SCS/AS)的数据网络传输接入点标识(DNAI)对应的UPF，或者应用服务器(SCS/AS)对应的本地数据网络(LADN)的数据网络名称(DNN)对应的UPF，或者，终端设备对应的SMF。
可选的，应用服务器(SCS/AS)的DNAI对应的UPF可以根据该数据量信息缓存应用服务器向终端设备发送的数据包。可选的，终端设备对应的SMF可以根据该数据量信息缓存应用服务器向终端设备发送的数据包。
可以理解的，实施第五方面和第六方面描述的方法，移动通信运营商开放的网络能力可包括：缓存应用数据包，尤其是在终端设备不可达时。通过开放这种网络能力，第三方服务提供商可以向网络侧请求缓存应用数据包，可便于第三方服务提供商向终端设备传输下行数据包。
结合第五方面或第六方面，在一些实施例中，请求消息还可以包括应用的标识信息，数据量信息为应用对应的待缓存的数据量信息。进一步的，核心网设备可具体检测应用服务器向终端设备发送的数据包的类型，判断数据包是不是应用对应的数据包，若是，则缓存数据包。这样可实现核心网设备区别处理来自不同的第三方应用的应用数据包，仅仅缓存来自应用的标识信息指示的第三方应用的应用数据包，可更好的支撑第三方服务提供商的不同业务需求。
第七方面，本申请提供了一种应用服务器，包括多个功能单元，用于相应的执行第一方面或第三方面或第五方面可能的实施方式中的任意一种所提供的方法。
第八方面，本申请提供了一种接入网设备，包括多个功能单元，用于相应的执行第二方面或第四方面可能的实施方式中的任意一种所提供的方法。
第九方面，本申请提供了一种核心网设备，包括多个功能单元，用于相应的执行第六方面可能的实施方式中的任意一种所提供的方法。
第十方面，本申请提供了一种应用服务器，用于执行第一方面或第三方面或第五方面可能的实施方式中的任意一种所描述的能力开放方法。应用服务器可包括：存储器以及与存储器耦合的处理器、收发器，其中：收发器用于与其他通信设备(如核心网设备)通信。存储器用于存储第一方面或第三方面或第五方面可能的实施方式中的任意一种所描述的能力开放方法的实现代码，处理器用于执行存储器中存储的程序代码，即执行第一方面或第三方面或第五方面可能的实施方式中的任意一种所提供的方法。
第十一方面，本申请提供了一种接入网设备，用于执行第二方面或第四方面可能的实施方式中的任意一种所描述的能力开放方法。应用服务器可包括：存储器以及与存储器耦合的处理器、收发器，其中：收发器用于与其他通信设备(如核心网设备)通信。存储器用于存储第二方面或第四方面可能的实施方式中的任意一种所描述的能力开放方法的实现代码，处理器用于执行存储器中存储的程序代码，即执行第二方面或第四方面可能的实施方式中的任意一种所提供的方法。
第十二方面，本申请提供了一种核心网设备，用于执行第六方面可能的实施方式中的 任意一种所描述的能力开放方法。应用服务器可包括：存储器以及与存储器耦合的处理器、收发器，其中：收发器用于与其他通信设备(如应用服务器、核心网设备)通信。存储器用于存储第六方面可能的实施方式中的任意一种所描述的能力开放方法的实现代码，处理器用于执行存储器中存储的程序代码，即执行第六方面可能的实施方式中的任意一种所提供的方法。
第十三方面，本申请提供了一种通信系统，通信系统包括：应用服务器和接入网设备，其中：应用服务器可以是第一方面或第三方面中描述的应用服务器。接入网设备可以是第二方面或第四方面中描述的接入网设备。
第十四方面，本申请提供了一种通信系统，通信系统包括：应用服务器和核心网设备，其中：应用服务器可以是第五方面中描述的应用服务器。接入网设备可以是第六方面中描述的核心网设备。
第十五方面，本申请提供了另一种计算机可读存储介质，可读存储介质上存储有指令，当其在计算机上运行时，使得计算机执行上述第一方面至第六方面中任一项描述的能力开放方法。
第十六方面，本申请提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面至第六方面中任一项描述的能力开放方法。
附图说明
为了更清楚地说明本申请实施例中的技术方案，下面将对本申请实施例或背景技术中所需要使用的附图进行说明。
图1是本申请涉及的一种无线通信系统的架构示意图；
图2是本申请提供的一种能力开放方法的流程示意图；
图3是本申请提供的又一种能力开放方法的流程示意图；
图4是本申请提供的再一种能力开放方法的流程示意图；
图5是本申请提供的再一种能力开放方法的流程示意图；
图6是图5实施例涉及的UL CL的网络架构的示意图；
图7是本申请的一个实施例提供的应用服务器的架构示意图；
图8是本申请的一个实施例提供的接入网设备的架构示意图；
图9是本申请的一个实施例提供的核心网设备的架构示意图；
图10是本申请的提供的一种通信系统，相关通信装置的功能框图；
图11是本申请的提供的又一种通信系统，相关通信装置的功能框图。
具体实施方式
本申请的实施方式部分使用的术语仅用于对本申请的具体实施例进行解释，而非旨在限定本申请。
图1示出了本申请涉及的通信系统100的架构。图1所示的通信系统100包括第三方业务提供商提供的业务能力服务器/应用服务器(service capability server/applicantserver，SCS/AS)10和移动通信运营商提供的移动通信系统。该业务能力服务器/应用服务器10为 第三方业务提供商和/或网络运营商的应用服务器，可提供一个或多个应用服务，如语音服务、视频服务、基于位置的服务等。该移动通信系统向应用服务器10开放网络能力。该移动通信系统不限于长期演进(long term evolution，LTE)系统，还可以是未来演进的第五代移动通信(the 5th Generation，5G)系统、新空口(NR)系统，机器与机器通信(machine to machine，M2M)系统等。如图1所示，该移动通信系统可包括终端设备12、接入网设备13和核心网设备。
终端设备12：可以为用户设备(userequipment，UE)、手持终端、笔记本电脑、用户单元(subscriberunit)、蜂窝电话(cellularphone)、智能电话(smartphone)、无线数据卡、个人数字助理(personal digital assistant，PDA)电脑、平板型电脑、无线调制解调器(modem)、手持设备(handheld)、膝上型电脑(laptopcomputer)、无绳电话(cordlessphone)或者无线本地环路(wireless local loop，WLL)台、机器类型通信(machine type communication，MTC)终端设备或是其他可以接入网络的设备。终端设备12与接入网设备13之间采用某种空口技术相互通信。
接入网((R)AN)设备13：可包含RAN设备或者AN设备。RAN设备主要是3GPP无线网络设备，例如基站。AN设备可以是non-3GPP定义的接入网设备，例如Wi-Fi路由器。RAN设备主要负责空口侧的无线资源管理、服务质量(quality of service，QoS)管理、数据压缩和加密等功能。其中，RAN设备可以包括：宏基站，微基站(也称为小站)，中继站等。在采用不同的无线接入技术的系统中，具备基站功能的设备的名称可能会有所不同，例如，在第五代(5th generation，5G)系统中，称为gNB；在LTE系统中，称为演进的节点B(evolved NodeB，eNB或者eNodeB)；在第三代(3rd generation，3G)系统中，称为节点B(Node B)等。其中，AN设备允许终端设备和3GPP核心网之间采用非3GPP技术互连互通，其中，非3GPP技术例如：无线保真(wirelessfidelity，Wi-Fi)、全球微波互联接入(worldwide interoperability for microwave access，WiMAX)、码分多址(code division multiple access，CDMA)网络等。
核心网设备可如图1所示包括NEF 11、UPF 14、AF16、PCF 17、SMF18、AMF19、UDM 20、AUSF21等。其中：
网络开放功能(network exposure function，NEF)网元11：主要支持3GPP网络和第三方应用安全的交互，通过NEF能够安全的向第三方开放移动通信网络能力和事件，用于加强或者改善应用服务质量，3GPP网络同样可以安全的从第三方获取相关数据，用以增强网络的智能决策；同时该网元支持从统一数据库恢复结构化数据或者向统一数据库中存储结构化数据。
用户面功能(user plane function，UPF)网元14：负责数据包的转发和接收。UPF网元可以从数据网络接收用户数据，通过接入网设备传输给终端设备；UPF网元还可以通过接入网设备从终端设备接收用户数据，转发到数据网络。UPF网元中为终端设备提供服务的传输资源和调度功能由SMF网元管理控制的。UPF网元可以缓存数据包。
应用功能(application function，AF)网元16：向终端设备提供应用服务的应用服务器设备等，可以与3GPP核心网交互来提供服务，例如影响数据路由决策，策略控制功能或者向网络侧提供第三方的一些服务。
策略控制功能(policy control function，PCF)网元17：主要支持提供统一的策略框架来控制网络行为，提供策略规则给控制层设备以及终端设备提供策略信息，同时负责获取与策略决策相关的用户签约信息。
会话管理功能(session management function，SMF)网元18：负责用户面网元选择，用户面网元重定向，因特网协议(internetprotocol，IP)地址分配，数据传输通道的建立、修改和释放以及QoS控制。SMF网元可以缓存数据包。
接入和移动性管理功能(access and mobility management function，AMF)网元19：属于核心网网元，主要负责信令处理部分，例如：接入控制、移动性管理、附着与去附着以及网关选择等功能。AMF网元为终端设备中的会话提供服务的情况下，会为该会话提供控制面的存储资源，以存储会话标识、与会话标识关联的SMF网元标识等。
统一数据管理(unified data management，UDM)网元20：统一的数据管理，由两部分构成，一部分叫应用前段(FE)，另一部分叫用户数据仓库(UDR)。FE可以访问存储在UDR中的订阅用户信息，并支持鉴权信用处理、用户标识处理、访问授权、订阅管理、短消息管理等。UDR是一个用户订阅数据存储服务器，提供订阅数据存储服务。
鉴权服务器功能(authentication server function，AUSF)网元21：主要提供认证和鉴权功能。
另外，通信系统100还包括数据网络(data network，DN)15，DN15为由应用功能组成的向终端设备提供应用数据服务器的网络。
应理解的，图1中的网络功能，如NEF 11、UPF 14、AF16、PCF 17、SMF18、AMF19、UDM 20、AUSF21等，属于移动通信系统的核心网设备。为了简化附图，核心网中的非结构化数据存储网络功能(unstructured data storage network function，UDSF)、结构化数据存储网络功能(structured data storage network function，SDSF)和NF存储功能(NF repository function，NRF)未示出。
应理解的，图1中的移动通信系统是基于参考点的通信架构。基于参考点的通信架构体现了点对点的网络功能之间的交互，例如UDM 20和SMF 18之间基于参考点N10进行交互。关于图中各个参考点的定义和说明，请参考相关3gpp协议，比如TS23.501、TS23.502以及TS23.503等，这里不赘述。另外，NEF和其他网元(如PCF网元、UDM网元)之间通过NEF展示的基于服务接口(Service-based interface exhibited by NEF，Nnef)进行通信。
目前，应用服务器10可实现移动通信运营商提供的开放应用程序接口(application programming interface，API)，以获取移动通信运营商开放的网络能力。移动通信运营商开放的网络能力主要包括通信能力，上下文信息，签约信息和控制能力等。其中，通信能力是指语音、短消息、多媒体消息服务；上下文信息包含实时的用户信息，例如用户位置，终端设备能力和数据连接类型等；签约信息包括签约标识、优先权等信息；控制能力指的是对业务质量、策略和安全方面的控制和监控功能。实际应用中，第三方业务提供商可以结合目前已有的各种网络能力开发出更多满足用户实际需要的新型业务。
但是，目前移动通信网络向第三方业务提供商已经开放的网络能力有限，不能够很好的支撑新空口(NR)或未来通信系统下第三方业务提供商的业务需求。
本申请提供一种能力开放方法，可实现移动通信网络向第三方业务提供商开放更多的 网络能力，更好的支撑第三方业务提供商的业务需求。本申请中，针对NR新引入的RRC INACTIVE状态，移动通信运营商开放的网络能力可包括：设置终端设备处于RRC INACTIVE状态的时长。本申请中，针对NR中支持的仅移动发起连接(mobile initiated connection only，MICO)模式，移动通信运营商开放的网络能力还可包括：设置MICO模式下的终端设备的状态。关于本申请提供的能力开放方法，后续实施例会详细说明，这里先不赘述。
图1示出的通信系统100仅仅是为了更加清楚的说明本申请的技术方案，并不构成对本申请的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请提供的技术方案对于类似的技术问题，同样适用。
本申请提供了一种能力开放方法，可实现移动通信网络向第三方业务提供商开放更多的网络能力，更好的支撑第三方业务提供商的业务需求。
首先，介绍本申请涉及的NR中新引入的RRC INACTIVE状态、NR支持的终端设备MICO模式。
(1)RRC INACTIVE状态
在大规模物联网下，大量的设备零星传送少量的数据，会带来过高的信令开销。一边是功耗，一边是快速接入，还要减少信令开销，要兼顾三者，NR新引入了一种新的RRC状态：RRC INACTIVE状态。RRC INACTIVE状态和RRC CONNECTED状态都为连接态。在RRC INACTIVE状态下，它仍然保留部分RAN上下文(例如：安全上下文，UE能力信息等)，但终端设备与RAN设备之间的连接释放，可以通过类似于寻呼的消息快速从RRC INACTIVE状态转移到RRC CONNECTED状态，且减少信令数量。
对于处于RRC INACTIVE状态的终端设备，在上下行数据包待传输时，需要先建立终端设备与接入网设备之间的连接。具体的，当下行数据包到来时，接入网设备向终端设备发起寻呼过程，从而建立终端设备与接入设备之间的连接。
(2)MICO模式
5G系统中增加了对终端设备MICO模式的支撑，可以在终端设备在初始注册或者注册更新期间协商终端设备处于MICO模式。而且，当终端设备处于MICO模式时，AMF认为空闲态下的终端设备不可达，AMF拒绝任何向终端设备进行下行数据传输的请求。也即是说，当MICO模式下的终端设备的状态为空闲态时，只能由该终端设备发起传输数据的信令过程，而不能由网络侧发起传输数据的信令过程。当MICO模式下的终端设备的状态为连接态时，网络侧和该终端设备都可以发起传输数据的信令过程。
本申请中，针对NR新引入的RRC INACTIVE状态，移动通信运营商开放的网络能力可包括：设置终端设备处于RRC INACTIVE状态的时长。通过开放这种网络能力，第三方服务提供商可以向网络侧请求设置终端设备处于RRC INACTIVE状态的时长。网络侧可以响应第三方服务提供商的请求，相应的设置终端设备处于RRC INACTIVE状态的时长，可便于第三方服务提供商向终端设备传输下行数据包。
本申请中，针对NR中支持的MICO模式，移动通信运营商开放的网络能力还可包括：设置MICO模式下的终端设备的状态。通过开放这种网络能力，第三方服务提供商可以向 网络侧请求设置MICO模式下的终端设备的状态。网络侧可以响应第三方服务提供商的请求，相应的设置MICO模式下的终端设备的状态，可便于第三方服务提供商向终端设备传输下行数据包。
本申请中，可以将RRC INACTIVE状态称为连接态的非激活状态，可以将RRC CONNECTED状态称为连接态的激活状态。不限于RRC INACTIVE状态，非激活状态还可以包括其他类似RRC INACTIVE状态的连接状态。不限于RRC CONNECTED状态，激活状态还可以包括其他类似RRC CONNECTED状态的连接状态。未来通信标准可能改变RRC INACTIVE状态、RRC CONNECTED状态的命名，本申请提供的技术方案不受此影响。
应理解的，激活状态、非激活状态仅是本申请提供的能力开放方法可适用的连接态包括的两种具体示例状态，后续内容中，本申请中激活状态、非激活状态可以分别概括的称为连接态的第一状态、连接态的第二状态。
(一)实施例一
本实施例中，针对NR新引入的RRC INACTIVE状态，移动通信运营商开放的网络能力可包括：设置终端设备处于RRC INACTIVE状态的时长。如图2所示，实施例一提供的能力开放方法可包括：
S101-S106，接入网设备获取来自应用服务器的请求消息，该请求消息可包括第一时间信息和/或第二时间信息。其中，第一时间信息可用于设置终端设备处于连接态的第一状态的时间，第二时间信息可用于设置终端设备处于连接态的第二状态的时间。
这里，连接态的第一状态可以是连接态的激活状态，如RRC CONNECTED状态。连接态的第二状态可以是连接态的非激活状态，如RRC INACTIVE状态。第一时间信息也可以是指用于设置数据包的传输时长的信息，例如最大响应时间信息。第二时间信息也可以是指用于设置数据包的传输时延的信息，例如最大延迟时间信息。
这里，来自应用服务器的请求消息是指从应用服务器发起，经历核心网，最后到达接入网设备的一系列请求消息，这一系列请求消息共同用于请求接入网设备设置终端设备的连接态。这里，请求消息经历的核心网网元具体可包括但不限于：NEF网元、UDM网元、AMF网元。
如图2所示，接入网设备获取来自应用服务器的请求消息的过程可包括但不限于：
S101，应用服务器向NEF网元发送监控请求，该监控请求可包括：第一时间信息和/或第二时间信息。可选的，该监控请求还可包括应用服务器的标识信息和/或终端设备的标识信息，终端设备的标识信息可以是终端设备的外部标识，或者永久设备标识(Permanent Equipment Identifier，PEI)等。可选的，该监控请求还可包括应用的标识信息，应用的标识信息用于标识发起监控请求过程的第三方应用。可选的，该监控请求还可包括监控事件类型，本申请中的该监控事件类型就是监控终端设备的连接状态的事件类型。
S102，NEF网元在接收到应用服务器发送的监控请求后，可进行NEF处理。
NEF处理可包括但不限于如下过程：
可选的，NEF网元可以保存应用的标识信息。可选的，NEF网元可以不保存应用的标 识信息，而是在NEF网元需要该信息时向应用服务器获取该信息。关于NEF网元向应用服务器获取应用的标识信息的具体实现过程，本申请不作限制。
可选地，NEF网元可以分配NEF参考标识。
可选地，NEF网元可以根据运营商的策略，确定应用服务器发送的监控请求是否合法，如果不合法，则向SCS/AS发送响应消息，该响应消息可包括拒绝原因等信息。
S103，NEF网元向UDM网元发送监控请求，该监控请求可包括：第一时间信息和/或第二时间信息。可选的，该监控请求还可包括应用服务器的标识信息、终端设备的标识信息，终端设备的标识信息可以是终端设备的外部标识，或者永久设备标识等。可选的，该监控请求还可包括应用的标识信息。可选的，该监控请求还可包括NEF相关信息，如NEF参考标识。可选的，该监控请求还可包括监控事件类型，本申请中的该监控事件类型就是监控终端设备的连接状态的事件类型。
S104，UDM网元在接收到NEF网元发送的监控请求后，可进行UDM处理。
UDM处理可包括但不限于：UDM网元根据运营商的策略检查该监控请求中的参数是否合法等，以及根据终端设备的表示信息确定终端设备对应的AMF。此外，UDM处理还可包括：UDM网元根据终端设备的外部标识确定终端设备的网内标识，如签约永久标识(Subscriber Permanent Identifier，SUPI)。
S105，UDM网元向AMF网元发送消息，该消息可包括第一时间信息和/或第二时间信息。这里，该消息可用于指示终端设备请求RAN根据第一时间信息和/或第二时间信息设置终端设备的连接态。仅作为一种示例，该消息可以是插入签约数据的消息。
可选的，该消息还可包括应用服务器的标识信息、终端设备的标识信息，终端设备的标识信息可以是终端设备的外部标识，或者永久设备标识等。可选的，该消息还可包括应用的标识信息。可选的，该消息还可包括NEF相关信息，如NEF参考标识。可选的，该消息还可包括监控事件类型，本申请中的该监控事件类型就是监控终端设备的连接状态的事件类型。
S106，AMF网元向接入网设备发送请求消息，用于请求设置终端设备的连接态。
具体的，该请求消息可以为RRC INACTIVE辅助信息请求消息，该请求消息可包括第一时间信息和/或第二时间信息。可选的，该请求消息还可包括应用服务器的标识信息、终端设备的标识信息，终端设备的标识信息可以是终端设备的外部标识，或者永久设备标识等。可选的，该请求消息还可包括应用的标识信息。可选的，该请求消息还可包括监控事件类型，本申请中的该监控事件类型就是监控终端设备的连接状态的事件类型。
应理解的，图2中，应用服务器向NEF网元发送的监控请求与NEF网元向UDM网元发送的监控请求是不同的信令，二者在信令实现上是不同。这里，监控请求仅仅是一种消息命名，本申请对此不作限制，只要功能相同即可。后续实施例中提及的监控请求同样适用，不限制消息名称。
从图2可以看出，实施例一中，上述来自应用服务器的请求消息所对应的一系列请求消息可包括：S101中被发送的监控请求、S103中被发送的监控请求、S105中被发送的消息、S106中被发送的请求消息。不限于S101-S106所示，上述来自应用服务器的请求消息所对应的一系列请求消息还可以实施为其他信令，本申请对此不作限制。
S107，在接收到AMF网元发送的请求之后，接入网设备可以根据第一时间信息和/或第二时间信息设置终端设备的连接态。具体的，接入网设备可以根据第一时间信息设置终端设备处于RRC CONNECTED状态的时长，和/或，接入网设备可以根据第二时间信息设置终端设备处于RRC INACTIVE状态的时长。
可选的，在接入网设备接收到的请求消息包括应用的标识信息的条件下，终端设备的连接态具体可以是指终端设备对应该应用的标识信息指示的应用的连接态。这样，可实现针对特定应用来设置终端设备的连接态，可以更好的支撑第三方服务商的业务需求。
举例说明，假设第一时间信息是指最大响应时间10ms，那么，接入网设备可以设置终端设备处于RRC CONNECTED状态的时长为大于或等于10ms。这样，可以确保终端设备保持可达性，便于应用服务器向终端设备持续传输应用数据包。
又举例说明，假设第二时间信息是指最大延迟时间5ms，那么，接入网设备可以设置终端设备处于RRC INACTIVE状态的时长为小于或等于5ms。这样，可以确保终端设备及时可达，便于应用服务器向终端设备持续传输应用数据包。可选的，接入网设备可以根据该最大延时时间设置周期性RAN通知区域更新定时器(periodic RAN Notification Area Update timer)，来设置终端设备处于RRC INACTIVE状态的时长。
S108-S109，在接入网设备完成设置终端设备处于RRC CONNECTED状态和/或RRC INACTIVE状态的时长后，AMF网元可以经NEF网元向应用服务器返回监控指示，该监控指示可包括：终端设备的连接状态、接入类型等。
可选地，AMF可以根据应用的标识信息确定第三方应用对应的接入技术，如果不是3GPP接入技术，则设置失败，此时监控指示便是设置失败的消息。关于如何判断第三方应用对应的接入技术，本申请不作不限制。可选地，AMF可以判断接入网设备是否是3GPP的接入网设备，如果不是3GPP的接入网设备，则设置失败，此时监控指示便是设置失败的消息。
实施例一的相关扩展一
可选的，S101中被发送的监控请求中包含的可以不是第一时间信息和/或第二时间信息，而可以是第三时间信息和/或第四时间信息，其中，第三时间信息可以用于确定出第一时间信息，第四时间信息可以用于确定出第二时间信息。
例如，第三时间信息可以是应用服务器请求的最大响应时间10ms，核心网设备(如NEF网元或UDM网元或AMF网元)可以根据该10ms确定第一时间信息为大于或等于10ms的时长，如15ms，以确保终端设备能够在应用服务器向终端设备传输应用数据包时始终处于可达状态，实现持续的数据传输。
又例如，第四时间信息可以是应用服务器请求的最大延迟时间5ms，核心网设备(如NEF网元或UDM网元或AMF网元)可以根据该5ms确定第一时间信息为大于或等于5ms的时长，如4ms，以确保终端设备能够在应用服务器向终端设备传输应用数据包时及时处于可达状态，实现有效的数据传输。
实施例一的相关扩展二
具体的，终端设备可以处于MICO模式下。第一时间信息可用于设置终端设备在MICO模式下处于连接态的时间，第二时间信息可用于设置终端设备在MICO模式下在空闲态后发起上行信令或者数据的时间。
如图3中的S207所示，针对处于MICO模式下的终端设备，在接收到AMF网元发送的请求之后，接入网设备可以根据第一时间信息和/或第二时间信息设置处于MICO模式下的终端设备状态。具体的，接入网设备可以根据第一时间信息设置终端设备在MICO模式下处于连接态的时间，和/或，接入网设备可以根据第二时间信息设置终端设备在MICO模式下在空闲态后发起上行信令或者数据的时间。
也即是说，移动通信运营商开放的网络能力还可包括：设置MICO模式下的终端设备的状态。通过开放这种网络能力，第三方服务提供商可以向网络侧请求设置MICO模式下的终端设备的状态。网络侧可以响应第三方服务提供商的请求，相应的设置MICO模式下的终端设备的状态，可便于第三方服务提供商向终端设备传输下行数据包。
图3中的S201-S206可参考图2中的S101-S106，图3中的S208-S209可参考图2中的S108-S109，这里不再赘述。
在一些可选的实施例中，实施例一和实施例一的相关扩展可以结合。具体的，在接收到AMF网元发送的请求之后，接入网设备可以判断终端设备是否处于MICO模式下，如果终端设备处于MICO模式下，则采用图3实施例提供的能力开放方法；否则，采用图2实施例提供的能力开放方法。
(二)实施例二
实施例一中，AMF网元接收来自应用服务器的请求消息。与实施例一不同的是，本实施例中，接入网设备经终端设备接收来自应用服务器的请求消息。
如图4所示，接入网设备获取来自应用服务器的请求消息的过程可包括如下两个阶段：
(1)第一阶段：终端设备接收来自应用服务器的请求消息。具体可包括：
S301，应用服务器向NEF网元发送监控请求，该监控请求可包括：第一时间信息和/或第二时间信息。可选的，该监控请求还可包括应用服务器的标识信息和/或终端设备的标识信息，终端设备的标识信息可以是终端设备的外部标识，或者永久设备标识等。可选的，该监控请求还可包括应用的标识信息，应用的标识信息用于标识发起监控请求过程的第三方应用。可选的，该监控请求还可包括监控事件类型，本申请中的该监控事件类型就是监控终端设备的连接状态的事件类型。
S302，NEF网元在接收到应用服务器发送的监控请求后，可进行NEF处理。
NEF处理可包括但不限于如下过程：
可选的，NEF网元可以保存应用的标识信息。可选的，NEF网元可以不保存应用的标识信息，而是在NEF网元需要该信息时向应用服务器获取该信息。关于NEF网元向应用服务器获取应用的标识信息的具体实现过程，本申请不作限制。
可选地，NEF网元可以分配NEF参考标识。
可选地，NEF网元可以根据运营商的策略，确定应用服务器发送的监控请求是否合法，如果不合法，则向SCS/AS发送响应消息，该响应消息可包括拒绝原因等信息。
S303，NEF网元向UDM网元发送监控请求，该监控请求可包括：第一时间信息和/或第二时间信息。可选的，该监控请求还可包括应用服务器的标识信息和/或终端设备的标识信息，终端设备的标识信息可以是终端设备的外部标识，或者永久设备标识等。可选的，该监控请求还可包括应用的标识信息。可选的，该监控请求还可包括NEF相关信息，如NEF参考标识。可选的，该监控请求还可包括监控事件类型，本申请中的该监控事件类型就是监控终端设备的连接状态的事件类型。
可选地，或者，NEF网元向PCF网元发送消息，消息可以包括：第一时间信息和/或第二时间信息，进一步地，还可以包含有终端设备的标识信息和/或服务器的标识信息等。当PCF接收到第一时间信息和/或第二时间信息后，可以将该信息作为用户路由选择策略(user routing selectionpolicy,URSP)信息发送到终端设备，向终端设备发达URSP信息的过程同于现有技术，在此不详述。
S304，UDM网元在接收到NEF网元发送的监控请求后，可进行UDM处理。
UDM处理可包括但不限于：UDM网元根据运营商的策略检查该监控请求中的参数是否合法等，以及根据终端设备的标识信息确定终端设备对应的AMF。此外，UDM处理还可包括：UDM网元根据终端设备的外部标识确定终端设备的网内标识，如签约永久标识。
S305，UDM网元向AMF网元发送消息，该消息可包括第一时间信息和/或第二时间信息。这里，该消息可用于指示终端设备请求RAN根据第一时间信息和/或第二时间信息设置终端设备的连接态。仅作为一种示例，该消息可以是插入签约数据的消息。
可选的，该消息还可包括应用服务器的标识信息、终端设备的标识信息，终端设备的标识信息可以是终端设备的外部标识，或者永久设备标识等。可选的，该消息还可包括应用的标识信息。可选的，该消息还可包括NEF相关信息，如NEF参考标识。可选的，该消息还可包括监控事件类型，本申请中的该监控事件类型就是监控终端设备的连接状态的事件类型。
S306，AMF网元向终端设备发送消息，该消息可包括第一时间信息和/或第二时间信息。这里，该消息可用于指示终端设备请求RAN根据第一时间信息和/或第二时间信息设置终端设备的连接态。仅作为一种示例，该消息可以是插入签约数据的消息。
可选地，AMF可以根据应用的标识信息确定第三方应用对应的接入技术，如果是3GPP接入技术，则将第一时间信息和/或第二时间信息通知给终端设备。关于如何判断第三方应用对应的接入技术，本申请不作不限制。
应理解的，S306中的消息和S305中的消息是不同的消息，二者在信令实现上是不同。
(2)第二阶段：终端设备请求接入网设备设置终端设备的连接态。具体可包括：
S307，终端设备向接入网设备发送请求消息，用于请求接入网设备设置终端设备的连接态。该请求消息可包括第一时间信息和/或第二时间信息。可选的，该消息还可包括应用的标识信息。可选的，该消息还可包括监控事件类型，本申请中的该监控事件类型就是监控终端设备的连接状态的事件类型。
S308，接入网设备可以根据第一时间信息设置终端设备处于RRC CONNECTED状态的时长，和/或，接入网设备可以根据第二时间信息设置终端设备处于RRC INACTIVE状 态的时长。
举例说明，假设第一时间信息是指最大响应时间10ms，那么，接入网设备可以设置终端设备处于RRC CONNECTED状态的时长为大于或等于10ms。这样，可以确保终端设备保持可达性，便于应用服务器向终端设备持续传输应用数据包。
又举例说明，假设第二时间信息是指最大延迟时间5ms，那么，接入网设备可以设置终端设备处于RRC INACTIVE状态的时长为小于或等于5ms。这样，可以确保终端设备及时可达，便于应用服务器向终端设备持续传输应用数据包。可选的，接入网设备可以根据该最大延时时间设置周期性RAN通知区域更新定时器，来设置终端设备处于RRC INACTIVE状态的时长。
从图4可以看出，实施例二中，上述来自应用服务器的请求消息所对应的一系列请求消息可包括：S301中被发送的监控请求、S303中被发送的监控请求、S305中被发送的消息、S306中被发送的消息、S307中被发送的请求消息。不限于S301-S307所示，上述来自应用服务器的请求消息所对应的一系列请求消息还可以实施为其他信令，本申请对此不作限制。
实施例二也可以参考实施例一进行相同扩展，具体可参考实施例一的相关扩展一和实施例一的相关扩展二，这里不再赘述。
另外，本申请还提供了一种能力开放方法，可缓存应用数据包，尤其是在终端设备不可达时。如图5所示，该方法可包括：
S401-S410，核心网设备获取来自应用服务器的请求消息。该请求消息可包括终端设备的标识信息、数据量信息。
S411或S412，核心网设备根据该数据量信息缓存应用服务器向终端设备发送的数据包。
这里，来自应用服务器的请求消息是指从应用服务器发起，经历多个核心网网元，最后到达用于应用数据包缓存的核心网网元的一系列请求消息，这一系列请求消息共同用于请求缓存应用数据包。
本申请中，用于应用数据包缓存的核心网网元可包括：应用服务器的数据网络传输接入点标识(Data Network Access Identifier，DNAI)对应的UPF网元，或者应用服务器对应的本地数据网络(Local Area Data Network，LADN)的数据网络名称(Data Network Name，DNN)对应的UPF网元，或者，终端设备对应的SMF网元。
可选的，如S411所示，UPF网元可以根据该数据量信息缓存应用服务器向终端设备发送的数据包。可选的，如S412所示，终端设备对应的SMF可以根据该数据量信息缓存应用服务器向终端设备发送的数据包。
如图5所示，核心网设备获取来自应用服务器的请求消息的过程可包括：
S401，应用服务器向NEF网元发送监控请求，该监控请求可包括：数据量信息和终端设备的标识信息。终端设备的标识信息可以是终端设备的外部标识，或者永久设备标识，或者终端设备的IP地址信息等。
可选的，该监控请求还可包括应用的标识信息，应用的标识信息用于标识发起监控请求过程的第三方应用。可选的，UPF网元或SMF网元可以检测应用数据包的类型，判断该 应用数据包是不是应用的标识信息对应的数据包，如果是，则缓存该应用数据包。这样，第三方服务提供商可请求核心网设备缓存来自指定的第三应用的应用数据包，可实现核心网设备区别处理来自不同的第三方应用的应用数据包，仅仅缓存来自应用的标识信息指示的第三方应用的应用数据包，可更好的支撑第三方服务提供商的不同业务需求。
S402，NEF网元在接收到应用服务器发送的监控请求后，可进行NEF处理。
可选的，NEF网元可以确定应用服务器对应的数据网络接入点标识，该DNAI是指应用数据包传输接入点。具体地，该DNAI可以是指UPF的标识。如何确定DNAI，本专利不限制，比如，NEF网元向该应用标识标识的应用数据流的PDU会话所属的SM网元请求DNAI。
可选的，NEF网元可以根据应用的标识信息确定应用服务器所属的DNN，具体如何确定本申请不作限制，比如可以包括但不限于以下几种方式：
A.NEF网元向核心网设备(如SMF网元或者PCF网元、OSS网管设备等)请求应用服务器与DNN的对应关系。
B.核心网设备(如SMF网元或者PCF网元、OSS网管设备等)向NEF网元发送应用服务器与DNN的对应关系。
可选的，NEF网元可以根据终端设备的IP地址等信息确定该终端设备所在的PCF。
S403-S410，用于应用数据包缓存的核心网网元获取来自NEF网元的请求消息。
如图5所示，用于应用数据包缓存的核心网网元可以通过但不限于下面几种方式获取来自NEF网元的请求消息。
方式一：
S403，NEF网元向PCF网元发送监控请求，该监控请求可包括数据量信息和终端设备的标识信息。可选的，该监控请求还可包括应用服务器的DNAI，或者应用服务器对应的LADN的DNN。可选的，该监控请求还可包括应用的标识信息。
S404，PCF网元可以根据终端设备的标识信息确定终端设备对应的SMF网元，并向该SM网元F发送监控请求，该监控请求可包括数据量信息和终端设备的标识信息。可选的，该监控请求还可包括应用服务器的DNAI，或者应用服务器对应的LADN的DNN。可选的，该监控请求还可包括应用的标识信息。
S410，SMF网元可以根据应用服务器的DNAI确定相应的UPF网元，或者根据应用服务器对应的LADN的DNN确定相应的UPF网元。然后，SMF网元可以向相应的UPF网元发送监控请求，该监控请求可包括数据量信息和终端设备的标识信息。
方式二：
S406，NEF网元可以根据终端设备的标识信息确定终端设备对应的SMF网元，并向该SMF网元发送监控请求，该监控请求可包括数据量信息和终端设备的标识信息。可选的，该监控请求还可包括应用服务器的DNAI，或者应用服务器对应的LADN的DNN。可选的，该监控请求还可包括应用的标识信息。
S410，SMF网元可以根据应用服务器的DNAI确定相应的UPF网元，或者根据应用服务器对应的LADN的DNN确定相应的UPF网元。然后，SMF网元可以向相应的UPF网元发送监控请求，该监控请求可包括数据量信息和终端设备的标识信息。
方式三：
S408，NEF网元可以向AMF网元发送监控请求，该监控请求可包括数据量信息和终端设备的标识信息。可选的，该监控请求还可包括应用服务器的DNAI，或者应用服务器对应的LADN的DNN。可选的，该监控请求还可包括应用的标识信息。
需要说明的，NEF网元向AMF网元发送监控请求并不限制为NEF网元直接向AMF网元发送监控请求，也可以是NEF网元经其他网络设备向AMF网元发送监控请求。例如，NEF网元向UDM网元发送监控请求，然后UDM网元根据终端设备的标识信息确定相应的AMF网元，并向该相应的AMF网元发送监控请求，或者，UDM网元在确定出相应的AMF网元后，向NEF发送AMF的标识信息，然后NEF网元根据AMF网元的标识信息向AMF网元发送监控请求。示例仅仅用于解释本申请，不应构成限定。
S409，AMF网元可以根据终端设备的标识信息确定终端设备对应的SMF网元，并向该SMF网元发送监控请求，该监控请求可包括数据量信息和终端设备的标识信息。可选的，该监控请求还可包括应用服务器的DNAI，或者应用服务器对应的LADN的DNN。可选的，该监控请求还可包括应用的标识信息。
S410，SMF网元可以根据应用服务器的DNAI确定相应的UPF网元，或者根据应用服务器对应的LADN的DNN确定相应的UPF网元。然后，SMF网元可以向相应的UPF网元发送监控请求，该监控请求可包括数据量信息和终端设备的标识信息。
不限于上面三种方式，核心网设备还可以通过其他信令流程获取来自网络开放功能(NEF)的请求消息。
在一些可选的实施例中，UPF网元可以是图6中的上行分类器(uplink classifier，UL CL)网元。在图6所示的UL CL的网络架构中，DNAI可以是图6中的PDU会话锚点1(PDU session anchor 1)的标识，或者PDU会话锚点2(PDU session anchor 2)的标识，或者，是有UL CL功能的UPF网元的标识。
参考图7，图7示出了本申请的一些实施例提供的应用服务器200。如图7所示，应用服务器200可包括：一个或多个处理器201、存储器202、通信接口203。这些部件可通过总线204或者其他方式连接，图7以通过总线连接为例。其中：
通信接口203可用于应用服务器200与其他通信设备，例如核心网设备，进行通信。具体的，该核心网设备可以是图9所示的核心网设备400。具体的，通信接口203可以包括有线通信接口，例如广域网(Wide Area Network，WAN)接口、局域接入网(Local Access Network，LAN)接口等。不限于有线通信接口，在一些可能的实施例中，通信接口203还可包括无线通信接口，如无线局域网(Wireless Local Area Networks，WLAN)接口等。
存储器202与处理器201耦合，用于存储各种软件程序和/或多组指令。具体的，存储器202可包括高速随机存取的存储器，并且也可包括非易失性存储器，例如一个或多个磁盘存储设备、闪存设备或其他非易失性固态存储设备。存储器202可以存储操作系统(下述简称系统)，例如uCOS、VxWorks、RTLinux等嵌入式操作系统。存储器202还可以存储网络通信程序，该网络通信程序可用于与一个或多个附加设备，一个或多个终端设备，一个或多个网络设备进行通信。
在本申请的一些实施例中，存储器202可用于存储本申请的一个或多个实施例提供的能力开放方法在应用服务器200侧的实现程序。关于本申请的一个或多个实施例提供的能力开放方法的实现，请参考后续实施例。
处理器201可用于读取和执行计算机可读指令。具体的，处理器201可用于调用存储于存储器212中的程序，例如本申请的一个或多个实施例提供的能力开放方法在应用服务器200侧的实现程序，并执行该程序包含的指令。
可以理解的，应用服务器200可以是图1示出的通信系统100中的业务能力服务器/应用服务器10。图7所示的应用服务器200仅仅是本申请实施例的一种实现方式，实际应用中，应用服务器200还可以包括更多或更少的部件，这里不作限制。
参考图8，图8示出了本申请的一些实施例提供的接入网设备300。如图8所示，接入网设备300可包括：一个或多个处理器301、存储器302、通信接口303、发射器305、接收器306、耦合器307和天线308。这些部件可通过总线304或者其他方式连接，图8以通过总线连接为例。其中：
发射器305可用于对处理器301输出的信号进行发射处理，例如信号调制。接收器306可用于对天线308接收的信号进行接收处理。例如信号解调。在本申请的一些实施例中，发射器305和接收器306可看作一个无线调制解调器。在接入网设备300中，发射器305和接收器306的数量均可以是一个或者多个。
天线308可用于将传输线中的电磁能转换成自由空间中的电磁波，或者将自由空间中的电磁波转换成传输线中的电磁能。耦合器307可用于将移动通信号分成多路，分配给多个的接收器306。
存储器302与处理器301耦合，用于存储各种软件程序和/或多组指令。具体的，存储器302可包括高速随机存取的存储器，并且也可包括非易失性存储器，例如一个或多个磁盘存储设备、闪存设备或其他非易失性固态存储设备。存储器302可以存储操作系统(下述简称系统)，例如uCOS、VxWorks、RTLinux等嵌入式操作系统。存储器302还可以存储网络通信程序，该网络通信程序可用于与一个或多个附加设备，一个或多个终端设备，一个或多个网络设备进行通信。
处理器301可用于进行无线信道管理、实施呼叫和通信链路的建立和拆除，并为本控制区内的用户提供小区切换控制等。具体的，处理器301可包括：管理/通信模块(Administration Module/Communication Module，AM/CM)(用于话路交换和信息交换的中心)、基本模块(Basic Module，BM)(用于完成呼叫处理、信令处理、无线资源管理、无线链路的管理和电路维护功能)、码变换及子复用单元(Transcoder and SubMultiplexer，TCSM)(用于完成复用解复用及码变换功能)等等。
本申请实施例中，处理器301可用于读取和执行计算机可读指令。具体的，处理器301可用于调用存储于存储器302中的程序，例如本申请的一个或多个实施例提供的能力开放方法在接入网设备300侧的实现程序，并执行该程序包含的指令。
可以理解的，接入网设备300可以是图1示出的通信系统100中的接入网设备((R)AN)13，可实施为基站收发台，无线收发器，一个基本服务集(BSS)，一个扩展服务集(ESS)， NodeB，eNodeB，接入点或TRP等等。图8所示的接入网设备300仅仅是本申请实施例的一种实现方式，实际应用中，接入网设备300还可以包括更多或更少的部件，这里不作限制。
参考图9，图9示出了本申请的一些实施例提供的核心网设备400。如图9所示，核心网设备400可包括：一个或多个处理器401、存储器403、通信接口405。这些部件可通过总线404或者其他方式连接，图9以通过总线连接为例。其中：
通信接口405可用于核心网设备400与其他通信设备，例如接入网设备、应用服务器，进行通信。具体的，该应用服务器可以是图7所示的应用服务器200，该接入网设备可以是图8所示的接入网设备300。具体的，通信接口405可以包括有线通信接口，例如广域网(WAN)接口、局域接入网(LAN)接口等。不限于有线通信接口，在一些可能的实施例中，通信接口405还可包括无线通信接口，如无线局域网(WLAN)接口等。
存储器403与处理器401耦合，用于存储各种软件程序和/或多组指令。具体的，存储器403可包括高速随机存取的存储器，并且也可包括非易失性存储器，例如一个或多个磁盘存储设备、闪存设备或其他非易失性固态存储设备。存储器403可以存储操作系统(下述简称系统)，例如uCOS、VxWorks、RTLinux等嵌入式操作系统。存储器403还可以存储网络通信程序，该网络通信程序可用于与一个或多个附加设备，一个或多个终端设备，一个或多个网络设备进行通信。
在本申请的一些实施例中，存储器403可用于存储本申请的一个或多个实施例提供的能力开放方法在核心网设备400侧的实现程序。关于本申请的一个或多个实施例提供的能力开放方法的实现，请参考后续实施例。
处理器401可用于读取和执行计算机可读指令。具体的，处理器401可用于调用存储于存储器405中的程序，例如本申请的一个或多个实施例提供的能力开放方法在核心网设备400侧的实现程序，并执行该程序包含的指令。
可以理解的，核心网设备400可以是图1示出的通信系统100中的核心网设备，可实施为NEF 11、AMF19、SMF18、PCF17、UDM20、UPF 14等等。图9所示的核心网设备400仅仅是本申请实施例的一种实现方式，实际应用中，核心网设备400还可以包括更多或更少的部件，这里不作限制。
参考图10，图10示出了本申请提供一种通信系统及通信装置。通信系统30可包括如下通信装置：应用服务器700、核心网设备600、接入网设备500和终端设备800。通信系统30以及其中的通信装置可以实施图2-图4分别对应的实施例描述的能力开放方法，即核心网设备600(包括但不限于以下功能：NEF、UDM、PCF、AMF、SMF、UPF等)和接入网设备500所在的移动通信网络开放的网络能力可包括：设置终端设备处于RRC INACTIVE状态的时长；和/或，设置MICO模式下的终端设备的状态。下面展开描述。
如图10所示，应用服务器700可包括：接收单元701和发送单元703。其中：
接收单元701可用于向接入网设备500发送请求消息，请求消息包括第一时间信息和/或第二时间信息。
发送单元703可用于接收来自接入网设备500的请求消息的响应消息。
本申请中，第一时间信息也可以是指用于设置数据包的传输时长的信息，例如最大响应时间信息。第二时间信息也可以是指用于设置数据包的传输时延的信息，例如最大延迟时间信息。
在一些实施例中，第一时间信息可用于设置终端设备800处于连接态的第一状态的时间，第二时间信息可用于设置终端设备800处于连接态的第二状态的时间。本申请中，连接态的第一状态可包括但不限于激活状态，如RRC CONNECTED状态。连接态的第二状态可包括但不限于非激活状态，如RRC INACTIVE状态。
在一些实施例中，第一时间信息可用于设置终端设备800在仅移动发起连接MICO模式下处于连接态的时间，第二时间信息可用于设置终端设备800在MICO模式下在空闲态后发起上行信令或者数据的时间。
在一些实施例中，请求消息还可以包括应用的标识信息，连接态可具体为终端设备800对应应用的连接态。
在一些实施例中，请求消息还可以包括终端设备800的标识信息和/或应用服务器的的标识信息。
可以理解的，关于应用服务器700的各个功能单元的具体实现可参考图2-图4分别对应的方法实施例，这里不再赘述。
如图10所示，接入网设备500可包括：接收单元501和处理单元503。其中：
接收单元501，用于获取来自应用服务器700的请求消息，请求消息包括第一时间信息和/或第二时间信息。
处理单元503，用于根据第一时间信息和/或第二时间信息设置终端设备800的连接态。
这里，来自应用服务器700的请求消息是指从应用服务器700发起，经历核心网设备600，最后到达接入网设备的一系列请求消息，这一系列请求消息共同用于请求接入网设备设置终端设备800的连接态。这里，请求消息经历的核心网网元具体可包括但不限于：NEF、UDM、AMF。具体的，接收单元501可以具体用于经接入管理网元(AMF)接收来自应用服务器700的请求消息或者经终端设备800接收来自应用服务器700的请求消息，具体可参考图5或图4实施例，这里不再赘述。
本申请中，第一时间信息也可以是指用于设置数据包的传输时长的信息，例如最大响应时间信息。第二时间信息也可以是指用于设置数据包的传输时延的信息，例如最大延迟时间信息。
在一些实施例中，第一时间信息可用于设置终端设备800处于连接态的第一状态的时间，第二时间信息可用于设置终端设备800处于连接态的第二状态的时间。本申请中，连接态的第一状态可包括但不限于激活状态，如RRC CONNECTED状态。连接态的第二状态可包括但不限于非激活状态，如RRC INACTIVE状态。相应的，处理单元503可具体用于根据第一时间信息设置终端设备800处于连接态的第一状态的时间，和/或，根据第二时间信息设置终端设备800处于连接态的第二状态的时间。
在一些实施例中，第一时间信息可用于设置终端设备800在仅移动发起连接MICO模式下处于连接态的时间，第二时间信息可用于设置终端设备800在MICO模式下在空闲态 后发起上行信令或者数据的时间。相应的，处理单元503可具体用于根据第一时间信息设置终端设备800在仅移动发起连接MICO模式下处于连接态的时间，和/或，根据第二时间信息设置终端设备800在MICO模式下在空闲态后发起上行信令或者数据的时间。
在一些实施例中，请求消息还可以包括应用的标识信息，连接态可具体为终端设备800对应应用的连接态。
在一些实施例中，请求消息还可以包括终端设备800的标识信息和/或应用服务器700的的标识信息。
可以理解的，关于接入网设备500的各个功能单元的具体实现可参考图2-图4分别对应的方法实施例，这里不再赘述。
可以看出，通过实施图10所示的通信系统30以及其中的通信装置，移动通信运营商开放的网络能力可包括：设置终端设备处于RRC INACTIVE状态的时长，和/或，设置MICO模式下的终端设备的状态。通过开放这种网络能力，第三方服务提供商可以向网络侧请求设置终端设备处于RRC INACTIVE状态的时长，和/或，设置MICO模式下的终端设备的状态，可便于第三方服务提供商向终端设备传输下行数据包。
应理解的，图10所示的通信系统30可以实施成图1所示的通信系统100。其中，应用服务器700可以是SCS/AS 100。核心网设备600可以包括网络开放功能网元(NEF)11、接入和移动性管理功能网元(AMF)19、会话管理功能网元(SMF)18、用户面功能网元(UPF)14、数据网络(DN)15、应用功能网元(AF)16、策略控制功能网元(PCF)17、统一数据管理网元(UDM)20和鉴权服务器功能网元(AUSF)21等。接入网设备500可以是(R)AN13。终端设备800可以是UE 12。
参考图11，图11示出了本申请提供另一种通信系统及通信装置。通信系统40可包括如下通信装置：应用服务器110、核心网设备120、接入网设备130和终端设备140。通信系统40以及其中的通信装置可以实施图5实施例描述的能力开放方法。下面展开描述。
如图11所示，应用服务器110可包括：发送单元111和接收单元113。其中：
发送单元111，可用于向核心网设备120发送请求消息，请求消息包括终端设备的标识信息、数据量信息。
接收单元113，可用于接收来自核心网设备120的请求消息的响应消息。
在一些实施例中，请求消息还可包括应用的标识信息，数据量信息可以具体为应用对应的待缓存的数据量信息。
在一些实施例中，核心网设备120可以为应用服务器的数据包传输接入点标识对应的用户面功能网元UPF，或者应用服务器对应的本地数据网络LADN的数据网络名称对应的UPF，或者终端设备对应的会话管理网元SMF。
可以理解的，关于应用服务器110的各个功能单元的具体实现可参考图8实施例，这里不再赘述。
如图11所示，核心网设备120可包括：接收单元121和处理单元123。其中：
接收单元121，可用于获取来自应用服务器110的请求消息请求消息包括终端设备的标识信息、数据量信息。
处理单元123，可用于根据数据量信息缓存应用服务器110向终端设备发送的数据包。
这里，来自应用服务器110的请求消息是指从应用服务器110发起，经历多个核心网网元，最后到达用于应用数据包缓存的核心网网元的一系列请求消息，这一系列请求消息共同用于请求缓存应用数据包。
本申请中，用于应用数据包缓存的核心网网元可包括：应用服务器110的数据网络传输接入点标识(Data Network Access Identifier，DNAI)对应的UPF，或者应用服务器110对应的本地数据网络(Local Area Data Network，LADN)的数据网络名称(Data Network Name，DNN)对应的UPF，或者，终端设备对应的SMF。
可选的，处理单元123可以具体为UPF中的处理单元，UPF可以根据该数据量信息缓存应用服务器110向终端设备发送的数据包。可选的，处理单元123可以具体为终端设备对应的SMF中的处理单元，终端设备对应的SMF可以根据该数据量信息缓存应用服务器110向终端设备发送的数据包。
在一些实施例中，请求消息还包括应用的标识信息，数据量信息为应用对应的待缓存的数据量信息。进一步的，处理单元123可具体用于检测应用服务器110向终端设备发送的数据包的类型，判断数据包是不是应用对应的数据包，若是，则缓存数据包。这样可实现核心网设备120区别处理来自不同的第三方应用的应用数据包，仅仅缓存来自应用的标识信息指示的第三方应用的应用数据包，可更好的支撑第三方服务提供商的不同业务需求。
可以理解的，关于核心网设备120的各个功能单元的具体实现可参考图5对应的方法实施例，这里不再赘述。
可以看出，通过实施图11所示的通信系统40以及其中的通信装置，移动通信运营商开放的网络能力可包括：缓存应用数据包，尤其是在终端设备不可达时。
应理解的，图11所示的通信系统40可以实施成图1所示的通信系统100。其中，应用服务器700可以是SCS/AS 100。核心网设备600可以包括网络开放功能网元(NEF)11、接入和移动性管理功能网元(AMF)19、会话管理功能网元(SMF)18、用户面功能网元(UPF)14、数据网络(DN)15、应用功能网元(AF)16、策略控制功能网元(PCF)17、统一数据管理网元(UDM)20和鉴权服务器功能网元(AUSF)21等。接入网设备500可以是(R)AN13。终端设备800可以是UE 12。
综上，实施本申请提供的技术方案，可实现移动通信网络向第三方业务提供商开放更多的网络能力，更好的支撑第三方业务提供商的业务需求。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，该流程可以由计算机程序来指令相关的硬件完成，该程序可存储于计算机可读取存储介质中，该程序在执行时，可包括如上述各方法实施例的流程。而前述的存储介质包括：ROM或随机存储记忆体RAM、磁碟或者光盘等各种可存储程序代码的介质。

Claims (26)

  1. 一种网络能力开放方法，其特征在于，包括：
    接入网设备获取来自应用服务器的请求消息，所述请求消息包括第一时间信息和/或第二时间信息，所述第一时间信息用于设置终端设备处于连接态的第一状态的时间，所述第二时间信息用于设置所述终端设备处于连接态的第二状态的时间；
    所述接入网设备根据所述第一时间信息和/或所述第二时间信息设置所述终端设备的连接态。
  2. 如权利要求1所述的方法，其特征在于，所述接入网设备获取来自应用服务器的请求消息，包括：
    所述接入网设备经接入管理网元接收来自所述应用服务器的请求消息或者所述接入网设备经所述终端设备接收来自所述应用服务器的请求消息。
  3. 一种网络能力开放方法，其特征在于，包括：
    应用服务器向接入网设备发送请求消息，所述请求消息包括第一时间信息和/或第二时间信息，所述第一时间信息用于设置终端设备处于连接态的第一状态的时间，所述第二时间信息用于设置所述终端设备处于连接态的第二状态的时间；
    所述应用服务器接收来自所述接入网设备的所述请求消息的响应消息。
  4. 如权利要求1-3中任意一项所述的方法，其特征在于，所述连接态的第一状态为激活状态，所述连接态的第二状态为非激活状态。
  5. 如权利要求1-4中任意一项所述的方法，其特征在于，所述请求消息还包括应用的标识信息，所述连接态为所述终端设备对应所述应用的连接态。
  6. 一种网络能力开放方法，其特征在于，包括：
    接入网设备获取来自应用服务器的请求消息，所述请求消息包括第一时间信息和/或第二时间信息，所述第一时间信息用于设置终端设备在仅移动发起连接MICO模式下处于连接态的时间，所述第二时间信息用于设置所述终端设备在MICO模式下在空闲态后发起上行信令或者数据的时间；
    所述接入网设备根据所述第一时间信息和/或所述第二时间信息设置所述终端设备的在MICO模式下的状态。
  7. 如权利要求6所述的方法，其特征在于，所述接入网设备获取来自应用服务器的请求消息，包括：
    所述接入网设备经接入管理网元接收来自所述应用服务器的请求消息，或者所述接入网设备经所述终端设备接收来自所述应用服务器的请求消息。
  8. 一种网络能力开放方法，其特征在于，包括：
    应用服务器向接入网设备发送请求消息，所述请求消息包括第一时间信息和/或第二时间信息，所述第一时间信息用于设置终端设备在仅移动发起连接MICO模式下处于连接态的时间，所述第二时间信息用于设置所述终端设备在MICO模式下在空闲态后发起上行信令或者数据的时间；
    所述应用服务器接收来自所述接入网设备的所述请求消息的响应消息。
  9. 如权利要求6-8中任意一项所述的方法，其特征在于，所述请求消息还包括应用的标识信息，所述连接态为所述终端设备在MICO模式下对应所述应用的连接态。
  10. 如权利要求1-9中任意一项所述的方法，其特征在于，所述连接态为无线资源控制连接态。
  11. 如权利要求1-10中任意一项所述的方法，其特征在于，所述请求消息还包括所述终端设备的标识信息和/或所述应用服务器的的标识信息。
  12. 一种通信装置，其特征在于，包括：
    接收单元，用于获取来自应用服务器的请求消息，所述请求消息包括第一时间信息和/或第二时间信息，所述第一时间信息用于设置终端设备处于连接态的第一状态的时间，所述第二时间信息用于设置所述终端设备处于连接态的第二状态的时间；
    处理单元，用于根据所述第一时间信息和/或所述第二时间信息设置所述终端设备的连接态。
  13. 如权利要求12所述的通信装置，其特征在于，所述接收单元具体用于经接入管理网元接收来自所述应用服务器的请求消息或者经所述终端设备接收来自所述应用服务器的请求消息。
  14. 一种通信装置，其特征在于，包括：
    发送单元，用于向接入网设备发送请求消息，所述请求消息包括第一时间信息和/或第二时间信息，所述第一时间信息用于设置终端设备处于连接态的第一状态的时间，所述第二时间信息用于设置所述终端设备处于连接态的第二状态的时间；
    接收单元，用于接收来自所述接入网设备的所述请求消息的响应消息。
  15. 如权利要求12-14中任一项所述的通信装置，其特征在于，所述连接态的第一状态为激活状态，所述连接态的第二状态为非激活状态。
  16. 如权利要求12-15中任一项所述的通信装置，其特征在于，所述请求消息还包括应用的标识信息，所述连接态为所述终端设备对应所述应用的连接态。
  17. 一种通信装置，其特征在于，包括：
    接收单元，用于获取来自应用服务器的请求消息，所述请求消息包括第一时间信息和/或第二时间信息，所述第一时间信息用于设置终端设备在仅移动发起连接MICO模式下处于连接态的时间，所述第二时间信息用于设置所述终端设备在MICO模式下在空闲态后发起上行信令或者数据的时间；
    处理单元，根据所述第一时间信息和/或所述第二时间信息设置所述终端设备的在MICO模式下的状态。
  18. 如权利要求17所述的通信装置，其特征在于，所述接收单元具体用于经接入管理网元接收来自所述应用服务器的请求消息，或者经所述终端设备接收来自所述应用服务器的请求消息。
  19. 一种通信装置，其特征在于，包括：
    发送单元，用于向接入网设备发送请求消息，所述请求消息包括第一时间信息和/或第二时间信息，所述第一时间信息用于设置终端设备在仅移动发起连接MICO模式下处于连接态的时间，所述第二时间信息用于设置所述终端设备在MICO模式下在空闲态后发起上 行信令或者数据的时间；
    接收单元，用于接收来自所述接入网设备的所述请求消息的响应消息。
  20. 如权利要求17-19中任一项所述的通信装置，其特征在于，所述请求消息还包括应用的标识信息，所述连接态为所述终端设备在MICO模式下对应所述应用的连接态。
  21. 如权利要求14-20中任一项所述的通信装置，其特征在于，所述连接态为无线资源控制连接态。
  22. 如权利要求14-21中任一项所述的通信装置，其特征在于，所述请求消息还包括所述终端设备的标识信息和/或所述应用服务器的的标识信息。
  23. 一种通信系统，其特征在于，包括：接入网设备和应用服务器，其中：
    所述接入网设备为权利要求12-13中任一项所述的通信装置；
    所述应用服务器为权利要求14-16中任一项所述的通信装置。
  24. 一种通信系统，其特征在于，包括：接入网设备和应用服务器，其中：
    所述接入网设备为权利要求17-18中任一项所述的通信装置；
    所述应用服务器为权利要求19-22中任一项所述的通信装置。
  25. 一种计算机可读存储介质，其特征在于，包括：所述计算机可读存储介质上存储有指令，当所述指令在计算机上运行时，所述计算机执行权利要求1-11中任一项所述的方法。
  26. 一种计算机程序产品，其特征在于，包括：当所述计算机程序产品在计算机上运行时，所述计算机执行权利要求1-11中任一项所述的方法。
PCT/CN2019/084741 2018-04-28 2019-04-28 能力开放方法、相关装置及系统 WO2019206322A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP19792517.5A EP3761711A4 (en) 2018-04-28 2019-04-28 CAPABILITY OPENING PROCEDURES, ASSOCIATED DEVICE AND SYSTEM
US17/029,577 US20210007172A1 (en) 2018-04-28 2020-09-23 Capability exposure method, related apparatus, and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810399673.7 2018-04-28
CN201810399673.7A CN110418395B (zh) 2018-04-28 2018-04-28 能力开放方法、相关装置、系统及介质

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/029,577 Continuation US20210007172A1 (en) 2018-04-28 2020-09-23 Capability exposure method, related apparatus, and system

Publications (1)

Publication Number Publication Date
WO2019206322A1 true WO2019206322A1 (zh) 2019-10-31

Family

ID=68293467

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/084741 WO2019206322A1 (zh) 2018-04-28 2019-04-28 能力开放方法、相关装置及系统

Country Status (4)

Country Link
US (1) US20210007172A1 (zh)
EP (1) EP3761711A4 (zh)
CN (1) CN110418395B (zh)
WO (1) WO2019206322A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4191972A4 (en) * 2020-08-13 2023-09-27 Huawei Technologies Co., Ltd. NETWORK CAPACITY OPENING METHOD, APPARATUS AND SYSTEM

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111356157A (zh) * 2020-03-15 2020-06-30 腾讯科技（深圳）有限公司 实现网络能力开放的方法及相关设备
US20220368765A1 (en) * 2021-05-13 2022-11-17 Agora Lab, Inc. Universal Transport Framework For Heterogeneous Data Streams
CN114363202A (zh) * 2021-12-30 2022-04-15 中国电信股份有限公司 终端接入状态监测方法及装置、系统、电子设备、介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101022653A (zh) * 2006-02-15 2007-08-22 中兴通讯股份有限公司 移动性管理状态转换的控制方法
WO2014117854A1 (en) * 2013-02-01 2014-08-07 Nokia Solutions And Networks Oy Handling a radio link failure in communications
CN107534833A (zh) * 2015-05-15 2018-01-02 三星电子株式会社 用户设备监视配置方法及装置

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101079878A (zh) * 2006-05-22 2007-11-28 华为技术有限公司 一种用于网络路由优化的方法及设备
US8923873B2 (en) * 2011-11-14 2014-12-30 T-Mobile Usa, Inc. Device triggered channel selection
JP2016536882A (ja) * 2013-10-28 2016-11-24 華為技術有限公司Ｈｕａｗｅｉ Ｔｅｃｈｎｏｌｏｇｉｅｓ Ｃｏ．，Ｌｔｄ． Ｒｒｃステータス制御方法、装置およびデバイス
CN106027631B (zh) * 2016-05-12 2021-03-02 腾讯科技（深圳）有限公司 一种数据传输方法及装置
CN105898894B (zh) * 2016-05-13 2021-08-20 华为技术有限公司 Rrc状态的控制方法和装置
KR102216428B1 (ko) * 2016-08-16 2021-02-17 콘비다 와이어리스, 엘엘씨 Ｕｅ를 각성상태로 유지하기

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101022653A (zh) * 2006-02-15 2007-08-22 中兴通讯股份有限公司 移动性管理状态转换的控制方法
WO2014117854A1 (en) * 2013-02-01 2014-08-07 Nokia Solutions And Networks Oy Handling a radio link failure in communications
CN107534833A (zh) * 2015-05-15 2018-01-02 三星电子株式会社 用户设备监视配置方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3761711A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4191972A4 (en) * 2020-08-13 2023-09-27 Huawei Technologies Co., Ltd. NETWORK CAPACITY OPENING METHOD, APPARATUS AND SYSTEM

Also Published As

Publication number Publication date
CN110418395A (zh) 2019-11-05
US20210007172A1 (en) 2021-01-07
EP3761711A4 (en) 2021-04-28
EP3761711A1 (en) 2021-01-06
CN110418395B (zh) 2021-07-16

Similar Documents

Publication Publication Date Title
US11246172B2 (en) Method for selecting session and service continuity mode in wireless communication system and device therefor
US11678268B2 (en) Method and apparatus for operating protocol layer of terminal in inactive mode in next-generation mobile communication system
JP7433488B2 (ja) 無線アクセスネットワーク通知エリア（ｒｎａ）更新の拒否時の構成を処理するための方法および装置
US20190021064A1 (en) Method for managing registration in wireless communication system and device for same
WO2019206322A1 (zh) 能力开放方法、相关装置及系统
US20220060935A1 (en) Communications Method and Apparatus
WO2019196643A1 (zh) 通信的方法和通信装置
EP3925182A1 (en) Methods and apparatuses for alternative data over non-access stratum, donas, data delivery in a roaming scenario
US11968565B2 (en) User plane information reporting method and apparatus
CN114143871B (zh) 网络连接方法、网络去连接方法及通信装置
CN113873478B (zh) 通信方法及装置
US20230112588A1 (en) Communication method and related device
EP4037373A1 (en) Communication method and device
CN112534957B (zh) 处于无线电资源控制层处的不活动模式中的用户设备的公共陆地移动网络选择
TWI792415B (zh) Ue和網路之間的多存取pdu會話狀態同步
KR20220150951A (ko) 업링크 및 사이드링크 송신들의 우선순위화
WO2022199451A1 (zh) 会话切换的方法和装置
US20240107417A1 (en) Communication method and apparatus
US20230388863A1 (en) Communication method and apparatus
KR20220045181A (ko) 페이징 방법 및 기기
US20230132454A1 (en) Method and apparatus for supporting edge computing service for roaming ue in wireless communication system
US11985652B2 (en) P-BSR enhancements for IAB networks to improve E2E latency
WO2023202503A1 (zh) 通信方法和装置
CN114642079B (zh) 通信方法及装置
US20240155325A1 (en) Information obtaining method and apparatus, and system

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: 19792517

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019792517

Country of ref document: EP

Effective date: 20200928

NENP Non-entry into the national phase

Ref country code: DE