Slice event subscription reporting method, device and storage medium based on access type
Through the subscription request mechanism of AF and NEF to NSACF, the network slice event report associated with access type is obtained, which solves the problem that access type affects network status in the communication system and improves the accuracy of user experience and resource configuration.
Patent Information
- Application Number
- CN202280000179.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-01-14
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2042-01-14
AI Technical Summary
The impact of the number of users of different access types and the number of activated PDU sessions on network slice status information in existing communication systems is difficult to accurately locate, resulting in the inability to meet the needs of operational services and the user's business experience is poor.
Through AF, NEF sends a subscription request to NEF, and NEF sends a subscription request to NSACF to obtain the network slice event report associated with the access type, realizing accurate monitoring of network status by network devices and resource configuration.
This enables network equipment to accurately locate and meet the operator's business needs, improve user experience, and ensure the effective configuration and business execution of network resources.
Smart Images

Figure CN117044248B_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to but is not limited to the field of communication technology, and in particular to a method, device and storage medium for slice event subscription reporting based on access type. Background Art
[0002] In a communication system, a network slice can provide complete network functions, such as radio access network functions, core network functions, and Internet Protocol Multimedia System (IMS) functions. A network can support one or more network slices. A network slice can provide different committed services and be dedicated to user equipment (UE), such as the number of registered UEs or activated protocol data unit (PDU) sessions that can be associated with at least one access type in a network slice.
[0003] However, the billing modes and rates of different access types are different. The number of users of different access types and / or the number of activated PDU sessions have an increasingly significant impact on the network slice status information. For example, at different times or different service types, the number of registered UEs and the number of established PDUs of different access types vary significantly. However, it is often impossible to accurately locate and meet the needs of operating services, and it is impossible to configure resources and execute related services accordingly based on the network status, resulting in a poor user service experience. Summary of the invention
[0004] The embodiments of the present disclosure provide a method, apparatus, communication device and storage medium for slice event subscription reporting based on access type.
[0005] According to a first aspect of the present disclosure, a slice event subscription reporting method based on access type is provided, which is performed by an AF and includes:
[0006] A first subscription request is sent to NEF to request an event report of a network slice associated with an access type; wherein the first subscription request includes access type information indicating the access type, and the first subscription request is used to instruct NEF to send a second subscription request to NSACF to subscribe to the event report requested in the first subscription request.
[0007] According to a second aspect of the present disclosure, a slice event subscription reporting method based on access type is provided, which is executed by NEF and includes:
[0008] receiving a first subscription request sent by the AF, wherein the first subscription request is used to request an event report of a network slice associated with an access type; wherein the first subscription request includes access type information indicating the access type;
[0009] A second subscription request is sent to the NSACF, where the second subscription request is used to subscribe to the event report requested by the first subscription request.
[0010] According to a third aspect of the present disclosure, a slice event subscription reporting method based on access type is provided, which is executed by NSACF and includes:
[0011] Receiving a second subscription request sent by the NEF; wherein the second subscription request is sent by the NEF based on the received first subscription request instruction; wherein the first subscription request is used to request an event report of a network slice associated with an access type, wherein the first subscription request includes access type information indicating the access type;
[0012] The event report requested by the first subscription request subscribed by the second subscription request is sent to the NEF.
[0013] According to a fourth aspect of the present disclosure, a slice event subscription reporting device based on access type is provided, which is applied to AF, including:
[0014] The first sending module is configured to send a first subscription request to NEF to request an event report of a network slice associated with an access type; wherein the first subscription request includes access type information indicating the access type, and the first subscription request is used to instruct NEF to send a second subscription request to NSACF to subscribe to the event report requested in the first subscription request.
[0015] According to a fifth aspect of the present disclosure, a slice event subscription reporting device based on access type is provided, which is applied to NEF, including:
[0016] A second receiving module is configured to receive a first subscription request sent by the application function AF, wherein the first subscription request is used to request an event report of a network slice associated with an access type; wherein the first subscription request includes access type information indicating the access type;
[0017] The second sending module is configured to send a second subscription request to the NSACF, wherein the second subscription request is used to subscribe to the event report requested by the first subscription request.
[0018] According to a sixth aspect of the present disclosure, a slice event subscription reporting device based on access type is provided, which is applied to NSACF, including:
[0019] A third receiving module is configured to receive a second subscription request sent by the NEF; wherein the second subscription request is sent by the NEF based on the received first subscription request instruction; wherein the first subscription request is used to request an event report of a network slice associated with an access type, wherein the first subscription request includes access type information indicating the access type;
[0020] The third sending module is configured to send, to the NEF, the event report requested by the first subscription request subscribed by the second subscription request.
[0021] According to a seventh aspect of the present disclosure, a communication device is provided, the communication device comprising:
[0022] processor;
[0023] a memory for storing processor-executable instructions;
[0024] Among them, the processor is configured to: when running executable instructions, implement the slice event subscription reporting method based on access type of any embodiment of the present disclosure.
[0025] According to an eighth aspect of the present disclosure, a computer storage medium is provided, which stores a computer executable program. When the executable program is executed by a processor, the access type-based slice event subscription reporting method of any embodiment of the present disclosure is implemented.
[0026] The technical solution provided by the embodiments of the present disclosure may have the following beneficial effects:
[0027] In the disclosed embodiment, a first subscription request may be sent by AF to NEF to request an event report of a network slice associated with an access type; the first subscription request includes access type information indicating the access type, and the first subscription request is used to instruct NEF to send a second subscription request to NSACF to subscribe to the event report requested by the first subscription request. In this way, a network device (such as AF or NEF, etc.) may obtain an event report of a network slice associated with an access type sent by at least one NSACF based on a subscription request (first subscription request or second subscription request), that is, the network device may obtain the network status of the network slice; in this way, the network device may accurately locate and meet the needs of the operator's services, and may also configure resources and execute services accordingly according to the network status to improve the user experience satisfaction.
[0028] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS
[0029] Figure 1 The schematic diagram is a structural diagram of a wireless communication system.
[0030] Figure 2 It is a flowchart of a slice event subscription reporting method based on access type according to an exemplary embodiment.
[0031] Figure 3It is a flowchart of a slice event subscription reporting method based on access type according to an exemplary embodiment.
[0032] Figure 4 It is a flowchart of a slice event subscription reporting method based on access type according to an exemplary embodiment.
[0033] Figure 5 It is a flowchart of a slice event subscription reporting method based on access type according to an exemplary embodiment.
[0034] Figure 6 It is a flowchart of a slice event subscription reporting method based on access type according to an exemplary embodiment.
[0035] Figure 7 It is a flowchart of a slice event subscription reporting method based on access type according to an exemplary embodiment.
[0036] Figure 8 It is a flowchart of a slice event subscription reporting method based on access type according to an exemplary embodiment.
[0037] Fig. 9 It is a flowchart of a slice event subscription reporting method based on access type according to an exemplary embodiment.
[0038] Fig.10 It is a flowchart of a slice event subscription reporting method based on access type according to an exemplary embodiment.
[0039] Fig.11 It is a block diagram of a slice event subscription and reporting device based on access type according to an exemplary embodiment.
[0040] Fig.12 It is a block diagram of a slice event subscription and reporting device based on access type according to an exemplary embodiment.
[0041] Fig.13 It is a block diagram of a slice event subscription and reporting device based on access type according to an exemplary embodiment.
[0042] Fig.14 It is a block diagram of a UE according to an exemplary embodiment.
[0043] Fig.15 It is a block diagram of a base station according to an exemplary embodiment. DETAILED DESCRIPTION
[0044] Here, exemplary embodiments will be described in detail, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the embodiments of the present disclosure. Instead, they are only examples of devices and methods consistent with some aspects of the embodiments of the present disclosure.
[0045] The terms used in the disclosed embodiments are only for the purpose of describing specific embodiments, and are not intended to limit the disclosed embodiments. The singular forms of "a" and "the" used in the disclosed embodiments are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used herein refers to and includes any or all possible combinations of one or more associated listed items.
[0046] It should be understood that although the terms first, second, third, etc. may be used to describe various information in the disclosed embodiments, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of the disclosed embodiments, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".
[0047] Please refer to Figure 1 , which shows a schematic diagram of the structure of a wireless communication system provided by an embodiment of the present disclosure. Figure 1 As shown, the wireless communication system is a communication system based on cellular mobile communication technology, and the wireless communication system may include: a plurality of user equipments 110 and a plurality of base stations 120 .
[0048] Among them, the user equipment 110 can be a device that provides voice and / or data connectivity to the user. The user equipment 110 can communicate with one or more core networks via a radio access network (RAN). The user equipment 110 can be an Internet of Things user equipment, such as a sensor device, a mobile phone (or a "cellular" phone), and a computer with an Internet of Things user equipment. For example, it can be a fixed, portable, pocket-sized, handheld, computer-built-in or vehicle-mounted device. For example, a station (STA), a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, a remote user device, an access terminal, a user terminal, a user agent, a user device, or a user equipment. Alternatively, the user equipment 110 can also be a device of an unmanned aerial vehicle. Alternatively, the user equipment 110 can also be a vehicle-mounted device, for example, it can be a driving computer with wireless communication function, or a wireless user device connected to an external driving computer. Alternatively, the user equipment 110 may also be a roadside device, for example, a street lamp, a signal lamp or other roadside device with a wireless communication function.
[0049] The base station 120 may be a network-side device in a wireless communication system. The wireless communication system may be a fourth generation mobile communication technology (4G) system, also known as a long term evolution (LTE) system; or, the wireless communication system may be a 5G system, also known as a new air interface system or a 5G NR system. Alternatively, the wireless communication system may be a next generation system of the 5G system. The access network in the 5G system may be referred to as a new generation radio access network (NG-RAN).
[0050] Among them, the base station 120 can be an evolved base station (eNB) adopted in the 4G system. Alternatively, the base station 120 can also be a base station (gNB) adopting a centralized distributed architecture in the 5G system. When the base station 120 adopts a centralized distributed architecture, it usually includes a centralized unit (CU) and at least two distributed units (DU). The centralized unit is provided with a protocol stack of a packet data convergence protocol (PDCP) layer, a radio link layer control protocol (RLC) layer, and a medium access control (MAC) layer; the distributed unit is provided with a physical (Physical, PHY) layer protocol stack. The specific implementation method of the base station 120 is not limited in the embodiment of the present disclosure.
[0051] A wireless connection may be established between the base station 120 and the user equipment 110 via a wireless air interface. In different implementations, the wireless air interface is a wireless air interface based on the fourth generation mobile communication network technology (4G) standard; or, the wireless air interface is a wireless air interface based on the fifth generation mobile communication network technology (5G) standard, for example, the wireless air interface is a new air interface; or, the wireless air interface may also be a wireless air interface based on the next generation mobile communication network technology standard of 5G.
[0052] In some embodiments, an E2E (End to End) connection may also be established between the user devices 110, such as vehicle to vehicle (V2V) communication, vehicle to infrastructure (V2I) communication, and vehicle to pedestrian (V2P) communication in vehicle to everything (V2X) communication.
[0053] Here, the above-mentioned user equipment can be considered as the terminal equipment of the following embodiments.
[0054] In some embodiments, the wireless communication system may further include a network management device 130 .
[0055] Several base stations 120 are respectively connected to a network management device 130. The network management device 130 may be a core network device in a wireless communication system. For example, the network management device 130 may be an access and mobility management function (AMF). Alternatively, the network management device may also be other core network devices, such as a session management function (SMF), a user plane function (UPF), a network exposure function (NEF), a network registration function (NF Repository Function, NRF) or a network slice selection function (NSSF). The embodiment of the present disclosure does not limit the implementation form of the network management device 130.
[0056] In order to facilitate the understanding of those skilled in the art, the embodiments of the present disclosure list multiple implementation methods to clearly illustrate the technical solutions of the embodiments of the present disclosure. Of course, those skilled in the art can understand that the multiple embodiments provided by the embodiments of the present disclosure can be executed separately, or can be executed together with the methods of other embodiments of the embodiments of the present disclosure, or can be executed together with some methods in other related technologies separately or in combination; the embodiments of the present disclosure do not limit this.
[0057] In order to better understand the technical solution described in any embodiment of the present disclosure, first, the network slicing related parts are described:
[0058] In one embodiment, a network slice may be associated with a network slice admission control function (NSACF). In another embodiment, a network slice may be associated with multiple NSACFs. In some disclosed embodiments, multiple refers to 2 or more.
[0059] In one embodiment, an operator may deploy multiple network slices to provide the same functionality, or may deploy different network slices to provide different functionality.
[0060] In one embodiment, the selection of a set of network slice instances for the UE is typically triggered by the first contacted Access and Mobility Management Function (AMF) in the registration process through interaction with the Network Slice Selection Function (NSSF); and the selection of the set of network slice instances may result in a change of the AMF. In each PLMN (Public Land Mobile Network), a Protocol Data Unit (PDU) session belongs to one and only one specific network slice instance. Here, different network slice instances may have PDU sessions for specific slices using the same Data Network Name (DNN), but different network slice instances do not share PDU sessions. Here, during the switching process, the source AMF selects the target AMF by interacting with the Network Registration Function (NRF, NF Repository Function).
[0061] In one embodiment, a Generic Network Slice Template (NEST) may be applied to a network slice, which is usually supported by multiple network slice instances. A Generic Network Slice Template (GST) may define the attributes supported by a network slice.
[0062] In one embodiment, the NSACF may be used to monitor the number of registered terminal UEs and / or the number of PDU sessions of the network slices supporting the network slice admission function. The NSACF may also configure the access type information of the network slice selection assistance information (S-NSSAI) for executing the network slice admission function.
[0063] In one embodiment, the NSACF may configure the maximum number of UEs allowed to access the network slice and / or the number of PDU sessions allowed to access. Here, the NSACF may support monitoring and / or admission control of the maximum number of UEs allowed to access the PLMN and / or the number of PDU sessions allowed to access. For example, if the number of UEs registered to a certain NSACF exceeds a certain threshold (such as the maximum number of UEs allowed to access), the NSACF will refuse registration to control the number of currently accessed UEs to not exceed the maximum number of UEs allowed to access configured by the network. For another example, if the number of PDU sessions activated in a certain NSACF exceeds a certain threshold (such as the maximum number of PDU sessions allowed to access), the NSACF will refuse activation of the PDU session to control the number of currently accessed PDU sessions to not exceed the maximum number of PDU sessions allowed to access configured by the network. Here, the PDU session activated in the NSACF may refer to the PDU session accessed in the NSACF.
[0064] In one embodiment, the operator network may deploy one NSACF or multiple NSACFs. One NSACF may serve one or more network slices in a service area. In a service area, one network slice may be handled by one NSACF, or one network slice may also be an NSACF instance, or one network slice may be an NSACF set. One PLMN may have one or more service areas.
[0065] In one embodiment, an application function (AF) can be used to obtain status information of a network slice; for example, the AF can obtain at least one of the following status information of the network slice: the number of registered UEs, the number of established PDU sessions, the ratio of the number of registered UEs to the maximum number of registered UEs allowed, and the ratio of the number of established PDU sessions to the maximum number of established PDU sessions allowed.
[0066] like Figure 2 As shown, the embodiment of the present disclosure provides a slice event subscription reporting method based on access type, which is executed by AF, including:
[0067] Step S21: Send a first subscription request to NEF to request event reports of network slices associated with an access type; wherein the first subscription request includes access type information indicating the access type, and the first subscription request is used to instruct NEF to send a second subscription request to NSACF to subscribe to the event report requested by the first subscription request.
[0068] Here, AF, NEF, and NSACF can be a physical device or a function performed by a physical device, and are not limited here. For example, AF, NEF, and NSACF can be various network-side devices, entities, or network elements of an access network or a core network.
[0069] In step S21, the first subscription request is sent to the NEF, or the AF sends the first subscription request to the network function (NF), and the NF forwards the first subscription request to the NEF. It should be noted that a network function is a physical device or a function performed by a physical device, which is not limited here. For example, the NF can be, but is not limited to, various network-side devices, entities, or network elements of the access network or the core network.
[0070] Here, the first subscription request is used to request event reports of network slices associated with the access type. Here, the second subscription request is used to subscribe to event reports of network slices associated with the access type; for example, the second subscription request is used to subscribe to event reports of network slices associated with the access type requested by the first subscription request. Here, the second subscription request may also include access severity information indicating the access type. Here, the first subscription request is the same as or different from the second subscription request.
[0071] Of course, in some other embodiments, the first subscription request may be used to request event reports associated with the access type; the second subscription request may be used to subscribe to event reports of network slices associated with the access type requested by the first subscription request.
[0072] In some embodiments, the access type information indicates at least one of the following:
[0073] An access type, wherein the access type indicates a 3rd Generation Partnership Project (3GPP) type and / or a non-3GPP type;
[0074] Wireless access type;
[0075] Access auxiliary information (addAccessInfo).
[0076] Here, the access assistance information may include access type and / or wireless access type access assistance information.
[0077] In some embodiments, the access type information indicates at least one of the following:
[0078] Access type, wireless access type, access assistance information of access type, and access assistance information of wireless access type.
[0079] The access type includes at least one of the following: 3GPP type; non-3GPP type; and 3GPP type and non-3GPP type.
[0080] The wireless access type includes at least one of the following:
[0081] New Radio (NR) access type, Evolved Universal Terrestrial Radio Access (EUTRA) type, Untrusted Wireless LAN (IEEE 802.11) (WLAN) access type, Virtual Network (Virtual shall be used if the N3IWF does not know the access technology used for an untrusted non-3GPPaccess, VIRTUAL) access type, Narrowband Internet of Things (NB IoT, NBIOT) access type, Wired Network (WIRELINE) access type, Wired Cable Network (WIRELINE_CABLE) access type, Wired Broadband Network (WIRELINE_BBF) access type, Urban Rail Transit Vehicle-Ground Integrated Communication System (LTE-M) access type, New Radio in unlicensed bands (NR_U) access type, Evolved Universal Terrestrial Radio Access in unlicensed bands, EUTRA_U) access type, Trusted Non-3GPP access (TRUSTED_N3GA) access type, Trusted Wireless LAN (IEEE 802.11, TRUSTED_WLAN) access type, Universal Terrestrial Radio Access (UMTS Terrestrial Radio, UTRA) type, Global System for Mobile Communications Edge Radio Network (GSM EDGE Radio Access Network, GERA) access type, New Air Interface Low Orbit (NR (LEO) satellite access type, NR_LEO) access type, New Air Interface Medium and High Orbit Access (NR (MEO) satellite access type, NR_MEO) access type, New Air Interface Geostationary Earth Orbit Access (NR (GEO) satellite access type, NR_GEO) access type and other satellite access (NR (OTHERSAT) satellite access type, NR_OTHER_SA) access type.
[0082] In some embodiments, the event report includes at least one of the following:
[0083] Number of registered UEs;
[0084] The number of established PDU sessions;
[0085] The ratio of the number of registered UEs to the maximum number of allowed registered UEs;
[0086] The ratio of the number of established PDU sessions to the maximum number of PDU sessions allowed to be established.
[0087] In some embodiments, the first subscription request and the second subscription request may include an event identifier; the event identifier is used to indicate an event report of one of the following: the number of registered UEs; the number of established PDU sessions; the ratio of the number of registered UEs to the maximum number of registered UEs allowed; and the ratio of the number of established PDU sessions to the maximum number of established PDU sessions allowed.
[0088] Here, UE may be various mobile terminals or fixed terminals; for example, UE may be, but is not limited to, a mobile phone, a computer, a server, a wearable device, a game control platform, or a multimedia device.
[0089] Here, the number of established PDU sessions included in the event report can also be replaced by the number of other types of sessions, and no restriction is imposed on the specific session type; the ratio of the number of established PDU sessions included in the event report to the maximum number of PDU sessions allowed to be established can also be replaced by the ratio of the number of established other types of sessions to the maximum number of other types of sessions allowed to be established, and no restriction is imposed on the specific session type.
[0090] In some embodiments, the first subscription request and the second subscription request may include the same information. Here, the second subscription request is the first subscription request.
[0091] Exemplarily, both the first subscription request and the second subscription request may include: a slice identifier indicating a network slice; wherein the slice identifier is used for the NEF to determine one or more NSACFs associated with the slice. Here, the second subscription request may be used to subscribe to event reports of network slices associated with the access type sent by one or more NSACFs.
[0092] Here, the slice identifier is used to indicate the network slice; the slice identifier can also be used to request the network slice that needs to be subscribed.
[0093] Thus, in the disclosed embodiment, after receiving the first subscription request, the NEF can determine the NSACF to which the second subscription request needs to be sent based on the slice identifier in the first subscription request. If the slice identifier is associated with one NSACF, the NEF can send the second subscription request to the NSACF; if the slice identifier is associated with multiple NSACFs, the NEF can send the second subscription request to some or all of the multiple NSACFs.
[0094] In some other embodiments, the first subscription request and the second subscription request may include different information. Here, the second subscription request is determined by the NEF based on the first subscription request.
[0095] Exemplarily, the first subscription request may include: an application identifier; the application identifier is used to determine a slice identifier associated with the application identifier; the second subscription request may include: a slice identifier.
[0096] The application identifier is used to identify the service and / or application. Here, the NEF or other core network devices, such as the Network Repository Function (NRF), can store the association between the application identifier and the slice identifier; the NEF or NRF can determine the slice identifier associated with the application identifier based on the obtained application identifier and the association between the application identifier and the slice identifier.
[0097] If the first subscription request does not carry a network slice, the network may not open a slice identifier indicating a network slice to the AF. The NEF can determine the slice identifier associated with the application identifier based on the application identifier included in the first subscription request.
[0098] Thus, in the disclosed embodiment, if the NEF receives a first subscription request, it can determine the slice identifier of the network slice that needs to be subscribed based on the application identifier in the first subscription request, and thus the NSACF that needs to send a second subscription request based on the slice identifier.
[0099] In some embodiments, the first subscription request includes: a slice identifier, and a DNN corresponding to the slice identifier. In this way, in the disclosed embodiment, the NEF can know the data network name associated with the slice identifier that the AF needs to subscribe to.
[0100] Here, if the first subscription request includes a slice identifier and a DNN corresponding to the slice identifier, the second subscription request may also include: a slice identifier and a DNN corresponding to the slice identifier.
[0101] In some embodiments, the first subscription request includes report configuration information; the report configuration information includes at least one of the following:
[0102] Threshold used to trigger reporting;
[0103] a predetermined time interval for periodic reporting;
[0104] Immediate reporting flag, used to indicate that a subscription request is received and reported.
[0105] In some embodiments, the second subscription request includes report configuration information; the report configuration information includes at least one of the following:
[0106] Threshold used to trigger reporting;
[0107] a predetermined time interval for periodic reporting;
[0108] An immediate reporting flag, wherein the immediate reporting flag is used to indicate that a subscription request is received and reported.
[0109] In the disclosed embodiment, a first subscription request may be sent from AF to NEF, the first subscription request including access type information indicating the access type; the first subscription request is used by NEF to send a second subscription request to NSACF, the second subscription request being used to subscribe to event reports of network slices associated with the access type requested by the first subscription request. In this way, a network device (such as AF or NEF, etc.) may obtain event reports of network slices associated with the access type sent by at least one NSACF based on the subscription request (first subscription request or second subscription request), that is, the network device may obtain the network status of the network slice; in this way, the network device may accurately locate and meet the needs of the operator's services, and may also configure resources and execute services accordingly based on the network status, thereby improving the user experience satisfaction.
[0110] In some embodiments, the event report includes: a first event report and / or a second event report. Here, the second event report is determined by the NEF based on the first event report.
[0111] It should be noted that the first subscription request and the second subscription request are not in one-to-one correspondence with the first event report and the second event report, respectively. The first event report is a response to the second subscription request or the first subscription request; the second event report is determined based on the first event report.
[0112] like Figure 3 As shown, the embodiment of the present disclosure provides a slice event subscription reporting method based on access type, which is executed by AF, including:
[0113] Step S31: Receive a second event report returned by the NEF, wherein the second event report is determined based on multiple first event reports; wherein the first event report includes: registration statistics of UEs registered to the network slice and / or session statistics of sessions established by the network slice; the second event report includes: aggregated statistical information after the statistical data contained in multiple first event reports are aggregated.
[0114] Here, the second event report may also be determined based on a first event report.
[0115] Here, the second event report being determined based on at least one first event report may mean that: the second event report is determined by the NEF based on at least one first event report, or the second event report is determined by the NSACF based on at least one first event report.
[0116] Here, the statistical data may include but is not limited to: registration statistical data and / or session statistical data.
[0117] Here, the registration statistics data may be, but is not limited to: the number of registered UEs and / or the ratio of the number of registered UEs to the maximum number of allowed registered UEs.
[0118] Here, the session statistics data may be, but is not limited to: the number of established PDU sessions and / or the ratio of the number of established PDU sessions to the maximum number of PDU sessions allowed to be established.
[0119] In one embodiment, the aggregated statistical information includes statistical data included in at least one first event report.
[0120] In this way, in the embodiment of the present disclosure, the AF can receive a first event report returned by at least one NSACF based on the second subscription request, or receive a second event report after the NEF aggregates and counts the first event report. This allows the AF or NEF to accurately know the status information of the network slices associated with each access type in the network, thereby configuring resources and executing services according to the corresponding network status.
[0121] like Figure 4 As shown, the embodiment of the present disclosure provides a slice event subscription reporting method based on access type, which is executed by AF, including:
[0122] Step S41: Send an unsubscribe request to NEF, where the unsubscribe request is used to unsubscribe from the reporting of event reports of the network slice associated with the access type.
[0123] In the embodiment of the present disclosure, the access type is the access type of the above embodiment; the event report is the event report of the above embodiment.
[0124] Here, the unsubscribe request is used for NEF to send to at least one NSACF. For example, the unsubscribe request is used for NEF to send to one or more NSACFs associated with the slice identifier, or for NEF to send to an NSACF that supports the subscription function.
[0125] In one embodiment, the unsubscribe request includes, but is not limited to, at least one of the following: access type information, a slice identifier, a DNN corresponding to the slice identifier, and an application identifier.
[0126] Here, if the unsubscribe request includes access type information, the reporting of event reports of the network slice associated with the access type can be unsubscribed. If the unsubscribe request includes a slice identifier, the NEF can determine the NSACF to which the unsubscribe request needs to be sent; or if the unsubscribe request includes an application identifier, the NEF can determine the slice identifier based on the application identifier, and then determine the NSACF to which the unsubscribe request needs to be sent. If the unsubscribe request reports the slice identifier and the DNN corresponding to the slice identifier, the NEF can determine the NSACF to which the unsubscribe request needs to be sent, and unsubscribe from the reporting of event reports of the data network associated with the network slice.
[0127] In this way, in the embodiment of the present disclosure, the AF can send a cancellation request to the NEF, so that the NEF can cancel the subscription and report the event report of the network slice associated with the access type, so that the NSACF does not need to report the event report all the time; thereby saving network resources and energy consumption of network equipment (such as NEF or NSACF, etc.).
[0128] It should be noted that those skilled in the art can understand that the method provided in the embodiments of the present disclosure can be executed alone or together with some methods in the embodiments of the present disclosure or some methods in related technologies.
[0129] The following slice event subscription reporting method based on access type is executed by NEF, which is similar to the description of the slice event subscription reporting method based on access type executed by AF above; and for technical details not disclosed in the embodiment of the slice event subscription reporting method based on access type executed by NEF, please refer to the description of the example of the slice event subscription reporting method based on access type executed by AF, and no detailed description is given here.
[0130] like Figure 5 As shown, the embodiment of the present disclosure provides a slice event subscription reporting method based on access type, which is executed by NEF and includes:
[0131] Step S51: receiving a first subscription request sent by the AF; wherein the first subscription request is used to request an event report of a network slice associated with an access type; wherein the first subscription request includes access type information indicating the access type;
[0132] Step S52: Send a second subscription request to the NSACF, where the second subscription request is used to subscribe to the event report requested by the first subscription request.
[0133] In some embodiments of the present disclosure, the first subscription request is the first subscription request in step S21; the second subscription request is the second subscription request in step S21; the event report is the event report in step S21; the access type and access type information are the access type and access type information in step S21 respectively.
[0134] Exemplarily, the first subscription request and the second subscription request both include: a slice identifier. For another example, the first subscription request includes an application identifier, and the second subscription request includes a slice identifier.
[0135] Exemplarily, the access type information is used to indicate that in some embodiments, the access type information indicates at least one of the following: an access type, wherein the access type indicates a 3GPP type and / or a non-3GPP type; a wireless access type; and access assistance information.
[0136] Exemplarily, the wireless access type includes but is not limited to at least one of the following: NR access type, EUTRA access type, WLAN access type, VIRTUAL access type, NBIOT access type, WIRELINE access type, WIRELINE_CABLE access type, WIRELINE_BBF access type, LTE-M access type, NR_U access type, EUTRA_U access type, TRUSTED_N3GA access type, TRUSTED_WLAN access type, UTRA access type, GERA access type, NR_LEO access type, NR_MEO access type, NR_GEO access type and NR_OTHER_SA access type.
[0137] Exemplarily, the first subscription request and / or the second subscription request includes an event identifier for indicating an event report.
[0138] Exemplarily, the event report includes at least one of the following: the number of registered UEs; the number of established PDU sessions; the ratio of the number of registered UEs to the maximum allowed number of registered UEs; and the ratio of the number of established PDU sessions to the maximum allowed number of established PDU sessions.
[0139] Exemplarily, the second subscription request includes: report configuration information, wherein the report configuration information includes: at least one of the following:
[0140] Threshold used to trigger reporting;
[0141] a predetermined time interval for periodic reporting;
[0142] An immediate reporting flag, wherein the immediate reporting flag is used to indicate that a subscription request is received and reported.
[0143] In this way, in the embodiment of the present disclosure, the first subscription request of the AF can be received by the NEF, and the second subscription request can be sent to the NSACF, where the second subscription request is used to subscribe to the event report of the network slice associated with the access type requested by the first subscription request; in this way, the network device (such as NEF, etc.) can obtain the event report of the network slice associated with the access type sent by at least one NSACF based on the subscription request and the second subscription request, that is, the NEF can obtain the network status of the network slice; it is also beneficial for the NEF to send the network status of the network slice to the AF, so that the network device (AF or NEF, etc.) can accurately locate and meet the needs of the operator's services, and can also enable the network device (AF or NEF, etc.) to configure resources and execute services accordingly according to the network status, and improve the user experience satisfaction.
[0144] In some embodiments, the first subscription request includes: a slice identifier indicating a network slice; or, a slice identifier and a DNN corresponding to the slice identifier.
[0145] In some embodiments, the first subscription request includes: a slice identifier indicating a network slice;
[0146] The method includes: obtaining a slice identifier based on a first subscription request.
[0147] Exemplarily, the NEF receives a first subscription request, and obtains a slice identifier based on the slice identifier included in the first subscription request; the NEF determines one or more NSACFs associated with the slice identifier based on the slice identifier, and sends a second subscription request to the one or more NSACFs; wherein the second subscription request may be the first subscription request.
[0148] Here, NEF can pre-store or set a preset association relationship between the slice identifier and the NSACF; if NEF obtains the slice identifier included in the first subscription request, it can determine one or more NSACFs associated with the slice identifier based on the slice identifier and the preset association relationship.
[0149] Thus, in the embodiment of the present disclosure, if the NEF receives a first subscription request including a slice identifier, it can directly determine the NSACF to which the second subscription request needs to be sent based on the NSACF associated with the slice identifier, and can also send the first subscription request as the second subscription request.
[0150] In some other embodiments, the first subscription request includes: a slice identifier indicating a network slice, and a DNN corresponding to the slice identifier.
[0151] Exemplarily, NEF receives a first subscription request, and obtains a slice identifier based on the slice identifier included in the first subscription request; based on the slice identifier, NEF determines one or more NSACFs associated with the slice identifier, and sends a second subscription request to the one or more NSACFs, wherein the second subscription request may be the first subscription request. Here, if NEF sends the second subscription request to the one or more NSACFs, the NSACF may be informed of the reporting event of the data network name of the access type associated network slice that needs to be subscribed. For example, the access type is a 3GPP type, the slice identifier is associated with NSACF1 and NSACF2, and the data network name is network 1; then event reports of network 1 with 3GPP type access may be subscribed to NSACF and NSACF, such as the number of registered UEs and / or the number of established PDU sessions of network 1 with 3GPP type access.
[0152] Thus, in an embodiment of the present disclosure, if the first subscription request also includes a DNN corresponding to the slice identifier, an event report of the data network name associated with the access type can also be determined; thus, the corresponding event report can be obtained at a smaller granularity.
[0153] In some embodiments, the first subscription request includes an application identifier;
[0154] The method includes: determining a slice identifier indicating a network slice based on an application identifier.
[0155] An embodiment of the present disclosure provides a slice event subscription reporting method based on access type, which is executed by NEF, including: determining a slice identifier indicating a network slice based on an application identifier.
[0156] The determining, based on the application identifier, a slice identifier indicating a network slice, includes one of the following:
[0157] Based on the application identifier, obtain the slice identifier corresponding to the application identifier from the NRF;
[0158] Based on the application identifier and configuration information, the slice identifier is determined, wherein the configuration information includes the correspondence between the application identifier and the slice identifier.
[0159] The embodiment of the present disclosure provides a processing method, which is executed by NEF, including: determining a slice identifier based on an application identifier and configuration information, wherein the configuration information includes a correspondence between the application identifier and the slice identifier.
[0160] Here, the application identifier is used to identify a service or an application.
[0161] Exemplarily, the NEF receives a first subscription request and obtains an application identifier included in the first subscription request; the NEF determines a slice identifier corresponding to the application identifier based on the application identifier and configuration information; wherein the configuration information includes a correspondence between the application identifier and the slice identifier. In this way, the NEF can determine one or more NSACFs associated with the slice identifier based on the slice identifier, and send a second subscription request including the application identifier to the one or more NSACFs.
[0162] Thus, in the disclosed embodiment, if the NEF does not obtain the slice identifier from the first subscription request, it can also obtain the slice identifier associated with the application identifier based on the application identifier included in the first subscription identifier and the configuration information in the NEF; and then, based on the slice identifier, it can accurately determine that a second subscription request needs to be sent, that is, the NSACF that needs to subscribe to the event report.
[0163] The embodiment of the present disclosure provides a processing method, which is executed by NEF, including: based on the application identifier, obtaining a slice identifier corresponding to the application identifier.
[0164] Exemplarily, NEF receives a first subscription request and obtains the application identifier included in the first subscription request; NEF sends a request message carrying the application identifier to NRF, or, NEF fails to obtain a slice identifier associated with the application identifier based on query configuration information, and sends a request message carrying the application identifier to NRF, wherein the request message is used to request a slice identifier associated with the application identifier; NFE receives a response message returned by NRF based on the request message, and obtains the slice identifier associated with the application identifier from the response message. Here, NRF stores or configures a correspondence between at least one application identifier and a slice identifier; the application identifier included in the correspondence is greater than the application identifier included in the configuration message of NEF.
[0165] Thus, in the disclosed embodiment, if the NEF does not obtain the slice identifier from the first subscription request, it can also obtain the slice identifier corresponding to the application identifier from the NRF, that is, the NEF can perform the mapping of the application identifier to the slice identifier; and then, based on the slice identifier, it can accurately determine that the second subscription request needs to be sent, that is, the NSACF that needs to subscribe to the event report.
[0166] The sending of the second subscription request to the NSACF in step S52 includes one of the following:
[0167] Sending a second subscription request to one or more NSACFs associated with the network slice;
[0168] A second subscription request is sent to the NSACF that supports the subscription function.
[0169] Here, the NSACF subscription function may be: the NSACF may report an event report based on a subscription request.
[0170] The disclosed embodiment provides a slice event subscription reporting method based on access type, which is executed by NEF and may include: if a slice identifier that needs to be subscribed is determined, and the slice identifier is associated with an NSACF, sending a second subscription request to the NSACF.
[0171] The embodiment of the present disclosure provides a method for reporting slice event subscription based on access type, which is executed by NEF and may include: if a slice identifier that needs to be subscribed is determined, and the slice identifier is associated with multiple NSACFs, a second subscription request is sent to at least some of the multiple NSACFs. Here, the second subscription request may be sent to each NSACF in the multiple NSACFs, or the second subscription request may be sent to some of the multiple NSACFs.
[0172] The disclosed embodiment provides a slice event subscription reporting method based on access type, which is executed by NEF and may include: if the slice identifier that needs to be subscribed is not determined, sending a second subscription request to the NSACF that supports the subscription function.
[0173] Exemplarily, the NEF receives a first subscription request; if the NEF does not determine the slice identifier that needs to be subscribed based on the first subscription request, a second subscription request is sent to the NSACF that supports the subscription function. Alternatively, if the NEF determines the slice identifier that needs to be subscribed based on the first subscription request, if it is determined that the slice identifier is associated with one NSACF, a second subscription request is sent to the NSACF; or if it is determined that the slice identifier is associated with multiple NSACFs, a second subscription request is sent to each of the multiple NSACFs; wherein the second subscription request is used to subscribe to event reports of network slices associated with the access type requested by the first subscription request.
[0174] Thus, in the disclosed embodiment, the NSACF to which the second subscription request is sent can be determined based on whether the NEF has determined the network slice that needs to be subscribed. For example, if the NEF has not yet determined the network slice that needs to be subscribed, a second subscription request can be sent to all NSACFs that support the subscription function, so that a more comprehensive event report can be obtained. For another example, if the NEF determines the network slice that needs to be subscribed, it can accurately obtain the service or application, or the event report associated with the network slice, so as to accurately locate and meet the needs of the operator and other services; and since there is no need to obtain event reports associated with all services or network slices, it can also reduce the power consumption of network equipment, such as NSACF, NEF, etc.
[0175] It should be noted that those skilled in the art can understand that the method provided in the embodiments of the present disclosure can be executed alone or together with some methods in the embodiments of the present disclosure or some methods in related technologies.
[0176] like Figure 6 As shown, the embodiment of the present disclosure provides a slice event subscription reporting method based on access type, which is executed by NEF and may include:
[0177] Step S61: receiving a second event report sent by the NSACF; wherein the second event report is determined by the NSACF based on multiple first event reports; the first event report includes: registration statistics of UEs registered to the network slice and / or session statistics of sessions established by the network slice; the second event report includes aggregated statistical information after the statistical data included in the multiple first event reports are aggregated;
[0178] Step S62: Send a second event report to AF.
[0179] In some embodiments of the present disclosure, the first event report is the first event report in step S31; the registration statistics data is the registration statistics data in step S31; and the session statistics data is the session statistics data in step S31.
[0180] Receiving the second event report sent by the NSACF in step S61 includes: receiving the second event report sent by one or more NSACFs.
[0181] Exemplarily, if the network slice is associated with NSACF1, NSACF2 and NSACF3, the NEF can obtain the aggregated statistical information sent by one of NSACF1, NSACF2 and NSACF3, which is the registration statistical data of UEs registered to the network slice and / or the session statistical data of sessions established by the network slice based on the access type association of NSACF1, NSACF2 and NSACF3. The aggregated statistical information can be considered as the second event report.
[0182] In this way, in the embodiment of the present disclosure, the NEF can directly receive the second event report determined by the NSACF based on the first event report, and send the second event report to the AF, so that the AF can accurately know the network status of the network slice.
[0183] Receiving the second event report sent by the NSACF in step S61 includes: receiving a notification sent by the NSACF carrying the second event report;
[0184] The sending of the second event report to the AF in step S61 includes: sending a notification carrying the second event report to the AF.
[0185] Here, the notification may be any realizable message or signaling, and the notification type is not limited here.
[0186] In this way, the embodiment of the present disclosure can also receive and / or send a second event report based on the notification, so that the original function of the notification and the notification of reporting the second event report can be realized through one notification; thereby improving the utilization rate of the notification and reducing signaling overhead, etc.
[0187] like Figure 7 As shown, the embodiment of the present disclosure provides a slice event subscription reporting method based on access type, which is executed by NEF and may include:
[0188] Step S71: receiving a first event report sent by NSACF;
[0189] Step S72: determining a second event report based on the plurality of first event reports, wherein the second event report includes aggregated statistical information obtained by aggregating statistical data included in the plurality of first event reports;
[0190] Step S73: Send a second event report to AF.
[0191] In some embodiments of the present disclosure, the second event report is the second event report in step S31; the statistical data is the statistical data in step S31; and the aggregated statistical information is the aggregated statistical information in step S31.
[0192] Exemplarily, if the network slice is associated with NSACF1, NSACF2 and NSACF3, the NEF can obtain the registration statistics of UEs registered to the network slice and / or the session statistics of sessions established by the network slice, which are associated with the access types sent by NSACF1, NSACF2 and NSACF3 respectively; and aggregate the registration statistics and / or session statistics of NSACF1, the registration statistics and / or session statistics of NSACF2, and the registration statistics and / or session statistics of NSACF3 into a second event report; the NEF sends the second event report to the AF.
[0193] Receiving the first event report sent by the NSACF in step S71 includes: receiving the first event report sent by one or more NSACFs.
[0194] In step S72, determining the second event report based on the multiple first event reports may be: aggregating the multiple first event reports to obtain the second event report.
[0195] The aggregation method in step S72 may be determined according to the operator policy or NEF configuration. For example, if a slice identifier is associated with multiple NSACFs, the operator policy is: use one NSACF among the multiple NSACFs as the master NSACF and the other NSACFs as slave NSACFs. For example, the slice identifier of a network slice is associated with NSACF1, NSACF2 and NSACF3; the operator policy is: use NSACF1 as the master NSACF, and NSACF2 and NSACF3 as slave NSACFs. The aggregated statistical information included in the second event report determined by the NEF may include: the master NSACF (NSACF1), and the information after the statistical data of the slave NSACFs (NSACF2 and NSACF3) are aggregated.
[0196] The aggregation method in step S72 can also be performed by NSACF, and NSACF aggregates multiple first event reports into a second event report; NEF receives the second event report sent by NSACF. Exemplarily, if a slice identifier is associated with multiple NSACFs, the operator policy is: select one of the multiple NSACFs as the proxy NSACF. For example, the slice identifier of a network slice is associated with NSACF1, NSACF2 and NSACF3; the operator policy is: then one of NSACF1, NSACF2 and NSACF3 can be selected as the proxy NSACF, such as selecting NSACF1 as the proxy NSACF. The NSACF1 obtains the first event reports of NSACF1, NSACF2 and NSACF3, and aggregates the first event reports of NSACF1, NSACF2 and NSACF3 to obtain a second event report including aggregated statistical information. NEF receives the second event report sent by NSACF1, and the aggregated statistical information included in the second event report may include: statistical data of NSACF1, NSACF2 and NSACF3.
[0197] Of course, the aggregation method may also be any other feasible method, which is not limited here.
[0198] Thus, in the disclosed embodiment, the first event report received from the NSACF can be further aggregated by the NEF to obtain the aggregated second event report and send it to the AF. In this way, the AF can accurately know the network status of the network slice and obtain clearer network status information (i.e., the second event report), so as to facilitate the AF and other network devices to more reasonably perform corresponding resource configuration and execute business operations.
[0199] Receiving the first event report sent by the NSACF in step S71 includes: receiving a notification sent by the NSACF carrying the first event report;
[0200] The sending of the second event report to the AF in step S73 includes: sending a notification carrying the second event report to the AF.
[0201] Here, the notification may be any realizable message or signaling, and the notification type is not limited here.
[0202] In this way, in the embodiment of the present disclosure, the first event report can be received and the second event report can be sent based on the notification, so that the original function of the notification and the notification of reporting the first event report can be realized through one notification; thereby improving the utilization rate of the notification and reducing the signaling overhead, etc.
[0203] The embodiment of the present disclosure provides a method for subscribing and reporting slice events based on access type, which is executed by NEF, including: sending a second event report carrying a slice identifier to AF. Here, if the first subscription request received by NEF includes a slice identifier, it can be determined that AF is a trusted third party; then NEF can send the second event report carrying the slice identifier to AF.
[0204] The disclosed embodiment provides a method for reporting slice event subscription based on access type, which is executed by NEF, including: sending a second event report carrying an application identifier to AF. Here, if the first subscription request received by NEF does not include a slice identifier but includes an application identifier, it can be determined that AF is an untrusted third party; then after NEF obtains the first event report of at least one NSACF, it will also map the slice identifier corresponding to the NSACF to an application identifier; and send the second event report carrying the application identifier to AF.
[0205] Here, the method of mapping the slice identifier to the application identifier is similar to the method of determining the slice identifier based on the application identifier in the above embodiment; for example, it can be but not limited to: determining the slice identifier based on the slice identifier and configuration information, wherein the configuration information includes the correspondence between the application identifier and the slice identifier; or, based on the slice identifier, obtaining the application identifier corresponding to the slice identifier from the NRF.
[0206] It should be noted that those skilled in the art can understand that the method provided in the embodiments of the present disclosure can be executed alone or together with some methods in the embodiments of the present disclosure or some methods in related technologies.
[0207] The embodiment of the present disclosure provides a slice event subscription reporting method based on access type, which is executed by NEF and includes:
[0208] Receive the unsubscribe request sent by AF;
[0209] Send an unsubscribe request to NSACF; wherein the unsubscribe request is used to unsubscribe from the reporting of event reports of the network slice associated with the access type.
[0210] In some embodiments of the present disclosure, the unsubscribe request is the unsubscribe request in step S41; the access type is the access type of the above-mentioned embodiment; the event report includes a first event report or a second event report; the first event report is the first event report of the above-mentioned embodiment, and the second event report is the second event report of the above-mentioned embodiment.
[0211] In this way, in the embodiment of the present disclosure, the NEF can receive the AF's unsubscription request and send the unsubscription request to the NSACF, so that the NEF does not need to always send the first event report or the second event report to the AF, or the NSACF does not need to always send the first event report to the NEF; thereby saving network resources and energy consumption of network equipment (such as NEF or NSACF, etc.).
[0212] It should be noted that those skilled in the art can understand that the method provided in the embodiments of the present disclosure can be executed alone or together with some methods in the embodiments of the present disclosure or some methods in related technologies.
[0213] The following slice event subscription reporting method based on access type is executed by NSACF, which is similar to the description of the slice event subscription reporting method based on access type executed by AF and NEF above; and for technical details not disclosed in the embodiment of the slice event subscription reporting method based on access type executed by NSACF, please refer to the description of the example of the slice event subscription reporting method based on access type executed by AF and NEF, which will not be described in detail here.
[0214] like Figure 8 As shown, the embodiment of the present disclosure provides a slice event subscription reporting method based on access type, which is executed by NSACF and includes:
[0215] Step S81: receiving a second subscription request sent by the NEF; wherein the second subscription request is sent by the NEF based on the received first subscription request instruction; wherein the first subscription request is used to request an event report of a network slice associated with an access type, wherein the first subscription request includes access type information indicating the access type;
[0216] Step S82: Sending the event report requested by the first subscription request subscribed by the second subscription request to the NEF.
[0217] Here, the NSACF may be one or more. For example, there is one NSACF that can support the subscription function or one NSACF associated with the slice identifier, then step S81 may be: the one NSACF receives the second subscription request sent by NEF; step S82 may be: the one NSACF sends an event report of the network slice associated with the access type subscribed by the second subscription request to NEF. For another example, there are multiple NSACFs that can support the subscription function or multiple NSACFs associated with the slice identifier, for example, the multiple NSACFs are NSACF1, NSACF2, ... NSACF n, where n is an integer greater than 1; then in step S81, NSACF1, NSACF2, ... NSACF n receive the second subscription request sent by NEF; step S82 may be: NSACF1, NSACF2, ... NSACF n respectively send event reports of the network slice associated with the access type subscribed by the second subscription request to NEF.
[0218] In some embodiments of the present disclosure, the first subscription request is the first subscription request in step S21; the second subscription request is the second subscription request in step S21; the event report is the event report in step S21; the access type and access type information are the access type and access type information in step S21 respectively.
[0219] Exemplarily, the first subscription request and the second subscription request both include: a slice identifier. For another example, the first subscription request includes an application identifier, and the second subscription request includes a slice identifier.
[0220] Exemplarily, the first subscription request and the second subscription request both include: a slice identifier and a DNN corresponding to the slice identifier.
[0221] Exemplarily, the access type information is used to indicate that in some embodiments, the access type information indicates at least one of the following: an access type, indicating a 3GPP type and / or a non-3GPP type; a wireless access type; and access assistance information.
[0222] Exemplarily, the wireless access type includes but is not limited to at least one of the following: NR access type, EUTRA access type, WLAN access type, VIRTUAL access type, NBIOT access type, WIRELINE access type, WIRELINE_CABLE access type, WIRELINE_BBF access type, LTE-M access type, NR_U access type, EUTRA_U access type, TRUSTED_N3GA access type, TRUSTED_WLAN access type, UTRA access type, GERA access type, NR_LEO access type, NR_MEO access type, NR_GEO access type and NR_OTHER_SA access type.
[0223] Exemplarily, the event report includes at least one of the following: the number of registered UEs; the number of established PDU sessions; the ratio of the number of registered UEs to the maximum number of registered UEs allowed; and the ratio of the number of established PDU sessions to the maximum number of established PDU sessions allowed. Here, the event report includes a first event report.
[0224] In some embodiments of the present disclosure, the first event report and the second event report are respectively the first event report and the second event report in the above embodiments; the registration statistics data, the session statistics data and the aggregate statistics information are respectively the registration statistics data, the session statistics data and the aggregate statistics information in the above embodiments.
[0225] The step S82 includes:
[0226] Send a first event report to the NEF; wherein the first event report includes: registration statistics of UEs registered to the network slice and / or session statistics of sessions established by the network slice.
[0227] An embodiment of the present disclosure provides an access type slice event subscription reporting method, which is executed by NSACF, including: sending a first event report to the NEF; wherein the first event report includes: registration statistics of UEs registered to the network slice and / or session statistics of sessions established by the network slice.
[0228] The step S82 includes:
[0229] Obtain multiple first event reports; wherein the first event report includes: registration statistics of UEs registered to the network slice and / or session statistics of sessions established by the network slice;
[0230] Based on the first event report, determining a second event report; wherein the second event report includes aggregated statistical information obtained by aggregating statistical data included in a plurality of the first event reports;
[0231] The second event report is sent to the NEF.
[0232] The present disclosure provides a method for reporting slice event subscriptions of access types, which is executed by NSACF and includes:
[0233] Obtain multiple first event reports; wherein the first event report includes: registration statistics of UEs registered to the network slice and / or session statistics of sessions established by the network slice;
[0234] Based on the first event report, determining a second event report; wherein the second event report includes aggregated statistical information obtained by aggregating statistical data included in a plurality of the first event reports;
[0235] The second event report is sent to the NEF.
[0236] The embodiment of the present disclosure provides a slice event subscription reporting method based on access type, which is executed by NSACF and includes:
[0237] Exemplarily, the first subscription request and the second subscription request may both include: report configuration information.
[0238] The embodiment of the present disclosure provides a slice event subscription reporting method based on access type, which is executed by NSACF and includes:
[0239] Receive the unsubscribe request sent by NEF;
[0240] Based on the unsubscribe request, it is determined not to report event reports associated with the access type.
[0241] The second subscription request includes report configuration information; the report configuration information includes: at least one of the following:
[0242] Threshold used to trigger reporting;
[0243] a predetermined time interval for periodic reporting;
[0244] An immediate reporting flag, wherein the immediate reporting flag is used to indicate that a subscription request is received and reported.
[0245] The step S81 includes one of the following:
[0246] Based on the NSACF meeting the threshold for triggering reporting, an event report of the network slice associated with the access type is sent to the NEF;
[0247] Sending event reports of the network slice associated with the access type to the NEF based on a predetermined time interval;
[0248] Based on the immediate reporting flag included in the second subscription request, a network slice event report associated with the access type is sent to the NEF.
[0249] like Fig. 9 As shown, the embodiment of the present disclosure provides a slice event subscription reporting method based on access type, which is executed by NSACF and includes:
[0250] Step S91: Based on the NSACF satisfying the threshold for triggering reporting, an event report of the network slice associated with the access type is sent to the NEF; or, based on a predetermined time interval, an event report of the network slice associated with the access type is sent to the NEF; or, based on the second subscription request including an immediate reporting flag, an event report of the network slice associated with the access type is sent to the NEF.
[0251] Here, the threshold value may be a time threshold value, or a threshold value of a triggering event. For example, if the threshold value is the first time, when the current time of the NSACF reaches the first time, it is determined that the NSACF meets the threshold value for triggering reporting. For another example, if the threshold value is a threshold value for a triggering event, such as a threshold value for the number of registered UEs; when the NSACF determines that the number of currently registered UEs is greater than or equal to the threshold value for the number of registered UEs, the threshold value for triggering reporting by the NSACF is determined.
[0252] Here, the threshold value and the predetermined time interval may be determined by the AF or other network devices, or may be determined through a wireless communication protocol, etc.
[0253] Here, the immediate reporting flag is used to instruct the NSACF to report the event report. The immediate reporting flag may be a predetermined bit, for example, the immediate reporting flag is "000" or the like.
[0254] Exemplarily, the NSACF receives the second subscription request, and if it is determined that the second subscription request includes a threshold value for the number of registered UEs, determines whether the number of currently registered UEs is greater than the threshold value for the number of registered UEs; if the NSACF determines that the number of currently registered UEs is greater than or equal to the threshold value for the number of registered UEs, it sends a first event report of a network slice associated with the access type to the NEF. In this way, the embodiment of the present disclosure can realize reporting of an event report when the NSACF meets the threshold value.
[0255] Exemplarily, when the NSACF receives the second subscription request, if it is determined that the second subscription request includes a predetermined time interval, the NSACF sends a first event report of the network slice associated with the access type to the NEF at predetermined time intervals. In this way, the embodiment of the present disclosure can implement periodic reporting of event reports.
[0256] Exemplarily, when NSACF receives the second subscription request and determines that the second subscription request includes an immediate reporting flag, it sends a first event report of the network slice associated with the access type to NEF. In this way, the embodiment of the present disclosure can report an event report every time a second subscription request including an immediate reporting flag is received.
[0257] Thus, in the disclosed embodiment, the conditions for NSACF to report an event report can be determined by carrying the report configuration information for triggering the report in the second subscription request, such as the threshold for triggering the report, the predetermined time interval for periodic reporting, and / or the immediate reporting flag, etc. When the conditions are met, the event report is reported. Thus, multiple modes of event reporting can be realized, which is applicable to more application scenarios of event reporting.
[0258] In order to further explain any embodiment of the present disclosure, several specific embodiments are provided below.
[0259] like Fig.10 As shown, the embodiment of the present disclosure provides a slice event subscription reporting method based on access type, which is executed by a communication device and includes the following steps:
[0260] Here, the communication device may be, but is not limited to, AF, NEF or NSACF; NSACF may include NSACF1, NSACF2, ... NSACF n; wherein n is an integer greater than 0.
[0261] Step S101: AF sends a subscription request or a cancellation request to NEF;
[0262] In an optional embodiment, the AF sends a first subscription request or an unsubscription request to the NEF, wherein the first subscription request or the unsubscription request includes access type information indicating the access type; wherein the first subscription request is used to request an event report of a network slice of the access type; and the unsubscription request is used to cancel the reporting of an event report of a network slice associated with the access type.
[0263] Here, the first subscription request may include at least one of the following: an event identifier, access type information, and report configuration information.
[0264] Here, the event identifier is used to indicate at least one of the following: the number of registered UEs, the number of established PDU sessions, the ratio of the number of registered UEs to the maximum number of registered UEs allowed, and the ratio of the number of established PDU sessions to the maximum number of established PDU sessions allowed;
[0265] Here, the access type information is used to indicate at least one of the following: access type, wireless access type, and access assistance information of the access type and / or wireless access type; wherein the access type includes 3GPP type and / or non-3GPP type; the wireless access type includes at least one of the following: NR access type, EUTRA access type, WLAN access type, VIRTUAL access type, NBIOT access type, WIRELINE access type, WIRELINE_CABLE access type, WIRELINE_BBF access type, LTE-M access type, NR_U access type, EUTRA_U access type, TRUSTED_N3GA access type, TRUSTED_WLAN access type, UTRA access type, GERA access type, NR_LEO access type, NR_MEO access type, NR_GEO access type and NR_OTHER_SA access type.
[0266] Here, the report configuration information includes at least one of the following: a threshold for triggering reporting; a predetermined time interval for periodic reporting; and an immediate reporting flag for indicating that a report is to be made upon receipt of a subscription request.
[0267] Here, the unsubscribe request may include the event identifier and / or access type information in the above embodiment.
[0268] Step S102: NEF sends a response message of a subscription request or a response message of a cancellation subscription request to AF;
[0269] Here, the response message of the subscription request is used to confirm that the NEF has received the subscription request; the response message of the unsubscribe request is used to confirm that the NEF has received the unsubscribe request.
[0270] Step S103: The NEF determines one or more NSACFs associated with the slice identifier of the network slice;
[0271] In an optional embodiment, if the subscription request or the unsubscription request carries a slice identifier, the NEF queries one or more NSACFs associated with the slice identifier based on the slice identifier; or, if the subscription request or the unsubscription request carries an application identifier, the NEF determines the slice identifier based on the application identifier, and based on the slice identifier, queries one or more NSACFs associated with the slice identifier.
[0272] Step S104: NEF sends a subscription request or a cancellation request to NSACF1;
[0273] In an optional embodiment, if NEF determines that the slice identifier is associated with NSACF1, a second subscription request or a cancellation request is sent to NSACF1. Here, the second subscription request may be the first subscription request, or may be a request determined based on the first subscription request.
[0274] In an optional embodiment, if the NEF fails to determine the slice identifier, it sends a subscription request or a cancel subscription request to an NSACF that supports the subscription function among NSACF1, NSACF1, ... and NSACF n; or, if the NEF determines that the slice identifier is associated with multiple NSACFs among NSACF1, NSACF1, ... and NSACF n, it sends a subscription request or a cancel subscription request to the multiple NSACFs.
[0275] Step S105: NSACF1 sends a response message of a subscription request or a response message of a cancellation subscription request to NEF;
[0276] Step S106: NSACF1 determines that the trigger reporting condition is met;
[0277] In an optional embodiment, if NSACF1 determines that NSACF1 currently reaches a threshold for triggering reporting, or reaches the end time of each predetermined time interval, or determines that the subscription request includes an immediate reporting flag, then it determines that the triggering reporting condition is met.
[0278] Step S107: NSACF1 sends a notification of event report;
[0279] In an optional embodiment, NSACF1 sends a notification of the first event report, wherein the notification carries event report registration statistics and / or session statistics, and / or access type information.
[0280] Step S108: Optionally, the NEF aggregates multiple first event reports;
[0281] In an optional embodiment, if multiple NSACFs send first event reports to the NEF, the multiple first event reports are aggregated to obtain a second event report, which contains aggregated statistical information after the statistical data contained in the multiple first event reports are aggregated.
[0282] Step S109: NEF sends a notification of event report to AF.
[0283] In an optional embodiment, if the NEF does not execute step S108, a notification of the first event report is sent to the AF; if the NEF executes step S108, a notification of the second event report is sent to the AF.
[0284] like Fig.11As shown, the embodiment of the present disclosure provides a slice event subscription reporting device based on access type, which is applied to AF, including:
[0285] The first sending module 51 is configured to send a first subscription request to NEF to request an event report of a network slice associated with an access type; wherein the first subscription request includes access type information indicating the access type, and the first subscription request is used to instruct NEF to send a second subscription request to NSACF to subscribe to the event report requested by the first subscription request.
[0286] An embodiment of the present disclosure provides a slice event subscription and reporting device based on access type, which is applied to AF, including: a first receiving module, configured to receive a second event report returned by NEF, wherein the second event report is determined based on multiple first event reports; wherein the first event report includes: registration statistics of UEs registered to the network slice and / or session statistics of sessions established by the network slice; the second event report includes: aggregated statistical information after the statistical data contained in multiple first event reports are aggregated.
[0287] An embodiment of the present disclosure provides a slice event subscription and reporting device based on access type, applied to AF, including: a first receiving module, configured to receive a second event report returned by NEF, wherein the second event report includes: aggregated statistical information after aggregating statistical data contained in multiple first event reports.
[0288] An embodiment of the present disclosure provides a slice event subscription reporting device based on access type, which is applied to AF, including: a first sending module 51, configured to send a cancellation request to NEF, wherein the cancellation request is used to cancel the subscription to the reporting of event reports of network slices associated with the access type.
[0289] In some embodiments, the access type information indicates at least one of the following:
[0290] Access type, where the access type indicates a 3GPP type and / or a non-3GPP type;
[0291] Wireless access type;
[0292] Access auxiliary information.
[0293] In some embodiments, the access type information indicates at least one of the following:
[0294] Access type;
[0295] Wireless access type;
[0296] Access auxiliary information.
[0297] In some embodiments, the access type includes: 3GPP type and / or non-3GPP type.
[0298] In some embodiments, the wireless access type includes at least one of the following:
[0299] NR access type, EUTRA access type, WLAN access type, VIRTUAL access type, NBIOT access type, WIRELINE access type, WIRELINE_CABLE access type, WIRELINE_BBF access type, LTE-M access type, NR_U access type, EUTRA_U access type, TRUSTED_N3GA access type, TRUSTED_WLAN access type, UTRA access type, GERA access type, NR_LEO access type, NR_MEO access type, NR_GEO access type and NR_OTHER_SA access type.
[0300] In some embodiments, the first subscription request or the second subscription request includes: an event identifier indicating an event report.
[0301] In some embodiments, the event report includes at least one of the following:
[0302] Number of registered UEs;
[0303] The number of established protocol data unit (PDU) sessions;
[0304] The ratio of the number of registered UEs to the maximum number of allowed registered UEs;
[0305] The ratio of the number of established PDU sessions to the maximum number of PDU sessions allowed to be established.
[0306] In some embodiments, the first subscription request includes one of the following:
[0307] A slice identifier indicating a network slice;
[0308] Application identifier; the application identifier is used to determine the slice identifier associated with the application identifier;
[0309] Among them, the slice identifier is used by NEF to determine one or more NSACFs associated with the slice identifier.
[0310] In some embodiments, the first subscription request includes:
[0311] The slice identifier and the data network name DNN corresponding to the slice identifier.
[0312] In some embodiments, the first subscription request includes report configuration information; the report configuration information includes at least one of the following:
[0313] Threshold used to trigger reporting;
[0314] a predetermined time interval for periodic reporting;
[0315] An immediate reporting flag, wherein the immediate reporting flag is used to indicate that a subscription request is received and reported.
[0316] It should be noted that those skilled in the art can understand that the device provided in the embodiments of the present disclosure can be executed alone or together with some devices in the embodiments of the present disclosure or some devices in related technologies.
[0317] Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.
[0318] like Fig.12 As shown, the embodiment of the present disclosure provides a slice event subscription reporting device based on access type, which is applied to NEF, including:
[0319] The second receiving module 61 is configured to receive a first subscription request sent by the AF; wherein the first subscription request is used to request an event report of a network slice associated with an access type; wherein the first subscription request includes access type information indicating the access type;
[0320] The second sending module 62 is configured to send a second subscription request to the network slice admission control function NSACF, wherein the second subscription request is used to subscribe to the event report requested by the first subscription request.
[0321] In some embodiments, sending a second subscription request to a network slice admission control function NSACF includes one of the following:
[0322] Sending a second subscription request to one or more NSACFs associated with the network slice;
[0323] A second subscription request is sent to the NSACF that supports the subscription function.
[0324] An embodiment of the present disclosure provides a slice event subscription reporting method based on access type, which is applied to NEF, including: a second sending module 62, configured to send a second subscription request to one or more NSACFs associated with the network slice.
[0325] An embodiment of the present disclosure provides a slice event subscription reporting method based on access type, which is applied to NEF, including: a second sending module 62, configured to send a second subscription request to an NSACF supporting the subscription function.
[0326] In some embodiments, the first subscription request includes:
[0327] a slice identifier indicating a network slice; or,
[0328] Indicates a slice ID of the network slice and a data network name DNN corresponding to the slice ID.
[0329] In some embodiments, the first subscription request includes an application identifier.
[0330] An embodiment of the present disclosure provides a slice event subscription and reporting method based on access type, which is applied to NEF and includes: a processing module, which is configured to determine a slice identifier indicating a network slice based on an application identifier.
[0331] An embodiment of the present disclosure provides a slice event subscription reporting method based on access type, which is applied to NEF, including: a processing module, which is configured to obtain a slice identifier corresponding to the application identifier from a network registration function NRF based on an application identifier.
[0332] An embodiment of the present disclosure provides a slice event subscription and reporting method based on access type, which is applied to NEF and includes: a processing module, which is configured to determine the slice identifier based on the application identifier and configuration information, wherein the configuration information includes the correspondence between the application identifier and the slice identifier.
[0333] The embodiment of the present disclosure provides a slice event subscription reporting method based on access type, which is applied to NEF, including: a second receiving module 61, configured to receive a subscription cancellation request sent by AF;
[0334] The second sending module 62 is configured to send a cancellation request to the NSACF; wherein the cancellation request is used to cancel the subscription to the event report of the network slice associated with the access type.
[0335] The embodiment of the present disclosure provides a slice event subscription reporting method based on access type, which is applied to NEF, including: a second receiving module 61, configured to receive a second event report sent by NSACF; wherein the second event report is determined by NSACF based on multiple first event reports; the first event report includes: registration statistics of UEs registered to the network slice and / or session statistics of sessions established by the network slice; the second event report includes aggregated statistical information after the statistical data of multiple first event reports are aggregated;
[0336] The second sending module 62 is configured to send a second event report to the AF.
[0337] The embodiment of the present disclosure provides a slice event subscription reporting method based on access type, which is applied to NEF, including: a second receiving module 61, configured to receive a first event report sent by NSACF;
[0338] A processing module is configured to determine a second event report based on the plurality of first event reports, wherein the second event report includes aggregated statistical information obtained by aggregating statistical data included in the plurality of first event reports;
[0339] The second sending module 62 is configured to send a second event report to the AF.
[0340] In some embodiments, the access type information indicates at least one of the following:
[0341] Access type, wherein the access type indicates a 3GPP type and / or a non-3GPP type;
[0342] Wireless access type;
[0343] Access auxiliary information.
[0344] In some embodiments, the wireless access type includes at least one of the following:
[0345] NR access type, EUTRA access type, WLAN access type, VIRTUAL access type, NBIOT access type, WIRELINE access type, WIRELINE_CABLE access type, WIRELINE_BBF access type, LTE-M access type, NR_U access type, EUTRA_U access type, TRUSTED_N3GA access type, TRUSTED_WLAN access type, UTRA access type, GERA access type, NR_LEO access type, NR_MEO access type, NR_GEO access type and NR_OTHER_SA access type.
[0346] In some embodiments, the event report includes at least one of the following:
[0347] Number of registered UEs;
[0348] The number of established protocol data unit (PDU) sessions;
[0349] The ratio of the number of registered UEs to the maximum number of allowed registered UEs;
[0350] The ratio of the number of established PDU sessions to the maximum number of PDU sessions allowed to be established.
[0351] In some embodiments, the second subscription request includes: report configuration information, wherein the report configuration information includes: at least one of the following:
[0352] Threshold used to trigger reporting;
[0353] a predetermined time interval for periodic reporting;
[0354] An immediate reporting flag, wherein the immediate reporting flag is used to indicate that a subscription request is received and reported.
[0355] It should be noted that those skilled in the art can understand that the device provided in the embodiments of the present disclosure can be executed alone or together with some devices in the embodiments of the present disclosure or some devices in related technologies.
[0356] Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.
[0357] like Fig.13 As shown, the embodiment of the present disclosure provides a slice event subscription reporting device based on access type, which is applied to NSACF, including:
[0358] The third receiving module 71 is configured to receive a second subscription request sent by the NEF; wherein the second subscription request is sent by the NEF based on the received first subscription request instruction; wherein the first subscription request includes access type information indicating an access type;
[0359] The third sending module 72 is configured to send, to the NEF, the event report requested by the first subscription request subscribed by the second subscription request.
[0360] An embodiment of the present disclosure provides a slice event subscription reporting device based on access type, applied to NSACF, including: a third sending module, configured to send a first event report to NEF, wherein the first event report includes: registration statistics of UEs registered to the network slice and / or session statistics of sessions established by the network slice.
[0361] The embodiment of the present disclosure provides a slice event subscription reporting device based on access type, which is applied to NSACF, including:
[0362] The third receiving module 71 is configured to obtain multiple first event reports, wherein the first event report includes: registration statistics of UEs registered to the network slice and / or session statistics of sessions established by the network slice;
[0363] A processing module is configured to determine a second event report based on the first event report; wherein the second event report includes aggregated statistical information obtained by aggregating statistical data included in a plurality of first event reports;
[0364] The third sending module 72 is configured to send a second event report to the NEF.
[0365] The embodiment of the present disclosure provides a slice event subscription reporting device based on access type, which is applied to NSACF, including: a third receiving module 71, configured to receive a subscription cancellation request sent by NEF;
[0366] The third sending module 72 is configured to determine not to report the event report associated with the access type based on the unsubscribe request.
[0367] In some embodiments, the second subscription request includes report configuration information; the report configuration information includes at least one of the following:
[0368] Threshold used to trigger reporting;
[0369] a predetermined time interval for periodic reporting;
[0370] An immediate reporting flag, wherein the immediate reporting flag is used to indicate that a subscription request is received and reported.
[0371] The embodiment of the present disclosure provides a slice event subscription reporting method based on access type, which is applied to NSACF, including: a third sending module 72, which is configured to do at least one of the following:
[0372] Based on the NSACF meeting the threshold for triggering reporting, an event report of the network slice associated with the access type is sent to the NEF;
[0373] Sending event reports of the network slice associated with the access type to the NEF based on a predetermined time interval;
[0374] Based on the immediate reporting flag included in the second subscription request, a network slice event report associated with the access type is sent to the NEF.
[0375] In some embodiments, the event report includes at least one of the following:
[0376] Number of registered UEs;
[0377] The number of established protocol data unit (PDU) sessions;
[0378] The ratio of the number of registered UEs to the maximum number of allowed registered UEs;
[0379] The ratio of the number of established PDU sessions to the maximum number of PDU sessions allowed to be established.
[0380] In some embodiments, the access type information indicates at least one of the following:
[0381] Access type, where the access type indicates a 3GPP type or a non-3GPP type;
[0382] Wireless access type;
[0383] Access auxiliary information.
[0384] In some embodiments, the wireless access type includes at least one of the following:
[0385] NR access type, EUTRA access type, WLAN access type, VIRTUAL access type, NBIOT access type, WIRELINE access type, WIRELINE_CABLE access type, WIRELINE_BBF access type, LTE-M access type, NR_U access type, EUTRA_U access type, TRUSTED_N3GA access type, TRUSTED_WLAN access type, UTRA access type, GERA access type, NR_LEO access type, NR_MEO access type, NR_GEO access type and NR_OTHER_SA access type.
[0386] It should be noted that those skilled in the art can understand that the device provided in the embodiments of the present disclosure can be executed alone or together with some devices in the embodiments of the present disclosure or some devices in related technologies.
[0387] Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.
[0388] The embodiment of the present disclosure provides a slice event subscription reporting device based on access type, including:
[0389] processor;
[0390] a memory for storing processor-executable instructions;
[0391] The processor is configured to implement the positioning method of any embodiment of the present disclosure when running the executable instructions.
[0392] In one embodiment, the slice event subscription reporting device based on the access type is applied to a communication device. In another embodiment, the slice event subscription reporting device based on the access type is a communication device.
[0393] In one embodiment, the communication device may include but is not limited to at least one of: a core network device, an access network device, and a UE. Here, the access network device includes: a base station. The core network device includes the AF, NEF, or NSACF in the above embodiment.
[0394] The processor may include various types of storage media, which are non-temporary computer storage media that can continue to memorize information stored thereon after the user device loses power.
[0395] The processor may be connected to the memory via a bus or the like to read the executable program stored in the memory, for example, Figures 2 to 10 At least one of the methods shown.
[0396] The present disclosure also provides a computer storage medium, which stores a computer executable program. When the executable program is executed by a processor, the positioning method of any embodiment of the present disclosure is implemented. Figures 2 to 10 At least one of the methods shown.
[0397] Regarding the device or storage medium in the above embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment of the method, and will not be elaborated here.
[0398] Fig.14 8 is a block diagram of a user device 800 according to an exemplary embodiment. For example, the user device 800 may be a mobile phone, a computer, a digital broadcast user device, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.
[0399] Reference Fig.14 , the user device 800 may include one or more of the following components: a processing component 802 , a memory 804 , a power component 806 , a multimedia component 808 , an audio component 810 , an input / output (I / O) interface 812 , a sensor component 814 , and a communication component 816 .
[0400] The processing component 802 generally controls the overall operation of the user device 800, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. The processing component 802 may include one or more processors 820 to execute instructions to complete all or part of the steps of the above-mentioned method. In addition, the processing component 802 may include one or more modules to facilitate the interaction between the processing component 802 and other components. For example, the processing component 802 may include a multimedia module to facilitate the interaction between the multimedia component 808 and the processing component 802.
[0401] The memory 804 is configured to store various types of data to support operations on the user device 800. Examples of such data include instructions for any application or method operating on the user device 800, contact data, phone book data, messages, pictures, videos, etc. The memory 804 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.
[0402] The power supply component 806 provides power to the various components of the user device 800. The power supply component 806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the user device 800.
[0403] The multimedia component 808 includes a screen that provides an output interface between the user device 800 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundaries of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 808 includes a front camera and / or a rear camera. When the user device 800 is in an operating mode, such as a shooting mode or a video mode, the front camera and / or the rear camera may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.
[0404] The audio component 810 is configured to output and / or input audio signals. For example, the audio component 810 includes a microphone (MIC), and when the user device 800 is in an operation mode, such as a call mode, a recording mode, and a speech recognition mode, the microphone is configured to receive an external audio signal. The received audio signal can be further stored in the memory 804 or sent via the communication component 816. In some embodiments, the audio component 810 also includes a speaker for outputting audio signals.
[0405] I / O interface 812 provides an interface between processing component 802 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include but are not limited to: home button, volume button, start button, and lock button.
[0406] The sensor assembly 814 includes one or more sensors for providing various aspects of status assessment for the user device 800. For example, the sensor assembly 814 can detect the open / closed state of the user device 800, the relative positioning of the components, such as the display and keypad of the user device 800, and the sensor assembly 814 can also detect the position change of the user device 800 or a component of the user device 800, the presence or absence of contact between the user and the user device 800, the orientation or acceleration / deceleration of the user device 800, and the temperature change of the user device 800. The sensor assembly 814 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor assembly 814 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 814 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
[0407] The communication component 816 is configured to facilitate wired or wireless communication between the user device 800 and other devices. The user device 800 can access a wireless network based on a communication standard, such as WiFi, 4G or 5G, or a combination thereof. In an exemplary embodiment, the communication component 816 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 816 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.
[0408] In an exemplary embodiment, the user device 800 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the above methods.
[0409] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 804 including instructions, and the instructions can be executed by the processor 820 of the user device 800 to perform the above method. For example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.
[0410] like Fig.15As shown, an embodiment of the present disclosure shows a structure of a base station. For example, the base station 900 can be provided as a network side device. Fig.15 The base station 900 includes a processing component 922, which further includes one or more processors, and a memory resource represented by a memory 932 for storing instructions executable by the processing component 922, such as an application. The application stored in the memory 932 may include one or more modules, each corresponding to a set of instructions. In addition, the processing component 922 is configured to execute instructions to perform any method of the aforementioned method applied in the base station.
[0411] The base station 900 may also include a power supply component 926 configured to perform power management of the base station 900, a wired or wireless network interface 950 configured to connect the base station 900 to a network, and an input / output (I / O) interface 958. The base station 900 may operate based on an operating system stored in the memory 932, such as Windows Server TM, Mac OS X TM, Unix TM, Linux TM, FreeBSD TM or the like.
[0412] Those skilled in the art will readily appreciate other embodiments of the present invention after considering the specification and practicing the invention disclosed herein. The present disclosure is intended to cover any variations, uses or adaptations of the present invention that follow the general principles of the present invention and include common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The description and examples are to be considered exemplary only, and the true scope and spirit of the present invention are indicated by the following claims.
[0413] It should be understood that the present invention is not limited to the exact construction that has been described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present invention is limited only by the appended claims.
Claims
1. A method for subscribing and reporting slice events based on access type, wherein: Executed by application functions AF, including: A first subscription request is sent to a network open function NEF to request an event report of a network slice associated with an access type; wherein the first subscription request includes access type information indicating the access type, and the first subscription request is used to instruct the NEF to send a second subscription request to a network slice admission function NSACF to subscribe to the event report requested by the first subscription request.
2. The method according to claim 1, wherein: The event report includes: a first event report and / or a second event report; The method comprises: Receive the second event report returned by NEF, wherein the second event report is determined based on multiple first event reports; wherein the first event report includes: registration statistics of UEs registered to the network slice and / or session statistics of sessions established by the network slice; the second event report includes: aggregated statistical information after aggregating the statistical data contained in multiple first event reports.
3. The method according to claim 1, wherein: The method further comprises: Send an unsubscribe request to the NEF, wherein the unsubscribe request is used to unsubscribe from reporting of the event report of the network slice associated with the access type.
4. The method according to any one of claims 1 to 3, wherein: The access type information indicates at least one of the following: Access type; Wireless access type; Access auxiliary information.
5. The method according to claim 4, wherein: The access type indicates at least one of the following: 3GPP type; Non-3GPP type; 3GPP type and non-3GPP type.
6. The method according to claim 4, wherein: The wireless access type includes at least one of the following: New air interface NR access type, evolved universal mobile communications system land wireless EUTRA type, wireless local area network WLAN access type, virtual network VIRTUAL access type, narrowband Internet of Things NBIOT access type, wired network WIRELINE access type, wired cable network WIRELINE_CABLE access type, wired broadband network WIRELINE_BBF access type, urban rail transit vehicle-ground integrated communication system LTE-M access type, new air interface unlicensed spectrum NR_U access type, evolved universal mobile communications system land unlicensed spectrum wireless EUTRA_U access type, trusted non-3GPP TRUSTED_N3GA type, trusted wireless local area network TRUSTED_WLAN access type, universal terrestrial wireless UTRA type, global mobile communications system edge wireless network GERA type, new air interface low orbit NR_LEO access type, new air interface medium and high orbit access NR_MEO access type, new air interface geostationary earth orbit access NR_GEO access type and other satellite access NR_OTHER_SA access type.
7. The method according to any one of claims 1 to 3, wherein: The incident report includes at least one of the following: Number of registered UEs; The number of established protocol data unit (PDU) sessions; The ratio of the number of registered UEs to the maximum number of allowed registered UEs; The ratio of the number of established PDU sessions to the maximum number of PDU sessions allowed to be established.
8. The method according to any one of claims 1 to 3, wherein: The first subscription request includes one of the following: A slice identifier indicating a network slice; Application identifier; the application identifier is used to determine the slice identifier associated with the application identifier; The slice identifier is used by the NEF to determine one or more NSACFs associated with the slice identifier.
9. The method according to any one of claims 1 to 3, wherein: The first subscription request includes: The slice identifier, and the data network name DNN corresponding to the slice identifier.
10. The method according to any one of claims 1 to 3, wherein: The first subscription request includes report configuration information, wherein the report configuration information includes at least one of the following: Threshold used to trigger reporting; a predetermined time interval for periodic reporting; An immediate reporting flag, wherein the immediate reporting flag is used to indicate that the subscription request is received and reported.
11. A method for subscribing and reporting slice events based on access type, wherein: Executed by the network open function NEF, including: Receiving a first subscription request sent by an application function AF; wherein the first subscription request is used to request an event report of a network slice associated with an access type; wherein the first subscription request includes access type information indicating the access type; A second subscription request is sent to the network slice admission control function NSACF, wherein the second subscription request is used to subscribe to the event report requested by the first subscription request.
12. The method according to claim 11, wherein: The sending a second subscription request to the network slice admission control function NSACF includes one of the following: Sending the second subscription request to one or more NSACFs associated with the network slice; Send the second subscription request to the NSACF supporting the subscription function.
13. The method according to claim 12, wherein: The first subscription request includes: A slice identifier indicating the network slice; or, Indicates a slice identifier of the network slice and a data network name DNN corresponding to the slice identifier.
14. The method according to claim 12, wherein: The first subscription request includes an application identifier; The method includes: determining a slice identifier indicating the network slice based on the application identifier.
15. The method according to claim 14, wherein: The determining, based on the application identifier, a slice identifier indicating a network slice, includes one of the following: Based on the application identifier, obtaining the slice identifier corresponding to the application identifier from a network registration function NRF; Based on the application identifier and configuration information, determine the slice identifier, wherein the configuration information includes a correspondence between the application identifier and the slice identifier.
16. The method according to any one of claims 11 to 15, wherein: The method comprises: Receiving a subscription cancellation request sent by the AF; Send the unsubscribe request to the NSACF; wherein the unsubscribe request is used to unsubscribe from the reporting of the event report of the network slice associated with the access type.
17. The method according to any one of claims 11 to 15, wherein: The event report includes: a first event report and / or a second event report; The method comprises: Receive the second event report sent by the NSACF; wherein the second event report is determined by the NSACF based on multiple first event reports; the first event report includes: registration statistics of UEs registered to the network slice and / or session statistics of sessions established by the network slice; the second event report includes aggregated statistical information after the statistical data included in multiple first event reports are aggregated; Send the second event report to the AF.
18. The method according to any one of claims 11 to 15, wherein: The event report includes: a first event report and / or a second event report; The method comprises: Receiving the first event report sent by the NSACF; Determine the second event report based on the plurality of first event reports, wherein the second event report includes aggregated statistical information obtained by aggregating statistical data included in the plurality of first event reports; Send the second event report to the AF.
19. The method according to any one of claims 11 to 15, wherein: The access type information indicates at least one of the following: Access type; Wireless access type; Access auxiliary information.
20. The method according to claim 19, wherein: The access type indicates at least one of the following: 3GPP type; Non-3GPP type; 3GPP type and non-3GPP type.
21. The method according to claim 19, wherein: The wireless access type includes at least one of the following: New air interface NR access type, evolved universal mobile communications system land wireless EUTRA type, wireless local area network WLAN access type, virtual network VIRTUAL access type, narrowband Internet of Things NBIOT access type, wired network WIRELINE access type, wired cable network WIRELINE_CABLE access type, wired broadband network WIRELINE_BBF access type, urban rail transit vehicle-ground integrated communication system LTE-M access type, new air interface unlicensed spectrum NR_U access type, evolved universal mobile communications system land unlicensed spectrum wireless EUTRA_U access type, trusted non-3GPP TRUSTED_N3GA type, trusted wireless local area network TRUSTED_WLAN access type, universal terrestrial wireless UTRA type, global mobile communications system edge wireless network GERA type, new air interface low orbit NR_LEO access type, new air interface medium and high orbit access NR_MEO access type, new air interface geostationary earth orbit access NR_GEO access type and other satellite access NR_OTHER_SA access type.
22. The method according to any one of claims 11 to 15, wherein the event report comprises at least one of the following: Number of registered UEs; The number of established protocol data unit (PDU) sessions; The ratio of the number of registered UEs to the maximum number of allowed registered UEs; The ratio of the number of established PDU sessions to the maximum number of PDU sessions allowed to be established.
23. The method according to any one of claims 11 to 15, wherein: The second subscription request includes: report configuration information, wherein the report configuration information includes: at least one of the following: Threshold used to trigger reporting; a predetermined time interval for periodic reporting; An immediate reporting flag, wherein the immediate reporting flag is used to indicate that the subscription request is received and reported.
24. A method for subscribing and reporting slice events based on access type, wherein: Executed by the network slice admission control function NSACF, including: Receiving a second subscription request sent by a network open function NEF; wherein the second subscription request is sent by the NEF based on the received first subscription request instruction; wherein the first subscription request is used to request an event report of a network slice associated with an access type, wherein the first subscription request includes access type information indicating the access type; Sending, to the NEF, an event report requested by the first subscription request to which the second subscription request subscribes.
25. The method according to claim 24, wherein: The event report includes: a first event report; The sending, to the NEF, the event report requested by the first subscription request subscribed to by the second subscription request, comprises: Send the first event report to the NEF; wherein the first event report includes: registration statistics of UEs registered to the network slice and / or session statistics of sessions established by the network slice.
26. The method according to claim 24, wherein: The event report includes: a first event report and / or a second event report; The sending, to the NEF, the event report requested by the first subscription request subscribed to by the second subscription request, comprises: Obtain multiple first event reports; wherein the first event report includes: registration statistics of UEs registered to the network slice and / or session statistics of sessions established by the network slice; Based on the first event report, determining the second event report; wherein the second event report includes aggregated statistical information obtained by aggregating statistical data included in a plurality of the first event reports; The second event report is sent to the NEF.
27. The method according to claim 24, wherein: The method comprises: Receiving a unsubscribe request sent by the NEF; Based on the unsubscribe request, determine not to report the event report associated with the access type.
28. The method of claim 24, wherein: The second subscription request includes report configuration information; the report configuration information includes at least one of the following: Threshold used to trigger reporting; a predetermined time interval for periodic reporting; An immediate reporting flag, wherein the immediate reporting flag is used to indicate that the subscription request is received and reported.
29. The method according to claim 28, wherein: The sending, to the NEF, an event report of the network slice associated with the access type subscribed to by the second subscription request, comprises one of the following: Sending, based on the NSACF satisfying a threshold for triggering reporting, the event report of the network slice associated with the access type to the NEF; Sending, based on the predetermined time interval, the event report of the network slice associated with the access type to the NEF; Based on the immediate reporting flag included in the second subscription request, the event report of the network slice associated with the access type is sent to the NEF.
30. The method according to any one of claims 24 to 29, wherein: The incident report includes at least one of the following: Number of registered UEs; The number of established protocol data unit (PDU) sessions; The ratio of the number of registered UEs to the maximum number of allowed registered UEs; The ratio of the number of established PDU sessions to the maximum number of PDU sessions allowed to be established.
31. The method according to any one of claims 24 to 29, wherein: The access type information indicates at least one of the following: Access type, wherein the access type indicates a 3GPP type or a non-3GPP type; Wireless access type; Access auxiliary information.
32. The method of claim 31 , wherein the access type indicates at least one of the following: 3GPP type; Non-3GPP type; 3GPP type and non-3GPP type.
33. The method of claim 32, wherein: The wireless access type includes at least one of the following: New air interface NR access type, evolved universal mobile communications system land wireless EUTRA type, wireless local area network WLAN access type, virtual network VIRTUAL access type, narrowband Internet of Things NBIOT access type, wired network WIRELINE access type, wired cable network WIRELINE_CABLE access type, wired broadband network WIRELINE_BBF access type, urban rail transit vehicle-ground integrated communication system LTE-M access type, new air interface unlicensed spectrum NR_U access type, evolved universal mobile communications system land unlicensed spectrum wireless EUTRA_U access type, trusted non-3GPP TRUSTED_N3GA type, trusted wireless local area network TRUSTED_WLAN access type, universal terrestrial wireless UTRA type, global mobile communications system edge wireless network GERA type, new air interface low orbit NR_LEO access type, new air interface medium and high orbit access NR_MEO access type, new air interface geostationary earth orbit access NR_GEO access type and other satellite access NR_OTHER_SA access type.
34. A slice event subscription reporting device based on access type, wherein: Applied to application functions AF, including: The first sending module is configured to send a first subscription request to a network open function NEF, wherein the first subscription request includes access type information indicating an access type; the first subscription request is used by the NEF to send a second subscription request to a network slice admission function NSACF, wherein the second subscription request is used to subscribe to event reports of network slices associated with the access type requested by the first subscription request.
35. A slice event subscription reporting device based on access type, wherein: Applied to the network open function NEF, including: A second receiving module is configured to receive a first subscription request sent by the application function AF, wherein the first subscription request includes access type information indicating an access type; The second sending module is configured to send a second subscription request to the network slice admission control function NSACF, wherein the second subscription request is used to subscribe to the event report of the network slice associated with the access type requested by the first subscription request.
36. A slice event subscription reporting device based on access type, wherein: Applied to the network slice admission control function NSACF, including: A third receiving module is configured to receive a second subscription request sent by a network open function NEF; wherein the second subscription request is sent by the NEF based on the received first subscription request; wherein the first subscription request includes access type information indicating an access type; The third sending module is configured to send an event report of the network slice associated with the access type subscribed to by the second subscription request to the NEF.
37. A slice event subscription reporting device based on access type, wherein: include: processor; a memory for storing instructions executable by the processor; The processor is configured to: when running the executable instructions, implement the access type-based slice event subscription reporting method described in any one of claims 1 to 10, or claims 11 to 23, or claims 24 to 33.
38. A computer storage medium, wherein: The computer storage medium stores a computer executable program, which, when executed by a processor, implements the access type-based slice event subscription reporting method described in any one of claims 1 to 10, or claims 11 to 23, or claims 24 to 33.
