Information processing method, and network element, communication device, communication system and storage medium

By introducing a network slicing access control mechanism into the communication system and using group identifiers to manage network resources, we solve the problem of difficulty in effectively managing multi-modal data flows of XR services with existing technologies, and achieve the improvement of user experience and the optimal use of network resources. .

WO2025010691A1PCT designated stage expired Publication Date: 2025-01-16BEIJING XIAOMI MOBILE SOFTWARE CO LTD

Patent Information

Application Number
PCT/CN2023/107095
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-07-12
Publication Date
2025-01-16

AI Technical Summary

Technical Problem

Existing communication technologies are difficult to effectively manage and control multimodal data flows in augmented reality (AR) and virtual reality (VR) services, resulting in complex network transmission requirements and inconsistent user experience.

Method used

By introducing the Network Slice Admission Control (NSAC) mechanism into the communication system and using the group ID to manage and allocate network resources, the consistency of the admission control policy for related terminals or PDU sessions is achieved.

Benefits of technology

It improves user experience, ensures the stability and consistency of XR services, optimizes the use of network resources through hierarchical access control, and meets the needs of XR services for high bandwidth and low latency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2023107095_16012025_PF_FP_ABST
    Figure CN2023107095_16012025_PF_FP_ABST
Patent Text Reader

Abstract

Provided in the embodiments of the present disclosure are an information processing method, and a network element, a communication device, a communication system and a storage medium. The information processing method, which is executed by a first network element, comprises: sending first information to a second network element, wherein the first information is used for instructing the second network element to execute network slice admission control (NSAC) on a terminal, which requests registration, or a data packet unit (PDU) session, which requests activation, wherein the first information comprises a group identifier (Group ID) associated with the terminal or the PDU session.
Need to check novelty before this filing date? Find Prior Art

Description

Information processing method, network element, communication equipment, communication system and storage medium Technical Field

[0001] The present disclosure relates to the field of communication technologies, and in particular to an information processing method and a network element, a communication device, a communication system, and a storage medium. Background Art

[0002] Mobile media services, extended reality (XR) services such as cloud augmented reality (AR) or virtual reality (VR), cloud gaming, and video-based remote control of machines or drones are expected to contribute increasingly higher traffic to communication networks (such as 5G networks).

[0003] In addition to audio and video streams, XR services also involve multimodal data streams, such as data streams for biotactile perception. This multimodal data describes the same service or application, input from the same device or different devices (including sensors), and may be output to one or more destination devices. The various data streams in multimodal data often have certain, or even strong, correlations, such as the synchronization of audio and video streams, or the synchronization of touch and vision. The data streams of these media services, the relationships between the data streams, and the network transmission requirements of these service data streams all share common characteristics. The effective identification and utilization of these characteristics will facilitate network and service transmission and control, as well as service assurance and user experience.

[0004] Summary of the Invention

[0005] With the rapid development of communication technologies, there is a need to provide users with enhanced communication capabilities.

[0006] The embodiments of the present disclosure provide an information processing method, a network element, a communication device, and a storage medium.

[0007] According to a first aspect of an embodiment of the present disclosure, there is provided an information processing method, which is performed by a first network element. The method includes:

[0008] Sending first information to a second network element; wherein the first information is used to instruct the second network element to perform network slice admission control (NSAC) on a terminal requesting registration or a data packet unit (PDU) session requesting activation; wherein the first information includes a group identifier (Group ID) associated with the terminal or the PDU session.

[0009] According to a second aspect of an embodiment of the present disclosure, there is provided an information processing method, which is performed by a second network element. The method includes:

[0010] Receive first information sent by a first network element; wherein the first information is used to instruct the second network element to perform network slice admission control (NSAC) on a terminal requesting registration or a data packet unit (PDU) session requesting activation; wherein the first information includes a group identifier associated with the terminal or the PDU session.

[0011] According to a third aspect of an embodiment of the present disclosure, there is provided an information processing method, which is performed by a third network element. The method includes:

[0012] Sending first information to a first network element, wherein the first information is used to instruct the second network element to perform network slice admission control (NSAC) on a terminal requesting registration; wherein the first information includes a group identifier associated with the terminal.

[0013] According to a fourth aspect of an embodiment of the present disclosure, there is provided an information processing method, which is performed by a fourth network element. The method includes:

[0014] Sending first information to a first network element, wherein the first information is used to instruct the second network element to perform network slice admission control (NSAC) on a data packet unit (PDU) session requested to be activated; wherein the first information includes a group identifier associated with the PDU session.

[0015] According to a fifth aspect of an embodiment of the present disclosure, there is provided an information processing method, which is performed by a communication system, the method comprising:

[0016] A first network element sends first information to a second network element; wherein the first information is used to instruct the second network element to perform network slice admission control (NSAC) on a terminal requesting registration or a data packet unit (PDU) session requesting activation; wherein the first information includes a group identifier associated with the terminal or the PDU session.

[0017] According to a sixth aspect of an embodiment of the present disclosure, a first network element is provided, wherein the first network element includes:

[0018] A sending module is configured to send first information to a second network element; wherein the first information is used to instruct the second network element to perform network slice admission control (NSAC) on a terminal requested to be registered or a data packet unit (PDU) session requested to be activated; wherein the first information includes a group identifier associated with the terminal or the PDU session.

[0019] According to a seventh aspect of an embodiment of the present disclosure, a second network element is provided, wherein the second network element includes:

[0020] A receiving module is configured to receive first information sent by a first network element; wherein the first information is used to instruct the second network element to perform network slice admission control (NSAC) on a terminal requesting registration or a data packet unit (PDU) session requesting activation; wherein the first information includes a group identifier associated with the terminal or the PDU session.

[0021] According to an eighth aspect of an embodiment of the present disclosure, a third network element is provided, wherein the third network element includes:

[0022] A sending module is configured to send first information to a first network element, wherein the first information is used to instruct the second network element to perform network slice admission control (NSAC) on a registered terminal; wherein the first information includes a group identifier associated with the terminal.

[0023] According to a ninth aspect of an embodiment of the present disclosure, a fourth network element is provided, wherein the fourth network element includes:

[0024] A sending module is configured to send first information to a first network element, wherein the first information is used to instruct the second network element to perform network slice admission control (NSAC) on a data packet unit (PDU) session requested to be activated; wherein the first information includes a group identifier associated with the PDU session.

[0025] According to the tenth aspect of an embodiment of the present disclosure, a communication system is provided, wherein the communication system includes a first network element, a second network element, a third network element and a fourth network element, the first network element is configured to implement the information processing method provided by the first aspect, the second network element is configured to implement the information processing method provided by the second aspect, the third network element is configured to implement the information processing method provided by the third aspect, and the fourth network element is configured to implement the information processing method provided by the fourth aspect.

[0026] According to an eleventh aspect of the embodiments of the present disclosure, a communication device is provided, wherein the communication device includes:

[0027] one or more processors;

[0028] The processor is used to call instructions to enable the communication device to execute the information processing method provided by the first aspect, the second aspect, the third aspect or the fourth aspect.

[0029] According to the twelfth aspect of an embodiment of the present disclosure, a storage medium is provided, wherein the storage medium stores instructions, and when the instructions are executed on a communication device, the communication device executes the information processing method provided by the first aspect, the second aspect, the third aspect or the fourth aspect.

[0030] It should be understood that the foregoing general description and the following detailed description are merely exemplary and explanatory and are not restrictive of the embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present invention and, together with the description, serve to explain the principles of the embodiments of the present invention.

[0032] FIG1a is a schematic diagram showing an architecture of a communication system according to an exemplary embodiment;

[0033] FIG1b is a schematic diagram showing the architecture of a 5G communication system according to an exemplary embodiment;

[0034] FIG2a is a schematic flow chart showing an information processing method according to an exemplary embodiment;

[0035] FIG2 b is a schematic flow chart showing an information processing method according to an exemplary embodiment;

[0036] FIG2c is a schematic flow chart showing an information processing method according to an exemplary embodiment;

[0037] FIG3a is a schematic flow chart showing an information processing method according to an exemplary embodiment;

[0038] FIG3 b is a schematic flow chart showing an information processing method according to an exemplary embodiment;

[0039] FIG3 c is a schematic flow chart showing an information processing method according to an exemplary embodiment;

[0040] FIG3 d is a schematic flow chart showing an information processing method according to an exemplary embodiment;

[0041] FIG4a is a schematic flow chart showing an information processing method according to an exemplary embodiment;

[0042] FIG4 b is a schematic flow chart showing an information processing method according to an exemplary embodiment;

[0043] FIG4c is a schematic flow chart showing an information processing method according to an exemplary embodiment;

[0044] FIG4 d is a schematic flow chart showing an information processing method according to an exemplary embodiment;

[0045] FIG5a is a schematic flow chart showing an information processing method according to an exemplary embodiment;

[0046] FIG5 b is a schematic flow chart showing an information processing method according to an exemplary embodiment;

[0047] FIG5c is a schematic flow chart showing an information processing method according to an exemplary embodiment;

[0048] FIG5 d is a schematic flow chart showing an information processing method according to an exemplary embodiment;

[0049] FIG6 is a flow chart showing an information processing method according to an exemplary embodiment;

[0050] FIG7 a is a schematic flow chart showing an information processing method according to an exemplary embodiment;

[0051] FIG7 b is a schematic flow chart showing an information processing method according to an exemplary embodiment;

[0052] FIG7c is a schematic flow chart showing an information processing method according to an exemplary embodiment;

[0053] FIG8a is a schematic structural diagram of a first network element according to an exemplary embodiment;

[0054] FIG8b is a schematic structural diagram of a second network element according to an exemplary embodiment;

[0055] FIG8c is a schematic structural diagram of a third network element according to an exemplary embodiment;

[0056] FIG8d is a schematic structural diagram of a fourth network element according to an exemplary embodiment;

[0057] FIG9a is a schematic structural diagram of a UE according to an exemplary embodiment;

[0058] Fig. 9b is a schematic structural diagram of a communication device according to an exemplary embodiment. DETAILED DESCRIPTION

[0059] Embodiments of the present disclosure provide an information processing method, a network element, a communication device, a communication system, and a storage medium.

[0060] In a first aspect, an embodiment of the present disclosure provides an information processing method, performed by a first network element, the method including:

[0061] Sending first information to a second network element; wherein the first information is used to instruct the second network element to perform network slice admission control (NSAC) on a terminal requesting registration or a data packet unit (PDU) session requesting activation; wherein the first information includes a group identifier associated with the terminal or the PDU session.

[0062] In the above embodiment, since the first information includes the group identifier associated with the terminal or PDU session, the second network element can at least consider the group identifier associated with the terminal or PDU session when using the first information to perform network slice admission control on the terminal requesting registration or the PDU session requesting activation. This can achieve consistency in the admission control policy for the relevant terminals or PDU sessions in the network slice and improve the user experience.

[0063] With reference to some embodiments of the first aspect, in some embodiments, sending the first information to the second network element includes:

[0064] receiving a first request sent by a third network element, where the first request is used to update the number of registered terminals, and the first request includes the first information;

[0065] A second request is sent to the second network element, where the second request includes the first information.

[0066] In the above embodiment, the first network element sends a second request including the first information to the second network element, so that the second network element can perform network slice admission control on the terminal requesting registration. In this way, through hierarchical admission control, consistency of admission control policies for related terminals in the network slice can be achieved, thereby improving user experience.

[0067] With reference to some embodiments of the first aspect, in some embodiments, sending the first information to the second network element includes:

[0068] receiving a third request sent by a fourth network element, where the third request is used to update the number of activated PDU sessions, and the third request includes the first information;

[0069] Send a fourth request to the second network element, where the fourth request includes the first information.

[0070] In the above embodiment, the first network element sends a fourth request including the first information to the second network element, so that the second network element can perform network slice admission control on the PDU session requested to be activated. In this way, through hierarchical admission control, consistency of admission control policies for related PDU sessions in the network slice can be achieved, thereby improving user experience.

[0071] With reference to some embodiments of the first aspect, in some embodiments, sending the first information to the second network element includes:

[0072] The number of registered terminals of the network slice of the first network element reaches or does not reach the maximum number of registered terminals of the network slice, and the first information is sent to the second network element.

[0073] In the above embodiment, regardless of whether the number of registered terminals in the network slice of the first network element reaches the maximum number of registered terminals in the network slice, the first network element will send a request message including the first information to the second network element. In this way, through hierarchical access control, the second network element uniformly executes network slice access control, thereby achieving consistency in the access control policies for relevant terminals in the network slice and improving user experience.

[0074] With reference to some embodiments of the first aspect, in some embodiments, sending the first information to the second network element includes:

[0075] The number of registered terminal groups of the network slice of the first network element reaches the maximum number of registered terminal groups of the network slice, and the first information is sent to the second network element; and / or,

[0076] The number of PDU session groups of the network slice of the first network element reaches the maximum number of PDU session groups of the network slice, and the first information is sent to the second network element.

[0077] In the above embodiment, network slice admission control is performed based on the number of registered terminal groups in the network slice. When the capacity of the local first network element is exceeded, admission control is requested from the second network element with higher capacity. In this way, through hierarchical admission control, consistency of admission control policies for related terminals in the network slice is achieved, thereby improving user experience.

[0078] In the above embodiment, network slice admission control is performed based on the number of PDU session groups in the network slice. When the number exceeds the capacity of the local first network element, admission control is requested from the second network element with higher capacity. In this way, through hierarchical admission control, consistency of admission control policies for related PDU sessions in the network slice is achieved, thereby improving user experience.

[0079] With reference to some embodiments of the first aspect, in some embodiments, sending the second request to the second network element includes:

[0080] The number of registered terminal groups of the network slice of the first network element reaches the maximum number of registered terminal groups of the network slice, and the second request is sent to the second network element.

[0081] In the above embodiment, network slice admission control is performed based on the number of registered terminal groups in the network slice. When the capacity of the local first network element is exceeded, admission control is requested from the second network element with higher capacity. In this way, through hierarchical admission control, consistency of admission control policies for related terminals in the network slice is achieved, thereby improving user experience.

[0082] With reference to some embodiments of the first aspect, in some embodiments, sending the first information to the second network element includes:

[0083] The number of PDU sessions of the network slice of the first network element reaches or does not reach the maximum PDU session number of the network slice, and the first information is sent to the second network element.

[0084] With reference to some embodiments of the first aspect, in some embodiments, sending the fourth request to the second network element includes:

[0085] The number of PDU sessions of the network slice of the first network element reaches or does not reach the maximum number of PDU sessions of the network slice, and the fourth request is sent to the second network element.

[0086] In the above embodiment, regardless of whether the number of PDU sessions of the network slice of the first network element reaches the maximum number of PDU sessions of the network slice, the first network element will send a request message including the first information to the second network element. In this way, through hierarchical access control, the second network element uniformly executes network slice access control, thereby achieving consistency in the access control policy for related PDU sessions in the network slice and improving user experience.

[0087] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0088] Receive a first response corresponding to the second request sent by the second network element; wherein the first response includes second information, and the second information is used to update the maximum number of registered terminals of the network slice of the first network element.

[0089] In the above embodiment, the maximum number of registered terminals of the network slice of the first network element is updated through the second network element indication, thereby achieving flexible adjustment of the capabilities of the first network element by the second network element, while achieving consistency of the admission control policy for the relevant terminals in the network slice and improving the flexibility of the admission control.

[0090] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0091] Receive a second response corresponding to the fourth request sent by the second network element; wherein the second response includes third information, and the third information is used to update the maximum PDU session number of the network slice of the first network element.

[0092] In the above embodiment, the maximum number of PDU sessions of the network slice of the first network element is updated through the second network element indication, thereby achieving flexible adjustment of the capabilities of the first network element by the second network element, while achieving consistency of the admission control policy for related PDU sessions in the network slice, and improving the flexibility of admission control.

[0093] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0094] Sending fourth information to the second network element; wherein, the fourth information is used to indicate the remaining quota or used quota in the NSAC quota allocated by the second network element to the first network element; the NSAC quota is used to indicate: at least one of the maximum number of registered terminal groups and the maximum number of PDU session groups of the network slice of the first network element.

[0095] In the above embodiment, the first network element sends the remaining quota or the used quota in the NSAC quota to the second network element, so that the second network element can flexibly adjust the NSAC quota allocated to the first network element, thereby improving the flexibility of admission control.

[0096] With reference to some embodiments of the first aspect, in some embodiments, sending fourth information to the second network element includes:

[0097] The fourth information is sent to the second network element according to the subscription request from the second network element, wherein the subscription request is used to subscribe the remaining quota or the used quota in the NSAC quota to the first network element.

[0098] In the above embodiment, the first network element sends the remaining quota or used quota in the NSAC quota to the second network element based on the subscription request of the second network element, which can reduce the situation where the first network element actively sends the real-time remaining quota or used quota and causes heavy network load.

[0099] In combination with some embodiments of the first aspect, in some embodiments, the first network element is a local network slice admission control function (NSACF) network element, and the second network element is a main NSACF network element;

[0100] The third network element is the access and mobility management function (AMF) network element, and the fourth network element is the session management function (SMF) network element.

[0101] In the above embodiment, through the hierarchical architecture of local NSACF network elements and master NSACF network elements, consistency of access control policies for relevant terminals in the network slice is achieved, thereby improving user experience.

[0102] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes one of the following:

[0103] Determining the group identifier based on local configuration information and / or operation, maintenance and management (OAM) configuration information of the first network element;

[0104] Receive the group identifier sent by the fifth network element.

[0105] In the above embodiment, the first network element may determine the group identifier based on local configuration information and / or OAM configuration information, or may receive the group identifier from the fifth network element. In this way, when the terminal requests to register to the network slice or the PDU session requests to be activated to the network slice, the group identifier associated with the terminal or PDU session may be sent through the first network element, so that when the second network element performs network slice admission control on the terminal requesting registration or the PDU session requesting activation, it at least considers the group identifier associated with the terminal or PDU session, thereby achieving consistency in the admission control policy for the relevant terminals or PDU sessions in the network slice and improving the user experience.

[0106] In conjunction with some embodiments of the first aspect, in some embodiments, the group identifier is used to identify at least one of the following:

[0107] The service group associated with the terminal requesting registration;

[0108] The application group associated with the terminal requesting registration;

[0109] The service group associated with the PDU session requested to be activated;

[0110] The application group associated with the PDU session requested to be activated.

[0111] In the above embodiment, the first information is sent to the second network element by the first network element, so that when the second network element uses the first information to perform network slice admission control on the terminal requesting registration or the PDU session requesting activation, it at least considers the service group or application group associated with the terminal or the service group or application group associated with the PDU session. This can achieve consistency in the admission control policy for the terminals associated with the service group or application group in the network slice, and can also achieve consistency in the admission control policy for the PDU session associated with the service group or application group in the network slice, which can ensure the normal provision of services in specific scenarios and improve user experience.

