Communication method and device

Abstract

The invention discloses a communication method and device. In the method, a terminal determines a network slice with a failed request service, and the failed request service comprises a network slice service request failure, a PDU session establishment request failure based on the network slice or a PDU session activation failure based on the network slice; the failure of the network slice service request comprises that the network slice requested by the terminal equipment is not supported by the TA where the terminal equipment is located; sending first information to a base station, the first information comprising one or more of the following information: an identifier of a network slice with failed request service, an identifier of an NSAG associated with the network slice with failed request service, a failure reason of the network slice with failed request service, and a slice type of the network slice with failed request service, and the network slice which fails to request the service has the service request failure time.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and in particular to a communication method and apparatus. Background Technology

[0002] With the development of mobile communication technology, various new services and application scenarios are constantly emerging, and these services have significantly different requirements for network functionality, connectivity performance, and security. Using a single network to carry these services makes it difficult to simultaneously meet the demands for high bandwidth, low latency, and high reliability; building a separate network for each service would incur enormous costs. This necessitates that communication systems be flexible and scalable while meeting diverse service needs. Therefore, 5G communication systems provide customized network services to users through end-to-end network slicing. By flexibly allocating network resources and deploying networks on demand, 5G communication systems virtualize multiple isolated network slices with different characteristics on the same physical infrastructure to provide targeted services to users.

[0003] To enable automatic optimization of parameter configuration in mobile communication network equipment, reduce manual intervention in network management, improve network reliability, and lower operating costs, self-organizing network (SON) technology has been introduced into mobile communication systems. SON can include functions such as self-configuration, self-optimization, and self-healing.

[0004] The mobile communication system has researched and standardized the Minimization of Drive Tests (MDT) technique to automate the collection and analysis of user equipment (UE) measurement reports containing location information. This reduces the workload of manual drive testing, lowers network maintenance costs, and also helps to solve the real-time and broad-based problems in mobile communication network quality assessment.

[0005] However, current SON / MDT technology does not have optimizations for network slices that fail to handle request service failures. Summary of the Invention

[0006] This application provides a communication method and apparatus for enabling network devices to perform self-optimization on network slices that have failed to request services using SON / MDT.

[0007] In a first aspect, embodiments of this application provide a communication method that can be applied to the terminal device side, such as the terminal device or the communication module in the terminal device, or the circuit or chip in the terminal device responsible for communication functions (such as a modem chip, also known as a baseband chip, or a system on chip (SoC) chip containing a modem core or a system in package (SIP) chip).

[0008] Taking the application of this method to a terminal as an example, the method includes: determining a network slice where the requested service failed, wherein the requested service failure includes network slice service request failure, protocol data unit (PDU) session establishment request failure based on network slice, or PDU session activation failure based on network slice, wherein the network slice service request failure includes the network slice requested by the terminal device not being supported by the tracking area (TA) where the terminal device is located; sending first information, wherein the first information includes information about the network slice where the requested service failed; the first information includes one or more of the following: the identifier of the network slice where the requested service failed; the identifier of the network slice access layer group (NSAG) associated with the network slice where the requested service failed; the reason for the failure of the network slice where the requested service failed; the slice type of the network slice where the requested service failed; and the time when the requested service failure occurred in the network slice where the requested service failed.

[0009] In the above communication method, if a terminal device fails to initiate a network slice service request (such as a network slice registration request), a network slice-based PDU session establishment request, or a network slice-based PDU session activation request, the terminal device can send the information of the network slice for which the service request failed to the access network device. The access network device can then statistically analyze the information of the network slice for which the service request failed and use SON / MDT technology to perform self-configuration and self-optimization operations on the network slice, thereby better providing services to the terminal device and improving the user experience.

[0010] In one possible implementation, determining the network slice where the requested service failed includes: identifying the network slice where the requested service failed based on the rejection reason of the rejected network slice. When a terminal device makes a service request and it fails, the network side can notify the terminal device of the reason for the failure. The terminal device can quickly determine whether there is a network slice where the requested service failed due to the network side not configuring the corresponding resources, thereby facilitating the terminal device to record and report the failure.

[0011] In one possible implementation, determining the network slice for which the requested service failed based on the rejection reason of the rejected network slice includes: the non-access stratum (NAS) of the terminal device determining the network slice for which the requested service failed based on the rejection reason of the rejected network slice in the downlink NAS message. Typically, the rejection reason is carried in the non-access stratum (NAS) message and sent to the NAS of the terminal device. Therefore, it is more convenient for the NAS of the terminal device to determine the network slice for which the requested service failed based on the rejection reason.

[0012] In one possible implementation, determining the network slice where the requested service failed includes: identifying the network slice where the requested service failed based on the location information of the terminal device, and first TA information and / or second TA information. The first TA information includes one or more TA information supporting network slices partially allowed by the terminal device, and the second TA information includes one or more TA information supporting network slices partially rejected by the terminal device. For partially allowed / partially rejected network slices, the network side typically provides its corresponding TA information. The terminal device can quickly and accurately determine whether it can obtain the service of the corresponding network slice under the current TA based on its own location information and the TA information of the partially allowed / partially rejected network slices, thereby recording and reporting information about network slices where the corresponding service cannot be obtained.

[0013] In one possible implementation, determining the network slice for which the requested service failed based on the location information of the terminal device, and the first TA information and / or the second TA information, includes: the NAS of the terminal device determining the network slice for which the requested service failed based on the location information of the terminal device, and the first TA information and / or the second TA information; or, the NAS of the terminal device sending the first TA information and / or the second TA information to the access stratum (AS) of the terminal device, and the AS determining the network slice for which the requested service failed based on the location information of the terminal device, and the first TA information and / or the second TA information. The location information of the terminal device is usually determined by the AS of the terminal device, while the first TA information and the second TA information are usually sent to the NAS of the terminal device via NAS messages. Therefore, when determining the network slice for which the requested service failed, the terminal device can either have the NAS determine the network slice for which the requested service failed based on the first TA information and the second TA information obtained from the NAS message, and the location information obtained from the AS, or the AS can determine the network slice for which the requested service failed based on the location information, and the first TA information and the second TA information obtained from the NAS.

[0014] In one possible implementation, determining the network slice where the requested service failed includes: identifying the network slice where the requested service failed based on the location information of the terminal device, and first cell information and / or second cell information. The first cell information includes one or more cells where available resources exist for the partially allowed network slice of the terminal device, and the second cell information includes one or more cells where available resources exist for the allowed network slice of the terminal device. For allowed / partially allowed network slices, the network side typically provides its corresponding cell information (such as network slice area of ​​service (NS-AoS)). The terminal device can quickly and accurately determine whether it can obtain the service of the corresponding network slice in the current cell based on its own location information and the cell information of the allowed / partially allowed network slice, thereby recording and reporting information about network slices where the corresponding service cannot be obtained.

[0015] In one possible implementation, determining the network slice for which the requested service failed based on the location information of the terminal device, and the first cell information and / or the second cell information, includes: the NAS of the terminal device obtaining the location information of the terminal device sent by the AS of the terminal device; the NAS determining the network slice for which the requested service failed based on the location information, and the first cell information and / or the second cell information. The location information of the terminal device is typically determined by the AS of the terminal device, while the first cell information and the second cell information are typically sent to the NAS of the terminal device via NAS messages. Therefore, when determining the network slice for which the requested service failed, the NAS can determine the network slice for which the requested service failed based on the first cell information and the second cell information obtained from the NAS message, and the location information obtained from the AS.

[0016] In one possible implementation, determining the network slice where the requested service failed includes: when a PDU session based on the network slice cannot be established or activated, identifying the network slice associated with the PDU session that cannot be established or activated as the network slice where the requested service failed. In this implementation, for a partially allowed and partially denied network slice, when the terminal device needs to initiate a service request (such as requesting to establish a PDU session based on the network slice, or requesting to activate the user plane of a PDU session based on the network slice), it determines whether the service request can be initiated in the current TA or current cell based on the obtained TA information and cell information corresponding to the partially allowed / partially denied network slice. If it is determined that the service request cannot be initiated, the corresponding network slice is identified as the network slice where the service failed, and then recorded and reported.

[0017] In one possible implementation, the location information includes: the TA where the terminal device is located, or the cell where the terminal device is located.

[0018] In one possible implementation, before sending the first information, the method further includes: receiving first indication information, the first indication information being used to indicate one or more of the following: information included in the first information, a first triggering condition for recording the network slice where the requested service failed, and a second triggering condition for sending the first failure report; sending the first information includes: sending the first information according to the first configuration information. In this implementation, the terminal device can receive an indication from a network device (such as an access network device), record and report the network slice where the requested service failed, and determine the content to be recorded and reported according to the indication from the network device.

[0019] In one possible implementation, sending the first information includes: sending the first information according to second indication information, wherein the second indication information indicates one or more of the following: information contained in the first information report, a first trigger condition for recording the network slice where the requested service failed, and a second trigger condition for sending the first failure report. In this implementation, the terminal device can determine whether it needs to record and report the network slice where the requested service failed based on the pre-configured second indication information, and determine the content that needs to be recorded and reported based on the second indication information.

[0020] In one possible implementation, the first triggering condition includes one or more of the following conditions: a preset triggering event occurs; it is determined that there is a network slice with a failed service request; the number of network slices with failed service requests reaches a preset number; the service type of the network slices with failed service requests includes a preset service type; a first network slice experiences a service request failure; a network slice associated with a first NSAG experiences a service request failure; and the priority of the NSAG associated with the network slice with the failed service request meets a preset priority.

[0021] In one possible implementation, the slice type includes one or more of the following types: allowed network slice, rejected network slice, partially allowed network slice, partially rejected network slice, and requested network slice.

[0022] In one possible implementation, the second triggering condition includes one or more of the following conditions: the reporting time is reached according to the reporting cycle; a preset triggering event occurs; the number of network slices that requested the service failed reaches a preset number; the service type of the network slices that requested the service failed includes a preset service type; and the priority of the network slice access layer group (NSAG) associated with the network slices that requested the service failed meets a preset priority.

[0023] Secondly, embodiments of this application provide a communication method, which can be executed by an access network device, or by a module (e.g., a chip, chip system, or processor) applied to the access network device, or by a logical node, logical module, or software that implements all or part of the functions of the access network device.

[0024] Taking the application of this method to an access network device as an example, the method includes: determining the network slice where the terminal device's service request failed, wherein the service request failure includes network slice service request failure, PDU session establishment request failure based on the network slice, or PDU session user plane activation failure based on the network slice, and the service request failure includes the network slice requested by the terminal device not being supported by the Tracking Area (TA) where the terminal device is located; recording second information, the second information including information about the network slice where the service request failed; the second information includes one or more of the following: the identifier of the network slice where the service request failed; the identifier of the network slice access layer group (NSAG) associated with the network slice where the service request failed; the reason for the failure of the network slice where the service request failed; the slice type of the network slice where the service request failed; and the time when the service request failure occurred in the network slice where the service request failed.