[0112] According to a second aspect, an information processing method is provided, which is performed by a second network element. The method includes:

[0113] Receive first information sent by a first network element; wherein the first information is used to instruct the second network element to perform network slice admission control (NSAC) on a terminal requesting registration or a data packet unit (PDU) session requesting activation; wherein the first information includes a group identifier associated with the terminal or the PDU session.

[0114] In the above embodiment, since the first information includes the group identifier associated with the terminal or PDU session, the second network element can at least consider the group identifier associated with the terminal or PDU session when using the first information to perform network slice admission control on the terminal requesting registration or the PDU session requesting activation. This can achieve consistency in the admission control policy for the relevant terminals or PDU sessions in the network slice and improve the user experience.

[0115] In conjunction with some embodiments of the second aspect, in some embodiments, receiving the first information sent by the first network element includes at least one of the following:

[0116] receiving a second request including the first information sent by the first network element; wherein the second request is sent based on a first request including the first information from a third network element, and the first request is used to update the number of registered terminals;

[0117] Receive a fourth request including the first information sent by the first network element; wherein the fourth request is sent based on a third request including the first information from the fourth network element, and the third request is used to update the number of created PDU sessions.

[0118] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes at least one of the following:

[0119] Sending a first response corresponding to the second request to the first network element based on the overall maximum number of registered terminals and the first information;

[0120] Based on the overall maximum PDU session number and the first information, a second response corresponding to the fourth request is sent to the first network element.

[0121] In the above embodiment, the second network element can perform admission control on terminals requesting registration in the network slice based on the overall maximum number of registered terminals and taking into account the group identifier in the first information, thereby achieving consistency in the admission control policy for the relevant terminals in the network slice. The second network element can also perform admission control on PDU sessions requesting activation in the network slice based on the overall maximum number of PDU sessions and taking into account the group identifier in the first information, thereby achieving consistency in the admission control policy for the relevant PDU sessions in the network slice.

[0122] In combination with some embodiments of the second aspect, in some embodiments, the first response includes second information, and the second information is used to update the maximum number of registered terminals of the network slice of the first network element; and / or, the second response includes third information, and the third information is used to update the maximum number of PDU sessions of the network slice of the first network element.

[0123] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0124] Determine a reserved number in the overall maximum number of registered terminals or the overall maximum number of PDU sessions, wherein the reserved number is one of the following:

[0125] a terminal quota of the reserved NSAC associated with the group identifier;

[0126] The reserved NSAC PDU session quota associated with the group identifier;

[0127] A group quota of the NSAC is reserved, where the group quota is associated with the terminal group or PDU session group identified by the group.

[0128] In the above embodiment, by determining the reserved number in the overall maximum number of registered terminals or the overall maximum number of PDU sessions through the second network element, the occurrence of access failures of terminals requesting registration or PDU sessions requesting activation in the network slice can be reduced, thereby better meeting the business needs of the terminals and improving user experience.

[0129] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0130] Receive the fourth information sent by the first network element; wherein, the fourth information is used to indicate the remaining quota or used quota in the NSAC quota allocated by the second network element to the first network element; the NSAC quota is used to indicate: at least one of the maximum number of registered terminal groups and the maximum number of PDU session groups of the network slice of the first network element.

[0131] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0132] Send a subscription request to the first network element; wherein the subscription request is used to subscribe to the remaining quota or the used quota in the NSAC quota from the first network element.

[0133] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0134] The NSAC quota is updated according to the remaining quota or the used quota in the NSAC quota.

[0135] In combination with some embodiments of the second aspect, in some embodiments, the group identifier is determined by the first network element based on the local configuration information and / or operation, maintenance and management OAM configuration information of the first network element; or, the group identifier is received by the first network element from the fifth network element.

[0136] In conjunction with some embodiments of the second aspect, in some embodiments, the group identifier is used to identify at least one of the following:

[0137] The service group associated with the terminal requesting registration;

[0138] The application group associated with the terminal requesting registration;

[0139] The service group associated with the PDU session requested to be activated;

[0140] The application group associated with the PDU session requested to be activated.

[0141] According to a third aspect, an information processing method is provided, which is performed by a third network element. The method includes:

[0142] Sending first information to a first network element, wherein the first information is used to instruct the second network element to perform network slice admission control (NSAC) on a terminal requesting registration; wherein the first information includes a group identifier associated with the terminal.

[0143] In the above embodiment, since the first information includes the group identifier associated with the terminal, the second network element can at least consider the group identifier associated with the terminal when using the first information to perform network slice admission control on the terminal requesting registration, thereby achieving consistency in the admission control policy for the relevant terminals in the network slice and improving the user experience.

[0144] With reference to some embodiments of the third aspect, in some embodiments, sending the first information to the first network element includes:

[0145] Send a first request including the first information to the first network element; wherein the first request is used to update the number of registered terminals.

[0146] In conjunction with some embodiments of the third aspect, in some embodiments, the group identifier is determined by the third network element based on at least one of the following information:

[0147] Location configuration information;

[0148] Operation Administration and Maintenance (OAM) configuration information;

[0149] Unified Data Management (UDM) contract information;

[0150] Information indicating the Extended Reality (XR) multimodal service capability sent by the terminal;

[0151] Group information related to terminal identification;

[0152] Group information in the terminal context.

[0153] In the above embodiment, the group identifier associated with the terminal is determined by the third network element, so that when the second network element performs network slice admission control on the terminal requesting registration, the group identifier associated with the terminal can be taken into consideration, thereby achieving consistency in the admission control policy for related terminals in the admission control and improving user experience.

[0154] In conjunction with some embodiments of the third aspect, in some embodiments, the group identifier is used to identify at least one of the following:

[0155] The service group associated with the terminal requesting registration;

[0156] The application group associated with the terminal requesting registration.

[0157] According to a fourth aspect, an information processing method is provided, which is performed by a fourth network element. The method includes:

[0158] Sending first information to a first network element, wherein the first information is used to instruct the second network element to perform network slice admission control (NSAC) on a data packet unit (PDU) session requested to be activated; wherein the first information includes a group identifier associated with the PDU session.

[0159] In the above embodiment, since the first information includes the group identifier associated with the PDU session, the second network element can at least consider the group identifier associated with the PDU session when using the first information to perform network slice admission control on the PDU session requested to be activated, thereby achieving consistency in the admission control policy for related PDU sessions in the network slice and improving user experience.

[0160] With reference to some embodiments of the fourth aspect, in some embodiments, sending the first information to the first network element includes:

[0161] Send a third request including the first information to the first network element; wherein the third request is used to update the number of created PDUs.

[0162] In conjunction with some embodiments of the fourth aspect, in some embodiments, the group identifier is determined by the fourth network element based on at least one of the following information:

[0163] Local configuration information;

[0164] Operation, maintenance and management (OAM) configuration information;

[0165] Unified Data Management (UDM) contract information;

[0166] Information indicating the terminal's extended reality (XR) multimodal service capabilities;

[0167] Group information related to terminal identification;

[0168] Indication information of the terminal's XR application or XR service capabilities.

[0169] In the above embodiment, the group identifier of the PDU session is determined by the fourth network element, so that when the second network element performs network slice admission control on the PDU session requested to be activated, the group identifier associated with the PDU session can be taken into consideration, thereby achieving consistency in the admission control policy for related PDU sessions in the admission control and improving the user experience.

[0170] In conjunction with some embodiments of the fourth aspect, in some embodiments, the group identifier is used to identify at least one of the following:

[0171] The service group associated with the PDU session requested to be activated;

[0172] The application group associated with the PDU session requested to be activated.

[0173] According to a fifth aspect, an information processing method is provided, which is performed by a communication system, and the method includes:

[0174] A first network element sends first information to a second network element; wherein the first information is used to instruct the second network element to perform network slice admission control (NSAC) on a terminal requesting registration or a data packet unit (PDU) session requesting activation; wherein the first information includes a group identifier associated with the terminal or the PDU session.

[0175] In the above embodiment, since the first information includes the group identifier associated with the terminal, the second network element can at least consider the group identifier associated with the terminal when using the first information to perform network slice admission control on the terminal requesting registration, thereby achieving consistency in the admission control policy for the relevant terminals in the network slice and improving the user experience.

[0176] With reference to some embodiments of the fifth aspect, in some embodiments, the first network element sending the first information to the second network element includes:

[0177] The first network element receives a first request including the first information sent by a third network element;

[0178] The first network element sends a second request including the first information to the second network element; wherein the first request is used to update the number of registered terminals;

[0179] With reference to some embodiments of the fifth aspect, in some embodiments, the first network element sending the first information to the second network element includes:

[0180] The first network element receives a third request including the first information sent by the fourth network element;

[0181] The first network element sends a fourth request including the first information to the second network element; wherein the third request is used to update the number of activated PDU sessions.

[0182] In conjunction with some embodiments of the fifth aspect, in some embodiments, the first network element sending a second request including the first information to the second network element includes:

[0183] The number of registered terminal groups of the network slice of the first network element reaches the maximum number of registered terminal groups of the network slice, and the first network element sends a second request including the first information to the second network element.

[0184] In conjunction with some embodiments of the fifth aspect, in some embodiments, the first network element sending a fourth request including the first information to the second network element includes:

[0185] The number of PDU session groups of the network slice of the first network element reaches the maximum number of PDU session groups of the network slice, and the first network element sends a fourth request including the first information to the second network element.

[0186] With reference to some embodiments of the fifth aspect, in some embodiments, the first network element sending the first information to the second network element includes:

[0187] The number of registered terminal groups of the network slice of the first network element reaches the maximum number of registered terminal groups of the network slice, and the first network element sends the first information to the second network element; and / or,

[0188] The number of PDU session groups of the network slice of the first network element reaches the maximum number of PDU session groups of the network slice, and the first network element sends the first information to the second network element.

[0189] In conjunction with some embodiments of the fifth aspect, in some embodiments, the method further includes at least one of the following:

[0190] The first network element receives a first response corresponding to the second request sent by the second network element; wherein the first response includes second information, and the second information is used to update the maximum number of registered terminals in the network slice of the first network element;

[0191] The first network element receives a second response corresponding to the fourth request sent by the second network element; wherein the second response includes third information, and the third information is used to update the maximum PDU session number of the network slice of the first network element.

[0192] In conjunction with some embodiments of the fifth aspect, in some embodiments, the method further includes:

[0193] The first network element sends fourth information to the second network element; wherein, the fourth information is used to indicate the remaining quota or used quota in the NSAC quota allocated by the second network element to the first network element; the NSAC quota is used to indicate: at least one of the maximum number of registered terminal groups and the maximum number of PDU session groups of the network slice of the first network element.

[0194] With reference to some embodiments of the fifth aspect, in some embodiments, the first network element sending fourth information to the second network element includes:

[0195] The fourth information is sent to the second network element according to the subscription request from the second network element, wherein the subscription request is used to subscribe the remaining quota or the used quota in the NSAC quota to the first network element.

[0196] In conjunction with some embodiments of the fifth aspect, in some embodiments, the first network element is a local NSACF network element, and the second network element is a master NSACF network element;

[0197] The third network element is the AMF network element, and the fourth network element is the SMF network element.

[0198] In conjunction with some embodiments of the fifth aspect, in some embodiments, the method further includes one of the following:

[0199] Determining the group identifier based on local configuration information and / or operation, maintenance and management (OAM) configuration information of the first network element;

[0200] Receive the group identifier sent by the fifth network element.

[0201] In conjunction with some embodiments of the fifth aspect, in some embodiments, the group identifier is used to identify at least one of the following:

[0202] The service group associated with the terminal requesting registration;

[0203] The application group associated with the terminal requesting registration;

[0204] The service group associated with the PDU session requested to be activated;

[0205] The application group associated with the PDU session requested to be activated.

[0206] According to a sixth aspect, a first network element is provided, wherein the first network element includes:

[0207] A sending module is configured to send first information to a second network element; wherein the first information is used to instruct the second network element to perform network slice admission control (NSAC) on a terminal requested to be registered or a data packet unit (PDU) session requested to be activated; wherein the first information includes a group identifier associated with the terminal or the PDU session.

[0208] With reference to some embodiments of the sixth aspect, in some embodiments, the first network element further includes a first receiving module;

[0209] The first receiving module is configured to receive a first request sent by a third network element; wherein the first request is used to update the number of registered terminals, and the first request includes the first information;

[0210] The sending module is configured to send a second request to the second network element; the second request includes the first information.

[0211] With reference to some embodiments of the sixth aspect, in some embodiments, the first network element further includes a second receiving module;

[0212] The second receiving module is configured to receive a third request including the first information sent by a fourth network element; wherein the third request is used to update the number of activated PDU sessions; and the third request includes the first information;

[0213] The sending module is configured to send a fourth request to the second network element; the fourth request includes the first information.

[0214] With reference to some embodiments of the sixth aspect, in some embodiments, the sending module is configured to:

[0215] The number of registered terminal groups of the network slice of the first network element reaches the maximum number of registered terminal groups of the network slice, and the first information is sent to the second network element.

[0216] With reference to some embodiments of the sixth aspect, in some embodiments, the sending module is configured to:

[0217] The number of PDU session groups of the network slice of the first network element reaches the maximum number of PDU session groups of the network slice, and the first information is sent to the second network element.

[0218] In conjunction with some embodiments of the sixth aspect, in some embodiments, the apparatus further includes a third receiving module, configured to perform at least one of the following:

[0219] Receiving a first response corresponding to the second request sent by the second network element; wherein the first response includes second information, and the second information is used to update the maximum number of registered terminals of the network slice of the first network element;

[0220] Receive a second response corresponding to the fourth request sent by the second network element; wherein the second response includes third information, and the third information is used to update the maximum PDU session number of the network slice of the first network element.

[0221] In conjunction with some embodiments of the sixth aspect, in some embodiments, the sending module is further configured to:

[0222] Sending fourth information to the second network element; wherein, the fourth information is used to indicate the remaining quota or used quota in the NSAC quota allocated by the second network element to the first network element; the NSAC quota is used to indicate: at least one of the maximum number of registered terminal groups and the maximum number of PDU session groups of the network slice of the first network element.

[0223] In conjunction with some embodiments of the sixth aspect, in some embodiments, the sending module is further configured to:

[0224] The fourth information is sent to the second network element according to the subscription request from the second network element, wherein the subscription request is used to subscribe the remaining quota or the used quota in the NSAC quota to the first network element.

[0225] In combination with some embodiments of the sixth aspect, in some embodiments, the first network element is a local NSACF network element, the second network element is a main NSACF network element; the third network element is an AMF network element, and the fourth network element is an SMF network element.

[0226] In conjunction with some embodiments of the sixth aspect, in some embodiments, the apparatus further includes a receiving module, and the apparatus further includes an acquiring module, where the acquiring module is configured to perform one of the following:

[0227] Determining the group identifier based on local configuration information and / or operation, maintenance and management (OAM) configuration information of the first network element;

[0228] Receive the group identifier sent by the fifth network element.

[0229] In conjunction with some embodiments of the sixth aspect, in some embodiments, the group identifier is used to identify at least one of the following:

[0230] The service group associated with the terminal requesting registration;

[0231] The application group associated with the terminal requesting registration;

[0232] The service group associated with the PDU session requested to be activated;

[0233] The application group associated with the PDU session requested to be activated.

[0234] According to a seventh aspect, a second network element is provided, wherein the second network element includes:

[0235] A receiving module is configured to receive first information sent by a first network element; wherein the first information is used to instruct the second network element to perform network slice admission control (NSAC) on a terminal requesting registration or a data packet unit (PDU) session requesting activation; wherein the first information includes a group identifier associated with the terminal or the PDU session.

[0236] In conjunction with some embodiments of the seventh aspect, in some embodiments, the receiving module is configured to perform at least one of the following:

[0237] receiving a second request including the first information sent by the first network element; wherein the second request is sent based on a first request including the first information from a third network element, and the first request is used to update the number of registered terminals;

[0238] Receive a fourth request including the first information sent by the first network element; wherein the fourth request is sent based on a third request including the first information from the fourth network element, and the third request is used to update the number of created PDU sessions.

[0239] In conjunction with some embodiments of the seventh aspect, in some embodiments, the apparatus further includes a first sending module, where the first sending module is configured to perform at least one of the following:

[0240] Based on the overall maximum number of registered terminals and the first information, a first response corresponding to the second request is sent to the first network element; the first response includes second information, and the second information is used to update the maximum number of registered terminals of the network slice of the first network element.

[0241] In conjunction with some embodiments of the seventh aspect, in some embodiments, the apparatus further includes a second sending module, where the second sending module is configured to:

[0242] Based on the overall maximum number of PDU sessions and the first information, a second response corresponding to the fourth request is sent to the first network element; the second response includes third information, and the third information is used to update the maximum number of PDU sessions of the network slice of the first network element.

[0243] In conjunction with some embodiments of the seventh aspect, in some embodiments, the apparatus further includes:

[0244] A determination module is configured to determine a reserved number in the overall maximum number of registered terminals or the overall maximum number of PDU sessions, wherein the reserved number is one of the following:

[0245] a terminal quota of the reserved NSAC associated with the group identifier;

[0246] The reserved NSAC PDU session quota associated with the group identifier;

[0247] A group quota of the NSAC is reserved, where the group quota is associated with the terminal group or PDU session group identified by the group.

[0248] In conjunction with some embodiments of the seventh aspect, in some embodiments, the receiving module is further configured to:

[0249] Receive the fourth information sent by the first network element; wherein, the fourth information is used to indicate the remaining quota or used quota in the NSAC quota allocated by the second network element to the first network element; the NSAC quota is used to indicate: at least one of the maximum number of registered terminal groups and the maximum number of PDU session groups of the network slice of the first network element.

[0250] In conjunction with some embodiments of the seventh aspect, in some embodiments, the apparatus further includes:

[0251] The third sending module is configured to send a subscription request to the first network element; wherein the subscription request is used to subscribe to the remaining quota or the used quota in the NSAC quota from the first network element.

[0252] In conjunction with some embodiments of the seventh aspect, in some embodiments, the apparatus further includes:

[0253] The updating module is configured to update the NSAC quota according to the remaining quota or the used quota in the NSAC quota.

[0254] In combination with some embodiments of the seventh aspect, in some embodiments, the group identifier is determined by the first network element based on the local configuration information and / or operation, maintenance and management OAM configuration information of the first network element; or, the group identifier is received by the first network element from the fifth network element.

[0255] In conjunction with some embodiments of the seventh aspect, in some embodiments, the group identifier is used to identify at least one of the following:

[0256] The service group associated with the terminal requesting registration;

[0257] The application group associated with the terminal requesting registration;

[0258] The service group associated with the PDU session requested to be activated;

[0259] The application group associated with the PDU session requested to be activated.

[0260] In an eighth aspect, a third network element is provided, wherein the third network element includes:

[0261] A sending module is configured to send first information to a first network element, wherein the first information is used to instruct the second network element to perform network slice admission control (NSAC) on a registered terminal; wherein the first information includes a group identifier associated with the terminal.

[0262] With reference to some embodiments of the eighth aspect, in some embodiments, the sending module is configured to:

[0263] Send a first request including the first information to the first network element; wherein the first request is used to update the number of registered terminals.

[0264] In conjunction with some embodiments of the eighth aspect, in some embodiments, the group identifier is determined by the third network element based on at least one of the following information:

[0265] Local configuration information;

[0266] Operation, maintenance and management (OAM) configuration information;

[0267] Unified Data Management (UDM) contract information;

[0268] Information indicating the terminal's extended reality (XR) multimodal service capabilities;

[0269] Group information related to terminal identification;

[0270] Group information in the terminal context.

[0271] In conjunction with some embodiments of the eighth aspect, in some embodiments, the group identifier is used to identify at least one of the following:

[0272] The service group associated with the terminal requesting registration;

[0273] The application group associated with the terminal requesting registration.

[0274] According to a ninth aspect, a fourth network element is provided, wherein the fourth network element includes:

[0275] A sending module is configured to send first information to a first network element, wherein the first information is used to instruct the second network element to perform network slice admission control (NSAC) on a data packet unit (PDU) session requested to be activated; wherein the first information includes a group identifier associated with the PDU session.

[0276] In conjunction with some embodiments of the ninth aspect, in some embodiments, the sending module is configured to:

[0277] Send a third request including the first information to the first network element; wherein the third request is used to update the number of activated PDU sessions.

[0278] In conjunction with some embodiments of the ninth aspect, in some embodiments, the group identifier is determined by the third network element based on at least one of the following information:

[0279] Local configuration information;

[0280] Operation, maintenance and management (OAM) configuration information;

[0281] Unified Data Management (UDM) contract information;

[0282] Information indicating the terminal's extended reality (XR) multimodal service capabilities;

[0283] Group information related to terminal identification;

[0284] Indication information of the terminal's XR application or XR service capabilities.

[0285] In conjunction with some embodiments of the ninth aspect, in some embodiments, the group identifier is used to identify at least one of the following:

[0286] The service group associated with the PDU session requested to be activated;

[0287] The application group associated with the PDU session requested to be activated.

[0288] In the tenth aspect, a communication system is provided, wherein the communication system includes a first network element, a second network element, a third network element and a fourth network element, the first network element is configured to implement the information processing method described in the optional implementation manner of the first aspect, the second network element is configured to implement the information processing method described in the optional implementation manner of the second aspect, the third network element is configured to implement the information processing method described in the optional implementation manner of the third aspect, and the fourth network element is configured to implement the information processing method described in the optional implementation manner of the fourth aspect.

[0289] According to an eleventh aspect, a communication device is provided, wherein the communication device includes:

[0290] one or more processors;

[0291] The processor is used to call instructions to enable the communication device to execute the information processing method described in the optional implementation manner of the first aspect, the second aspect, the third aspect or the fourth aspect.

[0292] In the twelfth aspect, a storage medium is provided, wherein the storage medium stores instructions, and when the instructions are executed on a communication device, the communication device executes the information processing method described in the optional implementation of the first aspect, the second aspect, the third aspect or the fourth aspect.

[0293] In a thirteenth aspect, an embodiment of the present disclosure provides a program product, which, when executed by a communication device, enables the communication device to execute the information processing method described in the optional implementation manner of the first aspect, the second aspect, the third aspect or the fourth aspect.

[0294] In a fourteenth aspect, an embodiment of the present disclosure provides a computer program which, when executed on a computer, enables the computer to execute the information processing method described in the optional implementation of the first aspect, the second aspect, the third aspect or the fourth aspect.

[0295] It is understandable that the first to fourth network elements, communication devices, communication systems, storage media, program products, and computer programs described above are all used to execute the methods provided in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

[0296] In some embodiments, terms such as information processing method, communication method, and information transmission method can be interchangeable, and terms such as communication system, information processing system, and information transmission system can be interchangeable.

[0297] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0298] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0299] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0300] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

[0301] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0302] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

[0303] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "in one case A, in another case B," or "in one case A, in another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The same applies when there are more branches such as A, B, and C.

[0304] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is similar when there are more branches such as A, B, C, etc.

[0305] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0306] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0307] In some embodiments, terms such as "...", "determine...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0308] In some embodiments, terms such as "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not less than", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

[0309] In some embodiments, devices, etc. can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as "device", "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", and "subject" can be used interchangeably.

[0310] In some embodiments, "network" can be interpreted as devices included in the network (eg, access network equipment, core network equipment, etc.).

[0311] In some embodiments, the terms "access network device (AN device)", "radio access network device (RAN device)", "base station (BS)", "radio base station" "fixed station", "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission / reception point (TRP)", "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "serving cell", "carrier", "component carrier", "bandwidth part (BWP)" and the like may be used interchangeably.

[0312] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc. can be used interchangeably.

[0313] In some embodiments, the access network device, the core network device, or the network device can be replaced by a terminal. For example, the various embodiments of the present disclosure can also be applied to a structure in which the communication between the access network device, the core network device, or the network device and the terminal is replaced by communication between multiple terminals (for example, device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, it is also possible to set the structure in which the terminal has all or part of the functions of the access network device. In addition, terms such as "uplink" and "downlink" can also be replaced by terms corresponding to communication between terminals (for example, "side"). For example, uplink channels, downlink channels, etc. can be replaced by side channels, and uplinks, downlinks, etc. can be replaced by side links.

[0314] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, the core network device, or the network device may have a structure that has all or part of the functions of the terminal.

[0315] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

[0316] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0317] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0318] FIG1a is a schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure.

[0319] As shown in FIG. 1 a , a communication system 100 includes a terminal 101 , an access network device 102 , and a core network device 103 .

[0320] In some embodiments, the terminal 101 includes, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and at least one of a wireless terminal device in a smart home, but is not limited thereto.

[0321] In some embodiments, the access network device 102 can be, for example, a node or device that accesses the terminal to the wireless network. The access network device may include an evolved NodeB (eNB), a next generation evolved NodeB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved nodeB (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open base station (Open RAN), a cloud base station (Cloud RAN), a base station in other communication systems, and at least one of an access node in a Wi-Fi system, but is not limited thereto.

[0322] In some embodiments, the technical solution of the present disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within the access network devices involved in the embodiments of the present disclosure can be transformed into internal interfaces of the Open RAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.

[0323] In some embodiments, the access network device can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the access network device, with the functions of some protocol layers centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.

[0324] In some embodiments, the core network device 103 may include multiple network elements (network elements may also be referred to as "network functions"), such as a first network element 1031, a second network element 1032, a third network element 1033, and a fourth network element 1034. It may also be multiple devices or a group of devices, including the first network element 1031, the second network element 1032, the third network element 1033, and the fourth network element 1034, respectively. The network elements may be virtual or physical. The core network may include, for example, at least one of an evolved packet core (EPC), a 5G core network (5GCN), and a next-generation core (NGC).

[0325] In some embodiments, the second network element is at least used to perform global management on one or more first network elements.

[0326] In some embodiments, the service area of ​​the second network element includes the service area of ​​the first network element. For example, the service area of ​​the second network element is the entire service area, and the service area of ​​the first network element is one or more service areas in the entire service area.

[0327] In some embodiments, both the first network element and the second network element can be used to perform admission control on the network slice.

[0328] In some embodiments, the first network element may be: a local NSACF network element.

[0329] In some embodiments, the second network element may be: a master NSACF network element.

[0330] In some embodiments, the first network element 1031 and the second network element 1032 are arranged in a hierarchical manner, and the level of the second network element 1032 is higher than the level of the first network element 1031 .

[0331] In some embodiments, the third network element 1033 may be used for access and mobility management, such as registration management, connection management, and mobility management, etc., and the name is not limited thereto. For example, the third network element 1033 may be an AMF network element.

[0332] In some embodiments, the fourth network element 1034 may be used for session management, such as PDU session management, etc., and the name is not limited thereto. For example, the fourth network element 1034 may be an SMF network element.

[0333] For example, taking a 5G communication system as an example, Figure 1b is a schematic diagram of a non-roaming 5G communication system architecture. As shown in Figure 1b, the core network in the 5G communication system may include: multiple network elements. Multiple network elements may include but are not limited to: (1) AMF (Access and Mobility Management Function): responsible for user access and mobility management; (2) SMF (Session Management Function): responsible for user session management; (3) NSACF (Network Slice Admission Control Function): responsible for admission control of network slices; (4) UPF (User Plane Function): responsible for user plane processing; (5) NEF (Network Exposure Function): responsible for the collection, analysis and reorganization of network capabilities, and the opening of network capabilities; (6) PCF (Policy Control Function): responsible for user policy control, including session policy and mobility policy; (7) UDM (Unified Data Management): responsible for user contract data management; (8) NSSF (Network Slice Selection Function): responsible for selecting the network slice adopted by user services, etc. Among them, Nnsacf, Nnssf, Nnssaaf, Nausf, Nnef, Namf, Npcf, Nnrf, Nsmf, Nudm, Naf, N1, N2, N3, N4, and N6 are all interface serial numbers; for example, the meaning of each interface in Figure 1b can be found in the meaning defined in the 3GPP (3rd Generation Partnership Project) standard protocol, and the embodiments of the present disclosure do not impose specific restrictions on this.

[0334] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution provided by the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution provided by the embodiment of the present disclosure is also applicable to similar technical problems.

[0335] The embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1a, or a portion thereof, but are not limited thereto. The entities shown in FIG1a are illustrative only. The communication system may include all or part of the entities shown in FIG1a, or may include other entities other than those shown in FIG1a. The number and form of the entities may be arbitrary. The connection relationship between the entities is illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0336] The embodiments of the present disclosure can also be applied to the 5G communication system architecture shown in Figure 1b. It can be understood that the embodiments of the present disclosure do not specifically limit the communication system to which the information processing method provided by the present disclosure is applicable.

[0337] The embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), future radio access (FRA), new radio access technology (RAT), new radio (NR), new radio access (NX), future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X), systems utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0338] The data streams of XR multimodal services are highly correlated, and in many scenarios, the data streams of these services are distributed across multiple UEs. However, the NSAC function currently used by the 5GS system cannot support the multi-UE group admission function of XR multimodal services for admission control of the number of active sessions in the network. As a result, the admission control policies for the relevant UEs of XR multimodal services are inconsistent, resulting in the network being unable to guarantee the user experience of XR multimodal services, and even unable to guarantee the normal provision of services in specific scenarios.

[0339] Network admission control is a single-UE policy. The admission control policies for UEs related to XR multimodal services are inconsistent, resulting in the network being unable to guarantee the user experience of XR multimodal services, and even unable to guarantee the normal provision of services in specific scenarios.

[0340] How to effectively enhance the network slice admission control of related terminals or related PDU sessions in XR business scenarios, and achieve consistent admission control policies for UEs or related PDU sessions related to XR multimodal services, especially the admission control of related UEs or related PDU sessions under the hierarchical NSACF architecture, has become an urgent problem that needs to be solved.

[0341] FIG2a is an interactive diagram illustrating an information processing method according to an embodiment of the present disclosure. As shown in FIG2a, the present disclosure embodiment relates to an information processing method for a communication system 100, and the method may include:

[0342] Step S2101: The third network element determines the first information.

[0343] In some embodiments, the third network element may be an AMF.

[0344] In some embodiments, the first information may include a group identifier. For example, the first information may include a group identifier associated with the terminal.

[0345] In some embodiments, the group identifier may be used to identify a service group or application group associated with the terminal. The service group may be an XR service group.

[0346] In some embodiments, the group identifier includes at least one of the following: an internal group identifier, a standardized universal group identifier, an XR application ID, and an XR service capability indication.

[0347] In some embodiments, terminals associated with the same group identifier may be associated with the same service or the same application.

[0348] For example, terminals associated with the same group identifier of a service group may be associated with the same XR service.

[0349] In some embodiments, the third network element may determine the first group identifier based on fifth information; the fifth information includes at least one of the following:

[0350] Local configuration information;

[0351] Operation, maintenance and management (OAM) configuration information;

[0352] Unified Data Management (UDM) contract information;

[0353] Information indicating the extended reality (XR) multimodal service capabilities sent by the terminal;

[0354] Group information related to terminal identification;

[0355] Group information in the terminal context.

[0356] For example, the terminal identifier may be a UE PEI (Permanent Equipment Identifier).

[0357] For example, the group information in the terminal context may be sent by another AMF different from the third network element.

[0358] Step S2102: The third network element sends first information to the first network element.

[0359] In some embodiments, the first network element receives first information sent by the third network element.

[0360] In some embodiments, the first network element may be an NSACF, for example, a local NSACF.

[0361] In some embodiments, the first information including the group identifier may be included in the first request, and the first request may be used to request to update the number of registered terminals. For example, the first request includes at least one of the following: a terminal registration request, a terminal deregistration request, and a request to update the number of registered terminals.

[0362] In some examples, the first request may be a Nnsacf_NSAC_NumOfUEsUpdate_Request request.

[0363] In some embodiments, the first network element is used to perform admission control on terminals in a service area corresponding to the first network element.

[0364] In some embodiments, the first network element is associated with at least one service area.

[0365] In some embodiments, the first information may indicate the network slice for the admission operation via single network slice selection assistance information (Single Network Slice Selection Assistance Information, S-NSSAI).

[0366] When a network slice S-NSSAI needs to perform NSAC, and the slice identifier of the network slice is in the allowed NSSAI (for example, AMF requests the UE to register to the network slice), or is deleted from the allowed NSSAI (AMF requests the UE to deregister from the network slice), the AMF triggers the validity check and update process of the network slice and updates the number of registered terminal users.

[0367] In some embodiments, the first information may be triggered by a registration process or deregistration process initiated by the terminal for the network slice.

[0368] For example, the terminal may send a terminal registration request through the AMF, triggering the AMF to send the first information to the local NSACF. For another example, the terminal may send a terminal deregistration request through the AMF, triggering the AMF to send the first information to the local NSACF.

[0369] In some embodiments, the first information may be triggered by a change in the allowed NSSAI caused by handover across AMFs.

[0370] In some embodiments, the first information may be sent by the AMF to the local NSACF based on the terminal's configuration update process.

[0371] For example, the configuration update process can be triggered by the Network Slice-Specific Authentication and Authorization (NSSAA) process or the S-NSSAI contract change process.

[0372] In some embodiments, network slice admission control may trigger the first network element to update the number of registered terminals in the network slice.

[0373] In some embodiments, the update of the number of registered terminals includes one of the following: an increase in the number of registered terminals in the network slice, a decrease in the number of registered terminals in the network slice.

[0374] In some embodiments, the first information may also include the content in the registration request information sent by the terminal, such as: terminal identification, access type of authorized NSSAI, relevant slices S-NSSAIs requested to execute NSAC, AMF identification and / or update flag.

[0375] In some embodiments, the first information indicates that admission control of at least one network slice is performed on a terminal associated with the group identifier.

[0376] In some embodiments, the group identifier can be used to identify the service group or application group associated with the terminal. For example, the group identifier can be used to identify the service group associated with the terminal requesting registration, and / or the group identifier can be used to identify the application group associated with the terminal requesting registration.

[0377] In some embodiments, the first information may be used to indicate network slice admission control based on a service group or application group for the terminal.

[0378] In some embodiments, network slice admission control based on business groups or application groups may include: allowing terminals associated with business groups or application groups to register with the network slice; or denying terminals associated with business groups or application groups to register with the network slice.

[0379] In some embodiments, if the AMF is not aware of the peer NSACF, the AMF performs NSACF discovery and selection.

[0380] Step S2103: The first network element performs network slice admission control on the terminal.

[0381] In some embodiments, the first network element performs network slice admission control on the terminal requesting registration.

[0382] In some embodiments, the first network element performs network slice admission control on the terminal requesting registration based on the maximum number of registered terminals or the maximum number of registered terminal groups of the network slice to which the terminal requests registration.

[0383] In some embodiments, the number of registered terminal groups of the network slice of the first network element does not reach the maximum number of registered terminal groups of the network slice, and the first network element performs network slice admission control on the terminal requesting registration considering the group identifier associated with the terminal.

[0384] In some embodiments, the first network element allows the terminal to register with the network slice, including: accepting the terminal's registration request in the network slice, adding the terminal to the registered list, and increasing the number of registered terminals in the network slice.

[0385] In some embodiments, the number of registered terminal groups of the network slice of the first network element does not reach the maximum number of registered terminal groups of the network slice, and the first network element does not send a second request including the first information to the second network element.

[0386] Step S2104: The first network element sends first information to the second network element.

[0387] In some embodiments, the second network element receives the first information sent by the first network element.

[0388] In some embodiments, the second network element is at least used to perform global management on one or more first network elements.

[0389] In some embodiments, the service area of ​​the second network element includes the service area of ​​the first network element. For example, the service area of ​​the second network element is the entire service area, and the service area of ​​the first network element is one or more service areas in the entire service area.

[0390] In some embodiments, the second network element may be a primary NSACF.

[0391] In some embodiments, the first information is included in a second request sent from the first network element to the second network element. For example, the second request is an NSAC request.

[0392] In some embodiments, the first information may be used to indicate network slice admission control for a terminal requesting registration.

[0393] In some embodiments, the first information may be used to indicate network slice admission control for a terminal requesting deregistration.

[0394] For example, network slice admission control for terminals requesting registration may include increasing the number of registered terminals in the network slice.

[0395] For example, network slice admission control for terminals requesting to deregister may include reducing the number of registered terminals in the network slice.

[0396] In some embodiments, in step S2104, the first network element sending the first information to the second network element includes:

[0397] The first network element sends the first information from the third network element to the second network element; and / or,

[0398] The first network element sends the first information from the fourth network element to the second network element;

[0399] In some embodiments, in step S2104, the first network element sending the first information to the second network element includes:

[0400] receiving a first request sent by the third network element, wherein the first request is used to update the number of registered terminals, and the first request includes the first information;

[0401] A second request is sent to the second network element, where the second request includes the first information.

[0402] In some embodiments, in step S2104, the first network element sends the first information to the second network element, including at least one of the following:

[0403] The number of registered terminals of the network slice of the first network element reaches or does not reach the maximum number of registered terminals of the network slice, and the first network element sends first information to the second network element;