[0025] In the aforementioned communication method, considering that terminal devices may fail when initiating network slice service requests (such as network slice registration requests), PDU session establishment requests based on network slices, and PDU session activation requests based on network slices, the access network device can record the information of the network slices whose service requests failed. This facilitates the access network device's statistical analysis of the information on the network slices whose service requests failed, and enables it to perform self-configuration and self-optimization operations on the network slices using SON / MDT technology. Alternatively, it can facilitate the transmission of the recorded information to other devices, enabling statistical analysis of the information on the network slices whose service requests failed, thereby better providing services to terminal devices and improving user experience.

[0026] In one possible implementation, determining the network slice where the terminal device's service request failed includes: determining the network slice where the terminal device's service request failed based on the network slice requested by the terminal device and the network slices supported by the network device; or, determining the network slice where the terminal device's service request failed based on the network slice requested by the terminal device and resource configuration information for each network slice supported by the network device; or, determining the network slice where the terminal device's service request failed based on the network slice requested by the terminal device, the network slices supported by the network device, and the resource configuration information for each network slice supported by the network device. In this implementation, the access network device can obtain the network slice requested by the terminal device and determine, based on one or more of the following: the network slice requested by the terminal device, the network slices it supports, and the resource configuration information for each network slice it supports, the network slice where the terminal device may experience service request failure at its current location, and record it.

[0027] In one possible implementation, the method further includes: receiving network slice indication information requested by the terminal device; or receiving network slice indication information requested by the core network device.

[0028] In one possible implementation, determining the network slice where the terminal device's service request failed includes: determining the network slice where the terminal device's service request failed based on the network slices partially allowed by the terminal device and the network slices supported by the network device; or, determining the network slice where the terminal device's service request failed based on the network slices partially allowed by the terminal device and / or allowed network slices, and resource configuration information for each network slice supported by the network device; or, determining the network slice where the terminal device's service request failed based on the network slices partially allowed by the terminal device and / or allowed network slices, the network slices supported by the network device, and the resource configuration information for each network slice supported by the network device. In this implementation, the access network device can obtain the network slices allowed / partially allowed by the terminal device, and determine, based on one or more of the following information: the network slices allowed / partially allowed by the terminal device, the network slices it supports, and the resource configuration information for each network slice it supports, the network slices where the terminal device may experience service request failure at its current location, and record them.

[0029] In one possible implementation, a third instruction is received, which is used to instruct the recording of the second information.

[0030] Thirdly, embodiments of this application provide an apparatus capable of implementing the methods described in the first aspect or any possible implementation of the first aspect. The apparatus includes corresponding units or modules for performing the methods described above. The units or modules included in the apparatus can be implemented in software and / or hardware. The apparatus can be, for example, a terminal, a chip, chip system, or processor that supports the implementation of the methods in the terminal, or a logic node, logic module, or software capable of implementing all or part of the terminal's functions.

[0031] Fourthly, embodiments of this application provide an apparatus capable of implementing the methods described in the second aspect or any possible implementation of the second aspect. The apparatus includes corresponding units or modules for performing the described methods. The units or modules included in the apparatus can be implemented in software and / or hardware. The apparatus can be, for example, an access network device, a chip, chip system, or processor that supports the access network device in implementing the described methods, or a logical node, logical module, or software capable of implementing all or part of the access network functions.

[0032] Fifthly, embodiments of this application provide a communication device comprising: a processor coupled to a memory for storing programs or instructions, wherein when the programs or instructions are executed by the processor, the device performs a method as described in the first aspect and any possible implementation thereof.

[0033] In a sixth aspect, embodiments of this application provide a communication device comprising: a processor coupled to a memory for storing programs or instructions, wherein when the programs or instructions are executed by the processor, the device performs a method as described in the second aspect and any possible implementation thereof.

[0034] In a seventh aspect, embodiments of this application provide a communication system, including the communication device described in the third aspect and the communication device described in the fourth aspect.

[0035] Eighthly, embodiments of this application provide a communication system including the communication device described in the fifth aspect and the communication device described in the sixth aspect.

[0036] Ninthly, embodiments of this application provide a chip, including: a processor coupled to a memory for storing instructions, wherein when the instructions are executed by the processor, the chip causes the chip to implement the methods described in the first to second aspects and any of their implementations.

[0037] In a tenth aspect, embodiments of this application provide a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the methods described in the first to second aspects and any of their implementations.

[0038] Eleventhly, embodiments of this application provide a computer program product containing instructions that, when run on a computer, cause the computer to perform the methods described in the first aspect to the second aspect and any of their implementations. Attached Figure Description

[0039] Figure 1 A schematic diagram illustrating the process of a terminal device obtaining network slices as provided in an embodiment of this application;

[0040] Figure 2 This application provides a schematic diagram of a network slicing deployment.

[0041] Figure 3 This is another network slicing deployment diagram provided in an embodiment of this application;

[0042] Figures 4(a) and 4(b) are schematic diagrams of another network slice deployment provided in the embodiments of this application;

[0043] Figures 5(a) and 5(b) are schematic diagrams of the network architecture provided in the embodiments of this application;

[0044] Figure 6 A flowchart illustrating a communication method provided in an embodiment of this application;

[0045] Figure 7 A flowchart illustrating another communication method provided in an embodiment of this application;

[0046] Figure 8 A flowchart illustrating yet another communication method provided in an embodiment of this application;

[0047] Figure 9 A flowchart illustrating yet another communication method provided in an embodiment of this application;

[0048] Figure 10 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0049] Figure 11 This is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0050] To enable mobile communication network equipment to automatically measure, report, and optimize parameter configurations, reduce manual intervention in network management, improve network reliability, and reduce operating costs, SON and MDT technologies have been introduced into mobile communication systems.

[0051] In SON technology, self-configuration refers to the network device's ability to plug and play, automatically download and install software, automatically configure wireless and transmission parameters, and autonomously manage neighbor cell relationships; self-optimization refers to the network device's ability to adaptively adjust wireless parameters, such as transmit power, handover threshold, and cell-specific offset, based on its operating status to optimize network performance; and self-healing refers to the ability to autonomously detect faults and promptly isolate and restore them by monitoring and analyzing error data and alarm information.

[0052] Self-configuration includes physical cell identifier (PCI) self-configuration and automatic neighbor relation (ANR) functions. Through self-configuration, each base station can autonomously select a physical cell identifier and establish and maintain neighbor relationships within the node's allowed scope. These two technologies not only significantly reduce the planning and optimization workload for operators but also facilitate the widespread use of subsequent non-operator-deployed nodes such as femtocells.

[0053] Self-optimization primarily includes functions such as mobility load balancing (MLB), random access channel (RACH) optimization, and mobility robustness optimization (MRO). Through self-optimization, each network device can adjust parameters based on current load and performance statistics to optimize system performance. Network device self-optimization is typically performed under the control of the operations administration and maintenance (OAM) system. Based on network performance measurements and data collection, OAM can initiate or terminate network self-optimization operations when necessary; simultaneously, network device parameter adjustments are within the range allowed by OAM. The MRO technology solution is used to automatically detect handover parameter setting problems. By analyzing and statistically analyzing a large number of connection failures, the cause of the problem can be determined, allowing for corresponding parameter adjustments. Specifically, when a terminal device detects a radio link failure (RLF) or handover failure during the handover process, it can send a relevant RLF report to the network device to help adjust the network device's parameter configuration.

[0054] Operators need to conduct mobile network quality assessments, including identifying coverage strength and weaknesses, and coverage gaps. Previously, this was done manually via vehicle road testing. The main methodology was as follows: first, determine the test area and design the test route; then, collect measurement data while driving, including location information and data from the physical layer, media access control layer, signaling layer, and system information; finally, perform post-collection processing, mainly including data analysis and problem localization analysis. Data analysis is primarily based on network performance metrics, such as analyzing call drop rate, call completion rate, and traffic. Problem localization mainly involves combining measurement data (e.g., signal strength) and signaling messages to determine whether the fault lies in the terminal equipment or the network equipment, and what the possible causes are.

[0055] However, manual road testing is time-consuming and labor-intensive, so the industry researched and standardized MDT (Multi-Targeted Testing). MDT technology is a technique for communication systems to automatically collect and analyze UE (User Equipment) measurement reports containing location information. It is used to reduce the workload of manual road testing, reduce network maintenance costs, and also help solve the problem of difficulty in ensuring real-time and widespread coverage in mobile network quality assessment.

[0056] MDT (Multi-Targeting Technology) enables operators to select commercial terminal devices to participate in MDT reporting based on predefined conditions when they require drive testing. The reported content mainly includes data related to quality of service (QoS). MDT provides operators with real-time network quality assessment data, which is very helpful for timely detection of network problems and network optimization. It also reduces the need for drive testing, which is of great significance for reducing operating costs.

[0057] MDT functionality relies on reporting from terminal devices, which can be real-time or non-real-time as needed. MDT can include logged MDT and immediate MDT. Logged MDT involves the terminal device periodically logging data (e.g., for signal strength measurements) in idle or inactive states, or recording pre-defined events (e.g., RLF occurrences) according to network configuration. After connecting to the network, the terminal device can report these recorded events to the network device. The recorded content may include event type, time, location, and signal quality at the time of the event; a single report may include multiple events and / or multiple records. Immediate MDT, on the other hand, involves the network device configuring measurement parameters for the connected terminal device, and the terminal device immediately responding after detection. The network device can reuse existing RRC measurement procedures for configuring these parameters.

[0058] Currently, 5G communication systems provide customized network services to users through end-to-end network slicing. Different network slices can be identified and distinguished by single network slice selection assistance information (S-NSSAI). Each S-NSSAI can include the following information:

[0059] 1. Slice / service type (SST) indicates the characteristics and service type of a network slice;

[0060] 2. Slice Differentiator (SD): As a supplement to SST, it can further differentiate multiple network slices that satisfy the same SST. SD is optional information.

[0061] Network slice selection assistance information (NSSAI) can represent one or more network slices, such as a list of S-NSSAIs. NSSAIs can include several types:

[0062] 1. Subscribed Network Slice (NSSAI): Subscribed data belonging to the terminal device.

[0063] 2. Default Network Slice (default NSSAI): Depending on the operator's policy, one or more of the NSSAIs subscribed to by the terminal device may be set as the default NSSAI. If the terminal device does not carry an allowed NSSAI in the registration request message, and the terminal device has a default NSSAI, the network side can use the network slice corresponding to the default NSSAI to provide services to the terminal device.

[0064] 3. Requested NSSAI: This is the allowed NSSAI or configured NSSAI carried by the terminal device in the registration request message.

[0065] 4. Allowed NSSAI: This refers to one or more S-NSSAIs requested by the terminal device that are permitted by the network side. The allowed NSSAIs can be sent to the terminal device via the "allowed NSSAI" element (IE) in the registration accept message; all allowed NSSAIs are supported within the terminal device's registration area (RA).

[0066] 5. Partially Allowed Network Slices (NSSAI): This means that one or more S-NSSAIs are supported within a portion of the TA contained in the registration area of ​​the terminal device.

[0067] 6. Configured NSSAI: This refers to the NSSAI configured by the network side for use by the terminal device. The NSSAI configured by the network side can be sent to the terminal device through the "configured NSSAI" information element in the registration accept message. If the configuration of the terminal device changes after registration, the network side can notify the terminal device to update through the configuration update command.

[0068] 7. Rejected NSSAI: This indicates that one or more S-NSSAIs among the NSSAIs requested by the UE were rejected by the network side. For example, the core network or access network does not support the one or more S-NSSAIs.

[0069] 8. Partially rejected NSSAI: This means that one or more S-NSSAIs in the NSSAI requested by the UE are supported only in a portion of the TAs in the UE's registered area.

[0070] The following is combined with Figure 1 This section describes how terminal devices can access network slicing services. For example... Figure 1 As shown, the process for a terminal device to obtain network slice services may include:

[0071] Step 101: The access network device and the AMF exchange their respective lists of supported network slices.

[0072] The network slice list supported by the access network device can be pre-configured by the OAM at the TA granularity, meaning all cells within a TA support the same network slices. The access network device can report this network slice list to the AMF when establishing an NG interface with the core network. If the access network device also supports CU / DU separation, then the DU can first send the network slice list supported by each TA to the CU, and then the CU can report it to the AMF.

[0073] After receiving the network slice list at the TA granularity provided by the access network device, the AMF can use NG to establish a response and feed back the AMF-supported network slice list to the access network device, so that the access network device can select the AMF based on the slice service requested by the terminal device after the terminal device accesses the network.

[0074] Step 102: The terminal device sends a requested network slice (NSSAI) to the access network device.

[0075] After the terminal device connects, it can indicate the requested NSSAI to the access network device via an RRC setup complete message (i.e., the MSG5 message). This RRC setup complete message can also carry a registration request message sent by the terminal device to the AMF. Based on the requested NSSAI and the received list of network slices supported by the AMF, the base station selects an AMF (e.g., one that can support all or most of the network slices in the requested NSSAI) to serve the terminal device.

[0076] Step 103: The access network device transmits the terminal device's registration request message to the AMF.

[0077] After determining the AMF (Access Provider) to serve the terminal device, the access network device can transparently transmit a registration request message to the AMF, which also includes the requested NSSAI (Network Service Assistance Interface). Optionally, the registration request can be sent via an initial UE message.

[0078] Step 104: The AMF sends the allowed network slice (NSSAI) of the terminal device to the access network device.

[0079] Based on the terminal device's subscription information, the network slice list supported by the access network device, and its own supported network slice list, the AMF will identify network slices in the requested NSSAI that are both subscribed to by the terminal device and supported by both the access network device and the AMF as allowed NSSAIs. Other network slices will be identified as rejected NSSAIs. The allowed NSSAIs will then be sent to the access network device, which can use them to determine the RRM policy and handover decision for the terminal device. Optionally, the AMF can send the above information via an initial context setup request.

[0080] AMF can also send NAS messages, which are registration accept messages from the terminal to the terminal device. The access network base station forwards the registration accept message to the terminal device. The registration accept message may include allowed NSSAI and rejected NSSAI. Within the registration area, the terminal device can initiate a PDU session establishment request based on allowed NSSAI, but cannot initiate a registration request again based on rejected NSSAI.

[0081] Step 105: The terminal device sends a PDU session establishment request and the network slice associated with the PDU session to the AMF.

[0082] Terminal devices can send NAS messages, which may contain a PDU session establishment request and its associated network slice, to request the establishment of a PDU session associated with allowed S-NSSAI (one PDU session is associated with one network slice).

[0083] Step 106: The AMF instructs the access network device to establish radio resources for the PDU session.

[0084] After receiving the NAS message from the terminal device, the AMF forwards the PDU session establishment request message and its associated network slice to the SMF. After the SMF determines that a PDU session has been established, it sends a PDU session establishment acceptance message to the AMF. The AMF then sends a PDU session resource setup request message to the access network device to instruct the access network device to establish radio resources for the PDU session. This message includes a NAS message containing the PDU session establishment acceptance message, which is then forwarded by the access network device to the terminal device.

[0085] like Figure 2As shown, the terminal device initiates a registration request within TA1, which carries requested NSSAI: slice#1, slice#2; however, TA1 only supports slice#1, while TA2 can support both slice#1 and slice#2. After receiving the terminal device's registration request, the core network can determine the allowed NSSAI (slice#1) and rejected NSSAI (slice#2) for the terminal device by combining the terminal device's subscribed network slice and the list of network slices supported by the access network devices. The UE cannot initiate a registration request for slice#2 again in RA. Therefore, SA2 introduces partially allowed NSSAI (when the UE is in TA2, slice #2 can also be partially rejected NSSAI. The difference is that when the UE moves within the RA, it does not need to re-register for partially allowed NSSAI, similar to the handling of allowed NSSAI; however, for partially rejected NSSAI, the UE needs to re-register within the supported TA, similar to the handling of rejected NSSAI), to solve this key problem by expanding the RA range of the UE as much as possible. Taking the right column of the above diagram as an example, after introducing partially allowed / rejected NSSAI, based on the above scenario, the core network device can return the following to the UE through the registration accept message: allowed NSSAI includes slice #1, partially allowed NSSAI includes slice #2 (slice #2 can be supported by TA2 and / or cannot be supported by TA1), RA includes TA1 and TA2; or, allowed NSSAI includes slice #1, partially rejected NSSAI includes slice #2 (slice #2 can be supported by TA2 and / or cannot be supported by TA1), RA includes TA1 and TA2, so that the UE can re-initiate a registration request for slice #2 within TA2 of the current RA, while not breaking the TA deployment assumption of the existing protocol.

[0086] Allowed / rejected NSSAI is valid throughout the entire RA of the terminal device, meaning it applies to all TAs within the terminal device's RA. However, partially allowed and partially rejected NSSAI are valid only within certain TAs. The introduction of this feature does not affect... Figure 1The process shown illustrates that when identifying and responding to allowed NSSAI and rejected NSSAI, further additions such as partially allowed NSSAI and partially rejected NSSAI can be made. Terminal devices can only initiate PDU session establishment requests or request activation of an existing PDU session's user plane to obtain data transmission if they are located within a TA that supports partially allowed S-NSSAI.

[0087] Currently, network slices are deployed on the RAN side at the TA (Registered Area) granularity, meaning all cells within a TA support the same network slice. However, when network slices are deployed at certain time intervals or decommissioned, UE and network configurations may be affected. For example, when a network slice becomes unavailable or available again, it may affect allowed NSSAI and other parameters, potentially changing the Registration Area (RA). Therefore, a mismatch may occur between the service area of ​​a network slice and the network slices supported by the TA to which the service area belongs; that is, the granularity of the service area is smaller than the TA, which can be understood as the smallest granularity of the service area being the cell rather than the TA. Figure 3 For example, TA1 supports network slice #2. TA includes four cells: cell 1, cell 2, cell 3, and cell 4. Due to network deployment and other reasons, the resources allocated to slice #2 by cell 2 are suddenly limited. That is, no resources are configured for slice #2 within cell 2, so cell 2 cannot actually provide slice #2 service to the UE. In this embodiment, if a cell does not configure resources for a network slice, it can be said that the cell does not support that network slice; if a cell supports a network slice, it means that the cell has configured the corresponding resources for that network slice. To avoid impacting the UE and the network side, the concept of NS-AoS is introduced to indicate the service area of ​​a network slice. NS-AoS can be represented by one or more cell identifiers (such as NR cell global identifier (NCGI)).

[0088] NS-AoS is deployed on the RAN side, and the AMF can obtain the NS-AoS corresponding to each network slice within the UE's RA through OAM. When the UE indicates support for Single Network Slice Location Availability Information (S-NSSAI location availability information, which indicates the NS-AoS corresponding to the network slice), the AMF can send the NS-AoS corresponding to the configured NSSAI within the RA to the UE through a registration accept message or a UE configuration update message.

[0089] After sending the NS-AoS corresponding to different network slices to the UE, the following operations are possible:

[0090] If the UE receives an NS-AoS corresponding to a requested NSSAI, then after the UE initiates a registration request for that network slice outside of the NS-AoS, the network slice can be identified by the AMF as allowed NSSAI or partially allowed NSSAI.

[0091] If the UE receives an NS-AoS corresponding to a rejected NSSAI or partially rejected NSSAI, the UE can only initiate a registration request for that network slice in cells within the NS-AoS range corresponding to that network slice.

[0092] If the UE receives an NS-AoS corresponding to an allowed NSSAI or partially allowed NSSAI, the UE can only activate the user plane for the established PDU session within the NS-AoS range corresponding to that network slice.

[0093] In current network slicing deployment scenarios, terminal devices may fail to register network slices due to the lack of support for network slices within the TA (Targeting Unit). As shown in Figure 4(a), if the terminal device is camped in TA1, and TA1 only supports slice #1 and not slice #2, then when the terminal device UE initiates a registration request for slice #2 in TA1, the core network will determine slice #2 as a rejected NSSAI or partially rejected NSSAI. Furthermore, the terminal device may be unable to initiate related PDU session establishment or activation requests because the serving cell does not support partially allowed network slices, or has not allocated resources for allowed and / or partially allowed network slices. For example, in Figure 4(b), with a partially allowed network slice, if the terminal device is camped in cell #1, and slice #2 is the terminal device's partially allowed NSSAI, but the TA of cell #1 does not support slice #2 or cell #1 has not allocated available resources for slice #2, then the terminal device cannot request to establish or activate a PDU session associated with slice #2 within cell #1.

[0094] However, the current SON / MDT cannot perform self-optimization for the aforementioned network slice service request failures when performing self-measurement, self-configuration, and self-optimization operations. As a result, the network side cannot optimize the deployment of network slices based on the service needs of terminal devices, which affects the user experience.

[0095] In view of this, embodiments of this application provide a communication method that helps network devices to perform self-optimization on network slices that fail to request services using SON / MDT.

[0096] The communication method provided in this application embodiment can be applied to wireless communication systems, such as 5G communication systems, 6G communication systems, or other future communication systems. Figure 5(a) is an exemplary schematic diagram of a network architecture applicable to an embodiment of this application. As shown in Figure 5(a), the network architecture may include UE, RAN, core network, data network (DN), etc.