[0404] The number of registered terminal groups of the network slice of the first network element reaches the maximum number of registered terminal groups of the network slice, and the first network element sends the first information to the second network element.

[0405] In some embodiments, the number of registered terminals of the network slice of the first network element reaches or does not reach the maximum number of registered terminals of the network slice, and the first network element sends a second request including the first information to the second network element.

[0406] In some embodiments, the number of registered terminal groups of the network slice of the first network element reaches the maximum number of registered terminal groups of the network slice, and the first network element sends a second request including the first information to the second network element.

[0407] Here, both the first request and the second request include the identifier of the network slice.

[0408] In some embodiments, the first information is at least used to instruct the second network element to perform network slice admission control on the terminal requesting registration.

[0409] In some embodiments, the first information may be included in a second request sent by the first network element to the second network element. For example, the request message is: Nnscf_NSAC_NumOfUEsUpdate_Request message.

[0410] In the embodiment of the present disclosure, the number of registered terminals of a network slice is the number of registered terminals of the network slice.

[0411] In the embodiment of the present disclosure, the number of registered terminal groups of a network slice is the number of registered terminal groups of the network slice.

[0412] Step S2105: The second network element performs network slice admission control on the terminal.

[0413] In some embodiments, the second network element performs network slice admission control on the terminal requesting registration.

[0414] In some embodiments, the second network element may perform network slice admission control on the terminal based on the overall maximum number of registered terminals and the first information.

[0415] In some embodiments, the second network element determines whether to accept the NSAC request of the first network element based on the reserved number in the overall maximum number of registered terminals and the first information.

[0416] In some embodiments, the reserved quantity is one of the following:

[0417] a terminal quota of the reserved NSAC associated with the group identifier;

[0418] Reserve the NSAC group quota. The group quota is associated with the terminal group identified by the group ID.

[0419] In some implementations, the terminal quota (i.e., terminal quantity quota) may be the number of terminals allowed to be registered that the second network element configures for the network slice of the first network element.

[0420] In some embodiments, for the group identifier included in the first information, when there is a terminal quota of a reserved NSAC associated with the group identifier in the second network element, the second network element updates the number of registered terminals in the network slice, for example, increases the number of registered terminal groups in the network slice.

[0421] In some embodiments, for the group identifier included in the first information, when there is a group quota of a reserved NSAC associated with the group identifier in the second network element, the second network element allows the terminal requesting registration to be registered to the network slice.

[0422] For example, the second network element allows the terminal requesting registration to be registered to the network slice, which may include: the second network element accepts the NSAC request of the first network element and increases the number of registered terminal groups in the network slice.

[0423] In some embodiments, for the group identifier included in the first information, when there is no group quota of the reserved NSAC associated with the group identifier in the second network element, the second network element does not allow the terminal requesting registration to be registered to the network slice.

[0424] For example, the second network element does not allow the terminal requesting registration to be registered to the network slice, which may include: the second network element rejects the NSAC request of the first network element and does not update the number of registered terminal groups in the network slice.

[0425] Step S2106: The second network element sends seventh information to the first network element.

[0426] In some embodiments, the first network element receives seventh information sent by the second network element.

[0427] In some embodiments, the seventh information may be used to indicate whether the terminal is allowed to be registered to the network slice.

[0428] In some embodiments, the seventh information may be included in a first response sent by the second network element to the first network element. For example, the response message may be an Nnsacf_NSAC_NumOfUEsUpdate_Response message.

[0429] In some embodiments, the first response includes second information, and the second information is used to update the maximum number of registered terminals of the network slice of the first network element.

[0430] In some embodiments, if the second network element determines to adjust the configuration value stored on the first network element, the update information of the configuration value may be included in the seventh information.

[0431] In some embodiments, the configuration value may be the maximum number of registered terminals in the network slice of the first network element, and / or the maximum number of registered terminal groups in the network slice of the first network element.

[0432] In some embodiments, the configuration value update information may be used to indicate an increase in the maximum number of registered terminals and / or the maximum number of registered terminal groups, or the configuration value update information may be used to indicate a decrease in the maximum number of registered terminals and / or the maximum number of registered terminal groups.

[0433] In some embodiments, the second information and the seventh information may be interchangeable.

[0434] Step S2107: The first network element determines the eighth information.

[0435] In some embodiments, if the seventh information from the second network element includes an updated configuration value, the first network element performs NSAC on the terminal requesting registration based on the received update information to obtain the eighth information.

[0436] For example, based on the updated configuration value, NSAC is performed on the PDU session for the specified network slice according to the group identifier (XR group ID or XR service ID) associated with the PDU session.

[0437] In some embodiments, the eighth information may be used to indicate the result of the first network element performing NSAC on the terminal; for example, the eighth information indicates that the terminal is allowed to be registered with the network slice, or indicates that the terminal is refused to be registered with the network slice.

[0438] In some embodiments, if the seventh information from the second network element does not include update information of the configuration value, the seventh information is returned to the third network element as the eighth information.

[0439] Step S2108: The first network element sends the eighth information to the third network element.

[0440] In some embodiments, the third network element receives the eighth information sent by the first network element.

[0441] In some embodiments, the eighth information may be included in a response message sent by the first network element to the third network element. For example, the response message may be an Nnsacf_NSAC_NumOfUEsUpdate_Response message.

[0442] In some examples, the response message sent by the first network element to the third network element includes a slice identifier S-NSSAI(s) and a result indication, where the result indication indicates whether the number of registered terminals for the network slice has reached a maximum number of registered terminals. Optionally, the result indication may be used to indicate whether the number of registered terminals for the network slice has reached a maximum number of terminals.

[0443] In some embodiments, the slice identifier S-NSSAI(s) included in the response message may include at least one of the following:

[0444] The identifier of the network slice that the terminal is allowed to register;

[0445] The identifier of the network slice to which the terminal registration is rejected.

[0446] In some embodiments, if the number of registered terminals or registered terminal groups sent by the first network element to the third network element for the network slice has reached the maximum allowed value, the fourth network element may reject the terminal registration request, for example, the rejection reason is set to "the number of registered terminals allowed by the slice has been reached", or the rejection reason is set to "the number of terminal groups allowed by the slice has been reached".

[0447] In some embodiments, the term "information" can be interchangeable with terms such as "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "field", and "data".

[0448] In some embodiments, the term "send" can be interchanged with terms such as "transmit", "report", and "transmit".

[0449] The information processing method involved in the embodiments of the present disclosure may include at least one of steps S2101 to S2108. For example, step S2101 can be implemented as an independent embodiment, step S2103 can be implemented as an independent embodiment, and step S2104 can be implemented as an independent embodiment. For example, steps S2101 to S2103 combined with step S2108 can be implemented as an independent embodiment, steps S2104 to S2108 can be implemented as an independent embodiment, and steps S2101 to S2108 can be implemented as an independent embodiment, but are not limited thereto.

[0450] In some embodiments, step S2101, step S2102, and step S2103 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0451] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0452] FIG2b is an interactive diagram illustrating an information processing method according to an embodiment of the present disclosure. As shown in FIG2b , the present disclosure embodiment relates to an information processing method for use in a communication system 100. The method may include:

[0453] Step S2201: The fourth network element determines the first information.

[0454] In some embodiments, the fourth network element may be an SMF.

[0455] In some embodiments, the first information may include a group identifier. For example, the first information may include a group identifier associated with the PDU session.

[0456] In some embodiments, the group identifier is used to identify a service group or application group associated with a PDU session. For example, the group identifier is used to identify a service group associated with a PDU session requested to be activated, or the group identifier is used to identify an application group associated with a PDU session requested to be activated.

[0457] In some embodiments, the service group may be an XR service group.

[0458] In some embodiments, the group identifier includes at least one of the following: an internal group identifier, a standardized universal group identifier, an XR application ID, and an XR service capability indication.

[0459] In some embodiments, PDU sessions associated with the same group identifier may be associated with the same service or the same application.

[0460] For example, PDU sessions associated with the group identifier of the same service group may be associated with the same XR service.

[0461] In some embodiments, the third network element may determine the first group identifier based on sixth information; the sixth information includes at least one of the following:

[0462] Local configuration information;

[0463] Operation, maintenance and management (OAM) configuration information;

[0464] Unified Data Management (UDM) contract information;

[0465] Information indicating the extended reality (XR) multimodal service capability sent by the terminal;

[0466] Group information related to terminal identification;

[0467] Group information in the terminal context.

[0468] For example, the terminal identifier may be a UE PEI (Permanent Equipment Identifier).

[0469] For example, the indication information of the XR multimodal service capability may be sent by the RAN or the AMF.

[0470] Step S2202: The fourth network element sends first information to the first network element.

[0471] In some embodiments, the first network element receives first information sent by the fourth network element.

[0472] In some embodiments, the first network element may be an NSACF, for example, a local NSACF.

[0473] In some embodiments, the first information including the group identifier is included in a third request sent by the fourth network element to the first network element. For example, the third request is used to update the number of activated PDU sessions.

[0474] In some examples, the first request may be a nsacf_nsac_numofpdusupdate_request request.

[0475] In some embodiments, the fourth network element can be triggered to send the first information at the beginning of the new PDU session creation process or after a PDU session is successfully released, or the fourth network element triggers the sending of the first information to the first network element for the slice that needs to execute NSAC.

[0476] In some embodiments, the first network element is configured to perform admission control on a PDU session in a service area corresponding to the first network element.

[0477] In some embodiments, the first network element is associated with at least one service area.

[0478] In some embodiments, the first information may be used to indicate admission control of a network slice for a PDU session requested to be activated.

[0479] In some embodiments, the first information may be used to indicate admission control of a network slice for a PDU session requested to be deactivated.

[0480] In some embodiments, the first information may further include a UE ID, a session ID, a slice identifier or identifier list S-NSSAI(s) for which NSAC is required, an access type, and an update flag. The update flag is used to mark whether the number of sessions is increased, decreased, or updated.

[0481] For example, it increases during the session establishment process or a new access to an existing multi-access session, decreases after the session release process or when a certain access to an existing multi-access session is released, and updates when indicating that the access type of an existing PDU session is updated.

[0482] Step S2203: The first network element performs network slice admission control on the PDU session.

[0483] In some embodiments, the first network element performs network slice admission control on the PDU session requested to be activated.

[0484] In some embodiments, the first network element performs network slice admission control on the PDU session requested to be deactivated.

[0485] In some embodiments, the first network element performs network slice admission control on the PDU session requested to be activated based on the maximum number of PDU sessions or the maximum number of PDU session groups of the network slice to which the PDU session request is registered.

[0486] In some embodiments, the number of PDU session groups of the network slice of the first network element does not reach the maximum number of PDU session groups of the network slice, and the first network element performs network slice admission control on the PDU session requested to be activated considering the group identifier associated with the PDU session.

[0487] In some embodiments, the first network element allows the PDU session to be activated to the network slice, including: accepting the activation request of the PDU session in the network slice, adding the PDU session to the activated list, and increasing the number of activated PDU sessions of the network slice.

[0488] In some embodiments, the number of PDU session groups of the network slice of the first network element does not reach the maximum number of PDU session groups of the network slice, and the first network element does not send a fourth request including the first information to the second network element.

[0489] Step S2204: The first network element sends first information to the second network element.

[0490] In some embodiments, the second network element receives the first information sent by the first network element.

[0491] In some embodiments, the second network element is at least used to perform global management on one or more first network elements.

[0492] In some embodiments, the service area of ​​the second network element includes the service area of ​​the first network element. For example, the service area of ​​the second network element is the entire service area, and the service area of ​​the first network element is one or more service areas in the entire service area.

[0493] In some embodiments, the second network element may be a primary NSACF.

[0494] In some embodiments, the first information is included in a fourth request sent by the first network element to the second network element. For example, the fourth request is an NSAC request.

[0495] In some embodiments, in step S2204, the first network element sending the first information to the second network element may include:

[0496] receiving a third request including the first information sent by a fourth network element;

[0497] The fourth request sent by the first network element to the second network element; wherein the third request is used to update the number of activated PDU sessions, and the third request includes the first information.

[0498] In some embodiments, in step S2204, the first network element sending the first information to the second network element may include at least one of the following:

[0499] The number of PDU sessions of the network slice of the first network element reaches or does not reach the maximum number of PDU sessions of the network slice, and the first network element sends first information to the second network element;

[0500] The number of PDU session groups of the network slice of the first network element reaches the maximum number of PDU session groups of the network slice, and the first network element sends the first information to the second network element.

[0501] In some embodiments, the number of PDU sessions of the network slice of the first network element reaches or does not reach the maximum number of PDU sessions of the network slice, and the first network element sends a fourth request including the first information to the second network element.

[0502] In some embodiments, the number of PDU session groups of the network slice of the first network element reaches the maximum number of PDU session groups of the network slice, and the first network element sends a fourth request including the first information to the second network element.

[0503] Here, the third request and the fourth request both include the identifier of the network slice.

[0504] In some embodiments, the first information is at least used to instruct the second network element to perform network slice admission control on the PDU session requested to be activated.

[0505] In some embodiments, the first information may be used to indicate network slice admission control for the PDU session requested to be deactivated.

[0506] For example, network slice admission control for PDU sessions requested for activation may include increasing the number of activated PDU sessions in the network slice.

[0507] For example, network slice admission control for PDU sessions requested to be deactivated may include reducing the number of activated PDU sessions in the network slice.

[0508] In some embodiments, the first information may be included in a fourth request sent by the first network element to the second network element. For example, the request message is: Nnsacf_NSAC_NumOfPDUsUpdate_Request message.

[0509] In the embodiment of the present disclosure, the number of PDU sessions of a network slice is the number of activated PDU sessions of the network slice.

[0510] In the embodiment of the present disclosure, the number of PDU session groups of a network slice is the number of activated PDU session groups of the network slice.

[0511] Step S2205: The second network element performs network slice admission control on the PDU session.

[0512] In some embodiments, the second network element performs network slice admission control on the PDU session requested to be activated.

[0513] In some embodiments, the second network element may perform network slice admission control on the PDU session based on the overall maximum number of PDU sessions and the first information.

[0514] In some embodiments, the second network element determines whether to accept the NSAC request of the first network element based on the reserved number in the overall PDU session number and the first information.

[0515] In some embodiments, the reserved quantity is one of the following:

[0516] The reserved NSAC PDU session quota associated with the group identifier;

[0517] Reserve the NSAC group quota, which is associated with the PDU session group identified by the group identifier.

[0518] In some implementations, the PDU session quota (i.e., the PDU session number quota) may be the number of PDU sessions allowed to be activated that the second network element configures for the network slice of the first network element.

[0519] In some embodiments, for the group identifier included in the first information, when there is a group quota of a reserved NSAC associated with the group identifier in the second network element, the second network element allows the PDU session requested to be activated to the network slice.

[0520] For example, the second network element allows the PDU session requested to be activated to be registered to the network slice, which may include: the second network element accepts the NSAC request of the first network element and increases the number of PDU session groups in the network slice.

[0521] In some embodiments, for the group identifier included in the first information, when there is no group quota of the reserved NSAC associated with the group identifier in the second network element, the second network element does not allow the activated PDU session to be activated to the network slice.

[0522] For example, the second network element does not allow the PDU session requested to be activated to be activated to the network slice registered, which may include: the second network element rejects the NSAC request of the first network element and does not update the number of activated PDU session groups in the network slice.

[0523] Step S2206: The second network element sends ninth information to the first network element.

[0524] In some embodiments, the first network element receives ninth information sent by the second network element.

[0525] In some embodiments, the ninth information may be used to indicate whether activation of the PDU session to the network slice is allowed.

[0526] In some embodiments, the ninth information may be included in a second response sent by the second network element to the first network element. For example, the second response may be a Nnsacf_NSAC_NumOfPDUsUpdate_Response message.

[0527] In some embodiments, the second response includes third information, and the third information is used to update the maximum number of PDU sessions of the network slice of the first network element.

[0528] In some embodiments, if the second network element determines to adjust the configuration value stored on the first network element, the update information of the configuration value may be included in the ninth information.

[0529] In some embodiments, the configuration value may be the maximum number of PDU sessions of the network slice of the first network element, and / or the maximum number of PDU session groups of the network slice of the first network element.

[0530] In some embodiments, the updated information of the configuration value may be used to indicate an increase in the maximum number of PDU sessions and / or the maximum number of PDU session groups, or the updated information of the configuration value may be used to indicate a decrease in the maximum number of PDU sessions and / or the maximum number of PDU session groups.

[0531] In some embodiments, the third information and the ninth information may be interchangeable.

[0532] Step S2207: The first network element determines the tenth information.

[0533] In some embodiments, if the ninth information from the second network element includes an updated configuration value, the first network element performs NSAC on the PDU session requested to be activated based on the received update information to obtain the tenth information.

[0534] For example, based on the updated configuration value, NSAC for the specified network slice is performed on the terminal according to the group identifier (XR group ID or XR service ID) associated with the terminal.

[0535] In some embodiments, the tenth information may be used to indicate the result of the first network element performing NSAC on the PDU session; for example, the tenth information indicates that the PDU session is allowed to be activated to the network slice, or indicates that the PDU session is refused to be activated to the network slice.

[0536] In some embodiments, if the ninth information from the second network element does not include update information of the configuration value, the ninth information is returned to the fourth network element as the tenth information.

[0537] Step S2208: The first network element sends the tenth information to the fourth network element.

[0538] In some embodiments, the fourth network element receives the tenth information sent by the first network element.

[0539] In some embodiments, the tenth information may be included in a response message sent by the first network element to the fourth network element. For example, the response message may be an Nnsacf_NSAC_NumOfPDUsUpdate_Response message.

[0540] In some examples, the response message sent by the first network element to the fourth network element includes a slice identifier S-NSSAI(s) and a result indication, where the result indication indicates whether the number of activated PDU sessions for the network slice has reached a maximum number of registered terminals. Optionally, the result indication may be used to indicate whether the number of activated PDU session terminals for the network slice has reached a maximum number of PDU sessions.

[0541] In some embodiments, the slice identifier S-NSSAI(s) included in the response message may include at least one of the following:

[0542] Identifier of the network slice that allows the PDU session activation;

[0543] Identifier of the network slice that rejected the PDU session activation.

[0544] In some embodiments, if the number of activated PDU sessions or PDU session groups sent by the first network element to the fourth network element for the network slice has reached the maximum allowed value, the fourth network element may reject the session establishment request, for example, the rejection reason is set to "the number of sessions allowed by the slice has been reached", or the rejection reason is set to "the number of session groups allowed by the slice has been reached".