[0097] Radio Access Network (RAN) equipment is used to implement functions related to radio access. Also known as access network equipment or base stations, RAN is used to connect terminals to a wireless network. The RAN can be a base station, an evolved NodeB (eNodeB) in an LTE system or an evolved LTE-A system (LTE-Advanced, LTE-A), a next-generation NodeB (gNB) in a 5G communication system, a transmission reception point (TRP), a base band unit (BBU), a WiFi access point (AP), a base station in a future mobile communication system, or an access node in a WiFi system. The RAN can also be a module or unit that performs some of the functions of a base station; for example, it can be a central unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU), etc. RAN can also be an open access network (open RAN, O-RAN, or ORAN). In an ORAN system, CU can also be called an open CU (O-CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. This application does not limit the specific technology or equipment form used in the radio access network. In the following embodiments, the radio access network is referred to as RAN for illustrative purposes.

[0098] A terminal device is a device with wireless transceiver capabilities. It connects wirelessly to a wireless access network device to access a communication system. Terminal devices can also be called terminals, UEs, mobile stations, mobile terminals, etc. Terminal devices can be mobile phones, tablets, computers with wireless transceiver capabilities, virtual reality (VR) terminals, augmented reality (AR) terminals, wireless terminals in industrial control, complete vehicles, wireless communication modules within vehicles, telematics boxes (T-boxes), roadside units (RSUs), terminal devices in autonomous driving, terminal devices in Internet of Things (IoT) networks, terminal devices in remote medical care, terminal devices in smart grids, terminal devices in transportation safety, terminal devices in smart cities, or terminal devices in smart homes, etc. This application's embodiments are not limited to these categories. For ease of description, the following embodiments of this application will use UEs as examples.

[0099] The main functions of the core network include providing UE connectivity, managing UEs, carrying out service transmission, and providing interfaces to external networks as a bearer network. The core network may include network elements such as access and mobility management function (AMF), session management function (SMF), and user plane function (UPF).

[0100] The Access and Mobility Management (AMF) network element is a control plane network element provided by the operator's network, responsible for access control and mobility management of terminal devices accessing the operator's network. This includes functions such as mobility state management, allocation of temporary user identities, authentication, and authorization. In 5G, the AMF network element can be an Access and Mobility Management (AMF). In future communication systems, the AMF network element may still be an AMF, or may have other names; this application does not limit its scope. For ease of description, the following embodiments of this application will use the AMF as an example.

[0101] This application embodiment can also be applied to the O-RAN-based network architecture shown in Figure 5(b). As shown in Figure 5(b), the network architecture may include a UE, gNB-DU, gNB-CU, and a RAN intelligent controller (RIC). Here, gNB-DU is a gNB-DU supporting O-RAN functions; gNB-CU is a gNB-CU supporting O-RAN functions; the RIC is used to collect network information and perform optimization tasks, etc. The RIC communicates with gNB-CU and gNB-DU through an E2 interface. The RIC can directly control the gNB-DU, or control the gNB-DU through the gNB-CU.

[0102] Figure 6 This is a flowchart illustrating a communication method provided in an embodiment of this application. Figure 6 This application illustrates the method using terminal equipment and access network equipment as examples of the entities executing the interaction, but it does not limit the entities executing the interaction. For example, Figure 6 The method executed by the terminal device can also be executed by the communication module in the terminal device, or by the circuit or chip in the terminal device that is responsible for the communication function. Figure 6 The methods executed by the access network device can also be executed by modules (such as chips, chip systems, or processors) applied to the access network device, or by logical nodes, logical modules, or software that implement all or part of the functions of the access network device.

[0103] like Figure 6 As shown, the method may include the following steps:

[0104] Step 601: The terminal device determines the network slice where the requested service failed.

[0105] Specifically, service request failures can include network slicing service request failures, network slice-based PDU session establishment request failures, or network slice-based PDU session activation failures. Among these, network slicing service request failures can include situations where the network slice requested by the terminal device is not supported by the TA (Terrain Address) where the terminal device is located, or situations where the terminal device fails to reselect a cell because the cell to be reselected does not support the network slice requested by the terminal device.

[0106] For example, during the initial access process, a terminal device may request registration for a requested network slice (requested NSSAI), including network slice 1 (slice #1) and network slice 2 (slice #2). If the core network device (such as the AMF) determines that slice #1 is supported in all areas (RA) of the terminal device, but slice #2 is not supported, then the core network device can determine that slice #1 is an allowed network slice (allowed NSSAI) for the terminal device, and slice #2 is a rejected network slice (rejected NSSAI). Alternatively, if the core network device determines that slice #1 is supported in all areas (RA) of the terminal device, but some TAs (including the TA the terminal device is currently in) within the terminal device's RA do not support slice #2, then the core network device can determine that slice #1 is an allowed network slice (allowed NSSAI) for the terminal device, and slice #2 is a partially rejected network slice (partially rejected). NSSAI); then the terminal device can determine that slice#2 is the network slice for which the requested service failed.

[0107] For example, during the initial access process, a terminal device requests registration for slice #1 and slice #2. The core network equipment determines that both slice #1 and slice #2 are supported within the terminal device's RA (Regional Area), thus classifying slice #1 and slice #2 as allowed NSSAIs for the terminal device. However, cell 1 within the terminal device's RA does not have resources configured for slice #2. If the terminal device requests to establish or activate a PDU session based on slice #2 within cell 1, the request will fail. Therefore, the terminal device can determine that slice #2 is a network slice for which the service request failed.

[0108] Step 602: The terminal device sends first information to the access network device. The first information includes information about the network slice where the service request failed.

[0109] The aforementioned first information can be a report, for example, a failure report recorded and submitted by the terminal device according to the instructions of the access network device, which may include information about the network slice where the requested service failed. Alternatively, the first information can also be indication information about the failed network slice. Or, the first information may also be information about the identified network slice.

[0110] The first information may include one or more of the following:

[0111] 1) Identifier of the network slice whose service request failed. For example, S-NSSAI. If the first information includes the identifier of the network slice whose service request failed, then the recipient of the first information (such as access network equipment, or other equipment capable of parsing and processing the first information) can determine the network slice whose service request failed based on the identifier. This allows the network slice whose service request failed to be configured and optimized during subsequent self-configuration and self-optimization of network equipment (including access network equipment, core network equipment, etc.).

[0112] 2) The identifier of the NSAG associated with the network slice that failed to request service. For example, the NSAG ID. If the first information includes the identifier of the NSAG associated with the network slice that failed to request service, the recipient of the first information can determine the NSAG associated with the network slice that failed to request service based on the identifier. This allows for the configuration and optimization of the NSAG associated with the network slice that failed to request service during subsequent self-configuration and self-optimization of network devices. Optionally, it may also include the valid tracking area identity (TAI) and / or NSAG priority corresponding to the NSAG associated with the network slice that failed to request service, which is beneficial for subsequent optimization of network configuration parameters used for cell reselection.

[0113] 3) Reasons for network slice request failures. For example, the reason for a failed network slice request could be that the requested network slice is not supported by the TA (Target Area Network) where the terminal device is located, or that the cell where the terminal device is located has not allocated resources for the requested network slice. If the first information includes the reason for the failed network slice request, the recipient of the first information can obtain the reason for the failed network slice request. This allows the recipient to determine whether to configure or optimize the network slice during subsequent self-configuration and self-optimization of the network device. If configuration or optimization is required, the recipient can configure and optimize the corresponding network slice based on the reason for the failure, thereby reducing the number of service request failures caused by this reason.

[0114] 4) The slice type of the network slice for which the service request failed. For example, the slice type of the network slice for which the service request failed could indicate that the network slice is an allowed network slice (allowed NSSAI), a partially allowed network slice (partially allowed NSSAI), a rejected network slice (rejected NSSAI), a partially rejected network slice (partially rejected NSSAI), or a requested network slice (requested NSSAI). If the first information includes the slice type of the network slice for which the service request failed, the recipient of the first information can determine whether to configure or optimize the network slice based on the slice type. If configuration or optimization is required, configuration and optimization measures corresponding to the slice type can be implemented on the network slice.

[0115] 5) The time when the network slice request failed. If the first information includes the time of the failed request, the recipient of the first information can determine whether to configure or optimize the network slice, and how to configure or optimize it, based on the time of the failed request. For example, if a small number of terminal devices initiate and fail to request services from the network slice during this period, then the network slice may not need to be configured or optimized; if a large number of terminal devices initiate and fail to request services from the network slice during this period, then the network slice may be configured and optimized. Furthermore, configuration and optimization may only be performed within the corresponding time period.

[0116] 6) Cell reselection failure identifier. During cell reselection, the terminal device may encounter a cell that does not support the network slice requested by the terminal device, resulting in cell reselection failure. After the terminal device reselects and accesses the network, it can report the cell reselection failure identifier to the access network device so that the access network device can optimize the cell reselection parameters in the future.

[0117] In the above communication method, if a terminal device fails to initiate a network slice service request (such as a network slice registration request), a network slice-based PDU session establishment request, or a network slice-based PDU session activation request, the terminal device can send the information of the network slice for which the service request failed to the access network device. The access network device can then statistically analyze the information of the network slice for which the service request failed and use SON / MDT technology to perform self-configuration and self-optimization operations on the network slice, thereby better providing services to the terminal device and improving the user experience.

[0118] In one possible implementation, when performing step 601, the terminal device may determine the network slice where the requested service failed using one or more of the following determination methods:

[0119] Method 1: The terminal device can determine the network slice whose request for the service failed based on the reason for rejection of the rejected network slice.

[0120] Terminal devices can receive downlink non-access stratum (NAS) messages from core network devices, such as registration accept messages and configuration update command messages. These downlink NAS messages can carry the cause value for rejected network slices (rejected S-NSSAI) or partially rejected network slices (partially rejected S-NSSAI). The terminal device can determine the network slice whose service request failed based on the cause of rejection. For example, a cause value of "0001" indicates that the network slice was rejected because it was unavailable in the RA (Regulatory Area), so the terminal device can identify this network slice as the one whose service request failed. Similarly, for a partially rejected NSSAI, the corresponding cause value indicates that the network slice is available in some TAs (Target Areas) of the RA but unavailable in others, so the terminal device can identify this network slice as the one whose service request failed. For example, if the cause value indicates that the network slice is not a subscribed network slice of the terminal device, although the registration of the network slice has not been successful, it does not fall under the category of request service failures that need to be recorded and reported in this application embodiment.

[0121] Optionally, the determination method 1 described above can be performed by the NAS of the terminal device. Specifically, after receiving a downlink NAS message (such as registration accept, configuration update command, etc.), the NAS of the terminal device can determine the network slice whose service request failed based on the rejection reason of the rejected network slice in the downlink NAS message.

[0122] Method 2: The terminal device can determine the network slice where the requested service failed based on one or more of the following information: first TA information, second TA information, and the location information of the terminal device.

[0123] The first TA information includes TA information for one or more partially allowed network slices (NSSAI) supported by the terminal device. During the registration process of the terminal device for network slices, when the core network device determines the partially allowed network slices for the terminal device, it can further indicate the TA information corresponding to each partially allowed network slice, such as a list of TAs supporting that network slice. For example, the network slices partially allowed by the terminal device include slice #1 and slice #2. Slice #1 can be supported by TA1, TA2, and TA3, and slice #2 can be supported by TA1 and TA2. Among them, TA1, TA2, and TA3 all belong to the RA of the terminal device. Then, while indicating that the network slices partially allowed by the terminal device include slice #1 and slice #2, the core network device can further indicate the TA list {TA1, TA2, TA3} corresponding to slice #1 and the TA list {TA1, TA2} corresponding to slice #2. This allows the terminal device to determine whether it can initiate the establishment / activation of PDU sessions based on slice #1 and / or slice #2 in the new TA when it moves, based on the TA it is in after the move and the TA lists corresponding to slice #1 and slice #2.

[0124] The second TA information includes TA information for one or more network slices that support the partial rejection of the terminal device. During the registration process of the terminal device for network slices, when the core network device identifies the partial rejection of the network slices for the terminal device, it can further indicate the TA information corresponding to each partial rejection of the network slice, such as a list of TAs supporting the network slice. For example, if the network slices partially rejected by the terminal device include slice #1 and slice #2, and slice #1 can be supported by TA1 and TA3, and slice #2 can be supported by TA2 and TA3, where TA1, TA2, and TA3 all belong to the RA of the terminal device, then while indicating that the network slices partially rejected by the terminal device include slice #1 and slice #2, the core network device can further indicate the TA list {TA1, TA3} that supports slice #1, and the TA list {TA2, TA3} that supports slice #2. This allows the terminal device to determine whether it can initiate PDU session establishment / activation based on slice #1 and / or slice #2 in the new TA after the move, based on the TA it is in after the move and the TA lists corresponding to slice #1 and slice #2.

[0125] The location information of the terminal device may include the TA where the terminal device is located, and / or the cell where the terminal device is located. In the above determination method 2, the terminal device determines the network slice where the requested service failed based on the TA information corresponding to the network slice. Therefore, if the terminal device obtains the information of the cell where it is currently located, it can first determine the TA where the terminal device is currently located based on the cell information, and then determine the network slice where the requested service failed based on the TA where the terminal device is currently located, as well as the aforementioned first TA information and / or second TA information.

[0126] For example, the RA of a terminal device includes TA1, TA2, and TA3. The terminal device initiates a network slice registration request in TA1, requesting registration for slice #1, slice #2, and slice #3. The TAs supporting slice #1 include TA1, TA2, and TA3; the TAs supporting slice #2 include TA1 and TA2; and the TAs supporting slice #3 include TA2 and TA3. The core network equipment determines that slice#1 is available in all TAs within the RA of the terminal equipment, and therefore identifies slice#1 as allowed NSSAI; it determines that slice#2 is available in some TAs, unavailable in some TAs, and available in the current TA1, and therefore identifies slice#2 as partially allowed NSSAI, and indicates the list of TAs supporting slice#2 {TA1, TA2} (i.e., the first TA information mentioned above); it determines that slice#3 is available in some TAs, unavailable in some TAs, and unavailable in the current TA1, and therefore identifies slice#3 as partially rejected NSSAI, and indicates the list of TAs supporting slice#3 {TA2, TA3} (i.e., the second TA information mentioned above). Based on the list of TAs supporting slice #2 {TA1, TA2}, the list of TAs supporting slice #3 {TA2, TA3}, and the fact that the terminal device is currently located in TA1, it determines that the network slice that the current TA1 does not support is slice #3. Therefore, slice #3 is identified as the network slice for which the service request failed.

[0127] In one possible design, the aforementioned determination method 2 can be performed by the NAS of the terminal device. Specifically, the NAS of the terminal device can obtain the first TA information and / or the second TA information from the received downlink NAS messages (such as registration accept, configuration update command, etc.), and then determine the network slice where the requested service failed based on one or more of the terminal device's location information, the first TA information, and the second TA information. Optionally, the NAS of the terminal device can obtain the terminal device's location information from the terminal device's access stratum (AS).

[0128] In another possible design, the aforementioned determination method 2 can be performed by the AS of the terminal device. Specifically, the NAS of the terminal device can obtain the first TA information and / or the second TA information from the received downlink NAS messages (such as registration accept, configuration update command, etc.); then, the NAS of the terminal device can send the obtained first TA information and / or second TA information to the AS of the terminal device, and the AS of the terminal device can determine the network slice where the requested service failed based on one or more of the terminal device's location information, the first TA information, and the second TA information.

[0129] Method 3: The terminal device can determine the network slice where the requested service failed based on one or more of the following information: first cell information, second cell information, and the location information of the terminal device.

[0130] The first cell information includes information on one or more cells where available resources exist for the network slices partially permitted for the terminal device.

[0131] As mentioned earlier, even if a TA deploys network slice A, due to various factors, some cells within the TA can provide services based on network slice A, while others have not configured resources for network slice A and therefore cannot provide such services. In other words, the smallest granularity of the service area for network slice A may be a cell rather than a TA. Therefore, the service area corresponding to a network slice can be represented by an NS-AoS, which can be represented by one or more cell identifiers. Thus, the NS-AoS corresponding to the partially allowed network slices (NSSAI) of the terminal device can be used as the aforementioned first cell information.

[0132] During the registration process of network slices by the terminal device, when the core network device identifies some of the allowed network slices for the terminal device, it can further indicate the cell information of available resources for each of the partially allowed network slices. For example, the network slices allowed by the terminal device include slice#1 and slice#2. Cell 1 and cell 2 in TA1, and cell 3 and cell 4 in TA2 are all configured with available resources for slice#1. Cell 1 and cell 2 in TA1, and cell 3 in TA2 are all configured with available resources for slice#2. Then, while indicating that the network slices allowed by the terminal device include slice#1 and slice#2, the core network device can further indicate that it supports NS-AoS1{cell1, cell2, cell3, cell4} corresponding to slice#1 and NS-AoS2{cell1, cell2, cell3} corresponding to slice#2. This allows the terminal device to determine whether it can initiate PDU session establishment / activation based on slice#1 and / or slice#2 in its cell, according to the cell it is in and the NS-AoS corresponding to slice#1 and slice#2.

[0133] The second cell information includes information on one or more cells where available resources exist for the network slices permitted by the terminal device. Optionally, the NS-AoS corresponding to the network slice (allowed NSSAI) permitted by the terminal device can be used as the aforementioned second cell information.

[0134] During the registration process of network slices by terminal devices, when the core network equipment determines the allowed network slices (allowed NSSAI) for the terminal devices, it can further indicate the cell information of available resources for each part of the allowed network slices. For example, if the network slices allowed by the terminal device include slice#1 and slice#2, and cells 1 and 2 in TA1, as well as cells 3 and 4 in TA2, are all configured with available resources for slice#1; and cells 1 and 2 in TA1, as well as cells 3 in TA2, are all configured with available resources for slice#2, then while indicating to the terminal device that the allowed network slices include slice#1 and slice#2, the core network device can further indicate that it supports NS-AoS1 {cell1, cell2, cell3, cell4} corresponding to slice#1 and NS-AoS2 {cell1, cell2, cell3} corresponding to slice#2. This allows the terminal device to determine whether it can initiate PDU session establishment / activation based on slice#1 and / or slice#2 in its cell, according to the cell it is in and the NS-AoS corresponding to slice#1 and slice#2.

[0135] The location information of the terminal device may include the cell in which the terminal device is located. Optionally, the location information of the terminal device may be determined by the AS of the terminal device.

[0136] In one possible design, the aforementioned determination method 3 can be performed by the NAS of the terminal device. Specifically, the NAS of the terminal device can obtain the first cell information and / or the second cell information from the received downlink NAS messages (such as registration accept, configuration update command, etc.), and then determine the network slice for which the requested service failed based on one or more of the terminal device's location information, the first cell information, and the second cell information. Optionally, the NAS of the terminal device can obtain the terminal device's location information from the terminal device's AS.

[0137] In another possible design, the aforementioned determination method 3 can be performed by the AS of the terminal device. Specifically, the NAS of the terminal device can obtain the first cell information and / or the second cell information from the received downlink NAS messages (such as registration accept, configuration update command, etc.); then, the NAS of the terminal device can send the obtained first cell information and / or second cell information to the AS of the terminal device, and the AS of the terminal device can determine the network slice for which the requested service failed based on one or more of the terminal device's location information, the first cell information, and the second cell information.

[0138] Terminal devices can identify network slices that failed to request services by using one or more of the above methods, thereby reporting the network slices that failed to request services.

[0139] Among the various determination methods mentioned above, after completing the network slice registration process, the terminal device can obtain the information required to determine the network slice for which the requested service failed (such as the rejection reason of the rejected network slice, the first TA information, the second TA information, the first cell information, and the second cell information). One possible implementation is that after obtaining the required information, the terminal device determines the network slice for which the requested service failed according to one or more of the above determination methods.

[0140] In another possible implementation, the terminal device can also identify the corresponding network slice as a failed service request when the service requirement based on network slice cannot be fulfilled. For example, when the terminal device needs to establish / activate a PDU session based on network slice A, and determines, according to one or more of the above determination methods, that a PDU session based on network slice A cannot be established / activated in the current TA or the current cell, then the terminal device determines that network slice A is a failed service request and needs to report the information of network slice A.

[0141] In one possible implementation, the terminal device can record the first information before executing step 602. When the triggering condition for sending the first information is met, the terminal device then executes step 602 and sends the first information to the access network device. In other words, the terminal device does not need to report immediately when it determines that a network slice has failed to request services. Instead, it records the first information (including information about the network slice that failed to request services) first, and then sends the first information to the access network device when reporting is required.

[0142] Furthermore, the terminal device can record the first information when the triggering conditions for recording the first information are met. The triggering conditions for recording the first information may include one or more of the following conditions:

[0143] 1) Identify network slices where service requests have failed. When a network slice where a service request has failed is identified, the terminal device can record information about the failed network slice. For example, the terminal device can record initial information after a registration request for a network slice fails, or after a request to establish a PDU session based on a network slice fails, or after a request to activate a PDU session based on a network slice fails.

[0144] 2) The number of network slices whose service requests failed reaches a preset limit. For example, when a terminal device registers network slices, it requests to register 4 network slices. Assuming the preset limit is 2, if 3 network slices are successfully registered and 1 network slice fails to register, it can be assumed that the currently provided network slice service can meet the communication needs of the terminal device, and the information of the failed network slices does not need to be recorded and reported. If the terminal device successfully registers 2 network slices and fails to register 2 network slices, it can be assumed that the currently provided network slice service may affect the communication quality of the terminal device. In this case, the terminal device can record the information of the 2 failed network slices so that it can report the information of the failed network slices in the future.