[0545] The information processing method involved in the embodiments of the present disclosure may include at least one of steps S2201 to S2208. For example, step S2201 can be implemented as an independent embodiment, step S2203 can be implemented as an independent embodiment, and step S2204 can be implemented as an independent embodiment. For example, steps S2201 to S2203 combined with step S2208 can be implemented as an independent embodiment, steps S2204 to S2208 can be implemented as an independent embodiment, and steps S2201 to S2208 can be implemented as an independent embodiment, but are not limited thereto.

[0546] In some embodiments, step S2201, step S2202, and step S2203 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0547] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0548] Figure 2c is an interactive diagram of an information processing method according to an embodiment of the present disclosure. As shown in Figure 2c, the present disclosure embodiment relates to an information processing method for use in a communication system 100, and the method may include:

[0549] Step S2301: The second network element determines to update the local maximum number.

[0550] In some embodiments, the second network element is at least used to perform global management on one or more first network elements.

[0551] In some embodiments, the service area of ​​the second network element includes the service area of ​​the first network element. For example, the service area of ​​the second network element is the entire service area, and the service area of ​​the first network element is one or more service areas in the entire service area.

[0552] In some embodiments, the second network element may be a master NSACF and the first network element may be a local NSACF.

[0553] In some embodiments, the local maximum number may be a local maximum number of terminal groups or a local number of PDU session groups. For example, the master NSACF as the second network element determines to update the maximum number of terminal groups or the maximum number of PDU session groups of the local NSACF as the first network element.

[0554] In some embodiments, the local maximum number configured for the first network element may be configured by the second network element based on one of the number of currently registered terminal groups and the number of PDU session groups of the first network element and an operator policy.

[0555] In some embodiments, the updated local maximum number of groups may be higher or lower than the current local maximum number of groups.

[0556] In some embodiments, the second network element may update the local maximum number of terminal groups and / or the local maximum number of PDU session groups allocated to the first network element at any time.

[0557] In some embodiments, the second network element may update the NSAC quota according to the remaining quota or the used quota in the NSAC quota.

[0558] In some embodiments, the NSAC quota is used to indicate: at least one of the maximum number of registered terminal groups and the maximum number of PDU session groups of the network slice of the first network element.

[0559] In some embodiments, the second network element may determine to update the local maximum number based on the fourth information sent by the first network element.

[0560] In some embodiments, the fourth information is used to indicate the remaining quota or the used quota in the NSAC quota allocated by the second network element to the first network element.

[0561] In some embodiments, the second network element receives fourth information sent by the first network element.

[0562] In some embodiments, the second network element receives fourth information sent by the first network element based on a subscription request from the second network element; wherein the subscription request is used to subscribe to the fourth information sent by the first network element for the remaining quota or the used quota in the NSAC quota.

[0563] For example, the fourth information may be sent by the first network element to the second network element based on the subscription request when the remaining quota or the used quota changes.

[0564] For example, the fourth information may be periodically sent by the first network element to the second network element based on a subscription request.

[0565] Step S2302: The second network element sends the eleventh information to the first network element.

[0566] In some embodiments, the first network element receives eleventh information sent by the second network element.

[0567] In some embodiments, the eleventh information includes update information of the local maximum number of terminal groups or the local maximum number of PDU session groups. For example, the eleventh information includes the new local maximum number of terminal groups or the local maximum number of PDU session groups.

[0568] In some embodiments, the eleventh information is included in a fifth request sent by the second network element to the first network element. The fifth request may be, for example, an Nnsacf_NSAC_LocalNumberUpdate request.

[0569] Step S2303: The first network element updates the local maximum number.

[0570] In some embodiments, the first network element updates the local maximum number of terminal groups or the local maximum number of PDU session groups according to the update information of the local maximum number of terminal groups or the local maximum number of PDU session groups included in the eleventh information.

[0571] For example, the local NSACF replaces the original local maximum terminal group number with the received new local maximum terminal group number. Or, for example, the local NSACF replaces the original local maximum PDU session group number with the received new local maximum PDU session group number.

[0572] Step S2304: The first network element sends twelve pieces of information to the second network element.

[0573] In some embodiments, the second network element receives the twelfth information sent by the first network element.

[0574] In some embodiments, the twelfth information is included in a response sent by the first network element to the second network element. For example, the response may be an Nnsacf_NSAC_LocalNumberUpdate response returned by the NSACF to the master NSACF.

[0575] The information processing method involved in the embodiments of the present disclosure may include at least one of steps S2301 to S2304. For example, step S2302 may be implemented as an independent embodiment, and step S2303 may be implemented as an independent embodiment. For example, steps S2301 through step S2304 may be implemented as independent embodiments. Steps S2302 through S2304 may be implemented in combination as independent embodiments.

[0576] In some embodiments, step S2301 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0577] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0578] Figure 3a is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in Figure 3a, the embodiment of the present disclosure relates to an information processing method, which is executed by a first network element. The method includes:

[0579] Step S3101: Obtain first information.

[0580] In some embodiments, the optional implementation of step S3101 can refer to the optional implementation of step S2102 in Figure 2a and other related parts of the embodiment involved in Figure 2a, which will not be repeated here.

[0581] In some embodiments, the first network element receives the first information sent by the third network element, but is not limited thereto and may also receive the first information sent by other entities.

[0582] In some embodiments, the first information includes a group identifier.

[0583] In some embodiments, in step S3101, obtaining the first information may include at least one of the following:

[0584] The first network element receives the group identifier sent by the fifth network element.

[0585] The first network element determines the group identifier based on local configuration information and / or OAM configuration information. Exemplarily, the fifth network element may be used for policy control, and the fifth network element may be a network element such as a PCF or a NEF. For example, the local NSACF receives the group identifier sent by the PCF.

[0586] In some embodiments, the first network element receives the group identifier sent by the fifth network element, including at least one of the following:

[0587] In the case of not receiving the group identifier sent by the third network element, the first network element receives the group identifier from the fifth network element;

[0588] In a case where the first request sent by the third network element does not include the group identifier, the first network element receives the group identifier from the fifth network element.

[0589] In some embodiments, the first network element determines the group identifier based on the local configuration information and / or the OAM configuration information, including at least one of the following:

[0590] In the case of not receiving the group identifier sent by the third network element, the first network element determines the group identifier based on the local configuration information and / or the OAM configuration information;

[0591] In a case where the first request sent by the third network element does not include the group identifier, the first network element determines the group identifier based on local configuration information and / or OAM configuration information.

[0592] In some embodiments, the group identifier may include a first group identifier. The first group identifier is used to identify a service group or an application group associated with the terminal.

[0593] In some embodiments, the first network element obtains first information specified by a protocol.

[0594] In some embodiments, the first network element obtains the first information from an upper layer(s).

[0595] In some embodiments, the first network element performs processing to obtain the first information.

[0596] In some embodiments, step S3101 is omitted, the first network element autonomously implements the function indicated by the first information, or the above function is default or by default.

[0597] Step S3102: Perform network slice admission control on the terminal.

[0598] In some embodiments, the optional implementation of step S3102 can refer to the optional implementation of step S2103 in Figure 2a and other related parts of the embodiment involved in Figure 2a, which will not be repeated here.

[0599] Step S3103: Send the first information.

[0600] In some embodiments, the optional implementation of step S3103 can refer to the optional implementation of step S2104 in Figure 2a and other related parts of the embodiment involved in Figure 2a, which will not be repeated here.

[0601] In some embodiments, the first network element sends the first information to the second network element, but is not limited thereto, and the first information may also be sent to other entities.

[0602] Optionally, the first information is used to instruct the second network element to perform network slice admission control on the terminal. Its optional implementation method can refer to the optional implementation method of step S2105 of Figure 2a and other related parts in the embodiment involved in Figure 2a, which will not be repeated here.

[0603] In some embodiments, regardless of whether the group identifier included in the first information comes from a third network element, the first network element can send the first information including the group identifier to the second network element. For example, the first information is included in a second request sent by the first network element to the second network element, and the second request can be an NSAC request.

[0604] Step S3104: Obtain the seventh information.

[0605] In some embodiments, the optional implementation of step S3104 can refer to the optional implementation of step S2106 in Figure 2a and other related parts of the embodiment involved in Figure 2a, which will not be repeated here.

[0606] In some embodiments, the first network element receives the seventh information sent by the second network element, but is not limited thereto and may also receive the seventh information sent by other entities.

[0607] In some embodiments, the first network element obtains seventh information specified by the protocol.

[0608] In some embodiments, the first network element obtains the seventh information from an upper layer(s).

[0609] In some embodiments, the first network element performs processing to obtain the seventh information.

[0610] In some embodiments, step S3104 is omitted, the first network element autonomously implements the function indicated by the seventh information, or the above function is default or by default.

[0611] Step S3105: Determine the eighth information.

[0612] In some embodiments, the optional implementation of step S3105 can refer to the optional implementation of step S2107 in Figure 2a and other related parts of the embodiment involved in Figure 2a, which will not be repeated here.

[0613] Step S3106: Send the eighth information.

[0614] In some embodiments, the optional implementation of step S3106 can refer to the optional implementation of step S2108 in Figure 2a and other related parts of the embodiment involved in Figure 2a, which will not be repeated here.

[0615] In some embodiments, the first network element sends the eighth information to the third network element, but is not limited thereto, and the eighth information may also be sent to other entities.

[0616] The information processing method involved in the embodiments of the present disclosure may include at least one of steps S3101 to S3106. For example, step S3101 can be implemented as an independent embodiment, and step S3103 can be implemented as an independent embodiment. For example, steps S3101 to S3102 can be implemented as independent embodiments, steps S3103 to S3105 can be implemented as independent embodiments, and steps S3101 to S3106 can be implemented as independent embodiments, but are not limited thereto.

[0617] In some embodiments, steps S3101, S3102, and S3106 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0618] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0619] Figure 3b is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in Figure 3b, the embodiment of the present disclosure relates to an information processing method, which is executed by a first network element. The method includes:

[0620] Step S3201: Obtain first information.

[0621] In some embodiments, the optional implementation of step S3201 can refer to the optional implementation of step S2202 in Figure 2b and other related parts of the embodiment involved in Figure 2b, which will not be repeated here.

[0622] In some embodiments, the first network element receives the first information sent by the fourth network element, but is not limited thereto and may also receive the first information sent by other entities.

[0623] In some embodiments, the first information includes a group identifier.

[0624] In some embodiments, in step S3201, obtaining the first information may include at least one of the following:

[0625] The first network element receives the group identifier sent by the fifth network element.

[0626] The first network element determines the group identifier based on local configuration information and / or OAM configuration information. Exemplarily, the fifth network element may be used for policy control, and the fifth network element may be a network element such as a PCF or a NEF. For example, the local NSACF receives the group identifier sent by the PCF.

[0627] In some embodiments, the first network element receives the group identifier sent by the fifth network element, including at least one of the following:

[0628] In the case of not receiving the group identifier sent by the fourth network element, the first network element receives the group identifier from the fifth network element;

[0629] In a case where the third request sent by the fourth network element does not include the group identifier, the first network element receives the group identifier from the fifth network element.

[0630] In some embodiments, the first network element determines the group identifier based on the local configuration information and / or the OAM configuration information, including at least one of the following:

[0631] In a case where the group identifier sent by the fourth network element is not received, the first network element determines the group identifier based on the local configuration information and / or the OAM configuration information;

[0632] In a case where the third request sent by the fourth network element does not include the group identifier, the first network element determines the group identifier based on the local configuration information and / or the OAM configuration information.

[0633] In some embodiments, the group identifier may include a second group identifier. The second group identifier is used to identify a service group or an application group associated with the PDU session. In some embodiments, the first network element obtains first information specified by a protocol.

[0634] In some embodiments, the first network element obtains the first information from an upper layer(s).

[0635] In some embodiments, the first network element performs processing to obtain the first information.

[0636] In some embodiments, step S3201 is omitted, the first network element autonomously implements the function indicated by the first information, or the above function is default or by default.

[0637] Step S3202: Perform network slice admission control on the PDU session.

[0638] In some embodiments, the optional implementation of step S3202 can refer to the optional implementation of step S2203 in Figure 2b and other related parts of the embodiment involved in Figure 2b, which will not be repeated here.

[0639] Step S3203: Send the first information.

[0640] In some embodiments, the optional implementation of step S3203 can refer to the optional implementation of step S2204 in Figure 2b and other related parts of the embodiment involved in Figure 2b, which will not be repeated here.

[0641] In some embodiments, the first network element sends the first information to the second network element, but is not limited thereto, and the first information may also be sent to other entities.

[0642] Optionally, the first information is used to instruct the second network element to perform network slice admission control on the terminal. Its optional implementation method can be found in the optional implementation method of step S2205 of Figure 2b and other related parts of the embodiment involved in Figure 2b, which will not be repeated here.

[0643] In some embodiments, regardless of whether the group identifier included in the first information comes from the fourth network element, the first network element can send the first information including the group identifier to the second network element. For example, the first information is included in a fourth request sent by the first network element to the second network element, and the fourth request can be an NSAC request.

[0644] Step S3204: Obtain ninth information.

[0645] In some embodiments, the optional implementation of step S3204 can refer to the optional implementation of step S2206 in Figure 2b and other related parts of the embodiment involved in Figure 2b, which will not be repeated here.

[0646] In some embodiments, the first network element receives the ninth information sent by the second network element, but is not limited thereto and may also receive the ninth information sent by other entities.

[0647] In some embodiments, the first network element obtains ninth information specified by the protocol.

[0648] In some embodiments, the first network element obtains the ninth information from an upper layer(s).

[0649] In some embodiments, the first network element performs processing to obtain the ninth information.

[0650] In some embodiments, step S3204 is omitted, the first network element autonomously implements the function indicated by the ninth information, or the above function is default or by default.

[0651] Step S3205: Determine the tenth information.

[0652] In some embodiments, the optional implementation of step S3205 can refer to the optional implementation of step S2207 in Figure 2b and other related parts of the embodiment involved in Figure 2b, which will not be repeated here.

[0653] Step S3206: Send the tenth message.

[0654] In some embodiments, the optional implementation of step S3206 can refer to the optional implementation of step S2208 in Figure 2b and other related parts of the embodiment involved in Figure 2b, which will not be repeated here.

[0655] In some embodiments, the first network element sends the tenth information to the fourth network element, but is not limited thereto, and the tenth information may also be sent to other entities.

[0656] The information processing method involved in the embodiments of the present disclosure may include at least one of steps S3201 to S3206. For example, step S3201 can be implemented as an independent embodiment, and step S3203 can be implemented as an independent embodiment. For example, steps S3201 to S3202 can be implemented as independent embodiments, steps S3203 to S3205 can be implemented as independent embodiments, and steps S3201 to S3206 can be implemented as independent embodiments, but are not limited thereto.

[0657] In some embodiments, steps S3201, S3202, and S3206 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0658] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0659] Figure 3c is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in Figure 3c, the embodiment of the present disclosure relates to an information processing method, which is executed by a first network element. The method includes:

[0660] Step S3301: Obtain the eleventh information.

[0661] In some embodiments, the optional implementation of step S3301 can refer to the optional implementation of step S2302 in Figure 2c and other related parts of the embodiment involved in Figure 2c, which will not be repeated here.

[0662] In some embodiments, the first network element receives the eleventh information sent by the second network element, but is not limited thereto and may also receive the eleventh information sent by other entities.

[0663] In some embodiments, the first network element obtains eleventh information specified by the protocol.

[0664] In some embodiments, the first network element obtains the eleventh information from an upper layer(s).

[0665] In some embodiments, the first network element performs processing to obtain the ninth information.

[0666] In some embodiments, step S3204 is omitted, the first network element autonomously implements the function indicated by the eleventh information, or the above function is default or default.

[0667] Step S3302: Update the local maximum number.

[0668] In some embodiments, the optional implementation of step S3302 can refer to the optional implementation of step S2303 in Figure 2c and other related parts of the embodiment involved in Figure 2c, which will not be repeated here.

[0669] Step S3303: Send twelve messages.

[0670] In some embodiments, the optional implementation of step S3303 can refer to the optional implementation of step S2304 in Figure 2c and other related parts of the embodiment involved in Figure 2c, which will not be repeated here.

[0671] In some embodiments, the first network element sends the twelfth information to the second network element, but is not limited thereto, and the twelfth information may also be sent to other entities.

[0672] The information processing method involved in the embodiments of the present disclosure may include at least one of steps S3301 to S3303. For example, step S3301 can be implemented as an independent embodiment, and step S3302 can be implemented as an independent embodiment. For example, steps S3301 to S3302 can be implemented as independent embodiments, and steps S3301 to S3303 can be implemented as independent embodiments, but are not limited thereto.

[0673] In some embodiments, step S3301 and step S3303 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0674] Figure 3d is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in Figure 3d, the embodiment of the present disclosure relates to an information processing method, which is executed by a first network element. The method includes:

[0675] Step S3401: Send first information to the second network element; wherein the first information is used to instruct the second network element to perform NSAC on the terminal requesting registration or the PDU session requesting activation; wherein the first information includes a group identifier associated with the terminal or the PDU session.

[0676] In some embodiments, in step S3401, sending the first information to the second network element includes:

[0677] Step S3401a: Receive a first request including the first information sent by a third network element;

[0678] Step S3401b: Sending a second request including the first information to the second network element; wherein the first request is used to update the number of registered terminals;

[0679] In some embodiments, the optional implementation of step S3401a can refer to the optional implementation of step S2102 in Figure 2a, step S3101 in Figure 3a, and other related parts in the embodiments involved in Figures 2a and 3a, which will not be repeated here.

[0680] In some embodiments, the optional implementation of step S3401b can refer to the optional implementation of step S2104 in Figure 2a, step S3103 in Figure 3a, and other related parts in the embodiments involved in Figures 2a and 3a, which will not be repeated here.

[0681] In some embodiments, in step S3401, sending the first information to the second network element includes:

[0682] Step S3401c: Receive a third request including the first information sent by the fourth network element;

[0683] Step S3401d: Send a fourth request including the first information to the second network element; wherein the third request is used to update the number of activated PDU sessions.

[0684] In some embodiments, the optional implementation of step S3401c can refer to the optional implementation of step S2202 in Figure 2b, step S3201 in Figure 3b, and other related parts in the embodiments involved in Figures 2b and 3b, which will not be repeated here.

[0685] In some embodiments, the optional implementation method of step S3301d can refer to the optional implementation method of step S2204 in Figure 2b, step S3203 in Figure 3b, and other related parts in the embodiments involved in Figures 2b and 3b, which will not be repeated here.

[0686] In some embodiments, in step S3401b, sending a second request including the first information to the second network element includes:

[0687] The number of registered terminals of the network slice of the first network element reaches or does not reach the maximum number of registered terminals of the network slice, and a second request including the first information is sent to the second network element.

[0688] In some embodiments, in step S3401b, sending a second request including the first information to the second network element includes:

[0689] The number of registered terminal groups of the network slice of the first network element reaches the maximum number of registered terminal groups of the network slice, and a second request including the first information is sent to the second network element.

[0690] In some embodiments, in step S3401d, sending a fourth request including the first information to the second network element includes:

[0691] The number of PDU sessions of the network slice of the first network element reaches or does not reach the maximum number of PDU sessions of the network slice, and sends a fourth request including the first information to the second network element;

[0692] In some embodiments, in step S3401d, sending a fourth request including the first information to the second network element includes:

[0693] The number of PDU session groups of the network slice of the first network element reaches the maximum number of PDU session groups of the network slice, and a fourth request including the first information is sent to the second network element.

[0694] In some embodiments, in step S3401, sending the first information to the second network element includes:

[0695] The number of PDU sessions of the network slice of the first network element reaches or does not reach the maximum number of PDU sessions of the network slice, sending the first information to the second network element; and / or,

[0696] The number of PDU session groups of the network slice of the first network element reaches the maximum number of PDU session groups of the network slice, and the first information is sent to the second network element.

[0697] In some embodiments, the method further comprises at least one of the following:

[0698] Step S3402: Receive a first response corresponding to the second request sent by the second network element; wherein the first response includes second information, and the second information is used to update the maximum number of registered terminals of the network slice of the first network element;

[0699] Step S3403: Receive a second response corresponding to the fourth request sent by the second network element; wherein the second response includes third information, and the third information is used to update the maximum PDU session number of the network slice of the first network element.

[0700] In some embodiments, the optional implementation of step S3402 can refer to the optional implementation of step S2106 in Figure 2a, step S3104 in Figure 3a, and other related parts in the embodiments involved in Figures 2a and 3a, which will not be repeated here.

[0701] In some embodiments, the optional implementation of step S3403 can refer to the optional implementation of step S2206 in Figure 2b, step S3204 in Figure 3b, and other related parts in the embodiments involved in Figures 2b and 3b, which will not be repeated here.

[0702] In some embodiments, the method further comprises:

[0703] Step S3404: Send fourth information to the second network element; wherein, the fourth information is used to indicate the remaining quota or used quota in the NSAC quota allocated by the second network element to the first network element; the NSAC quota is used to indicate: at least one of the maximum number of registered terminal groups and the maximum number of PDU session groups of the network slice of the first network element.

[0704] In some embodiments, the optional implementation of step S3404 can refer to the optional implementation of step S2301 in Figure 2c and other related parts of the embodiment involved in Figure 2c, which will not be repeated here.

[0705] In some embodiments, in step S3404, sending fourth information to the second network element includes:

[0706] The fourth information is sent to the second network element according to the subscription request from the second network element, wherein the subscription request is used to subscribe the remaining quota or the used quota in the NSAC quota to the first network element.

[0707] In some embodiments, the first network element is a local NSACF network element, and the second network element is a master NSACF network element;

[0708] The third network element is the AMF network element, and the fourth network element is the SMF network element.

[0709] In some embodiments, the method further comprises at least one of the following:

[0710] Step S3405: ​​Determine the group identifier based on the local configuration information and / or operation, maintenance and management (OAM) configuration information of the first network element;

[0711] Step S3406: Receive the group identifier sent by the fifth network element.

[0712] In some embodiments, the optional implementation methods of step S3405 and step S3406 can refer to the optional implementation methods of step S3101 in Figure 3a and step S3201 in Figure 3b, as well as other related parts in the embodiments involved in Figures 3a and 3b, which will not be repeated here.

[0713] In some embodiments, the group identifier is used to identify at least one of the following:

[0714] The service group associated with the terminal requesting registration;

[0715] The application group associated with the terminal requesting registration;

[0716] The service group associated with the PDU session requested to be activated;

[0717] The application group associated with the PDU session requested to be activated.

[0718] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0719] Figure 4a is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in Figure 4a, the embodiment of the present disclosure relates to an information processing method, which is executed by a second network element. The method includes:

[0720] Step S4101: Obtain first information.

[0721] In some embodiments, the optional implementation of step S4101 can refer to the optional implementation of step S2104 in Figure 2a and other related parts of the embodiment involved in Figure 2a, which will not be repeated here.

[0722] In some embodiments, the second network element receives the first information sent by the first network element, but is not limited thereto and may also receive the first information sent by other entities.

[0723] In some embodiments, the second network element obtains first information specified by the protocol.

[0724] In some embodiments, the second network element obtains the first information from an upper layer(s).

[0725] In some embodiments, the second network element performs processing to obtain the first information.

[0726] In some embodiments, step S4101 is omitted, the second network element autonomously implements the function indicated by the first information, or the above function is default or by default.

[0727] Step S4102: Perform network slice admission control on the terminal.

[0728] In some embodiments, the optional implementation of step S4102 can refer to the optional implementation of step S2105 in Figure 2a and other related parts of the embodiment involved in Figure 2a, which will not be repeated here.

[0729] Step S4103: Send the seventh message.

[0730] In some embodiments, the optional implementation of step S4103 can refer to the optional implementation of step S2106 in Figure 2a and other related parts of the embodiment involved in Figure 2a, which will not be repeated here.

[0731] In some embodiments, the second network element sends the seventh information to the first network element, but is not limited thereto, and the seventh information may also be sent to other entities.

[0732] Optionally, the seventh information mentioned above can be used to indicate whether the terminal is allowed to be registered to the network slice.

[0733] The information processing method involved in the embodiments of the present disclosure may include at least one of steps S4101 to S4103. For example, step S4101 can be implemented as an independent embodiment, and step S4102 can be implemented as an independent embodiment. For example, steps S4101 to S4103 can be implemented as an independent embodiment, and steps S4102 to S4103 can be implemented as an independent embodiment, but are not limited thereto.

[0734] In some embodiments, step S4101 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0735] Figure 4b is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in Figure 4b, the embodiment of the present disclosure relates to an information processing method, which is executed by a second network element. The method includes:

[0736] Step S4201: Obtain first information.

[0737] In some embodiments, the optional implementation of step S4201 can refer to the optional implementation of step S2204 in Figure 2b and other related parts of the embodiment involved in Figure 2b, which will not be repeated here.

[0738] In some embodiments, the second network element receives the first information sent by the first network element, but is not limited thereto and may also receive the first information sent by other entities.

[0739] In some embodiments, the second network element obtains first information specified by the protocol.

[0740] In some embodiments, the second network element obtains the first information from an upper layer(s).

[0741] In some embodiments, the second network element performs processing to obtain the first information.

[0742] In some embodiments, step S4101 is omitted, the second network element autonomously implements the function indicated by the first information, or the above function is default or by default.

[0743] Step S4202: Perform network slice admission control on the PDU session.

[0744] In some embodiments, the optional implementation of step S4202 can refer to the optional implementation of step S2205 in Figure 2b and other related parts of the embodiment involved in Figure 2b, which will not be repeated here.

[0745] Step S4203: Send the ninth message.

[0746] In some embodiments, the optional implementation of step S4203 can refer to the optional implementation of step S2206 in Figure 2b and other related parts of the embodiment involved in Figure 2b, which will not be repeated here.

[0747] In some embodiments, the second network element sends the ninth information to the first network element, but is not limited thereto, and the ninth information may also be sent to other entities.

[0748] Optionally, the ninth information mentioned above can be used to indicate whether the PDU session is allowed to be activated to the network slice.

[0749] The information processing method involved in the embodiments of the present disclosure may include at least one of steps S4101 to S4203. For example, step S4201 can be implemented as an independent embodiment, and step S4202 can be implemented as an independent embodiment. For example, steps S4201 to S4203 can be implemented as an independent embodiment, and steps S4202 to S4203 can be implemented as an independent embodiment, but are not limited thereto.

[0750] In some embodiments, step S4201 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0751] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0752] Figure 4c is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in Figure 4c, the embodiment of the present disclosure relates to an information processing method, which is executed by the second network element. The method includes:

[0753] Step S4301: Determine the maximum number of local updates.

[0754] In some embodiments, the optional implementation of step S4301 can refer to the optional implementation of step S2301 in Figure 2c and other related parts of the embodiment involved in Figure 2c, which will not be repeated here.

[0755] Step S4302: Send the eleventh message.

[0756] In some embodiments, the optional implementation of step S4302 can refer to the optional implementation of step S2302 in Figure 2c and other related parts of the embodiment involved in Figure 2c, which will not be repeated here.

[0757] In some embodiments, the second network element sends the eleventh information to the first network element, but is not limited thereto, and the eleventh information may also be sent to other entities.

[0758] In some embodiments, the eleventh information may be used by the first network element to update the local maximum number.

[0759] The information processing method involved in the embodiment of the present disclosure may include at least one of step S4301 and step S4302. For example, step S4301 and step S4302 may be implemented as independent embodiments, but are not limited thereto.

[0760] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0761] Figure 4d is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in Figure 4d, the embodiment of the present disclosure relates to an information processing method, which is executed by a second network element. The method includes:

[0762] Step S4401: Receive first information sent by a first network element; wherein the first information is used to instruct a second network element to perform NSAC on a terminal requesting registration or a PDU session requesting activation; wherein the first information includes a group identifier associated with the terminal or the PDU session.

[0763] In some embodiments, in step S4401, the receiving of the first information sent by the first network element includes at least one of the following:

[0764] Step S4401a: Receive a second request including the first information sent by the first network element; wherein the second request is sent based on a first request including the first information from a third network element, and the first request is used to update the number of registered terminals;

[0765] Step S4401b: Receive a fourth request including the first information sent by the first network element; wherein the fourth request is sent based on a third request including the first information from the fourth network element, and the third request is used to update the number of created PDU sessions.

[0766] In some embodiments, the optional implementation of step S4401a can refer to the optional implementation of step S2104 in Figure 2a and other related parts of the embodiment involved in Figure 2a, which will not be repeated here.

[0767] In some embodiments, the optional implementation of step S4401b can refer to the optional implementation of step S2204 in Figure 2b and other related parts of the embodiment involved in Figure 2b, which will not be repeated here.

[0768] In some embodiments, the method further comprises at least one of the following:

[0769] Step S4402: Sending a first response corresponding to the second request to the first network element based on the overall maximum number of registered terminals and the first information;

[0770] Step S4403: Send a second response corresponding to the fourth request to the first network element based on the overall maximum PDU session number and the first information.

[0771] In some embodiments, the optional implementation of step S4402 can refer to the optional implementation of step S2106 in FIG2a and other related parts in the embodiment involved in FIG2a, which will not be repeated here.

[0772] In some embodiments, the optional implementation of step S4403 can refer to the optional implementation of step S2206 in Figure 2b and other related parts of the embodiment involved in Figure 2b, which will not be repeated here.

[0773] In some embodiments, the first response includes second information, and the second information is used to update the maximum number of registered terminals in the network slice of the first network element; and / or, the second response includes third information, and the third information is used to update the maximum number of PDU sessions in the network slice of the first network element.

[0774] In some embodiments, the method further comprises:

[0775] Step S4404: Determine a reserved number in the overall maximum number of registered terminals or the overall maximum number of PDU sessions, wherein the reserved number is one of the following:

[0776] a terminal quota of the reserved NSAC associated with the group identifier;

[0777] The reserved NSAC PDU session quota associated with the group identifier;

[0778] A group quota of the NSAC is reserved, where the group quota is associated with the terminal group or PDU session group identified by the group.

[0779] In some embodiments, the optional implementation of step S4404 can refer to the optional implementation of step S2105 in Figure 2a, step S2205 in Figure 2b, and other related parts in the embodiments involved in Figures 2a and 2b, which will not be repeated here.

[0780] In some embodiments, the method further comprises:

[0781] Step S4405: Receive the fourth information sent by the first network element; wherein the fourth information is used to indicate the remaining quota or used quota in the NSAC quota allocated by the second network element to the first network element; the NSAC quota is used to indicate: at least one of the maximum number of registered terminal groups and the maximum number of PDU session groups of the network slice of the first network element.

[0782] In some embodiments, the optional implementation of step S4405 can refer to the optional implementation of step S2301 in Figure 2c and other related parts of the embodiment involved in Figure 2c, which will not be repeated here.

[0783] In some embodiments, the method further comprises:

[0784] Send a subscription request to the first network element; wherein the subscription request is used to subscribe to the remaining quota or the used quota in the NSAC quota from the first network element.

[0785] In some embodiments, the method further comprises:

[0786] The NSAC quota is updated according to the remaining quota or the used quota in the NSAC quota.

[0787] In some embodiments, the group identifier is determined by the first network element based on local configuration information and / or operation, maintenance and management (OAM) configuration information of the first network element; or, the group identifier is received by the first network element from a fifth network element.

[0788] In some embodiments, the group identifier is used to identify at least one of the following:

[0789] The service group associated with the terminal requesting registration;

[0790] The application group associated with the terminal requesting registration;

[0791] The service group associated with the PDU session requested to be activated;

[0792] The application group associated with the PDU session requested to be activated.

[0793] The information processing method involved in the embodiment of the present disclosure may include at least one of steps S4401 to S4405. For example, steps S4401 to S4403 may be implemented as independent embodiments, but are not limited thereto.

[0794] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0795] Figure 5a is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in Figure 5a, the embodiment of the present disclosure relates to an information processing method, which is executed by a third network element, and the method includes:

[0796] Step S5101: Determine the first information.

[0797] In some embodiments, the optional implementation of step S5101 can refer to the optional implementation of step S2101 in Figure 2a and other related parts of the embodiment involved in Figure 2a, which will not be repeated here.

[0798] Step S5102: Send the first information.

[0799] In some embodiments, the optional implementation of step S5102 can refer to the optional implementation of step S2102 in Figure 2a and other related parts of the embodiment involved in Figure 2a, which will not be repeated here.

[0800] In some embodiments, the third network element sends the first information to the first network element, but is not limited thereto, and the first information may also be sent to other entities.

[0801] Step S5103: Receive the eighth information.

[0802] In some embodiments, the optional implementation of step S5102 can refer to the optional implementation of step S2102 in Figure 2a and other related parts of the embodiment involved in Figure 2a, which will not be repeated here.

[0803] In some embodiments, the third network element receives the eighth information sent by the first network element, but is not limited thereto, and may also receive the eighth information sent by other entities.

[0804] The information processing method involved in the embodiment of the present disclosure may include at least one of step S5101 to step S5102. For example, step S5101 to step S5103 may be implemented as an independent embodiment, but is not limited thereto.

[0805] Figure 5b is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in Figure 5b, the embodiment of the present disclosure relates to an information processing method, which is executed by a third network element, and the method includes:

[0806] Step S5201: Send first information to a first network element, wherein the first information is used to instruct a second network element to perform NSAC on a terminal requesting registration; wherein the first information includes a group identifier associated with the terminal.

[0807] In some embodiments, the optional implementation of step S5201 can refer to the optional implementation of step S2102 in Figure 2a, step S5102 in Figure 5a, and other related parts in the embodiments involved in Figures 2a and 5a, which will not be repeated here.

[0808] In some embodiments, in step S5201, sending the first information to the first network element includes:

[0809] Send a first request including the first information to the first network element; wherein the first request is used to update the number of registered terminals.

[0810] In some embodiments, the group identifier is determined by the third network element based on at least one of the following information:

[0811] Local configuration information;

[0812] Operation, maintenance and management (OAM) configuration information;

[0813] Unified Data Management (UDM) contract information;

[0814] Information indicating the extended reality (XR) multimodal service capability sent by the terminal;

[0815] Group information related to terminal identification;

[0816] Group information in the terminal context.

[0817] In some embodiments, the optional implementation of step S5202 can refer to the optional implementation of step S2101 in Figure 2a, step S5101 in Figure 5a, and other related parts in the embodiments involved in Figures 2a and 5a, which will not be repeated here.

[0818] In some embodiments, the group identifier is used to identify at least one of the following:

[0819] The service group associated with the terminal requesting registration;

[0820] The application group associated with the terminal requesting registration.

[0821] The information processing method involved in the embodiment of the present disclosure may include at least one of step S5201 and step S5202. For example, step S5201 and step S5202 may be implemented as independent embodiments, but are not limited thereto.

[0822] Figure 5c is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in Figure 5c, the embodiment of the present disclosure relates to an information processing method, which is executed by a fourth network element, and the method includes:

[0823] Step S5301: Determine the first information.

[0824] In some embodiments, the optional implementation of step S5301 can refer to the optional implementation of step S2201 in Figure 2b and other related parts of the embodiment involved in Figure 2b, which will not be repeated here.

[0825] Step S5302: Send the first information.

[0826] In some embodiments, the optional implementation of step S5302 can refer to the optional implementation of step S2202 in Figure 2b and other related parts of the embodiment involved in Figure 2b, which will not be repeated here.

[0827] In some embodiments, the fourth network element sends the first information to the first network element, but is not limited thereto, and the first information may also be sent to other entities.

[0828] Step S5303: Receive the tenth information.

[0829] In some embodiments, the optional implementation of step S5302 can refer to the optional implementation of step S2202 in Figure 2b and other related parts of the embodiment involved in Figure 2b, which will not be repeated here.

[0830] In some embodiments, the fourth network element receives the tenth information sent by the first network element, but is not limited thereto and may also receive the tenth information sent by other entities.

[0831] The information processing method involved in the embodiment of the present disclosure may include at least one of step S5301 to step S5302. For example, step S5301 to step S5303 may be implemented as an independent embodiment, but is not limited thereto.

[0832] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0833] Figure 5d is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in Figure 5d, the embodiment of the present disclosure relates to an information processing method, which is executed by a fourth network element, and the method includes:

[0834] Step S5401: Send first information to the first network element, wherein the first information is used to instruct the second network element to perform NSAC on the PDU session requested to be activated; wherein the first information includes a group identifier associated with the PDU session.

[0835] In some embodiments, the optional implementation of step S5401 can refer to the optional implementation of step S2202 in Figure 2b, step S5302 in Figure 5c, and other related parts in the embodiments involved in Figures 2b and 5c, which will not be repeated here.

[0836] In some embodiments, in step S5401, sending the first information to the first network element includes:

[0837] Send a third request including the first information to the first network element; wherein the third request is used to update the number of created PDUs.

[0838] In some embodiments, the group identifier is determined by the fourth network element based on at least one of the following information:

[0839] Local configuration information;

[0840] Operation, maintenance and management (OAM) configuration information;

[0841] Unified Data Management (UDM) contract information;

[0842] Information indicating the extended reality (XR) multimodal service capabilities sent by the terminal;

[0843] Group information related to terminal identification;

[0844] Indication information of the terminal's XR application or XR service capabilities.