[0145] 3) The service types of network slices whose service requests failed include preset service types. For example, services with high communication quality requirements, such as enhanced mobile broadband (eMBB) and ultra-reliable low-latency communication (URLLC), have communication quality that is a key focus of the communication system and requires continuous optimization. Therefore, service types such as eMBB and URLLC can be set as preset service types. When there are network slices of the eMBB or URLLC service type whose service requests failed, the terminal device can record the network slices whose service requests failed so that information about the failed network slices can be reported later.

[0146] 4) Service request failure in the first network slice. Network devices and / or terminal devices may pre-configure a first network slice, for example, designating a network slice requiring special attention as the first network slice. When a service request fails in the first network slice, the terminal device can record the information about the first network slice for subsequent reporting. Optionally, the first network slice can be pre-configured by the terminal device or sent to the terminal device by the network device (including access network devices and core network devices).

[0147] 5) A service request fails in a network slice associated with the first NSAG. Network devices and / or terminal devices may pre-configure a first NSAG, for example, setting a NSAG that requires special attention as the first NSAG. When a service request fails in a network slice associated with the first NSAG, the terminal device can record information about the failed network slice. This recorded information may include the network slice's information and the information of the first NSAG associated with that network slice. Optionally, the first NSAG may be pre-configured by the terminal device or sent to the terminal device by the network device (including access network devices and core network devices).

[0148] 6) The priority of the NSAG associated with the network slice that failed to request a service meets the preset priority. Network devices and / or terminal devices may be pre-configured with preset priorities. If the priority of the NSAG associated with the network slice that failed to request a service is higher than or equal to the preset priority, then the network slice can be considered a network slice of key concern to the communication system, and its information needs to be recorded. The recorded information may include the network slice information itself, or it may include the NSAG information associated with the network slice. Optionally, the preset priority may be pre-configured by the terminal device, or it may be sent to the terminal device by the network device (including access network devices and core network devices).

[0149] 7) Pre-configured trigger events occur. Network devices and / or terminal devices may be pre-configured with trigger events. If a pre-configured trigger event occurs, the terminal device records the information of the network slice where the service request failed for subsequent reporting. The trigger event may include determining that it is impossible to initiate / activate a PDU session based on a network slice. For example, when a terminal device needs to establish / activate a PDU session based on network slice A, it determines, according to one or more of the determination methods mentioned above, that it is impossible to establish / activate a PDU session based on network slice A in the current TA or the current cell. Then, the terminal device determines that network slice A is the network slice where the service request failed and records the information of network slice A.

[0150] Optionally, the terminal device may send the first information to the access network device when the triggering condition for sending the first information is met. The triggering condition for sending the first information may include one or more of the following conditions:

[0151] 1) Reporting time is reached according to the reporting cycle. The terminal device can periodically report the first information. Each time it reports, it sends the network slice information of failed service requests within a cycle to the access network device. Optionally, the reporting cycle can be pre-configured by the terminal device, or it can be sent to the terminal device by the network device (including access network device and core network device).

[0152] 2) Preset trigger event occurs. The terminal device can report the first information when the preset trigger event occurs. Optionally, the preset trigger event can be pre-configured by the terminal device, or it can be sent to the terminal device by the network device (including access network device and core network device).

[0153] 3) The number of network slices whose service requests have failed reaches a preset limit. If the number of network slices whose service requests have failed recorded by the terminal device reaches a preset limit, then the information of the recorded network slices whose service requests have failed is sent to the network device. Optionally, the preset limit can be pre-configured by the terminal device, or it can be sent to the terminal device by the network device (including access network devices and core network devices).

[0154] 4) The network slice for which the service request failed includes a preset service type. If the network slice for which the service request failed recorded by the terminal device includes a network slice for a preset service type (such as eMBB, URLLC, etc.), then the terminal device will send the information of the network slice for which the service request failed to the access network device.

[0155] 5) The priority of the NSAG associated with the network slice where the service request failed meets the preset priority. If the priority of the NSAG associated with the network slice where the service request failed is higher than or equal to the preset priority, then the network slice can be considered a network slice of key concern to the communication system, and information about the network slice needs to be reported. The information about the network slice can include the information of the NSAG associated with the network slice. Optionally, the preset priority can be pre-configured by the terminal device, or it can be sent to the terminal device by the network device (including access network device and core network device).

[0156] In one possible implementation, the terminal device receives first indication information and records and / or sends first information based on the first indication information. The first indication information indicates one or more of the following: whether to record the time when the requested service failed (e.g., the time when the network slice that requested the service failed was recorded), whether to record the NSAG associated with the network slice that requested the service failed, whether to record the reason for the failure of the network slice that requested the service failed, whether to record the slice type of the network slice that requested the service failed, the triggering condition for recording the first information, the triggering condition for sending the first information, and whether the first information is recorded by the terminal device's NAS or AS.

[0157] In another possible implementation, the terminal device may record and / or send first information based on second indication information. The second indication information indicates one or more of the following: information contained in the first information, triggering conditions for recording the first information, triggering conditions for sending the first information, and whether the first information is recorded by the terminal device's NAS or AS.

[0158] To better understand the above embodiments, the following is in conjunction with... Figure 7 Let's illustrate with examples. Figure 7 The specific example shown may include the following steps:

[0159] Step 701: The access network device sends the first indication information to the UE.

[0160] Optionally, the first indication information can be either immediate MDT configuration information or logged MDT configuration information.

[0161] Optionally, the first indication information is used to indicate one or more of the following: information contained in the first information, a first trigger condition for recording the first information, a second trigger condition for sending the first information, and whether the first information is recorded by the NAS or AS of the terminal device.

[0162] Furthermore, the first indication information may indicate that the first information includes one or more of the following: the identifier of the network slice whose request service failed, the identifier of the NSAG associated with the network slice whose request service failed, the reason for the failure of the network slice whose request service failed, the slice type of the network slice whose request service failed, and the time when the network slice whose request service failed experienced the request service failure.

[0163] Step 701 above is an optional step; when the access network device does not perform step 701 above, the terminal device can determine the information contained in the first information, the triggering condition for recording the first information, the triggering condition for sending the first information, and whether the first information is recorded by the terminal device's NAS or AS, etc., based on the second instruction information configured by itself.

[0164] Step 702: The terminal device sends an uplink NAS message, which includes information about the network slice requested by the terminal device (requested NSSAI).

[0165] This uplink NAS message can be used for network slice registration. The terminal device can carry the requested network slice (requested NSSAI) information in the NAS message so that the AMF can determine the allowed network slice (allowed NSSAI) for the terminal device based on the terminal device's subscription information, the network slice information supported by the access network device, and the network slice information supported by itself.

[0166] Optionally, the uplink NAS message can be a registration request message.

[0167] Step 703: AMF sends a downlink NAS message, which includes network slices allowed by the terminal device (allowed NSSAI), etc.

[0168] After receiving an uplink NAS message from the terminal device, the AMF can determine the allowed network slices (NSSAI) based on the network slice information requested by the terminal device, the terminal device's subscription information, the network slice information supported by the access network device, and its own supported network slice information. It can also determine partially allowed, partially rejected, and rejected network slices. The AMF can then send this information, along with the details of the allowed, partially allowed, partially rejected, and rejected network slices, to the terminal device in a downlink NAS message.

[0169] In addition, the downlink NAS message may also include the TA information and / or NS-AoS corresponding to each network slice in allowed NSSAI, partially allowed NSSAI, and partially rejected NSSAI.

[0170] Step 704: The terminal device identifies the network slice where the requested service failed and records the first information.

[0171] Upon receiving a downlink NAS message, the terminal device can determine the network slice from which the requested service failed based on the rejection reasons (including partially rejected NSSAI and rejected NSSAI) in the downlink NAS message, and record the network slice from which the requested service failed (i.e., the first information). For details, please refer to determination method 1 above.

[0172] Alternatively, the terminal device can determine the network slice where the requested service failed based on its own location information, the TA information of partially allowed NSSAI, and / or the TA information of partially rejected NSSAI, and record the first piece of information. See method 2 above for details.

[0173] Alternatively, the terminal device can also determine the network slice where the requested service failed based on its own location information, the NS-AoS with allowed NSSAI, and the NS-AoS with partially allowed NSSAI, and record the first piece of information. For details, please refer to determination method 3 above.

[0174] exist Figure 7 In the illustrated embodiment, the terminal device records the information of the network slice that failed to request a service when it determines that such a service has failed. However, in other embodiments, the terminal device may also record the information only when a preset first triggering condition is met. The first triggering condition may include the number of network slices that failed to request a service reaching a preset number, the service type of the network slice that failed to request a service including a preset service type, the first network slice experiencing a service request failure, the network slice associated with the first NSAG experiencing a service request failure, and the priority of the NSAG associated with the network slice that failed to request a service meeting a preset priority, etc.

[0175] Step 705: The terminal device sends the first information to the access network device.

[0176] The aforementioned first piece of information can be an MDT report, a Radio Link Failure Report (RLF report), or other reports used to report network slices that have failed to request services.

[0177] Optionally, the terminal device may send the first information to the access network device after completing the recording of the first information, or the terminal device may send the first information to the access network device when the second triggering condition is met. The second triggering condition may include receiving a request to report from the access network device, reaching the reporting time of the reporting week, the occurrence of a preset triggering event, the number of network slices that have failed to request services reaching a preset number, and the priority of the NSAG associated with the network slices that have failed to request services meeting a preset priority.

[0178] Figure 8 This is a flowchart illustrating another communication method provided in an embodiment of this application. Figure 8 The method is illustrated using an access network device as the execution subject, but the embodiments of this application do not limit the execution subject of the method. For example, Figure 8 The methods executed by the access network device can also be executed by modules (such as chips, chip systems, or processors) applied to the access network device, or by logical nodes, logical modules, or software that implement all or part of the functions of the access network device.

[0179] like Figure 8 As shown, the method may include the following steps:

[0180] Step 801: The access network device determines the network slice where the terminal device's service request failed.

[0181] Specifically, service request failures can include network slicing service request failures, network slicing-based PDU session establishment request failures, or network slicing-based PDU session activation failures. Among these, network slicing service request failures may occur when the network slice requested by the terminal device is not supported by the TA (Terrain Association) to which the terminal device is located.

[0182] In one possible implementation, when the access network device determines that the network slice for which the terminal device's service request has failed, it can determine the network slice based on one or more of the following information: the network slice requested by the terminal device, the network slices supported by the access network device itself, and the resource configuration information of the access network device for each supported network slice.

[0183] For example, during the initial access process, a terminal device may request to register a requested network slice (requestedNSSAI), which includes network slice 1 (slice#1) and network slice 2 (slice#2). If the access network device determines that it supports slice#1 but does not support slice#2, then the access network device can determine that slice#2 is the network slice for which the requested service failed.

[0184] For example, during the initial access process, a terminal device requests to register slice#1 and slice#2. The access network device determines that it supports slice#1 and slice#2, but cell 1 corresponding to the access network device has not configured resources for slice#1, and cell 2 has not configured resources for slice#2. If the terminal device is currently located in cell 1, the access network device can determine that slice#1 is a network slice for which the requested service failed. If the terminal device is currently located in cell 2, the access network device can determine that slice#2 is a network slice for which the requested service failed.

[0185] In this implementation, if the access network device needs to determine the network slice for which the requested service failed based on the network slice requested by the terminal device, the access network device can obtain the network slice requested by the terminal device. For example, the terminal device can send the network slice requested by the terminal device to the access network device via message 5 (msg5) during the initial access process; alternatively, the terminal device can send a registration update request to the access network device in the RRC connected state, and include the network slice requested by the terminal device in the registration update request; or, if the terminal device also reports information about the network slice for which the requested service failed (i.e., the network slice requested by the terminal device), the terminal device can also obtain the network slice through the reported information about the network slice for which the requested service failed (i.e., the network slice requested by the terminal device). Figure 6 , Figure 7 The first information in the illustrated embodiment is sent to the access network device.

[0186] Alternatively, the access network device can also obtain the network slice requested by the terminal device from the core network device (such as the AMF). For example, based on the network slice requested by the terminal device, the network slices supported by the access network device, and the network slices supported by the core network device, the AMF determines the allowed network slice (allowed NSSAI), partially allowed network slice (partially allowed NSSAI), rejected network slice (rejected NSSAI), and partially rejected network slice (partially rejected NSSAI) for the terminal device; then, the AMF can send one or more of the requested NSSAI, allowed NSSAI, and partially allowed NSSAI to the access network device.

[0187] In another possible implementation, when determining that a network slice for which a terminal device's service request has failed, the access network device may also determine the network slice based on one or more of the following information: network slices partially allowed by the terminal device, network slices allowed by the terminal device, network slices supported by the access network device, and resource configuration information of the access network device for each supported network slice.

[0188] Among them, the network slices allowed by the terminal equipment and the network slices allowed by the terminal equipment can be obtained by the access network equipment from the core network equipment (such as AMF).

[0189] For example, the AMF determines that slice #1 is a network slice allowed by the terminal device, and slice #2 is a network slice partially allowed by the terminal device; if the access network device supports slice #1 but does not support slice #2, then the access network device can determine that slice #2 is a network slice for which the requested service failed.

[0190] For example, the AMF determines that slice #1 is a network slice allowed by the terminal device, and slice #2 is a partially allowed network slice by the terminal device. Suppose that the access network device supports slice #1 and slice #2, but cell 1 corresponding to the access network device has not configured resources for slice #1, and cell 2 has not configured resources for slice #2. If the terminal device is currently located in cell 1, then the access network device can determine that slice #1 is a network slice for which the requested service failed. If the terminal device is currently located in cell 2, then the access network device can determine that slice #2 is a network slice for which the requested service failed.

[0191] In addition, the access network device can also receive the first information reported by the terminal device. In this case, the access network device can also determine the network slice that failed to request the service based on the first information.

[0192] Step 802: The access network device records the second information, which includes information about the network slice where the service request failed.

[0193] The second information may include one or more of the following:

[0194] 1) The identifier of the network slice whose service request failed, such as S-NSSAI. If the second information includes the identifier of the network slice whose service request failed, then when the access network device analyzes and processes the information subsequently, it can identify the network slice whose service request failed based on the identifier. This allows it to configure and optimize the network slice whose service request failed during subsequent self-configuration and self-optimization of network devices (including access network devices and core network devices). Alternatively, the access network device can send the second information to other devices (such as OAM devices, RAN intelligent controllers (RICs), etc.) for analysis and processing, thereby enabling self-configuration and self-optimization of network devices (including access network devices and core network devices).

[0195] 2) The identifier of the NSAG associated with the network slice that failed to request the service, such as the NSAG ID. If the second information includes the identifier of the NSAG associated with the network slice that failed to request the service, then the access network device or the recipient of the second information can determine the NSAG associated with the network slice that failed to request the service based on the identifier of the NSAG associated with the network slice that failed to request the service. Thus, in the subsequent self-configuration and self-optimization process of the network device, the NSAG associated with the network slice that failed to request the service can be configured and optimized.

[0196] 3) Reasons for network slice failures in requesting services. For example, the reason for a failed network slice request could be that the requested network slice is not supported by the TA (Target Access Center) where the terminal device is located, or that some or all cells of the access network device have not allocated resources for the requested network slice. If the second information includes the reason for the failure of the network slice request, then the access network device or the recipient of the second information can obtain the reason for the failure of the network slice request. This allows them to determine whether to configure or optimize the network slice during subsequent self-configuration and self-optimization of the network device. If configuration or optimization is required, the corresponding network slice can be configured and optimized based on the reason for the failure, thereby reducing service request failures caused by this reason.

[0197] 4) The slice type of the network slice for which the service request failed. For example, the slice type of the network slice for which the service request failed could indicate that the network slice is an allowed network slice (allowed NSSAI), a partially allowed network slice (partially allowed NSSAI), a rejected network slice (rejected NSSAI), a partially rejected network slice (partially rejected NSSAI), or a requested network slice (requested NSSAI). If the second information includes the slice type of the network slice for which the service request failed, the access network device or the recipient of the second information can determine whether to configure or optimize the network slice based on the slice type. If configuration or optimization is required, configuration and optimization measures corresponding to the slice type can be implemented on the network slice.

[0198] 5) The time when the network slice request for service failed. If the second information includes the time of the service request failure, the access network device or the recipient of the second information can determine whether to configure or optimize the network slice, and how to configure or optimize it, based on the time of the service request failure. For example, if a small number of terminal devices initiate service requests for the network slice within this time period and fail, then the network slice may not need to be configured or optimized; if a large number of terminal devices initiate service requests for the network slice within this time period and fail, then the network slice may be configured and optimized. Furthermore, configuration and optimization may only be performed within the corresponding time period.

[0199] Optionally, the access network device may execute the above communication method after receiving the third indication information, wherein the third indication information is used to instruct the access network device to record the network slice information of the requesting service device. This third indication information may be sent by the terminal device, or by a core network device (such as an AMF), or by an OAM, or by a RIC.

[0200] In the aforementioned communication method, considering that terminal devices may fail when initiating network slice service requests (such as network slice registration requests), PDU session establishment requests based on network slices, and PDU session activation requests based on network slices, the access network device can record the information of the network slices that failed to request services. This facilitates the access network device's statistical analysis of the information on the network slices that failed to request services, and enables it to perform self-configuration and self-optimization operations on network slices using SON / MDT technology. Alternatively, it can facilitate the transmission of the recorded information to other devices for statistical analysis of the information on the network slices that failed to request services, thereby better providing services to terminal devices and improving user experience.

[0201] Optionally, the access network device can perform self-configuration, self-optimization, and other operations on the network slice based on the recorded second information; or, the access network device can send the second information to devices such as RIC and OAM, which can then analyze and statistically analyze the second information to instruct the access network device to perform configuration, optimization, and other operations on the network slice.

[0202] To better understand the above embodiments, the following is in conjunction with... Figure 9 Let's illustrate with examples. Figure 9 The specific example shown may include the following steps:

[0203] Step 901a: The terminal device sends the requested network slice (NSSAI) information to the access network device.

[0204] Step 901b: The terminal device sends an uplink NAS message to the AMF, which includes information about requestedNSSAI.

[0205] The embodiments of this application do not limit the order of steps 901a and 901b, and step 901a is an optional step.

[0206] Step 902a: AMF sends a downlink NAS message, which includes network slices allowed by the terminal device (allowed NSSAI), etc.

[0207] Step 902b: The AMF sends information to the access network equipment regarding the terminal device's allowed NSSAI and / or partially allowed network slices.

[0208] After receiving an uplink NAS message from the terminal device, the AMF can determine the allowed network slices (NSSAIs), partially allowed network slices (NSSAIs), partially rejected network slices (NSSAIs), and rejected network slices (NSSAIs) based on the terminal device's requested NSSAI information, the terminal device's subscription information, the network slice information supported by the access network device, and its own supported network slice information. The AMF can then send this information, along with the determined allowed, partially allowed, partially rejected, and rejected network slices, to the terminal device in a downlink NAS message.

[0209] In addition, the downlink NAS message may also include the TA information and / or NS-AoS corresponding to each network slice in allowed NSSAI, partially allowed NSSAI, and partially rejected NSSAI.

[0210] AMF can also send allowed NSSAI information and / or partially allowed NSSAI information to access network devices, so that access network devices can determine the network slices whose service requests have failed based on the allowed NSSAI information and / or partially allowed NSSAI information.

[0211] This application embodiment does not limit the order of steps 902a and 902b, and step 902b is an optional step. For example, if the terminal device executes step 901a, then the AMF may not execute step 902b; if the AMF executes step 902b, then the terminal device may not execute step 901a.

[0212] Step 903: The access network device determines the network slice where the requested service failed and records the second information.

[0213] Optionally, the access network device can determine the network slice for which the terminal device failed to request services based on the obtained requested NSSAI, the information of the network slices it supports, and the resource configuration information for each supported network slice, and record the second information; or, the access network device can determine the network slice for which the terminal device failed to request services based on the obtained allowed NSSAI and / or partially allowed NSSAI, and the resource configuration information for each supported network slice, and record the second information.

[0214] Figure 10 This is a schematic diagram of a communication device according to an embodiment of this application. The communication device includes a processing module 1001 and a transceiver module 1002. The processing module 1001 is used to process data by the communication device. The transceiver module 1002 is used to receive content from the communication device and other units or network elements, or to send content from the communication device and other units or network elements. It should be understood that the processing module 1001 in this embodiment of the application can be implemented by a processor or processor-related circuit components (or, referred to as processing circuitry), and the transceiver module 1002 can be implemented by a receiver / transmitter or receiver / transmitter-related circuit components.

[0215] For example, the communication device may be a communication device equipment, or it may be a chip or other combination device or component that has the functions of the aforementioned communication device equipment applied in the communication device equipment.

[0216] When the communication device is a terminal device, the processing module 1001 determines the network slice where the requested service failed. The failed service request includes network slice service request failure, network slice-based Protocol Data Unit (PDU) session establishment request failure, or network slice-based PDU session activation failure. The failed network slice service request includes the network slice requested by the terminal device not being supported by the Tracking Area (TA) where the terminal device is located. The transceiver module 1002 sends first information, which includes information about the network slice where the requested service failed. The first information includes one or more of the following: the identifier of the network slice where the requested service failed; the identifier of the NSAG associated with the network slice where the requested service failed; the reason for the failure of the network slice where the requested service failed; the slice type of the network slice where the requested service failed; and the time when the network slice where the requested service failed experienced a service request failure.

[0217] In addition, the above modules can also be used to support Figures 6 to 9 Other processes performed by the terminal device in the illustrated embodiment. The beneficial effects are described above and will not be repeated here.