[0845] In some embodiments, the optional implementation of step S5402 can refer to the optional implementation of step S2201 in Figure 2b, step S5301 in Figure 5c, and other related parts in the embodiments involved in Figures 2b and 5c, which will not be repeated here.

[0846] In some embodiments, the group identifier is used to identify at least one of the following:

[0847] The service group associated with the PDU session requested to be activated;

[0848] The application group associated with the PDU session requested to be activated.

[0849] The information processing method involved in the embodiment of the present disclosure may include at least one of step S5401 and step S5402. For example, step S5401 and step S5402 may be implemented as independent embodiments, but are not limited thereto.

[0850] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0851] Figure 6 is an interactive diagram of an information processing method according to an embodiment of the present disclosure. As shown in Figure 6a, the embodiment of the present disclosure relates to an information processing method for a communication system, the method comprising:

[0852] Step S6101: The first network element sends first information to the second network element; wherein the first information is used to instruct the second network element to perform NSAC on the terminal requesting registration or the PDU session requesting activation; wherein the first information includes a group identifier associated with the terminal or the PDU session.

[0853] In some embodiments, the optional implementation methods of step S6101 can refer to step S2104 of Figure 2a, step S2204 of Figure 2b, step S3103 of Figure 3a, step S3203 of Figure 3b, step S3401 of Figure 3d, step S4201 of Figure 4b, and step S4401 of Figure 4d, as well as other related parts in the embodiments involved in Figures 2a, 2b, 3a, 3b, 3d, 4b, and 4d, which will not be repeated here.

[0854] In some embodiments, the above method may include the methods of the above-mentioned first network element, second network element, third network element, fourth network element and other embodiments, which will not be repeated here.

[0855] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0856] The present disclosure provides an information processing method that enables NSAC for a terminal group (Group UE) or a PDU session group (Group PDU session) in a hierarchical NSACF architecture to be uniformly performed by the master NSACF. The NSACF (i.e., the local NSACF) sends a group identifier (e.g., an XR service group ID or a universal group ID) to the master NSACF, and the primary NSACF performs the overall NSAC for the UE group or PDU session group.

[0857] In one embodiment, local NSACF: When the group identity is included in the NSAC request provided by the AMF or SMF, the local NSACF interacts with the master NSACF to process the NSAC request.

[0858] In some examples, when the local NSACF provides a group identifier, the local NSACF interacts with the master NSACF to process the NSAC request regardless of whether the local maximum number of PDU sessions or the local maximum number of registered terminals has been reached.

[0859] In some examples, when the local NSACF provides a group identifier, the local maximum number of PDU session groups is reached or the local maximum number of registered terminal groups is reached, the local NSACF interacts with the master NSACF to process the NSAC request.

[0860] In some examples, the local maximum number of PDU session groups and / or the local maximum number of registered terminal groups are provided by the master NSACF.

[0861] In one embodiment, the master NSACF checks the overall maximum number of registered terminals or the overall maximum number of PDU sessions and considers the group identifier included in the NSAC request when determining whether to accept or reject the NSAC request from the local NSACF. Furthermore, the response to the NSAC request may include an indication of updating the local maximum number of registered terminals or the local maximum number of PDU sessions.

[0862] In some examples, to support NSAC quotas (e.g., UE groups for XR services, or PDU session groups for XR services from one or more UEs), the master NSACF always reserves a portion of the global maximum for use by the group (e.g., group quota).

[0863] In some examples, NSAC quotas can be used only by the master NSACF or allocated to each NSACF for authorized use (i.e., local quotas). When NSAC quotas are allocated to an NSACF, the master NSACF can subscribe to the remaining quota or used quota from the NSACF. For example, the master NSACF can receive a remaining quota report from the NSACF and update the group quota based on the remaining quota report.

[0864] In one embodiment, the AMF sends a group identifier to the local NSACF, in which case the NSACF monitors and controls the number of registered terminals for each network slice constrained by the NSAC.

[0865] In some examples, the AMF sends a terminal number update request message to the NSACF, which includes the terminal identifier, the access type of the authorized NSSAI, the relevant slice S-NSSAI(s) for which NSAC is requested to be executed, the AMF identifier, and the update flag.

[0866] The AMF also includes a group identifier in the request message to the NSACF, where the group identifier is used to identify the XR service group or application group to which the UE belongs (or is associated).

[0867] In some examples, the group identifier may be an internal group identifier, or a standardized universal group identifier.

[0868] Furthermore, the AMF determines the group identifier. For example, the AMF may determine the group identifier based on local configuration, OAM configuration, UDM subscription information, XR multimodal service capabilities and / or group information related to UE PEI sent by the UE, or group information in the UE context sent by other AMFs.

[0869] In one embodiment, the SMF sends a group identifier to the local NSACF. In this scenario, the NSACF monitors the network slices managed by the NSAC and controls the number of PDU sessions for each network slice.

[0870] In some examples, the SMF sends a PDU session number update request message to the NSACF, which includes a terminal identifier, a session ID, a slice identifier or an identifier list S-NSSAI(s) on which NSAC needs to be executed, an access type, and an update flag.

[0871] The SMF also includes a group identifier in the request message to the NSACF, where the group identifier is used to identify the XR service group or application group to which the PDU session belongs (or is associated).

[0872] In some examples, the group identifier may be an internal group identifier, or a standardized universal group identifier, or may be an XR application ID, or an XR service capability indication, etc.

[0873] In some examples, the SMF determines a group identifier (e.g., an XR service ID or a universal identifier). The SMF may determine the XR service ID, group identifier, or universal ID based on at least one of local configuration, OAM configuration, UDM subscription information, XR multimodal service capability / UE PEI-related group information sent by the UE, and indication information of the UE XR application or XR service capability sent by the RAN / AMF.

[0874] In some embodiments, an information processing method is provided, which involves a validity check and update process of the number of registered users of a slice under a hierarchical NSACF architecture.

[0875] As shown in Figure 7a, for S-NSSAI that counts the number of registered terminals, if a hierarchical NSACF architecture is deployed in the network, the maximum number of registered terminals for S-NSSAI can be enforced as follows:

[0876] In the registration process of the terminal, including the initial registration or the registration of the mobile registration update type caused by the cross-AMF handover, NSAC is executed before or after the registration acceptance message according to whether the early validity check EAC mode is enabled (for example, when the EAC is activated, the NSAC process is executed before the registration acceptance message; when the EAC is not activated, the NSAC process is executed after the registration acceptance message).

[0877] Step S7101: If the AMF does not know the peer NSACF, the AMF performs NSACF discovery and selection.

[0878] When a network slice S-NSSAI needs to perform NSAC, and the slice identifier is in the allowed NSSAI (for example, AMF requests the UE to register to the slice), or is deleted from the allowed NSSAI (AMF requests the UE to deregister from the slice), the AMF triggers the network slice validity check and update process to update the number of registered terminal users. The triggering event of the process also includes the change of allowed NSAAI caused by cross-AMF switching. This process is triggered in the following situations:

[0879] - In the registration process of the terminal, including the initial registration or the registration of the mobile registration update type caused by the inter-AMF handover, NSAC is performed before or after the registration accept message, depending on whether the early validity check (EAC) mode is enabled (for example, when EAC is activated, the NSAC process is performed before the registration accept message; when EAC is not activated, the NSAC process is performed after the registration accept message).

[0880] - In the deregistration process, after the deregistration process is completed, the NSAC process is executed to subtract the UE from the statistics.

[0881] - In the terminal configuration update process, such as the NSSAA slice-specific authentication process or the subscription S-NSSAI change process triggering a configuration update, NSAC is executed before or after the configuration update message according to the EAC mode (for example, if the EAC mode is activated and the update flag is to increase the number, NSAC is executed before the UE configuration update message; if the EAC mode is activated but the update flag is to decrease the number or the EAC mode is not activated, NSAC is executed after the UE configuration update message)

[0882] Step S7102: AMF sends Nnsacf_NSAC_NumOfUEsUpdate_Request message to NSACF.

[0883] In some examples, the AMF includes the terminal identity (UE ID), the access type of the authorized NSSAI, the relevant slice S-NSSAIs for which NSAC is requested, the AMF identity, and the update flag in the message. The update flag indicates whether the number of registered user UEs is increased or decreased, for example, when the user registers to the slice, the number is increased, and when the UE deregisters from the slice or the registration cannot continue, the number is decreased. If the UE is already registered, the AMF will also send a UE registered indication.

[0884] In some examples, if the UE belongs to a certain XR service group or application group, the AMF also includes a group identifier in the request message to the NSACF, which is used to identify the XR service group or application group to which the UE belongs. The group identifier can be an internal group identifier or a standardized universal group identifier.

[0885] In some examples, the AMF determines whether the UE belongs to an XR group and the group ID. The AMF may determine the corresponding group ID based on local configuration, OAM configuration, or UDM subscription information, or group information related to the XR multimodal service capability / UE PEI sent by the UE, or the XR multimodal service capability sent by the RAN, or other group information in the UE context sent by the AMF.

[0886] In some examples, if it is the first interaction between AMF and NSACF for this network slice and the NSAC process is executed, AMF will carry the relevant endpoint NF information that EAC needs to notify in the message, thereby implicitly subscribing to the EAC-related notifications of the slice from NSACF.

[0887] Step S7103: The local NSACF performs NSAC for the indicated network slice (S-NSSAI).

[0888] When the AMF provides an NSAC request including a group identifier, the local NSACF interacts with the primary NSACF to process the NSAC request.

[0889] When a group identifier is provided, the local NSACF interacts with the master NSACF to process the NSAC request, regardless of whether the local maximum number of registered terminals has been reached.

[0890] When the group identifier is provided and the local maximum number of registered terminal groups is reached, the local NSACF exchanges an NSAC request with the master NSACF. In this scenario, the local maximum number of groups is provided by the master NSACF.

[0891] If the number of terminal groups does not reach the local maximum number of groups, the local NSACF performs NSAC for the terminal and ignores steps S7104 to S7108.

[0892] Step S7104: If the local NSACF has not discovered the master NSACF before, it discovers and selects the master NSACF.

[0893] Step S7105: The local NSACF sends the Nnscf_NSAC_NumOfUEsUpdate_Request message to the master NSACF.

[0894] The request includes the NSAC request information received from the AMF, which may include the UE's XRM group identity.

[0895] Step S7106: The master NSACF performs NSAC update and checks the maximum allowed number of UEs for S-NSSAI.

[0896] The master NSACF checks the overall maximum number of terminals and, based on the group ID, decides whether to accept or reject the request from the NSACF to update the local maximum number of terminals.

[0897] In some examples, to support NSAC quotas (e.g., UE groups for XR services, or PDU session groups for XR services from one or more UEs), the master NSACF always reserves a portion of the global maximum for use by the group (e.g., group quota).

[0898] In some examples, NSAC quotas can be used only by the master NSACF or allocated to each NSACF for authorized use (i.e., local quotas). When NSAC quotas are allocated to an NSACF, the master NSACF can subscribe to the remaining quota or used quota from the NSACF. For example, the master NSACF can receive a remaining quota report from the NSACF and update the group quota based on the remaining quota report.

[0899] Step S7107: The master NSACF returns a Nnscf_NSAC_NumOfUEsUpdate_Response message to the NSACF. The response may include an indication (eg, rejection).

[0900] If the master NSACF decides to adjust the configuration values ​​(quotas, thresholds, etc.) assigned to the NSACF, the updated information is also included in the response.

[0901] Step S7108: The NSACF checks the response from the master NSACF.

[0902] If the response includes updated configuration values, the NSACF updates local data based on the received update information and performs NSAC on the indicated S-NSSAI based on the updated local data.

[0903] If the response message does not contain update information, a message is returned to the AMF based on the response of the primary NSACF.

[0904] Step S7109: NSACF returns Nnsacf_NSAC_NumOfUEsUpdate_Response response message to AMF.

[0905] The message includes a slice identifier S-NSSAI(s) and a result indication, which indicates whether the slice has reached the maximum number of registered users (for example, the maximum number of registered terminals in the aforementioned embodiment).

[0906] Optionally, the result indication includes whether the slice reaches the maximum number of registered groups (for example, the maximum number of registered terminal groups in the aforementioned embodiment).

[0907] In the UE registration process, if only some slices have reached the maximum number of registered users, the AMF will send a registration acceptance message to the registered UE. In the message, the rejected slice list includes the slice identifiers that were rejected due to NSAC, and the corresponding rejection reason is set to the maximum number of users in the slice area has been reached. Optionally, a timer for initiating a re-request is set.

[0908] When the request message sent by AMF to NSACF contains all requested slices S-NSSAI(s) that have reached the maximum allowed value, and if one or more contracted slices are marked as default slices in the contract information, and NSAC is not required at the same time, AMF may decide to put these default slices into the allowed NSSAI as authorized slices. Otherwise, AMF will reject the registration request of the user UE. In the registration rejection message, AMF carries a list of rejected slice identifiers, and each slice carries a corresponding rejection reason value, such as the maximum number of registered users allowed in the slice area has been reached. Optionally, a timer is set to initiate a re-request.

[0909] Optionally, if the rejection is due to a group threshold or quota being reached, the rejection reason indicates that the maximum group threshold or quota has been reached.

[0910] The information processing method involved in the embodiments of the present disclosure may include at least one of steps S7101 to S7102. For example, steps S7101 to S7103 combined with step S7109 may be implemented as independent embodiments, and for example, steps S7105 to S7107 may be implemented as independent embodiments, but are not limited thereto.

[0911] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0912] In some embodiments, an information processing method is provided, which involves a process for checking and updating the validity of the number of slice creation sessions in a hierarchical NSACF architecture. The process for checking and updating the validity of the number of slice creation sessions is used to update (i.e., increase or decrease) the number of PDU sessions established in the corresponding area on the slice. The process is applicable to the hierarchical NSAC architecture. The NSACF has two roles that need to interact with each other:

[0913] -The master NSACF controls and distributes the maximum number of PDU sessions to other NSACFs deployed in different NSAC service areas. The master NSAC handles the overall NSAC of the S-NSSAI at the entire level (i.e., it is ultimately responsible for the NSAC of the S-NSSAI).

[0914] -NSACF (e.g., local NSACF) is responsible for one or more NSAC service areas. An NSAC service area can only be associated with one NSACF instance or one NSACF set.

[0915] As shown in Figure 7b, for S-NSSAI that counts the number of PDU sessions, if a hierarchical NSACF architecture is deployed in the network, the maximum number of PDU sessions established by S-NSSAI can be enforced as follows:

[0916] Step S7201: If the SMF does not know the peer NSACF, the SMF first performs NSACF discovery and selection.

[0917] The SMF (SMF that anchors the PDU session) triggers the validity check and update process for the slice session number. The triggering condition of this process can be when the new PDU session creation process is initiated, or after a PDU session is successfully released, the SMF triggers this process for the slice that needs to perform NSAC.

[0918] Step S7202: The SMF (SMF that anchors the PDU session) sends a nsacf_nsac_numofpdusupdate_request request message to the NSACF.

[0919] The request message includes the terminal identifier (UE ID), session ID, slice identifier or identifier list S-NSSAI(s) for which NSAC needs to be performed, access type and update flag.

[0920] The update flag is used to mark whether the session number is increased, decreased, or updated. For example, it is increased during the session establishment process or when a new access is made to an existing multi-access session. It is decreased after the session release process or when a new access is made to an existing multi-access session. It is also updated when indicating that the access type of an existing PDU session is updated.

[0921] In some examples, the SMF also includes a group identifier in the request message to the NSACF, which is used to identify the XR service group or application group to which the PDU session belongs. For example, the group identifier can be an internal group identifier, a standardized universal group identifier, or an XR application ID or an indication of XR service capabilities.

[0922] Furthermore, the SMF determines the group identifier. The SMF may determine the group identifier based on at least one of local configuration, OAM configuration, or UDM subscription information, group information related to XR multimodal service capabilities / UE PEI sent by the UE, and indication information of UE XR applications and XR service capabilities sent by the RAN / AMF.

[0923] Step S7203: The local NSACF performs NSAC according to the network slice (S-NSSAI) indicated by the XR group ID / XR service ID.

[0924] When the SMF provides an NSAC request including a group identifier, the local NSACF interacts with the master NSACF to process the NSAC request.

[0925] When a group identifier is provided, the local NSACF interacts with the master NSACF to process the NSAC request, regardless of whether the local maximum number of PDU sessions is reached. Or,

[0926] When the group identifier is provided and the local maximum number of PDU session groups is reached, the local NSACF exchanges NSAC requests with the master NSACF. In this scenario, the local maximum number of groups is provided by the master NSACF.

[0927] If the number of PDU session groups does not reach the local maximum number of groups, the local NSACF performs the NSAC of the terminal and ignores steps S7204 to S7208.

[0928] Step S7204: If the local NSACF has not discovered the master NSACF before, it discovers and selects the master NSACF that manages the entire service area.

[0929] Step S7205: The local NSACF calls Nnsacf_NSAC_NumOfPDUsUpdate to request the master NSACF.

[0930] The request message includes S-NSSAI and group ID.

[0931] Step S7206: The master NSACF performs NSAC update and check for the maximum allowed number of PDU sessions of the S-NSSAI.

[0932] The master NSACF checks the overall maximum number of PDU sessions and decides, based on the group ID, whether to accept or reject the request from the NSACF to update the local maximum number of PDU sessions.

[0933] In some examples, to support NSAC quotas (e.g., UE groups for XR services, or PDU session groups for XR services from one or more UEs), the master NSACF always reserves a portion of the global maximum for use by the group (e.g., group quota).

[0934] In some examples, NSAC quotas can be used only by the master NSACF or allocated to each NSACF for authorized use (i.e., local quotas). When NSAC quotas are allocated to an NSACF, the master NSACF can subscribe to the remaining quota or used quota from the NSACF. For example, the master NSACF can receive a remaining quota report from the NSACF and update the group quota based on the remaining quota report.

[0935] Step S7207: The master NSACF returns a Nnscf_NSAC_NumOfUEsUpdate_Response message to the NSACF.

[0936] The response may include the newly allocated local maximum number of PDU sessions and / or the newly allocated local maximum number of PDU session groups, or include indication information, which is used to indicate the rejection of the request to update the local maximum number of PDU sessions.

[0937] Step S7208: The NSACF checks the response from the master NSACF.

[0938] If the master NSACF provides an updated local maximum number of PDU sessions, the NSACF replaces the local maximum number of PDU sessions and / or the local maximum number of PDU session groups with the received value.

[0939] Based on the updated configuration value, step S7203 is executed. If there is no update information in the response message, a message is returned to the SMF based on the response of the master NSACF.

[0940] Step S7209: NSACF returns a Nnsacf_NSAC_NumOfPDUsUpdate_Response response message to SMF.

[0941] The NSACF acknowledges the update by returning an Nnsacf_NSAC_NumOfPDUsUpdate_Response message to the SMF, which includes a result indication. If the NSACF returns that the maximum number of sessions allowed for the slice has been reached, the SMF may reject the session establishment request with the rejection reason set to "Number of sessions allowed for the slice has been reached." A fallback timer and access type may also be optionally set.

[0942] For a multi-access session, the NSACF may receive the multi-access session and provide a result indication of arrival or non-arrival, as well as the corresponding access type. When the SMF rejects the multi-access session, the SMF sets the access type in at least one of the following ways: if the UE has dual access, the access type indicates dual access if the dual access indicated by the NSACF fails; if it indicates that one of the accesses failed, it indicates that the access has been received; if the UE has single access, it indicates that the access has been received.

[0943] If the UE receives a backoff timer, the UE will not request user plane resource creation for the restricted access type before the timer expires. The UE may request PDU session creation for unrestricted access types.

[0944] If the session creation ultimately fails in the subsequent process, SMF will trigger interaction with NSACF again, deduct the corresponding session number, and update the response information.

[0945] The information processing method involved in the embodiments of the present disclosure may include at least one of steps S7201 to S7209. For example, steps S7201 to S7203 combined with step S7209 may be implemented as independent embodiments, and for example, steps S7205 to S7207 may be implemented as independent embodiments, but are not limited thereto.

[0946] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0947] In some embodiments, an information processing method is provided, which relates to updating the local maximum number of groups in a hierarchical NSACF architecture. The master NSACF can update the local maximum number of terminal groups and / or PDU sessions allocated on the NSACF at any time.

[0948] As shown in FIG. 7c , the method may include:

[0949] Step S7301: The master NSACF determines the local maximum number of UE groups or PDU session groups configured for NSACF update.

[0950] For example, the value configured for the NSACF may be configured based on one of the number of terminal groups and the number of PDU session groups currently registered on the NSACF and an operator policy.

[0951] Step S7302: The master NSACF sends a Nnsacf_NSAC_LocalNumberUpdate request to the NSACF.

[0952] The message contains the newly configured local maximum number of terminal groups or PDU session groups. The new local maximum number of groups configured by the master NSACF can be higher or lower than the current local maximum number of groups configured for the NSACF.

[0953] Step S7303: NSACF replaces the original local maximum number of groups with the received new local maximum number of groups.

[0954] Step S7304: The NSACF returns a Nnsacf_NSAC_LocalNumberUpdate response to the master NSACF.

[0955] The information processing method involved in the embodiment of the present disclosure may include at least one of steps S7301 to S7304. For example, steps S7301 to S7304 may be implemented as independent embodiments, but are not limited thereto.

[0956] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0957] The embodiments of the present disclosure also provide a device for implementing any of the above information processing methods. For example, a device is provided, which includes units or modules for implementing the steps performed by the first network element, the second network element, the third network element or the fourth network element in any of the above methods.

[0958] It should be understood that the division of the various units or modules in the above devices is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above devices, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0959] In the embodiments of the present disclosure, a processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationship of a hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document to implement the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0960] Figure 8a is a structural diagram of the first network element provided by an embodiment of the present disclosure. As shown in Figure 8a, the first network element 8100 includes: a sending module 8101, configured to send a first message to the second network element; wherein, the first information is used to indicate that the second network element requests the terminal to register or the PDU session to activate to perform NSAC; wherein, the first information includes a group identifier associated with the terminal or the PDU session. Optionally, the sending module 8101 is used to execute the steps related to information sending performed by the first network element in any of the above information processing methods, which will not be repeated here. Optionally, the first network element 8100 also includes a receiving module, and the above-mentioned receiving module is used to execute the steps related to reception performed by the first network element in any of the above methods, which will not be repeated here.

[0961] Figure 8b is a structural diagram of the second network element provided by an embodiment of the present disclosure. As shown in Figure 8b, the second network element 8200 includes: a receiving module 8201, configured to receive a first message sent by the first network element; wherein, the first information is used to instruct the second network element to perform NSAC on a terminal requesting registration or a PDU session requesting activation; wherein, the first information includes a group identifier associated with the terminal or the PDU session. Optionally, the receiving module 8201 is used to execute the steps related to information reception performed by the second network element in any of the above information processing methods, which will not be repeated here. Optionally, the second network element 8200 also includes a sending module, and the above sending module is used to execute the steps related to sending performed by the second network element in any of the above methods, which will not be repeated here.

[0962] Figure 8c is a structural diagram of the third network element provided by an embodiment of the present disclosure. As shown in Figure 8c, the third network element 8300 includes: a sending module 8301, configured to send first information to the first network element, wherein the first information is used to instruct the second network element to perform NSAC on the registered terminal; wherein the first information includes a group identifier associated with the terminal. Optionally, the sending module 8301 is used to execute the steps related to information sending performed by the third network element in any of the above information processing methods, which will not be repeated here. Optionally, the third network element 8300 also includes a receiving module, and the above-mentioned receiving module is used to execute the steps related to reception performed by the third network element in any of the above methods, which will not be repeated here.

[0963] Figure 8d is a structural diagram of the fourth network element provided by an embodiment of the present disclosure. As shown in Figure 8d, the fourth network element 8400 includes: a sending module 8401, configured to send a first message to the first network element, wherein the first information is used to instruct the second network element to perform NSAC on the PDU session requested to be activated; wherein the first information includes a group identifier associated with the PDU session. Optionally, the sending module 8401 is used to execute the steps related to information sending performed by the fourth network element in any of the above information processing methods, which will not be repeated here. Optionally, the fourth network element 8400 also includes a receiving module, and the above-mentioned receiving module is used to execute the steps related to reception performed by the fourth network element in any of the above methods, which will not be repeated here.

[0964] Figure 9a is a schematic diagram of the structure of a communication device 9100 provided in an embodiment of the present disclosure. Communication device 9100 can be a network device (e.g., an access network device or a core network device), a terminal (e.g., a user device), a chip, a chip system, or a processor that supports a network device in implementing any of the above methods, or a chip, a chip system, or a processor that supports a terminal in implementing any of the above information processing methods. Communication device 9100 can be used to implement the information processing methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0965] As shown in Figure 9a, the communication device 9100 includes one or more processors 9101. The processor 9101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. The processor 9101 is used to call instructions to enable the communication device 9100 to execute any of the above communication methods.

[0966] In some embodiments, the communication device 9100 further includes one or more memories 9102 for storing instructions. Optionally, all or part of the memories 9102 may be located outside the communication device 9100.

[0967] In some embodiments, the communication device 9100 further includes one or more transceivers 9103. When the communication device 9100 includes one or more transceivers 9103, the communication steps such as sending and receiving in the above method are performed by the transceiver 9103, and the other steps are performed by the processor 9101.

[0968] In some embodiments, a transceiver may include a receiver and a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0969] Optionally, the communication device 9100 further includes one or more interface circuits 9104, which are connected to the memory 9102. The interface circuits 9104 can be used to receive signals from the memory 9102 or other devices, and can be used to send signals to the memory 9102 or other devices. For example, the interface circuits 9104 can read instructions stored in the memory 9102 and send the instructions to the processor 9101.

[0970] The communication device 9100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 9100 described in the present disclosure is not limited thereto, and the structure of the communication device 9100 may not be limited by FIG. 9a. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: (1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data or programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0971] FIG9 b is a schematic diagram of the structure of a chip 9200 provided in an embodiment of the present disclosure. If the communication device 9100 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 9200 shown in FIG9 b , but the present disclosure is not limited thereto.

[0972] The chip 9200 includes one or more processors 9201 , and the processor 9201 is used to call instructions so that the chip 9200 executes any of the above communication methods.

[0973] In some embodiments, chip 9200 further includes one or more interface circuits 9202, which are connected to memory 9203. Interface circuits 9202 can be used to receive signals from memory 9203 or other devices, and can be used to send signals to memory 9203 or other devices. For example, interface circuit 9202 can read instructions stored in memory 9203 and send the instructions to processor 9201. Optionally, the terms interface circuit, interface, transceiver pin, and transceiver are interchangeable.

[0974] In some embodiments, the chip 9200 further includes one or more memories 9203 for storing instructions. Alternatively, all or part of the memories 9203 may be located outside the chip 9200.

[0975] The present disclosure also provides a storage medium having instructions stored thereon, which, when executed on the communication device 9100, causes the communication device 9100 to execute any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but may also be a transient storage medium.

[0976] The present disclosure further provides a program product, which, when executed by the communication device 9100, enables the communication device 9100 to perform any of the above communication methods. Optionally, the program product is a computer program product.

[0977] The present disclosure also provides a computer program, which, when executed on a computer, enables the computer to execute any one of the above communication methods.

[0978] Other embodiments of the present invention will readily occur to those skilled in the art after considering the specification and practicing the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the invention that follow from the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, with the true scope and spirit of the invention being indicated by the following claims.

[0979] It should be understood that the present invention is not limited to the exact construction 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. An information processing method, wherein: The method is performed by a first network element and includes: Sending first information to a second network element; wherein the first information is used to instruct the second network element to perform network slice admission control NSAC on a terminal requesting registration or a data packet unit PDU session requesting activation; wherein the first information includes a group identifier associated with the terminal or the PDU session.

2. The method according to claim 1, wherein: The sending the first information to the second network element includes: receiving a first request sent by a third network element, where the first request is used to update the number of registered terminals, and the first request includes the first information; A second request is sent to the second network element, where the second request includes the first information.

3. The method according to claim 1, wherein: The sending the first information to the second network element includes: receiving a third request sent by a fourth network element, where the third request is used to update the number of activated PDU sessions, and the third request includes the first information; Send a fourth request to the second network element, where the fourth request includes the first information.

4. The method according to any one of claims 1 to 3, wherein: The sending the first information to the second network element includes: The number of registered terminal groups of the network slice of the first network element reaches the maximum number of registered terminal groups of the network slice, sending the first information to the second network element; and / or, The number of PDU session groups of the network slice of the first network element reaches the maximum number of PDU session groups of the network slice, and the first information is sent to the second network element.

5. The method according to claim 2, wherein: The method further comprises: Receive a first response corresponding to the second request sent by the second network element; wherein the first response includes second information, and the second information is used to update the maximum number of registered terminals of the network slice of the first network element.

6. The method according to claim 3, wherein: The method further comprises: Receive a second response corresponding to the fourth request sent by the second network element; wherein the second response includes third information, and the third information is used to update the maximum PDU session number of the network slice of the first network element.

7. The method according to any one of claims 1 to 6, wherein: The method further comprises: Send fourth information to the second network element; wherein the fourth information is used to indicate the remaining quota or used quota in the NSAC quota allocated by the second network element to the first network element; the NSAC quota is used to indicate at least one of the maximum number of registered terminal groups and the maximum number of PDU session groups of the network slice of the first network element.

8. The method according to claim 7, wherein: The sending fourth information to the second network element includes: The fourth information is sent to the second network element according to a subscription request from the second network element, wherein the subscription request is used to subscribe the remaining quota or the used quota in the NSAC quota to the first network element.

9. The method according to any one of claims 1 to 8, wherein: The first network element is a local network slice admission control function NSACF network element, and the second network element is a main NSACF network element; The third network element is the access and mobility management function AMF network element, and the fourth network element is the session management function SMF network element.

10. The method according to claim 1, wherein: The method further comprises one of the following: Determining the group identifier based on local configuration information and / or operation maintenance management (OAM) configuration information of the first network element; The group identifier sent by the fifth network element is received.

11. The method according to any one of claims 1 to 10, wherein: The group identifier is used to identify at least one of the following: The service group associated with the terminal requesting registration; The application group associated with the terminal requesting registration; The service group associated with the PDU session requested to be activated; The application group associated with the PDU session requested to be activated.

12. An information processing method, wherein: Executed by the second network element, the method includes: Receive first information sent by a first network element; wherein the first information is used to instruct the second network element to perform network slice admission control NSAC on a terminal requesting registration or a data packet unit PDU session requesting activation; wherein the first information includes a group identifier associated with the terminal or the PDU session.

13. The method according to claim 12, wherein: The receiving the first information sent by the first network element includes at least one of the following: Receiving a second request including the first information sent by the first network element; wherein the second request is sent based on a first request including the first information from a third network element, and the first request is used to update the number of registered terminals; receiving a fourth request including the first information sent by the first network element; wherein the fourth request is based on The third request including the first information is sent by the network element, and the third request is used to update the number of activated PDU sessions.

14. The method according to claim 13, wherein: The method further comprises at least one of the following: Sending a first response corresponding to the second request to the first network element according to the overall maximum number of registered terminals and the first information; Based on the overall maximum PDU session number and the first information, a second response corresponding to the fourth request is sent to the first network element.

15. The method according to claim 14, wherein: The first response includes second information, where the second information is used to update the maximum number of registered terminals in the network slice of the first network element; and / or, The second response includes third information, and the third information is used to update the maximum number of PDU sessions of the network slice of the first network element.

16. The method according to claim 14, wherein: The method further comprises: Determine a reserved number in the overall maximum number of registered terminals or the overall maximum number of PDU sessions, wherein the reserved number is one of the following: a terminal quota of the reserved NSAC associated with the group identifier; a PDU session quota of the reserved NSAC associated with the group identifier; A group quota of the NSAC is reserved, where the group quota is associated with the terminal group or PDU session group of the group identifier.

17. The method according to any one of claims 12 to 16, wherein: The method further comprises: Receive the fourth information sent by the first network element; wherein the fourth information is used to indicate the remaining quota or used quota in the NSAC quota allocated by the second network element to the first network element; the NSAC quota is used to indicate: at least one of the maximum number of registered terminal groups and the maximum number of PDU session groups of the network slice of the first network element.

18. The method according to claim 17, wherein: The method further comprises: Send a subscription request to the first network element; wherein the subscription request is used to subscribe to the remaining quota or the used quota in the NSAC quota from the first network element.

19. The method according to claim 17 or 18, wherein: The method further comprises: The NSAC quota is updated according to the remaining quota or the used quota in the NSAC quota.

20. The method according to claim 12, wherein: The group identifier is determined by the first network element based on local configuration information and / or operation, maintenance and management (OAM) configuration information of the first network element; or, The group identifier is received by the first network element from the fifth network element.

21. The method according to any one of claims 12 to 20, wherein: The group identifier is used to identify at least one of the following: The service group associated with the terminal requesting registration; The application group associated with the terminal requesting registration; The service group associated with the PDU session requested to be activated; The application group associated with the PDU session requested to be activated.

22. An information processing method, wherein: Executed by a third network element, the method includes: Send first information to a first network element, wherein the first information is used to instruct the second network element to perform network slice admission control NSAC on a terminal requesting registration; wherein the first information includes a group identifier associated with the terminal.

23. The method according to claim 22, wherein: The sending the first information to the first network element includes: Sending a first request including the first information to the first network element; wherein the first request is used to update the number of registered terminals.

24. The method according to claim 22 or 23, wherein: The group identifier is determined by the third network element based on at least one of the following information: Local configuration information; Operation, maintenance and management of OAM configuration information; Unified data management function UDM contract information; The indication information of the extended reality XR multimodal service capability sent by the terminal; Terminal identification related group information; Group information in the terminal context.

25. The method according to any one of claims 22 to 24, wherein: The group identifier is used to identify at least one of the following: The service group associated with the terminal requesting registration; The application group associated with the terminal requesting registration.

26. An information processing method, wherein: Executed by a fourth network element, the method includes: Send first information to a first network element, wherein the first information is used to instruct the second network element to perform network slice admission control NSAC on a data packet unit PDU session requested to be activated; wherein the first information includes a group identifier associated with the PDU session.

27. The method according to claim 26, wherein: The sending the first information to the first network element includes: Send a third request including the first information to the first network element; wherein the third request is used to update the number of activated PDU sessions.

28. The method according to claim 26 or 27, wherein: The group identifier is determined by the fourth network element based on at least one of the following information: Local configuration information; Operation, maintenance and management of OAM configuration information; Unified data management function UDM contract information; Information indicating the terminal's extended reality (XR) multimodal service capabilities; Terminal identification related group information; Indication information of the terminal's XR application or XR service capabilities.

29. The method according to any one of claims 26 to 28, wherein: The group identifier is used to identify at least one of the following: The service group associated with the PDU session requested to be activated; The application group associated with the PDU session requested to be activated.

30. A first network element, wherein: The first network element includes: A sending module is configured to send first information to a second network element; wherein the first information is used to indicate that the second network element requests the terminal to register or requests the data packet unit PDU session to activate to perform network slice admission control NSAC; wherein the first information includes a group identifier associated with the terminal or the PDU session.

31. A second network element, wherein: The second network element includes: The receiving module is configured to receive first information sent by a first network element; wherein the first information is used to instruct the second network element to perform network slice admission control NSAC on a terminal requesting registration or a data packet unit PDU session requesting activation; wherein the first information includes a group identifier associated with the terminal or the PDU session.

32. A third network element, wherein: The third network element includes: The sending module is configured to send first information to the first network element, wherein the first information is used to instruct the second network element to perform network slice admission control NSAC on the registered terminal; wherein the first information includes a group identifier associated with the terminal.

33. A fourth network element, wherein: The fourth network element includes: The sending module is configured to send first information to the first network element, wherein the first information is used to instruct the second network element to perform network slice admission control NSAC on the data packet unit PDU session requested to be activated; wherein the first information includes a group identifier associated with the PDU session.

34. A communication system, wherein: The communication system comprises: A first network element, configured to implement the information processing method according to any one of claims 1 to 11; A second network element, configured to implement the information processing method according to any one of claims 12 to 21; A third network element, configured to implement the information processing method according to any one of claims 22 to 25; The fourth network element is configured to implement the information processing method according to any one of claims 26 to 29.

35. A communication device, wherein: The communication device comprises: one or more processors; The processor is used to call instructions so that the communication device executes the information processing method described in any one of claims 1 to 11, claims 12 to 21, claims 22 to 25, and claims 26 to 29.

36. A storage medium, wherein: The storage medium stores instructions, and when the instructions are executed on the communication device, the communication device executes the information processing method described in any one of claims 1 to 11, claims 12 to 21, claims 22 to 25, and claims 26 to 29.

Citation Information

Patent Citations

  • Network slice access control method and device

    CN115707062A

  • Data transmission method and device, terminal and network equipment

    CN116419315A

  • Method of communication apparatus, method of user equipment (UE), communication apparatus, UE, method for first core network apparatus, method for third core network apparatus and method for first network slice control function node

    WO2023120046A1

Cited By

  • MULTI-MODAL SESSION ACTIVATION FOR MULTI-MODAL EXTENDED REALITY (XR) USER EQUIPMENT (UEs)

    US20250287443A1