[0218] When the communication device is an access network device, the processing module 1001 determines that the terminal device's request for a service has failed. The service request failure includes network slice service request failure, PDU session establishment request failure based on the network slice, or PDU session user plane activation failure based on the network slice. The service request failure includes the network slice requested by the terminal device not being supported by the Tracking Area (TA) where the terminal device is located. The module records second information, which includes information about the network slice whose service request failed. The second information includes one or more of the following: the identifier of the network slice whose service request failed; the identifier of the NSAG associated with the network slice whose service request failed; the reason for the failure of the network slice whose service request failed; the slice type of the network slice whose service request failed; and the time when the network slice whose service request failed experienced a service request failure.

[0219] In addition, the above modules can also be used to support Figures 6 to 9 Other processes performed by the access network device in the illustrated embodiment. The beneficial effects are described above and will not be repeated here.

[0220] Figure 11 This is a schematic diagram of another communication device provided according to an embodiment of this application. The communication device includes a processor 1101, a communication interface 1102, and may further include a memory 1103 and a bus 1104. The processor 1101, communication interface 1102, and memory 1103 can be interconnected via the bus 1104. The bus 1104 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus 1104 can be divided into an address bus, a data bus, and a control bus, etc. For ease of illustration, Figure 11 The symbol is represented by only one line, but this does not mean that there is only one bus or one type of bus.

[0221] Processor 1101 may be a central processing unit (CPU), a network processor (NP), or a combination of a CPU and an NP. The processor may further include hardware chips. These hardware chips may be application-specific integrated circuits (ASICs), programmable logic devices (PLDs), or combinations thereof. The PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof. Memory 1103 may be volatile memory or non-volatile memory, or may include both. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), which is used as an external cache.

[0222] The processor 1101 is used to implement the data processing operation of the communication device, and the communication interface 1102 is used to implement the receiving and sending operations of the communication device.

[0223] When the communication device is a terminal device, the processor 1101 determines a network slice whose requested service has failed. The failed service request includes network slice service request failure, network slice-based Protocol Data Unit (PDU) session establishment request failure, or network slice-based PDU session activation failure. The failed network slice service request includes the network slice requested by the terminal device not being supported by the Tracking Area (TA) where the terminal device is located. The processor 1101 sends first information through the communication interface 1102. The first information includes information about the network slice whose requested service has failed. The first information includes one or more of the following: the identifier of the network slice whose requested service has failed; the identifier of the NSAG associated with the network slice whose requested service has failed; the reason for the failure of the network slice whose requested service has failed; the slice type of the network slice whose requested service has failed; and the time when the network slice whose requested service has failed experienced a service request failure.

[0224] In addition, the aforementioned components can also be used to support Figures 6 to 9 Other processes performed by the terminal device in the illustrated embodiment. The beneficial effects are described above and will not be repeated here.

[0225] When the communication device is an access network device, the processor 1101 determines that the terminal device's request for a service has failed. The service request failure includes network slice service request failure, PDU session establishment request failure based on the network slice, or PDU session user plane activation failure based on the network slice. The service request failure includes the network slice requested by the terminal device not being supported by the Tracking Area (TA) where the terminal device is located. The processor 1101 records second information, which includes information about the network slice whose service request failed. The second information includes one or more of the following: the identifier of the network slice whose service request failed; the identifier of the NSAG associated with the network slice whose service request failed; the reason for the failure of the network slice whose service request failed; the slice type of the network slice whose service request failed; and the time when the network slice whose service request failed experienced a service request failure.

[0226] In addition, the aforementioned components can also be used to support Figures 6 to 9 Other processes performed by the network device in the illustrated embodiment. The beneficial effects are described above and will not be repeated here.

[0227] Based on the same technical concept, embodiments of this application also provide a computer-readable storage medium storing computer-readable instructions that, when executed on a computer, cause the method described in any of the possible implementations described above to be executed.

[0228] This application provides a computer program product containing instructions that, when run on a computer, cause the above-described method embodiments to be executed.

[0229] This application provides a chip, including: a processor coupled to a memory for storing instructions, which, when executed by the processor, cause the chip to implement the method steps performed by any of the above-mentioned nodes.

[0230] In the description of the embodiments of this application, "and / or" describes the relationship between associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. "Multiple" in this application refers to two or more.

[0231] Furthermore, it should be understood that in the description of this application, terms such as "first" and "second" are used only for distinguishing purposes and should not be construed as indicating or implying relative importance, nor as indicating or implying order. References to "one embodiment" or "some embodiments" in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, phrases such as "in one embodiment," "in some embodiments," "in other embodiments," and "in still other embodiments" appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof all mean "including but not limited to," unless otherwise specifically emphasized.

[0232] The method steps in the embodiments of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Alternatively, the ASIC can reside in a base station or terminal. Of course, the processor and storage medium can also exist as discrete components in the base station or terminal.

[0233] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both types of storage media.

[0234] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0235] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers described above does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

Claims

1. A communication method, characterized in that, The method includes: The network slice for which the requested service failed is identified. The failure to request the service includes failure of the network slice service request, failure of the protocol data unit (PDU) session establishment request based on the network slice, or failure of the PDU session activation based on the network slice. The failure of the network slice service request includes the network slice requested by the terminal device not being supported by the tracking area (TA) where the terminal device is located. Send first information, the first information including information about the network slice where the requested service failed; The first information includes one or more of the following: The identifier of the network slice where the requested service failed; The identifier of the network slice access layer group (NSAG) associated with the network slice whose requested service failed; The reason for the failure of the network slice requested for the service; The slice type of the network slice where the requested service failed; The time when the network slice where the requested service failed occurred.

2. The method according to claim 1, characterized in that, The network slice that determines the failed service request includes: Based on the reason for the rejection of the rejected network slice, determine the network slice from which the requested service failed.

3. The method according to claim 1, characterized in that, The network slice that determines the failed service request includes: Based on the location information of the terminal device, and the first TA information and / or the second TA information, the network slice for which the requested service failed is determined. The first TA information includes one or more TA information supporting network slices partially allowed by the terminal device, and the second TA information includes one or more TA information supporting network slices partially rejected by the terminal device.

4. The method according to claim 3, characterized in that, The step of determining the network slice where the requested service failed based on the location information of the terminal device, and the first TA information and / or the second TA information, includes: The NAS of the terminal device determines the network slice where the requested service failed based on the location information of the terminal device, as well as the first TA information and / or the second TA information. Alternatively, the NAS of the terminal device sends the first TA information and / or the second TA information to the access layer AS of the terminal device, and the AS determines the network slice where the requested service failed based on the location information of the terminal device and the first TA information and / or the second TA information.

5. The method according to claim 1, characterized in that, The network slice that determines the failed service request includes: Based on the location information of the terminal device, as well as the first cell information and / or the second cell information, the network slice for which the requested service failed is determined. The first cell information includes one or more cell information where available resources exist for the network slice partially permitted by the terminal device, and the second cell information includes one or more cell information where available resources exist for the network slice permitted by the terminal device.

6. The method according to claim 5, characterized in that, The step of determining the network slice where the requested service failed based on the location information of the terminal device, as well as the information of the first cell and / or the information of the second cell, includes: The NAS of the terminal device obtains the location information of the terminal device sent by the AS of the terminal device; The NAS determines the network slice where the requested service failed based on the location information, as well as the first cell information and / or the second cell information.

7. The method according to any one of claims 1-6, characterized in that, Before sending the first message, the method further includes: Receive first indication information, the first indication information being used to indicate one or more of the following: information contained in the first information, a first triggering condition for recording the network slice where the requested service failed, and a second triggering condition for sending the first failure report; The sending of the first information includes: The first information is sent according to the first configuration information.

8. The method according to any one of claims 1-6, characterized in that, The sending of the first information includes: The first information is sent according to the second indication information, wherein the second indication information is used to indicate one or more of the following: information contained in the first information report, a first trigger condition for recording the network slice where the requested service failed, and a second trigger condition for sending the first failure report.

9. The method according to claim 7 or 8, characterized in that, The first triggering condition includes one or more of the following conditions: The preset trigger event occurs; Identify a network slice where business requests have failed. The number of network slices whose requested services failed has reached a preset number; The service types of the network slices whose requested services failed include preset service types; The first network slice experienced a service request failure. A service request failed due to a network slice associated with the first NSAG. The priority of the NSAG associated with the network slice whose request failed meets the preset priority.

10. A communication method, characterized in that, The method includes: The network slice for which the terminal device requested services failed is identified. The failure to request services includes failure to request network slice services, failure to establish a PDU session based on the network slice, or failure to activate the user plane of a PDU session based on the network slice. The failure to request services includes the fact that the network slice requested by the terminal device is not supported by the Tracking Area (TA) where the terminal device is located. Record the second information, which includes information about the network slice where the requested service failed; The second information includes one or more of the following: The identifier of the network slice where the requested service failed; The identifier of the network slice access layer group (NSAG) associated with the network slice whose requested service failed; The reason for the failure of the network slice requested for the service; The slice type of the network slice where the requested service failed; The time when the network slice where the requested service failed occurred.

11. The method according to claim 10, characterized in that, The determination of the network slice where the terminal device's service request failed includes: Based on the network slice requested by the terminal device and the network slices supported by the network device, determine the network slice where the terminal device's service request failed. Alternatively, based on the network slice requested by the terminal device and the resource configuration information for each network slice supported by the network device, the network slice where the terminal device's service request failed can be determined. Alternatively, based on the network slice requested by the terminal device, the network slices supported by the network device, and the resource configuration information for each network slice supported by the network device, the network slice where the terminal device's service request failed can be determined.

12. The method according to claim 11, characterized in that, The method further includes: Receive network slice indication information sent by the terminal device in response to the request; Alternatively, receive network slice indication information from the core network device in response to the request.

13. The method according to claim 10, characterized in that, The determination of the network slice where the terminal device's service request failed includes: Based on the network slices partially allowed by the terminal device and the network slices supported by the network device, determine the network slice where the terminal device failed to request the service; Alternatively, based on the network slices partially allowed by the terminal device and / or the allowed network slices, and the resource configuration information for each network slice supported by the network device, the network slice where the terminal device's service request failed can be determined. Alternatively, based on the network slices allowed by the terminal device and / or the network slices supported by the network device, and the resource configuration information for each network slice supported by the network device.

14. A communication device, characterized in that, include: A processor coupled to a memory for storing programs or instructions that, when executed by the processor, cause the apparatus to perform the method as described in any one of claims 1-9.

15. A communication device, characterized in that, include: A processor coupled to a memory for storing programs or instructions that, when executed by the processor, cause the apparatus to perform the method as described in any one of claims 10-13.

16. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1-13.

17. A computer program product containing instructions, characterized in that, When the instructions are executed on a computer, the computer causes the computer to perform the method as described in any one of claims 1-13.

Images