Information processing method and apparatus, and storage medium

Abstract

The present disclosure relates to the technical field of communications, and provides an information processing method and apparatus, and a storage medium. The information processing method is applied to a terminal device, and comprises: acquiring slice-related information; and sending the slice-related information to an access network device, the slice-related information indicating the performance of a network slice, or the slice-related information being used for deployment optimization of a network slice. The present disclosure solves the problem in some scenarios where network slice overload and similar factors affect network quality.

Description

Information processing method, device and storage medium

[0001] This disclosure claims priority to the Chinese patent application filed with the China Patent Office on February 6, 2024, with application number 202410169196.0 and application name “Information Processing Method, Device and Storage Medium,” the entire contents of which are incorporated by reference into this disclosure. Technical Field

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

[0003] Rel-15 introduces the concept of network slicing, which can be implemented by scheduling and providing different configurations to meet different needs. While the network can support hundreds of network slices, end devices can only support eight at a time. In some scenarios, issues such as excessive network slice load can affect network quality. Summary of the Invention

[0004] The present disclosure provides an information processing method, device and storage medium, which solve the problem of network quality being affected by network load exceeding the limit in some scenarios.

[0005] In a first aspect, an embodiment of the present disclosure provides an information processing method, applied to a terminal device, the method comprising:

[0006] Get slice related information;

[0007] Slice-related information is sent to the access network device, where the slice-related information indicates the performance of the network slice, or is used for deployment optimization of the network slice.

[0008] In some embodiments, the slice-related information includes any one or more of the following information:

[0009] Absolute time information when the access network device sends configuration information;

[0010] Relative time relative to the time of receiving the configuration information;

[0011] Rejected network slices;

[0012] The data radio bearer corresponding to the rejected network slice;

[0013] Number of times network slices were rejected;

[0014] Cells that reject network slicing;

[0015] Reasons for rejecting network slicing;

[0016] The released protocol data unit PDU session;

[0017] Number of times a PDU session is released;

[0018] The network slice corresponding to the released PDU session;

[0019] The number of network slices corresponding to the released PDU session;

[0020] Release the cell ID of the PDU session corresponding to the network slice;

[0021] Release the tracking area code TAC of the cell corresponding to the PDU session of the network slice;

[0022] The cell radio network temporary identifier C-RNTI of the terminal device.

[0023] In some implementations, sending slice-related information to an access network device includes:

[0024] Send slice-related information to the access network device in the form of a single report or a report list.

[0025] In some embodiments, obtaining slice-related information occurs by performing at least one of the following processes:

[0026] Register a cell, switch a cell, add a secondary cell, change a secondary cell, establish a PDU session, and modify a PDU session.

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

[0028] Receive configuration information, where the configuration information is used to instruct the collection of slice-related information.

[0029] In some implementations, the configuration information is carried in a radio resource control (RRC) reconfiguration message and / or an RRC recovery message.

[0030] In some embodiments, the configuration information includes one or more of the following information:

[0031] The time when the terminal device collects slice-related information;

[0032] Absolute time information when the access network device sends configuration information;

[0033] The data radio bearer (DRB) list to be collected by the terminal device;

[0034] The list of network slices to be collected by the terminal device;

[0035] The area scope collected by the terminal device;

[0036] List of public land mobile networks (PLMNs) or independent non-public networks (SNPNs) that are allowed to report slice related information;

[0037] The configuration type of the terminal device recording slice-related information includes event triggering, which includes changes in the cell where the terminal device is located; when the terminal device is registering a cell, a network slice is rejected; when the terminal device is switching cells, adding secondary cells, or changing secondary cells, a PDU session corresponding to a slice is released;

[0038] The triggering conditions for the terminal device to report slice-related information include the threshold for the number of rejected network slices and the threshold for the number of released network slice-related PDU sessions.

[0039] In some implementations, if the configuration information includes a triggering condition for the terminal device to report slice related information, sending the slice related information to the access network device includes:

[0040] When the triggering conditions for the terminal device to report slice related information are met, the slice related information is sent to the access network device.

[0041] In some implementations, if the configuration information includes the time when the terminal device collects slice-related information, the method further includes:

[0042] The time for the terminal device to collect slice-related information is set to the value of the timer for collecting slice-related information, and the timer is started.

[0043] In some embodiments, further comprising:

[0044] When the timer expires, the configuration information is released, and the slice related information collected during the validity period of the timer is deleted after the preset length of time;

[0045] Alternatively, when the reserved memory resources are full, the configuration information is released, and the slice related information collected within the effective time of the timer is deleted after a preset time.

[0046] In some embodiments, further comprising:

[0047] A first message is sent to the access network device, where the first message indicates that slice-related information is available.

[0048] In some embodiments, the first information may be carried in an RRC creation complete message, an RRC recovery complete message, an RRC reconfiguration complete message, or an RRC reestablishment complete message.

[0049] In a second aspect, an embodiment of the present disclosure provides an information processing method, applied to an access network device, comprising:

[0050] Obtain slice-related information, including slice-related information reported by terminal devices;

[0051] Slice-related information is sent to the operation, maintenance and management OAM and / or core network equipment, where the slice-related information indicates the performance of the network slice, or is used for deployment optimization of the network slice.

[0052] In some embodiments, the slice-related information includes any one or more of the following:

[0053] Absolute time information when the access network device sends configuration information;

[0054] Relative time relative to the time of receiving the configuration information;

[0055] Rejected network slices;

[0056] The data radio bearer corresponding to the rejected network slice;

[0057] Number of times network slices were rejected;

[0058] Cells that reject network slicing;

[0059] Reasons for rejecting network slicing;

[0060] The released protocol data unit PDU session;

[0061] Number of times a PDU session is released;

[0062] The network slice corresponding to the released PDU session;

[0063] The number of network slices corresponding to the released PDU session;

[0064] Release the cell ID of the PDU session corresponding to the network slice;

[0065] Release the tracking area code TAC of the cell corresponding to the PDU session of the network slice;

[0066] The cell radio network temporary identifier C-RNTI of the terminal device.

[0067] In some embodiments, slice-related information is sent in the form of a single report or a list of reports.

[0068] In some embodiments, obtaining slice-related information occurs by performing at least one of the following processes:

[0069] Register a cell, switch a cell, add a secondary cell, change a secondary cell, establish a PDU session, and modify a PDU session.

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

[0071] Indicates configuration information, which is used to instruct the collection of slice-related information.

[0072] In some implementations, the configuration information is carried in a radio resource control (RRC) reconfiguration message and / or an RRC recovery message.

[0073] In some embodiments, the configuration information includes one or more of the following information:

[0074] The time when the terminal device collects slice-related information;

[0075] Absolute time information when the access network device sends configuration information;

[0076] The data radio bearer (DRB) list to be collected by the terminal device;

[0077] The list of network slices to be collected by the terminal device;

[0078] The area scope collected by the terminal device;

[0079] List of public land mobile networks (PLMNs) or independent non-public networks (SNPNs) that are allowed to report slice related information;

[0080] The configuration type of the terminal device recording slice-related information includes event triggering, which includes changes in the cell where the terminal device is located; when the terminal device is registering a cell, a network slice is rejected; when the terminal device is switching cells, adding secondary cells, or changing secondary cells, a PDU session corresponding to a slice is released;

[0081] The triggering conditions for the terminal device to report slice-related information include the threshold for the number of rejected network slices and the threshold for the number of released network slice-related PDU sessions.

[0082] In some embodiments, if the configuration information includes a triggering condition for a terminal device to report slice-related information, the slice-related information is reported when the triggering condition for the terminal device to report slice-related information is met.

[0083] In some embodiments, if the configuration information includes the time when the terminal device collects slice-related information, the slice-related information includes slice-related information collected after the timer for collecting slice-related information is started.

[0084] In some embodiments, further comprising:

[0085] First information is obtained, where the first information indicates that slice-related information is available.

[0086] In some embodiments, the first information may be carried in an RRC creation complete message, an RRC recovery complete message, an RRC reconfiguration complete message, or an RRC reestablishment complete message.

[0087] In some implementations, the slice-related information also includes slice-related information collected by the access network device itself.

[0088] In some implementations, the slice-related information collected by the access network device itself includes at least one or more of the following:

[0089] The network slice corresponding to the released PDU session;

[0090] The number of network slices corresponding to the released PDU session;

[0091] Released PDU session;

[0092] The number of released PDU sessions;

[0093] Release the cell ID of the PDU session corresponding to the network slice;

[0094] The reason why the PDU session corresponding to the network slice is released;

[0095] Tracking area code TAC corresponding to the cell.

[0096] In some implementations, the slice-related information collected by the access network device itself also includes:

[0097] The number of terminal devices activated on each network slice corresponding to the cell within a preset time period, and / or the duration of the PDU session established by the terminal device on each network slice.

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

[0099] Get the average duration of PDU sessions established by terminal devices on each network slice.

[0100] In some embodiments, the average duration is determined based on the sum of the durations of the PDU sessions corresponding to the network slice established by the terminal devices activated under the corresponding network slice and the number of terminal devices activated under the network slice.

[0101] In some implementations, sending slice-related information to an OAM or core network device includes:

[0102] According to the cell radio network temporary identifier C-RNTI, cell ID and time information of the terminal device, the slice related information collected by the terminal device is correlated and analyzed with the slice related information collected by itself to obtain a correlation analysis result;

[0103] Send correlation analysis results to OAM or core network equipment.

[0104] In a third aspect, an embodiment of the present disclosure provides a terminal device, including:

[0105] memory for storing computer programs;

[0106] a transceiver for transmitting and receiving data under the control of the processor;

[0107] A processor that reads a computer program from memory and performs the following operations:

[0108] Get slice related information;

[0109] Slice-related information is sent to the access network device, where the slice-related information indicates the performance of the network slice, or is used for deployment optimization of the network slice.

[0110] In some embodiments, the slice-related information includes any one or more of the following information:

[0111] Absolute time information when the access network device sends configuration information;

[0112] Relative time relative to the time of receiving the configuration information;

[0113] Rejected network slices;

[0114] The data radio bearer corresponding to the rejected network slice;

[0115] Number of times network slices were rejected;

[0116] Cells that reject network slicing;

[0117] Reasons for rejecting network slicing;

[0118] The released protocol data unit PDU session;

[0119] Number of times a PDU session is released;

[0120] The network slice corresponding to the released PDU session;

[0121] The number of network slices corresponding to the released PDU session;

[0122] Release the cell ID of the PDU session corresponding to the network slice;

[0123] Release the tracking area code TAC of the cell corresponding to the PDU session of the network slice;

[0124] The cell radio network temporary identifier C-RNTI of the terminal device.

[0125] In some embodiments, the processor is specifically configured to:

[0126] Send slice-related information to the access network device in the form of a single report or a report list.

[0127] In some embodiments, obtaining slice-related information occurs by performing at least one of the following processes:

[0128] Register a cell, switch a cell, add a secondary cell, change a secondary cell, establish a PDU session, and modify a PDU session.

[0129] In some embodiments, the processor is further configured to:

[0130] Receive configuration information, where the configuration information is used to instruct the collection of slice-related information.

[0131] In some implementations, the configuration information is carried in a radio resource control (RRC) reconfiguration message and / or an RRC recovery message.

[0132] In some embodiments, the configuration information includes one or more of the following information:

[0133] The time when the terminal device collects slice-related information;

[0134] Absolute time information when the access network device sends configuration information;

[0135] The data radio bearer (DRB) list to be collected by the terminal device;

[0136] The list of network slices to be collected by the terminal device;

[0137] The area scope collected by the terminal device;

[0138] List of public land mobile networks (PLMNs) or independent non-public networks (SNPNs) that are allowed to report slice related information;

[0139] The configuration type of the terminal device recording slice-related information includes event triggering, which includes changes in the cell where the terminal device is located; when the terminal device is registering a cell, a network slice is rejected; when the terminal device is switching cells, adding secondary cells, or changing secondary cells, a PDU session corresponding to a slice is released;

[0140] The triggering conditions for the terminal device to report slice-related information include the threshold for the number of rejected network slices and the threshold for the number of released network slice-related PDU sessions.

[0141] In some implementations, if the configuration information includes a triggering condition for the terminal device to report slice related information, the processor is specifically configured to:

[0142] When the triggering conditions for the terminal device to report slice related information are met, the slice related information is sent to the access network device.

[0143] In some implementations, if the configuration information includes the time when the terminal device collects slice-related information, the processor is further configured to:

[0144] The time for the terminal device to collect slice-related information is set to the value of the timer for collecting slice-related information, and the timer is started.

[0145] In some embodiments, the processor is further configured to:

[0146] When the timer expires, the configuration information is released, and the slice related information collected during the validity period of the timer is deleted after the preset length of time;

[0147] Alternatively, when the reserved memory resources are full, the configuration information is released, and the slice related information collected within the effective time of the timer is deleted after a preset time.

[0148] In some embodiments, the processor is further configured to:

[0149] A first message is sent to the access network device, where the first message indicates that slice-related information is available.

[0150] In some embodiments, the first information may be carried in an RRC creation complete message, an RRC recovery complete message, an RRC reconfiguration complete message, or an RRC reestablishment complete message.

[0151] In a fourth aspect, an embodiment of the present disclosure provides an access network device, including:

[0152] memory for storing computer programs;

[0153] a transceiver for transmitting and receiving data under the control of the processor;

[0154] A processor that reads a computer program from memory and performs the following operations:

[0155] Obtain slice-related information, including slice-related information reported by terminal devices;

[0156] Send slice-related information to operation, maintenance and management (OAM) and / or core network equipment.

[0157] In some embodiments, the slice-related information includes any one or more of the following:

[0158] Absolute time information when the access network device sends configuration information;

[0159] Relative time relative to the time of receiving the configuration information;

[0160] Rejected network slices;

[0161] The data radio bearer corresponding to the rejected network slice;

[0162] Number of times network slices were rejected;

[0163] Cells that reject network slicing;

[0164] Reasons for rejecting network slicing;

[0165] The released protocol data unit PDU session;

[0166] Number of times a PDU session is released;

[0167] The network slice corresponding to the released PDU session;

[0168] The number of network slices corresponding to the released PDU session;

[0169] Release the cell ID of the PDU session corresponding to the network slice;

[0170] Release the tracking area code TAC of the cell corresponding to the PDU session of the network slice;

[0171] The cell radio network temporary identifier C-RNTI of the terminal device.

[0172] In some embodiments, slice-related information is sent in the form of a single report or a list of reports.

[0173] In some embodiments, obtaining slice-related information occurs by performing at least one of the following processes:

[0174] Register a cell, switch a cell, add a secondary cell, change a secondary cell, establish a PDU session, and modify a PDU session.

[0175] In some embodiments, the processor is further configured to:

[0176] Indicates configuration information, which is used to instruct the collection of slice-related information.

[0177] In some implementations, the configuration information is carried in a radio resource control (RRC) reconfiguration message and / or an RRC recovery message.

[0178] In some embodiments, the configuration information includes one or more of the following information:

[0179] The time when the terminal device collects slice-related information;

[0180] Absolute time information when the access network device sends configuration information;

[0181] The data radio bearer (DRB) list to be collected by the terminal device;

[0182] The list of network slices to be collected by the terminal device;

[0183] The area scope collected by the terminal device;

[0184] List of public land mobile networks (PLMNs) or independent non-public networks (SNPNs) that are allowed to report slice related information;

[0185] The configuration type of the terminal device recording slice-related information includes event triggering, which includes changes in the cell where the terminal device is located; when the terminal device is registering a cell, a network slice is rejected; when the terminal device is switching cells, adding secondary cells, or changing secondary cells, a PDU session corresponding to a slice is released;

[0186] The triggering conditions for the terminal device to report slice-related information include the threshold for the number of rejected network slices and the threshold for the number of released network slice-related PDU sessions.

[0187] In some embodiments, if the configuration information includes a triggering condition for a terminal device to report slice-related information, the slice-related information is reported when the triggering condition for the terminal device to report slice-related information is met.

[0188] In some embodiments, if the configuration information includes the time when the terminal device collects slice-related information, the slice-related information includes slice-related information collected after the timer for collecting slice-related information is started.

[0189] In some embodiments, the processor is further configured to:

[0190] First information is obtained, where the first information indicates that slice-related information is available.

[0191] In some embodiments, the first information may be carried in an RRC creation complete message, an RRC recovery complete message, an RRC reconfiguration complete message, or an RRC reestablishment complete message.

[0192] In some implementations, the slice-related information also includes slice-related information collected by the access network device itself.

[0193] In some implementations, the slice-related information collected by the access network device itself includes at least one or more of the following:

[0194] The network slice corresponding to the released PDU session;

[0195] The number of network slices corresponding to the released PDU session;

[0196] Released PDU session;

[0197] The number of released PDU sessions;

[0198] Release the cell ID of the PDU session corresponding to the network slice;

[0199] The reason why the PDU session corresponding to the network slice is released;

[0200] Tracking area code TAC corresponding to the cell.

[0201] In some implementations, the slice-related information collected by the access network device itself also includes:

[0202] The number of terminal devices activated on each network slice corresponding to the cell within a preset time period, and / or the duration of the PDU session established by the terminal device on each network slice.

[0203] In some embodiments, the processor is further configured to:

[0204] Get the average duration of PDU sessions established by terminal devices on each network slice.

[0205] In some embodiments, the average duration is determined based on the sum of the durations of the PDU sessions corresponding to the network slice established by the terminal devices activated under the corresponding network slice and the number of terminal devices activated under the network slice.

[0206] In some embodiments, the processor is specifically configured to:

[0207] According to the cell radio network temporary identifier C-RNTI, cell ID and time information of the terminal device, the slice related information collected by the terminal device is correlated and analyzed with the slice related information collected by itself to obtain a correlation analysis result;

[0208] Send correlation analysis results to OAM or core network equipment.

[0209] In a fifth aspect, an embodiment of the present disclosure provides a processor-readable storage medium, which stores a computer program. The computer program is used to enable the processor to execute the information processing method of the first aspect, or to execute the information processing method of the second aspect.

[0210] In summary, the embodiments of the present disclosure provide an information processing method, apparatus, and storage medium. The information processing method includes: obtaining slice-related information, sending the slice-related information to an access network device, the slice-related information indicating the performance of the network slice, or the slice-related information being used for optimizing the deployment of the network slice. In the embodiments of the present disclosure, since the slice-related information is collected, the deployment of the network slice can be optimized based on the slice-related information, thereby solving problems that affect network quality, such as excessive load on the network slice, base stations not supporting some network slices, or being unable to allocate resources to some network slices, thereby improving network quality.

[0211] It should be understood that the contents described in the above summary of the invention are not intended to limit the key or important features of the embodiments of the present disclosure, nor are they intended to limit the scope of the present disclosure. Other features of the present disclosure will become easier to understand through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0212] In order to more clearly illustrate the technical solutions in the present disclosure or the prior art, a brief introduction will be given below to the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0213] FIG1 is a schematic diagram of an application scenario provided by an embodiment of the present disclosure;

[0214] FIG2 is a flow chart of an information processing method provided by an embodiment of the present disclosure;

[0215] FIG3 is a flow chart of an information processing method provided by another embodiment of the present disclosure;

[0216] FIG4 is a flow chart of an information processing method provided in yet another embodiment of the present disclosure;

[0217] FIG5 is a schematic diagram of an information processing device provided by an embodiment of the present disclosure;

[0218] FIG6 is a schematic diagram of an information processing device provided by another embodiment of the present disclosure;

[0219] FIG7 is a schematic diagram of a terminal device provided by an embodiment of the present disclosure;

[0220] FIG8 is a schematic diagram of an access side device provided by an embodiment of the present disclosure. DETAILED DESCRIPTION

[0221] In the embodiments of the present disclosure, the term "and / or" describes the association relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally indicates that the associated objects are in an "or" relationship.

[0222] In the embodiments of the present disclosure, the term "plurality" refers to two or more than two, and other quantifiers are similar thereto.

[0223] The following will be combined with the accompanying drawings in the embodiments of the present disclosure to clearly and completely describe the technical solutions in the embodiments of the present disclosure. Obviously, the embodiments described are only part of the embodiments of the present disclosure and not all of the embodiments. Based on the embodiments of the present disclosure, all other embodiments obtained by ordinary technicians in this field without making any creative efforts shall fall within the scope of protection of the present disclosure.

[0224] First, the terms involved in this disclosure are explained:

[0225] Base station: A public mobile communication base station is a form of radio station, which refers to a radio transceiver station that transmits information between mobile phone terminals through a mobile communication exchange center within a certain radio coverage area.

[0226] Cell: An area providing wireless communication services to users. It is the basic unit of a wireless network. A base station can support multiple cells.

[0227] Primary cell: a cell where the UE establishes an initial connection, or a cell where the UE reestablishes a Radio Resource Control (RRC) connection, or a primary cell designated during a handover.

[0228] Secondary Cell: Secondary Cell, referred to as SCell, is added during RRC reconfiguration to provide additional radio resources. There is no RRC communication between the SCell and the UE.

[0229] Next, the application scenario of the embodiment of the present disclosure is described with reference to Figure 1. Figure 1 is a schematic diagram of the application scenario provided by the embodiment of the present disclosure. As shown in Figure 1, the scenario includes a terminal device 101 and an access network device 102. The access network device is, for example, the aforementioned base station (gNB). The terminal device is, for example, a user equipment (UE).

[0230] It should be noted that FIG1 is schematic, and the above scenario may also include other access network devices, such as wireless repeater devices and wireless backhaul devices, which are not shown in FIG1. ​​The embodiments of the present disclosure illustrate the above scenario with one UE and one access network device as an example, but are not limited to this.

[0231] In different systems, the names of the above-mentioned UEs may also be different. For example, the above-mentioned UEs may also be wired terminal devices or wireless terminal devices. Among them, the wireless terminal devices can communicate with one or more core networks (CNs) through the wireless access network. The network elements included in the core network mainly include the Access and Mobility Management Function (AMF). The AMF is used to perform registration, connection, reachability, and mobility management. It is the access point for the terminal device and the wireless core network control plane. Specifically, AMF supports the following network slicing, access authentication of wireless terminal devices, cell management of wireless terminal devices, access authorization, and selection of the Session Management Function (SMF).

[0232] A wireless terminal device may be a mobile terminal device, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal device. For example, it may be a portable, pocket-sized, handheld, computer-built-in, or vehicle-mounted mobile device that exchanges voice and / or data with a wireless access network. For example, a Personal Communication Service (PCS) phone, a cordless phone, a Session Initiated Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), and the like. A wireless terminal may also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, a remote terminal, an access terminal, a user terminal, a user agent, or a user device, and is not limited in the embodiments of the present disclosure.

[0233] Among them, the above-mentioned access network device can be a master node (Master Node, MN), specifically a base station (Base Transceiver Station, BTS) and / or base station controller in Global System of Mobile communication (GSM) or Code Division Multiple Access (CDMA), or a base station (NodeB, NB) and / or radio network controller (Radio Network Controller, RNC) in Wideband Code Division Multiple Access (WCDMA), or an evolved base station (Evolutional Node B, 4G base station or eNodeB) in Long Term Evolution (LTE), or a relay station or access point, or a base station (5G base station) in a future 5G network, etc. The embodiments of the present disclosure are not limited here.

[0234] Rel-15 introduces the concept of network slicing, a new network architecture that provides multiple logical networks on a shared network infrastructure, each serving a specific business type or industry user. Simply put, it divides a physical network into multiple virtual end-to-end networks. Each virtual network, including its devices, access, transport, and core networks, is logically independent. A failure in any one virtual network will not affect the others. Each access network device supports a specific network slice, and the access network device allocates resources to the supported network slices.

[0235] The network can implement network slicing by scheduling and providing different configurations, and different network slices can correspond to different needs. The services of different network slices are processed through different protocol data unit (PDU) sessions. That is to say, one network slice can only correspond to one PDU session. Each network slice also has S-NSSAI as an identifier. Each S-NSSAI can be composed of two parts, namely mandatory SST (Slice / Service Type) and optional SD (Slice Differentiator). Among them, mandatory SST (Slice / Service Type) is used to identify the type of network slice, and optional SD (Slice Differentiator) is used to further distinguish network slices of the same type.

[0236] The network can support hundreds of network slices, but terminal devices can only support eight network slices at a time. In some scenarios, there are problems such as network slice load exceeding the limit, base stations not supporting some network slices, or being unable to allocate resources to some network slices, which affect network quality.

[0237] Based on this, the present disclosure provides an information processing method, apparatus, and storage medium. The information processing method is applied to a terminal device, including: obtaining slice-related information, sending the slice-related information to an access network device, wherein the slice-related information indicates the performance of the network slice, or the slice-related information is used for optimizing the deployment of the network slice. In an embodiment of the present disclosure, since the slice-related information is collected, the deployment of the network slice can be optimized based on the slice-related information, thereby solving problems that affect network quality, such as excessive load on the network slice, base stations not supporting some network slices, or being unable to allocate resources to some network slices, thereby improving network quality.

[0238] The following specific embodiments are used to describe in detail the technical solutions of the embodiments of the present disclosure and how the technical solutions of the present disclosure solve the above technical problems. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments.

[0239] It should be understood that the technical solutions provided in the embodiments of the present disclosure can be applicable to a variety of systems, such as 5G systems. For example, applicable systems may be global system of mobile communication (GSM) systems, code division multiple access (CDMA) systems, wideband code division multiple access (WCDMA) general packet radio service (GPRS) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, long term evolution advanced (LTE-A) systems, universal mobile telecommunication systems (UMTS), worldwide interoperability for microwave access (WiMAX) systems, 5G new air interface (NR) systems, etc. These various systems include terminal devices and access side devices.

[0240] It should be understood that the method and device provided in the embodiments of the present disclosure are based on the same application concept. Since the principles of solving problems by the method and device are similar, the implementation of the device and method can refer to each other, and the repeated parts will not be repeated.

[0241] 2 , one embodiment of the present disclosure provides an information processing method, which is applied to the terminal device described above. For ease of description, the terminal device is described below as UE.

[0242] The information processing method includes:

[0243] S201, obtaining slice related information.

[0244] The slice related information can be obtained when at least one process such as UE registering a cell, switching a cell, establishing a PDU session, adding a secondary cell, etc. occurs, for example.

[0245] The slice-related information includes, for example, the rejected network slice, the data radio bearer corresponding to the rejected network slice, the number of times the network slice is rejected, the cell that rejects the network slice, the reason for rejecting the network slice, the released protocol data unit PDU session, the number of released PDU sessions, the network slice corresponding to the released PDU session, the number of network slices corresponding to the released PDU session, the cell identifier of the PDU session corresponding to the released network slice, etc. The more quantity and types of slice-related information, the more conducive to the optimization of network quality.

[0246] Alternatively, the UE may first receive configuration information indicated by the access network device, and then obtain slice-related information based on the configuration information. The configuration information may include, for example, slice-related information that the UE needs to obtain, the time to obtain the slice-related information, and the reporting conditions for the slice-related information.

[0247] S202: Send the slice-related information to the access network device.

[0248] The slice-related information may be sent to the access network device in the form of a single report or a report list, or may be sent to the access network device in other forms, which is not limited in this embodiment.

[0249] Referring to the above description of the slice-related information, it can be seen that the slice-related information indicates the performance of the network slice, or the slice-related information is used for deployment optimization of the network slice. The deployment optimization of the network slice is, for example, optimizing the network slice information corresponding to the cell, or optimizing the deployment of the cell, the deployment of the network slice, etc. The specific method of deployment optimization can be selected according to actual needs, and this embodiment does not limit it. The purpose of network slicing deployment optimization is to solve problems that affect network quality, such as excessive load on the network slice, base stations not supporting some network slices, or being unable to allocate resources for some network slices.

[0250] In some embodiments, OAM and the core network can collect statistics on relevant information of a certain network slice and monitor the certain network slice based on the network slice identifier S-NSSAI to optimize the deployment of the certain network slice.

[0251] In summary, this embodiment provides an information processing method, including: obtaining slice-related information, and sending the slice-related information to an access network device, where the slice-related information indicates the performance of the network slice, or the slice-related information is used for optimizing the deployment of the network slice. In the embodiments of the present disclosure, since the slice-related information is collected, the deployment of the network slice can be optimized based on the slice-related information, thereby resolving issues that affect network quality, such as excessive load on the network slice, base stations not supporting some network slices, or being unable to allocate resources to some network slices, thereby improving network quality.

[0252] In some embodiments, step S210 occurs during at least one of the following processes:

[0253] Process 1: Registering a cell. This includes registering a cell and updating a cell.

[0254] The registered cells include: initially registered cells, cells registered based on mobility, or cells registered periodically.

[0255] Among them, the UE triggers a cell registration request when registering a cell, and carries the information of the requested network slice in the cell registration request. When the access network device determines that the cell does not support the requested network slice or only supports part of the requested network slice, the access network device can feedback the allowed network slices and rejected network slices in the subsequent feedback information.

[0256] Among them, the UE triggers an update request when updating the cell, and carries the information of the network slice requested to be updated in the update request. Similarly, the access network device feeds back the allowed network slices and rejected network slices in the subsequent feedback information.

[0257] Process 2: Cell handover, including normal cell handover, conditional handover (CHO), and dual-active protocol stack (DAPS) cell handover.

[0258] In the case of CHO cell switching, a group of potential target cells is pre-set for the UE, and a cell switching command is stored in the UE. When specific conditions are met, the cell switching command is executed to complete the cell switching.

[0259] Among them, DAPS switching cell can be defined as the switching cell process of maintaining the connection of the source access network device (source gNB, i.e. source base station) after receiving the RRC message (switching cell command) to switch the cell until successfully randomly accessing the target access network device (target gNB, i.e. target base station) and releasing the source cell.

[0260] For switching cells based on NG-based slices, the AMF sends a switching cell request to the target base station (which can be understood as an access network device), including the requested PDU session and the corresponding network slice information. The target base station feeds back to the UE the accepted PDU sessions and rejected PDU sessions, as well as the reason for rejecting the PDU session. The reason may be that the target base station cannot allocate resources to the slice, or the target base station does not support the slice.

[0261] For the switching cell of Xn-based slices, the source base station sends a switching cell request to the target base station, including the requested PDU session and the corresponding slice list. The target base station feeds back the switching cell request confirmation information, including the received and rejected PDU sessions, and the reason for the rejected PDU session. It may be that the target base station cannot allocate resources to the slice, or the target base station does not support the slice.

[0262] Process 3: Adding a secondary cell. This includes normal secondary cell addition and conditional secondary cell addition (CPA). Conditional secondary cell addition is the process where the UE spontaneously adds a PScell.

[0263] Process 4: Changing the secondary cell. This is also known as Conditional PScell ​​Change (CPC). This is the process where the UE spontaneously changes the PScell.

[0264] Process 5: Establishing a PDU Session. A PDU session is the communication process between a UE and an access network device. Once a PDU session is established, a data transmission channel is established between the UE and the access network device. In a 5G network, a PDU session can only be initiated by the UE.

[0265] Process 6: Modify PDU Session: A PDU session modification action occurs when one or more Quality of Service (QoS) parameters between the UE and the access network device change.

[0266] As described above, the UE may start collecting information related to the slice as soon as it starts executing any one of processes 1 to 6. The above 6 processes may be expanded or other processes may be added according to actual needs, which are not limited in this embodiment.

[0267] When the UE performs the initial cell registration, mobility-based cell registration, or periodic cell registration (process 1) in process 1, it sends a cell registration request message to the AMF, which includes the information of the requested network slice. The AMF feeds back a cell registration acceptance message or a cell registration rejection message, which includes the allowed network slices, and the cell registration rejection message includes the rejected network slices and the reasons for rejecting the network slices. The cell registration acceptance message or cell registration rejection message fed back by the AMF is a NAS (Non access stratum) message, which is transparently transmitted through the access network device, but the access network device cannot parse it, so the UE needs to report the statistics to the access network device.

[0268] When the UE executes any one of processes 2 to 6, if the target cell does not support the network slice corresponding to the PDU session, the unsupported PDU session is released.

[0269] In some embodiments, the slice-related information includes any one or more of the following information:

[0270] 1) Absolute time information of the access network device sending the configuration information. This refers to the absolute time information of the access network device sending the configuration information. The configuration information is sent by the access network device to the UE and is used to instruct the collection of slice-related information.

[0271] 2) Relative time relative to the time of receiving the configuration information. This refers to the relative time between the first time and the second time. The first time refers to the time when the collection of slice-related information is started in any of the above processes 1 to 6. The second time refers to the time when the configuration information is received.

[0272] 3) Rejected network slices. This refers to the network slices or rejected network slice lists that were rejected during at least one of the above processes.

[0273] 4) The data radio bearer (DRB) corresponding to the rejected network slice.

[0274] 5) Number of times the network slice is rejected. This refers to the number of times each network slice in the list of network slices to be collected by the terminal device is rejected.

[0275] 6) Cells that reject network slices. This refers to the cells corresponding to each rejected network slice in the list of network slices to be collected by the terminal device.

[0276] 7) Reasons for rejecting the network slice. Reasons include unsupported network slicing, network slice overload, or other reasons.

[0277] 8) Released protocol data unit (PDU) session.

[0278] 9) Number of released PDU sessions: Refers to the number of released PDU sessions.

[0279] 10) The network slice corresponding to the released PDU session. As described above, one PDU session corresponds to one network slice. Here, one released PDU session corresponds to one network slice. Multiple released PDU sessions correspond to multiple network slices.

[0280] 11) The number of network slices corresponding to the released PDU session. It should be noted that the release of the PDU session also means that the network slice corresponding to the PDU session is rejected. The number of network slices corresponding to the released PDU session can also be understood as the number of times the network slice corresponding to the released PDU session is rejected.

[0281] 12) Release the cell identifier (Identity Document, abbreviated as ID) of the PDU session corresponding to the network slice. The cell ID is allocated to the cell by the access network device. The cell in the cell registration process refers to the cell ID where the registration cell request or registration cell update occurs. The cell switching process refers to switching to the ID of the target cell. Adding a secondary cell refers to adding a secondary cell ID. Changing a secondary cell refers to changing to the ID of the target secondary cell. The frequency and other indication IDs can be added through the Common Gateway Interface (CGI) or the local bus (Peripheral Component Interconnect, PCI) of a personal computer.

[0282] 13) Release the tracking area code (TAC) corresponding to the cell of the PDU session corresponding to the network slice. TAC is a dynamic identifier assigned to the UE by the access side device.

[0283] 14) UE's Cell-Radio Network Temporary Identifier (C-RNTI). The C-RNTI is a dynamic identifier assigned to the UE by the access network device. During the UE's cell registration process, the access network device is unaware of the information provided during the registration process. Therefore, the access network device needs to obtain this information based on the C-RNTI.

[0284] The more information and the more types of information the slice-related information includes, the more helpful it is to improve network quality.

[0285] In some embodiments, the slice-related information is sent to the access network device in the form of a single report or a report list. The report includes a Minimization of Drive Tests (MDT) report, a Self-Organizing Network (SON) report, or a new report. MDT reports include logged MDT reports and Immediate MDT reports. SON reports include RLF (radio link failure) reports, RA (random access) reports, SHR (Successful handover report), SPR (successful PScell ​​change / addition report), MHI (mobility history inforamtion) report, UHI (UE history information) report, CEF (connection establishmet failure) report, etc.

[0286] The report is carried in the user equipment information response message, or the report list is carried in the UE information response message. Correspondingly, the access network device sends the collected slice-related information to the Operation Administration and Maintenance (OAM) or core network for OAM to observe the performance of the network slice or to optimize the deployment of the network slice.

[0287] In some embodiments, before executing step S201, the UE receives the configuration information when it is in a connected state. The configuration information is sent to the UE by the access network device. The configuration information can be carried in an RRC reconfiguration message and / or an RRC recovery message.

[0288] If the configuration information is not updated, it is sent to the UE once and then not sent again. That is, before the UE executes step S201 for the first time, it must first receive the configuration information sent by the access network device and then execute step S201. In this case, the UE does not need to receive the configuration information again when it is not the first time executing step S201. Alternatively, the UE may first receive the configuration information sent by the access network device before each execution of step S201 and then execute step S201.

[0289] In some embodiments, the configuration information includes one or more of the following information:

[0290] 1) The time when the terminal device collects slice-related information. This time may be the time when the above-described process is started.

[0291] 2) The absolute time information when the access network device sends the configuration information.

[0292] 3) A data radio bearer (DRB) list to be collected by the terminal device. The DRB list includes at least one DRB.

[0293] 4) A list of network slices to be collected by the terminal device. The network slice list includes at least one network slice.

[0294] 5) The area range collected by the terminal device. This area range includes, for example, the Physical Cell Identity (PCI) list, the Tracking Area Code (TAC) list, the Public Land Mobile Network (PLMN) list, and the Standalone Non-Public Network (SNPN) list.

[0295] 6) PLMN list or SNPN list that allows reporting of slice related information.

[0296] 7) The configuration type of the terminal device recording slice-related information includes event triggering, which includes: the cell where the UE is located changes; when the UE performs the cell registration process (process 1), a network slice is rejected; when the UE performs the cell switching (process 2), secondary cell addition (process 3) or secondary cell change (process 4), the PDU session corresponding to the slice is released.

[0297] The configuration type may also include other types, which are not limited in this embodiment.

[0298] 8) Trigger conditions for the terminal device to report slice-related information include: 1) a threshold for the number of rejected network slices; 2) a threshold for the number of released network slice-related PDU sessions. When the threshold for the number of rejected network slices exceeds a first threshold, slice-related information is reported. Alternatively, when the threshold for the number of released network slice-related PDU sessions exceeds a second threshold, slice-related information is reported.

[0299] In some embodiments, when the UE receives the configuration information, if the configuration information includes a trigger condition for the terminal device to report slice related information, then step S202 specifically includes: when the trigger condition for the terminal device to report slice related information is met, sending the slice related information to the access network device.

[0300] In some embodiments, when the UE receives the configuration information, if the configuration information includes the time for the configured terminal device to collect slice-related information, the time for the terminal device to collect slice-related information is set to the value of the timer for collecting slice-related information, and the timer is started.

[0301] In some embodiments, the UE releases the configuration information and slice-related information that have been stored to reserve storage space for other information. Specifically, when the timer expires, the configuration information is released, and the slice-related information collected during the effective duration of the timer is deleted after a preset duration. Alternatively, when the reserved memory resources are full, the configuration information is released, and the slice-related information collected during the effective duration of the timer is deleted after a preset duration. In some embodiments, the maximum duration for the UE to store the configuration information and the slice-related information is 48 hours. Regular or quantitative clearing of memory resources is beneficial to the operation of the UE.

[0302] In some embodiments, the UE may collect the slice related information in a connected state and a non-connected state. If the UE stores slice related information, when the UE returns to a connected state from an idle state (IDIE) or a deactivated state (Inactive), if the current PLMN is a registered PLMN (RPLMN), or the current PLMN is included in the PLMN list in the configuration information, the UE includes the first information in an RRC Setup Complete message, an RRC Resume Complete message, an RRC Reconfiguration Complete message, or an RRC Reestablishment Complete message. The UE sends the first information to the access network device, and the first information indicates that the slice related information is available. After the access network device receives the first information, the access network device obtains the slice related information stored by the UE through a user information request (UE Information Request) message or a new request message. Correspondingly, the UE includes the stored slice related information in a Logged MDT report, the above-mentioned SON report, or other reports, and reports it to the access network device through a user information reply message (UE Information Response).

[0303] It should be noted that the more information the configuration information contains and the more types of information it contains, the more helpful it will be in improving network quality in the future.

[0304] above.

[0305] For ease of understanding, the following is a most specific description of the configuration information received and the slice-related information obtained when the UE executes different processes. This description is only for example and does not limit the information processing method provided in this embodiment.

[0306] Example 1,

[0307] When the UE performs process 1, the information processing method includes:

[0308] In the first step, when the UE is in a connected state, the UE receives the configuration information. The access network device may send the configuration information to the UE via an RRC reconfiguration message (RRC Reconfiguration) or an RRC resume message (RRC Resume).

[0309] The configuration information includes one or more of the following:

[0310] 1) The time when the terminal device collects slice-related information.

[0311] 2) The absolute time information when the access network device sends the configuration information.

[0312] 3) The DRB list to be collected by the terminal device.

[0313] 4) List of network slices to be collected by the terminal device.

[0314] 5) The area scope collected by the terminal device.

[0315] 6) List of public land mobile networks PLMN or independent non-public networks SNPN that are allowed to report slice-related information.

[0316] 7) The configuration type of the terminal device recording slice-related information includes event triggering, and the event triggering includes changes in the cell where the UE is located; when the UE is registering a cell, a network slice is rejected; when the UE is switching cells, adding secondary cells or changing secondary cells, the PDU session corresponding to the slice is released.

[0317] 8) The triggering conditions for the terminal device to report slice-related information include the threshold value of the number of rejected network slices and the threshold value of the number of released network slice-related PDU sessions.

[0318] In the second step, after the UE receives the configuration information, if the configuration information includes the time for the terminal device to collect slice-related information, the time for the terminal device to collect slice-related information is set to the value of the timer for collecting slice-related information, and the timer is started.

[0319] In the third step, if the configuration information includes the area range collected by the terminal device, the UE performs process 1 within the area range, and then the UE records the rejected network slices and the number of times the network slices are rejected, and other slice-related information based on the registration cell acceptance message or registration cell rejection message fed back by the access network device.

[0320] If the configuration information includes a list of network slices to be collected by the terminal device, the UE records the slice-related information in the network slice list.

[0321] If the configuration information includes a list of DRBs to be collected by the terminal device, the UE records slice-related DRB-related information.

[0322] If the configuration information includes a configuration type for the terminal device to record slice-related information, and the configuration type includes an event trigger, then when the configured event trigger condition is met, the UE records the slice-related information.

[0323] The UE may record slice related information in a single report or a report list, which may include one or more of the following information:

[0324] 1) Accept the configured absolute time information.

[0325] 2) Relative time relative to the time of receiving the configuration information.

[0326] 3) Rejected network slices.

[0327] 4) The data radio bearer corresponding to the rejected network slice.

[0328] 5) Number of times network slices are rejected.

[0329] 6) Cells that reject network slicing.

[0330] 7) Reasons for rejecting network slicing.

[0331] 8) Tracking area code TAC corresponding to the cell.

[0332] 9) Cell Radio Network Temporary Identity (C-RNTI) of the UE.

[0333] In the fourth step, if the configuration information includes triggering conditions for the terminal device to report slice-related information, that is, the threshold value of the number of rejected network slices and the threshold value of the number of released network slice-related PDU sessions, when the threshold value is reached, the UE reports the slice-related information available indication (the above-mentioned first information) to the access network device in a subsequent completion message.

[0334] Step 5: When the timer for collecting slice-related information expires or the reserved memory resources are full, the UE releases the configuration information and saves the collected slice-related information for up to 48 hours.

[0335] In step 6, the UE may collect slice-related information in a connected state and a non-connected state. If the UE stores slice-related information, when the UE returns to a connected state from an IDLE state or an INACTIVE state, if the current PLMN is an RPLMN or is included in a configured PLMN table, the UE includes the first information in an RRC creation complete message, an RRC recovery complete message, an RRC reconfiguration complete message, or an RRC reestablishment complete message, where the first information indicates that slice-related information is available.

[0336] In the seventh step, after receiving the first information, the access side device obtains the slice-related information stored in the UE through a user message request information or a new message.

[0337] In the eighth step, the UE includes the recorded slice-related information in the Logged MDT report or a new report, and reports it to the network through the user information reply message (UE Information Response).

[0338] In the ninth step, the access network equipment sends the collected slice-related information to the OAM or core network for OAM to observe the performance of the network slice or for slice deployment optimization.

[0339] Example 2,

[0340] When the UE performs at least one of process 2 to process 6, the information processing method includes:

[0341] In the first step, when the UE is in a connected state, the UE receives the configuration information. The access network device may send the configuration information to the UE via an RRC reconfiguration message (RRC Reconfiguration) or an RRC resume message (RRC Resume).

[0342] The configuration information includes one or more of the following:

[0343] 1) The time when the terminal device collects slice-related information.

[0344] 2) The absolute time information when the access network device sends the configuration information.

[0345] 3) The DRB list to be collected by the terminal device.

[0346] 4) List of network slices to be collected by the terminal device.

[0347] 5) The area scope collected by the terminal device.

[0348] 6) The configuration type of the terminal device recording slice-related information includes event triggering, and the event triggering includes changes in the cell where the UE is located; when the UE is registering a cell, a network slice is rejected; when the UE is switching cells, adding secondary cells or changing secondary cells, the PDU session corresponding to the slice is released.

[0349] 7) The triggering conditions for the terminal device to report slice-related information include the threshold value of the number of rejected network slices and the threshold value of the number of released network slice-related PDU sessions.

[0350] In the second step, after the UE receives the configuration information, if the configuration information includes the time for the terminal device to collect slice-related information, the time for the terminal device to collect slice-related information is set to the value of the timer for collecting slice-related information, and the timer is started.

[0351] In the third step, if the configuration information includes the area range collected by the terminal device, such as the PCI list, TAC list, PLMN list, SNPN list, etc., the UE performs one or more procedures related to cell switching and secondary cell addition or change within the configured area range, such as cell switching, conditional cell switching, Dual Active Protocol Stack (DAPS) cell switching, PScell ​​addition, PScell ​​change, and Conditional PSCell Addition / Change. The UE also performs PDU session establishment and / or modification procedures within the configured area range.

[0352] If the configuration information includes a list of network slices to be collected by the terminal device, the UE records the slice-related information in the network slice list.

[0353] If the configuration information includes a list of DRBs to be collected by the terminal device, the UE records slice-related DRB-related information.

[0354] If the configuration information includes a configuration type for the terminal device to record slice-related information, and the configuration type includes an event trigger, then when the configured event trigger condition is met, the UE records the slice-related information.

[0355] The UE may record slice related information in a single report or a report list, which may include one or more of the following information:

[0356] 1) Accept the configured absolute event information.

[0357] 2) Relative time relative to the time of receiving the configuration information.

[0358] 3) Rejected network slices.

[0359] 4) The data radio bearer corresponding to the rejected network slice.

[0360] 5) Number of times network slices are rejected.

[0361] 6) Cells that reject network slicing.

[0362] 7) Reasons for rejecting network slicing.

[0363] 8) Tracking area code TAC corresponding to the cell.

[0364] 9) Cell Radio Network Temporary Identity (C-RNTI) of the UE.

[0365] In the fourth step, if the configuration information includes triggering conditions for the terminal device to report slice-related information, that is, the threshold value of the number of rejected network slices and the threshold value of the number of released network slice-related PDU sessions, when the threshold value is reached, the UE reports the slice-related information available indication (the above-mentioned first information) to the access network device in a subsequent completion message.

[0366] If the configuration information does not include the triggering conditions for the terminal device to report slice related information, the UE can directly report the slice related information using an indication (the first information mentioned above) to the access network device.

[0367] Step 5: When the timer for collecting slice-related information expires or the reserved memory resources are full, the UE releases the configuration information and saves the collected slice-related information for up to 48 hours.

[0368] In the sixth step, the UE may collect slice-related information in the connected state and the non-connected state, and may not discard the stored slice-related information when the UE enters the IDIE state. If the UE stores slice-related information, when the UE returns to the connected state from the IDLE state or the INACTIVE state, if the current PLMN is an RPLMN or is included in the configured PLMN table, the UE includes the first information in the RRC creation complete message, the RRC recovery complete message, the RRC reconfiguration complete message, or the RRC reconstruction complete message, and the first information indicates that the slice-related information is available.

[0369] In the seventh step, after receiving the first information, the access side device obtains the slice-related information stored in the UE through a user message request information or a new message.

[0370] In the eighth step, the UE includes the recorded slice-related information in the Logged MDT report or a new report, and reports it to the network through the user information reply message (UE Information Response).

[0371] In the ninth step, the access network equipment sends the collected slice-related information to the OAM or core network for OAM to observe the performance of the network slice or for slice deployment optimization.

[0372] In Example 3, when executing at least one of processes 1 to 6, in addition to recording the slice-related information described in Examples 1 and 2, the UE may also uniformly record the slice-related information in at least one of processes 1 to 6 within a configured time range. The UE configuration process and the reporting process of slice-related information are similar to those in Examples 1 and 2, and the configuration content and reporting content are a combination of Examples 1 and 2.

[0373] Referring to FIG3 , one embodiment of the present disclosure provides an information processing method, which is applied to an access network device. The information processing method includes:

[0374] S301, obtain slice related information, where the slice related information includes slice related information reported by the UE.

[0375] The slice related information may be obtained when at least one process occurs, such as UE registering a cell, updating a cell, establishing a PDU session, adding a secondary cell, etc. In some embodiments, the slice related information is obtained when at least one process 1 to process 6 described in the above embodiment is executed.

[0376] The slice-related information includes, for example, the rejected network slice, the data radio bearer corresponding to the rejected network slice, the number of times the network slice is rejected, the cell that rejects the network slice, the reason for rejecting the network slice, the released protocol data unit PDU session, the number of released PDU sessions, the network slice corresponding to the released PDU session, the number of network slices corresponding to the released PDU session, etc.

[0377] The UE can send the slice-related information to the access network device in the form of a single report or a report list.

[0378] , and can also indicate configuration information to the UE, which includes the slice-related information that the UE needs to obtain, the acquisition time of the slice-related information, the reporting conditions of the slice-related information, etc. Correspondingly, the UE obtains and reports the slice-related information according to the configuration information.

[0379] S302, sending the slice-related information to the operation, maintenance and management OAM and / or core network equipment, where the slice-related information indicates the performance of the network slice, or the slice-related information is used for deployment optimization of the network slice.

[0380] The slice-related information includes the slice-related information reported by the terminal as described above, and may also include the slice-related information collected by itself. The access network device sends the slice-related information to the operation and maintenance management (OAM) and / or core network equipment for OAM to observe the performance of the network slice or to optimize the deployment of the network slice.

[0381] Referring to the above description of the slice-related information, it can be seen that the slice-related information indicates the performance of the network slice, or the slice-related information is used for deployment optimization of the network slice. The deployment optimization of the network slice is, for example, optimizing the network slice information corresponding to the cell, or optimizing the deployment of the cell, the deployment of the network slice, etc. The specific method of deployment optimization can be selected according to actual needs, and this embodiment does not limit it. The purpose of network slicing deployment optimization is to solve problems that affect network quality, such as excessive load on the network slice, base stations not supporting some network slices, or being unable to allocate resources for some network slices.

[0382] In some embodiments, OAM and the core network can collect statistics on relevant information of a certain network slice and monitor the certain network slice based on the network slice identifier S-NSSAI to optimize the deployment of the certain network slice.

[0383] In summary, this embodiment provides an information processing method, which is applied to access network equipment. The information processing method includes: obtaining slice-related information, the slice-related information including slice-related information reported by the UE; sending the slice-related information to the operation, maintenance and management OAM and / or core network equipment, the slice-related information indicating the performance of the network slice, or the slice-related information is used for deployment optimization of the network slice. In this embodiment, since the slice-related information is collected, the network slice can be deployed and optimized based on the slice-related information, thereby solving problems that affect network quality, such as excessive load on the network slice, base stations not supporting some network slices, or being unable to allocate resources for some network slices, thereby improving network quality.

[0384] In some embodiments, the slice-related information includes any one or more of the following information:

[0385] 1) Absolute time information of the access network device sending the configuration information. This refers to the absolute time information of the access network device sending the configuration information. The configuration information is sent by the access network device to the UE and is used to instruct the collection of slice-related information.

[0386] 2) Relative time relative to the time of receiving the configuration information. This refers to the relative time between the first time and the second time. The first time refers to the time when the collection of slice-related information is started in any of the above processes 1 to 6. The second time refers to the time when the configuration information is received.

[0387] 3) Rejected network slices: Refers to network slices that are rejected during at least one of the above processes.

[0388] 4) The data radio bearer (DRB) corresponding to the rejected network slice.

[0389] 5) Number of times the network slice is rejected. This refers to the number of times each network slice in the list of network slices to be collected by the terminal device is rejected.

[0390] 6) Cells that reject network slices. This refers to the cells corresponding to each rejected network slice in the list of network slices to be collected by the terminal device.

[0391] 7) Reasons for rejecting the network slice. Reasons include unsupported network slicing, network slice overload, or other reasons.

[0392] 8) Released protocol data unit (PDU) session.

[0393] 9) Number of released PDU sessions: Refers to the number of released PDU sessions.

[0394] 10) The network slice corresponding to the released PDU session. As described above, one PDU session corresponds to one network slice. Here, one released PDU session corresponds to one network slice. Multiple released PDU sessions correspond to multiple network slices.

[0395] 11) The number of network slices corresponding to the released PDU session.

[0396] 12) Release the cell ID (Identity Document, ID) of the PDU session corresponding to the network slice. The cell ID is allocated by the access network equipment to the cell.

[0397] 13) Release the tracking area code (TAC) corresponding to the cell of the PDU session corresponding to the network slice. TAC is a dynamic identifier assigned to the UE by the access side device.

[0398] 14) UE's Cell-Radio Network Temporary Identifier (C-RNTI). The C-RNTI is a dynamic identifier assigned to the UE by the access network device. During the UE's cell registration process, the access network device is unaware of the information provided during the registration process. Therefore, the access network device needs to obtain this information based on the C-RNTI.

[0399] In some embodiments, the UE may uniformly record the slice-related information related to the processes executed in process 1 to process 6 within a configured time range, and report all the uniformly recorded slice-related information to the access network device. Correspondingly, the access network device receives the slice-related information reported by the UE.

[0400] In some embodiments, the slice related information is sent in the form of a single report or a report list as described above. The report includes a Minimization of Drive Tests (MDT) report, a Self-Organizing Network (SON) report, or a new report. The report is carried in the user equipment information response message, or the report list is carried in the UE information response message.

[0401] In some embodiments, the slice-related information also includes slice-related information collected by the access network device itself.

[0402] The slice-related information collected by the access network device itself includes at least one or more of the following information:

[0403] 1) The network slice corresponding to the released PDU session.

[0404] 2) The number of network slices corresponding to the released PDU session.

[0405] 3) Released PDU session.

[0406] 4) The number of PDU sessions released.

[0407] 5) Release the cell identification ID of the PDU session corresponding to the network slice.

[0408] 6) The reason why the PDU session corresponding to the network slice is released.

[0409] 7) Tracking area code TAC corresponding to the cell.

[0410] The more slice-related information the access network equipment collects, the more it helps improve network quality.

[0411] In some embodiments, configuration information is indicated, where the configuration information is used to instruct the collection of information related to the slice. The configuration information may be carried in an RRC reconfiguration message and / or an RRC recovery message. The UE receives the configuration information when in a connected state. If the configuration information is not updated, the configuration information is sent to the UE once and then not sent again.

[0412] In some embodiments, the configuration information includes one or more of the following information:

[0413] 1) The time when the terminal device collects slice-related information. This time may be the time when the above-described process is started.

[0414] 2) The absolute time information when the access network device sends the configuration information.

[0415] 3) A data radio bearer (DRB) list to be collected by the terminal device. The DRB list includes at least one DRB.

[0416] 4) A list of network slices to be collected by the terminal device. The network slice list includes at least one network slice.

[0417] 5) The area range collected by the terminal device. This area range includes, for example, the Physical Cell Identity (PCI) list, the Tracking Area Code (TAC) list, the Public Land Mobile Network (PLMN) list, and the Standalone Non-Public Network (SNPN) list.

[0418] 6) PLMN list or SNPN list that allows reporting of slice related information.

[0419] 7) The configuration type of the terminal device recording slice-related information includes event triggering, which includes: the cell where the UE is located changes; when the UE performs the cell registration process (process 1), a network slice is rejected; when the UE performs the cell switching (process 2), secondary cell addition (process 3) or secondary cell change (process 4), the PDU session corresponding to the slice is released.

[0420] The configuration type may also include other types, which are not limited in this embodiment.

[0421] 8) Trigger conditions for the terminal device to report slice-related information include: 1) a threshold for the number of rejected network slices; 2) a threshold for the number of released network slice-related PDU sessions. When the threshold for the number of rejected network slices exceeds a first threshold, slice-related information is reported. Alternatively, when the threshold for the number of released network slice-related PDU sessions exceeds a second threshold, slice-related information is reported.

[0422] In some embodiments, if the configuration information includes a trigger condition for a terminal device to report slice-related information, the slice-related information is reported when the trigger condition for the terminal device to report slice-related information is met. The trigger condition includes: 1) a threshold value for the number of rejected network slices; 2) a threshold value for the number of released network slice-related PDU sessions. When the threshold value for the number of rejected network slices exceeds a first threshold value, the slice-related information is reported. Alternatively, when the threshold value for the number of released network slice-related PDU sessions exceeds a second threshold value, the slice-related information is reported.

[0423] Correspondingly, when the triggering conditions for the terminal device to report slice-related information are met, the UE sends the slice-related information to the access network device.

[0424] In some embodiments, if the configuration information includes the time when the terminal device collects slice-related information, the slice-related information includes the slice-related information collected after the timer for collecting slice-related information is started. Correspondingly, the UE will release the configuration information and slice-related information that have been stored to reserve storage space for other information. Specifically, when the timer expires, the configuration information is released, and the slice-related information collected within the effective duration of the timer is deleted after a preset duration. Alternatively, when the reserved memory resources are full, the configuration information is released, and the slice-related information collected within the effective duration of the timer is deleted after a preset duration. In some embodiments, the maximum duration for the UE to store the configuration information and the slice-related information is 48 hours.

[0425] In some embodiments, first information is obtained, where the first information indicates that slice-related information is available. The first information may be carried in an RRC creation complete message, an RRC recovery complete message, an RRC reconfiguration complete message, or an RRC reestablishment complete message.

[0426] After the access network device receives the first information, the access network device obtains the slice-related information stored by the UE through a user information request (UE Information Request) message or a new request message. Correspondingly, the UE includes the stored slice-related information in the logged MDT (Logged MDT) report and reports it to the access network device through a user information request message.

[0427] In some embodiments, multiple UEs may be collecting slice-related information in the same time period. Correspondingly, the access network device counts the slice-related information collected by all UEs within a certain time range based on the UE's context information, and reports the counted slice-related information collected by all UEs to the OAM and / or core network.

[0428] In some embodiments, the slice-related information collected by the access network device itself also includes: the number of UEs activated on each network slice corresponding to the cell within a preset time period, and / or the duration of the PDU session established by the UE on each network slice. This information can be used to expand the capacity of the network slice or assist in switching cells.

[0429] The number of activated UEs can be obtained through L2 measurement.

[0430] Layer 2 (L2) measurements were introduced in NR Rel-16 / 17 to obtain measurements performed by the network or UE via standardized interfaces. Analysis of L2 measurement results supports NR radio link operation, radio resource management, network operation and maintenance, MDT, and SON.

[0431] The L2 measurements defined in Rel-16 / 17 mainly include the number of RA preambles received by each cell, packet delay, number of activated UEs, number of stored UE contexts, packet loss rate, PRB usage, etc.

[0432] like:

[0433] 1) Number of RA preambles received by each cell

[0434] L2 measurements primarily record the number of RA preambles received over a period of time. The reference point is the service access point between the MAC and L1 interfaces. L2 measurement results can be used to analyze connection rates. L2 measurements can be further categorized as the number of 4-step RA preambles received within each cell, the number of 2-step RA preambles received within each cell, the number of 4-step RA preambles received on each Synchronization Signal / PBCH (SSB), and the number of 2-step RA preambles received on each SSB.

[0435] (2) Packet delay

[0436] Packet delay includes the packet delay of the RAN part and the packet delay of the CN part, which can be further divided into the average uplink air interface packet delay per DRB per UE, the average RLC packet delay per DRB per UE, and the average uplink PDCP reordering delay per DRB per UE.

[0437] (3) Number of activated UEs

[0438] L2 measurement is used to count the number of active UEs at each QoS level for OAM performance observation or SON functions.

[0439] In some embodiments, the average duration of the PDU sessions established by the UE on each network slice can also be obtained.

[0440] The average duration is determined by the sum of the durations of the PDU sessions corresponding to the network slice established by the UEs activated in the corresponding network slice (A) and the number of UEs activated in the network slice (B). That is, average duration = A / B.

[0441] In some embodiments, the UE further performs correlation analysis on the slice-related information collected by the UE and the slice-related information collected by the UE itself based on the UE's cell radio network temporary identifier (C-RNTI), cell ID, and time information to obtain a correlation analysis result, and sends the correlation analysis result to the OAM or core network device.

[0442] The association analysis may be performed by comparing the slice-related information collected by the UE with the same information in the slice-related information collected by the UE itself to obtain the association analysis result. For example, if the slice-related information collected by the UE and the slice-related information collected by the UE itself both include rejected network slices and reasons for rejecting network slices, the similarities and differences in the rejected network slices and the similarities and differences in the reasons for rejecting network slices in the two pieces of information are compared to obtain the association analysis result.

[0443] For ease of understanding, the following provides the most specific description of the slice-related information obtained by the access network device during the execution of different processes by the UE and the slice-related information obtained by itself. This description is only for example and does not limit the information processing method provided in this embodiment.

[0444] Example 4,

[0445] The access network device counts the slice-related information of the UE when executing at least one of processes 1 to 6.

[0446] For the slice-related information in Example 2, a gNB-based solution can also be used. That is, the access network device can know the PDU session and corresponding network slice information released during the cell switching, PDU session establishment or modification process. The access network device can directly count the slice-related information over a period of time and report it to the OAM or core network.

[0447] Specifically, they include:

[0448] In the first step, the access network device counts the slice-related information of all UEs executing processes 1 to 6 within a certain time range based on the UE context information.

[0449] The slice-related information includes one or more of the following:

[0450] 1) The network slice corresponding to the released PDU session.

[0451] 2) The number of network slices corresponding to the released PDU session.

[0452] 3) Released PDU session.

[0453] 4) The number of PDU sessions released.

[0454] 5) Release the target cell ID of the PDU session corresponding to the slice.

[0455] 6) The reason why the PDU session corresponding to the slice is released.

[0456] 7) TAC corresponding to the cell.

[0457] In the second step, the access network equipment reports the slice-related information to the OAM or core network. The OAM or core network can jointly analyze the slice-related information reported by the UE and the slice-related information counted by the access network equipment to optimize the slice deployment.

[0458] Example 5,

[0459] In the first step, the access network equipment counts the number of UEs activated in each network slice in each cell or TAC over a period of time.

[0460] The slice-related information collected by the access network equipment may include: the number of UEs activated in each network slice under each cell or TAC within a period of time, and the duration of the established PDU session, which is used for slice expansion or assisted cell switching.

[0461] The slice-related information collected by the access network equipment may also include: the number of UEs activated on each network slice in the cell within a period of time, and the duration of the PDU session established by the UE in each network slice.

[0462] In the second step, the access network equipment counts the average duration of the PDU session corresponding to the network slice established by the UE.

[0463] In the third step, the access network equipment reports the statistical information to the OAM or core network. The OAM or core network can jointly analyze the slice-related information reported by the UE and the slice-related information counted by the base station to optimize the deployment of network slices.

[0464] Please refer to Figure 4, which is a schematic diagram of signaling interaction of the information processing method provided in the embodiment of the present disclosure. It should be noted that the terminal device in the embodiment of the present disclosure may be the above-mentioned UE, and the access side device may be the above-mentioned target base station.

[0465] As shown in FIG4 , the information processing method provided by the embodiment of the present disclosure includes the following steps:

[0466] S401, the terminal device obtains slice related information.

[0467] The description of this step can refer to the relevant description of step S210, which will not be repeated here.

[0468] S402, the terminal device sends the slice related information to the access network device.

[0469] The description of this step can refer to the relevant description of step S220, which will not be repeated here.

[0470] S403, the access side device sends the slice related information to the OAM and / or core network device.

[0471] The description of this step can refer to the relevant description of step S320, which will not be repeated here.

[0472] Please refer to Figure 4. In some implementations, the access side device can also send the slice-related information collected by itself to the OAM and / or core network.

[0473] In summary, this embodiment provides an information processing method, which includes: a terminal device obtaining slice-related information; the terminal device sending the slice-related information to an access network device; and the access-side device sending the slice-related information to an OAM and / or core network device. Since the slice-related information is collected, network slice deployment optimization can be performed based on the slice-related information, thereby resolving issues that affect network quality, such as excessive network slice load, base station inability to support some network slices, or inability to allocate resources to some network slices, thereby improving network quality.

[0474] Referring to FIG. 5 , an embodiment of the present disclosure provides an information processing apparatus 500 , which is applied to a terminal device.

[0475] The information processing device 500 includes:

[0476] The acquisition module 501 is used to acquire slice related information.

[0477] The sending module 502 is used to send the slice-related information to the access network device, where the slice-related information indicates the performance of the network slice, or the slice-related information is used for deployment optimization of the network slice.

[0478] In some embodiments, the slice-related information includes any one or more of the following information:

[0479] Absolute time information when the access network device sends configuration information;

[0480] Relative time relative to the time of receiving the configuration information;

[0481] Rejected network slices;

[0482] The data radio bearer corresponding to the rejected network slice;

[0483] Number of times network slices were rejected;

[0484] Cells that reject network slicing;

[0485] Reasons for rejecting network slicing;

[0486] The released protocol data unit PDU session;

[0487] Number of times a PDU session is released;

[0488] The network slice corresponding to the released PDU session;

[0489] The number of network slices corresponding to the released PDU session;

[0490] Release the cell ID of the PDU session corresponding to the network slice;

[0491] Release the tracking area code TAC of the cell corresponding to the PDU session of the network slice;

[0492] The cell radio network temporary identifier C-RNTI of the terminal device.

[0493] In some embodiments, the sending module 502 is specifically used to send the slice-related information to the access network device in the form of a single report or a report list.

[0494] In some implementations, obtaining the slice-related information occurs by performing at least one of the following processes:

[0495] Register a cell, switch a cell, add a secondary cell, change a secondary cell, establish a PDU session, and modify a PDU session.

[0496] In some implementations, the sending module 502 is further used to: receive configuration information, where the configuration information is used to instruct collection of information related to the slice.

[0497] In some embodiments, the configuration information includes one or more of the following information:

[0498] The time when the terminal device collects slice-related information;

[0499] The absolute time information of the access network device sending the configuration information;

[0500] The data radio bearer (DRB) list to be collected by the terminal device;

[0501] The list of network slices to be collected by the terminal device;

[0502] The area scope collected by the terminal device;

[0503] List of public land mobile networks (PLMNs) or independent non-public networks (SNPNs) that are allowed to report slice related information;

[0504] The configuration type for recording slice-related information by the terminal device includes event triggering, which includes changes in the cell where the terminal device is located; network slices are rejected during the terminal device's cell registration process; and the PDU session corresponding to the slice is released during the terminal device's cell handover, secondary cell addition, or secondary cell change process.

[0505] The triggering conditions for the terminal device to report slice-related information include the threshold for the number of rejected network slices and the threshold for the number of released network slice-related PDU sessions.

[0506] In some embodiments, if the configuration information includes a trigger condition for the terminal device to report slice-related information, the sending module 502 is specifically used to: when the trigger condition for the terminal device to report slice-related information is met, send the slice-related information to the access network device.

[0507] In some embodiments, if the configuration information includes the time for the terminal device to collect slice-related information, the information processing device 500 also includes a processing module 503, which is used to: set the time for the terminal device to collect slice-related information to the value of the timer for collecting slice-related information, and start the timer.

[0508] In some implementations, the processing module 503 is further configured to: release the configuration information when the timer expires, and delete the slice related information collected within the validity period of the timer after a preset time period;

[0509] Alternatively, when the reserved memory resources are full, the configuration information is released, and the slice related information collected within the effective time of the timer is deleted after a preset time.

[0510] In some embodiments, the sending module 502 is further used to: send first information to the access network device, where the first information indicates that slice-related information is available.

[0511] In some embodiments, the first information may be carried in an RRC creation complete message, an RRC recovery complete message, an RRC reconfiguration complete message, or an RRC reestablishment complete message.

[0512] Among them, the method and the device are based on the same application concept. Since the principles of solving problems by the method and the device are similar, the implementation of the device and the method can refer to each other, and the repeated parts will not be repeated.

[0513] Referring to FIG. 6 , an embodiment of the present disclosure provides an information processing apparatus 600 , which is applied to an access network device.

[0514] The information processing device 600 includes:

[0515] The acquisition module 601 is used to obtain slice related information, which includes slice related information reported by the terminal device.

[0516] The sending module 602 is used to send the slice-related information to the operation, maintenance and management OAM and / or core network equipment, where the slice-related information indicates the performance of the network slice, or the slice-related information is used for deployment optimization of the network slice.

[0517] In some embodiments, the slice-related information includes any one or more of the following:

[0518] Absolute time information when the access network device sends configuration information;

[0519] Relative time relative to the time of receiving the configuration information;

[0520] Rejected network slices;

[0521] The data radio bearer corresponding to the rejected network slice;

[0522] Number of times network slices were rejected;

[0523] Cells that reject network slicing;

[0524] Reasons for rejecting network slicing;

[0525] The released protocol data unit PDU session;

[0526] Number of times a PDU session is released;

[0527] The network slice corresponding to the released PDU session;

[0528] The number of network slices corresponding to the released PDU session;

[0529] Release the cell ID of the PDU session corresponding to the network slice;

[0530] Release the tracking area code TAC of the cell corresponding to the PDU session of the network slice;

[0531] The cell radio network temporary identifier C-RNTI of the terminal device.

[0532] In some embodiments, the slice-related information is sent in the form of a single report or a list of reports.

[0533] In some embodiments, obtaining the slice-related information occurs by performing at least one of the following processes:

[0534] Register a cell, switch a cell, add a secondary cell, change a secondary cell, establish a PDU session, and modify a PDU session.

[0535] In some embodiments, the information processing device 600 further includes a processing module 603 for indicating configuration information, where the configuration information is used to instruct collection of the slice-related information.

[0536] In some implementations, the configuration information is carried in a radio resource control (RRC) reconfiguration message and / or an RRC recovery message.

[0537] In some embodiments, the configuration information includes one or more of the following information:

[0538] The time when the terminal device collects slice-related information;

[0539] The absolute time information of the access network device sending the configuration information;

[0540] The data radio bearer (DRB) list to be collected by the terminal device;

[0541] The list of network slices to be collected by the terminal device;

[0542] The area scope collected by the terminal device;

[0543] List of public land mobile networks (PLMNs) or independent non-public networks (SNPNs) that are allowed to report slice related information;

[0544] The configuration type for recording slice-related information by the terminal device includes event triggering, which includes changes in the cell where the terminal device is located; network slices are rejected during the terminal device's cell registration process; and the PDU session corresponding to the slice is released during the terminal device's cell handover, secondary cell addition, or secondary cell change process.

[0545] The triggering conditions for the terminal device to report slice-related information include the threshold for the number of rejected network slices and the threshold for the number of released network slice-related PDU sessions.

[0546] In some embodiments, if the configuration information includes a triggering condition for a terminal device to report slice-related information, the slice-related information is reported when the triggering condition for the terminal device to report slice-related information is met.

[0547] In some embodiments, if the configuration information includes the time when the terminal device collects slice-related information, the slice-related information includes slice-related information collected after the timer for collecting slice-related information is started.

[0548] In some implementations, the acquisition module 601 is further configured to: acquire first information, where the first information indicates that slice-related information is available.

[0549] In some embodiments, the first information may be carried in an RRC creation complete message, an RRC recovery complete message, an RRC reconfiguration complete message, or an RRC reestablishment complete message.

[0550] In some embodiments, the slice-related information also includes slice-related information collected by the access network device itself.

[0551] In some implementations, the slice-related information collected by the access network device itself includes at least one or more of the following:

[0552] The network slice corresponding to the released PDU session;

[0553] The number of network slices corresponding to the released PDU session;

[0554] Released PDU session;

[0555] The number of released PDU sessions;

[0556] Release the cell ID of the PDU session corresponding to the network slice;

[0557] The reason why the PDU session corresponding to the network slice is released;

[0558] Tracking area code TAC corresponding to the cell.

[0559] In some implementations, the slice-related information collected by the access network device itself further includes:

[0560] The number of terminal devices activated on each network slice corresponding to the cell within a preset time period, and / or the duration of the PDU session established by the terminal device on each network slice.

[0561] In some embodiments, the acquisition module 601 is also used to obtain the average duration of the PDU sessions established by the terminal device on each network slice.

[0562] In some embodiments, the average duration is determined based on the sum of the durations of the PDU sessions corresponding to the network slice established by the terminal devices activated under the corresponding network slice and the number of terminal devices activated under the network slice.

[0563] In some embodiments, the sending module 602 is specifically configured to: perform correlation analysis on the slice related information collected by the terminal device and the slice related information collected by itself according to the cell radio network temporary identifier C-RNTI, the cell ID, and the time information of the terminal device, to obtain a correlation analysis result;

[0564] The correlation analysis result is sent to the OAM or core network equipment.

[0565] Among them, the method and the device are based on the same application concept. Since the principles of solving problems by the method and the device are similar, the implementation of the device and the method can refer to each other, and the repeated parts will not be repeated.

[0566] An embodiment of the present disclosure provides a terminal device, and Figure 7 is a schematic diagram of the structure of the terminal device provided by the embodiment of the present disclosure. As shown in Figure 7 , the terminal device 700 includes: a transceiver 701 , a processor 702 , and a memory 703 .

[0567] The transceiver 701 is used to receive and transmit data under the control of the processor 702. In FIG7 , the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by the processor 702 and the memory represented by the memory 703. The bus architecture may also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and are therefore not described further herein. The bus interface provides an interface. The transceiver 701 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, such as a wireless channel, a wired channel, an optical cable, and the like. The processor 702 is responsible for managing the bus architecture and general processing, and the memory 703 may store data used by the processor 702 when performing operations.

[0568] Processor 702 is responsible for managing the bus architecture and general processing. Memory 703 can store data used by processor 702 when performing operations. Processor 702 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor can also adopt a multi-core architecture. Processor 702 calls a computer program stored in memory 703 to execute any of the terminal device methods provided in the embodiments of the present disclosure according to the obtained executable instructions. The processor and memory can also be physically separated.

[0569] In some embodiments, the processor 702 is configured to read the computer program in the memory and perform the following operations:

[0570] Obtain slice-related information, including slice-related information reported by the terminal device;

[0571] Send slice-related information to operation, maintenance and management (OAM) and / or core network equipment.

[0572] In some embodiments, the slice-related information includes any one or more of the following information:

[0573] Absolute time information when the access network device sends configuration information;

[0574] Relative time relative to the time of receiving the configuration information;

[0575] Rejected network slices;

[0576] The data radio bearer corresponding to the rejected network slice;

[0577] Number of times network slices were rejected;

[0578] Cells that reject network slicing;

[0579] Reasons for rejecting network slicing;

[0580] The released protocol data unit PDU session;

[0581] Number of times a PDU session is released;

[0582] The network slice corresponding to the released PDU session;

[0583] The number of network slices corresponding to the released PDU session;

[0584] Release the cell ID of the PDU session corresponding to the network slice;

[0585] Release the tracking area code TAC of the cell corresponding to the PDU session of the network slice;

[0586] The cell radio network temporary identifier C-RNTI of the terminal device.

[0587] In some embodiments, the processor 702 is used to send the slice-related information to the access network device in the form of a single report or a report list.

[0588] In some implementations, obtaining the slice-related information occurs by performing at least one of the following processes:

[0589] Register a cell, switch a cell, add a secondary cell, change a secondary cell, establish a PDU session, and modify a PDU session.

[0590] In some implementations, the processor 702 is further configured to: receive configuration information, where the configuration information is used to instruct collection of information related to the slice.

[0591] In some implementations, the configuration information is carried in a radio resource control (RRC) reconfiguration message and / or an RRC recovery message.

[0592] In some embodiments, the configuration information includes one or more of the following information:

[0593] The time when the terminal device collects slice-related information;

[0594] The absolute time information of the access network device sending the configuration information;

[0595] The data radio bearer (DRB) list to be collected by the terminal device;

[0596] The list of network slices to be collected by the terminal device;

[0597] The area scope collected by the terminal device;

[0598] List of public land mobile networks (PLMNs) or independent non-public networks (SNPNs) that are allowed to report slice related information;

[0599] The configuration type for recording slice-related information by the terminal device includes event triggering, which includes changes in the cell where the terminal device is located; network slices are rejected during the terminal device's cell registration process; and the PDU session corresponding to the slice is released during the terminal device's cell handover, secondary cell addition, or secondary cell change process.

[0600] The triggering conditions for the terminal device to report slice-related information include the threshold for the number of rejected network slices and the threshold for the number of released network slice-related PDU sessions.

[0601] In some embodiments, if the configuration information includes a trigger condition for the terminal device to report slice-related information, the processor 702 is specifically used to: when the trigger condition for the terminal device to report slice-related information is met, send the slice-related information to the access network device.

[0602] In some embodiments, if the configuration information includes the time for the terminal device to collect slice-related information, the processor 702 is also used to: set the time for the terminal device to collect slice-related information to the value of the timer for collecting slice-related information, and start the timer.

[0603] In some implementations, the processor 702 is further configured to: release the configuration information when the timer expires, and delete the slice related information collected within the validity period of the timer after a preset time period;

[0604] Alternatively, when the reserved memory resources are full, the configuration information is released, and the slice related information collected within the effective time of the timer is deleted after a preset time.

[0605] In some embodiments, the processor 702 is further used to: send first information to the access network device, where the first information indicates that slice-related information is available.

[0606] In some embodiments, the first information may be carried in an RRC creation complete message, an RRC recovery complete message, an RRC reconfiguration complete message, or an RRC reestablishment complete message.

[0607] It should be noted here that the above-mentioned terminal device provided by the present disclosure can implement all the method steps corresponding to those implemented by the terminal device in the above-mentioned method embodiment, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0608] It should be noted that the division of units in the embodiments of the present disclosure is schematic and is merely a logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of the present disclosure may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0609] If the above-mentioned integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of the present disclosure is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, server, or terminal device, etc.) or a processor (processor) to perform all or part of the steps of the various embodiments of the present disclosure. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk, etc. Various media that can store program codes.

[0610] An embodiment of the present disclosure provides an access side device, and Figure 8 is a schematic diagram of the structure of the access side device provided by the embodiment of the present disclosure. As shown in Figure 8 , the terminal device 800 includes: a transceiver 801 , a processor 802 , and a memory 803 .

[0611] The transceiver 801 is used to receive and transmit data under the control of the processor 802. In FIG8 , the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by the processor 802 and the memory represented by the memory 803. The bus architecture may also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and are therefore not described further herein. The bus interface provides an interface. The transceiver 801 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium, such as a wireless channel, a wired channel, an optical cable, or the like. The processor 802 is responsible for managing the bus architecture and general processing, and the memory 803 may store data used by the processor 802 when performing operations.

[0612] Processor 802 is responsible for managing the bus architecture and general processing. Memory 803 can store data used by processor 802 when performing operations. Processor 802 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor can also adopt a multi-core architecture. Processor 802 calls a computer program stored in memory 803 to execute any of the terminal device methods provided in the embodiments of the present disclosure according to the obtained executable instructions. The processor and memory can also be physically separated.

[0613] In some embodiments, the processor 802 is configured to read the computer program in the memory and perform the following operations:

[0614] Obtain slice-related information, including slice-related information reported by the terminal device;

[0615] The slice-related information is sent to the operation, maintenance and management OAM and / or core network equipment, where the slice-related information indicates the performance of the network slice, or the slice-related information is used for deployment optimization of the network slice.

[0616] In some embodiments, the slice-related information includes any one or more of the following:

[0617] Absolute time information when the access network device sends configuration information;

[0618] Relative time relative to the time of receiving the configuration information;

[0619] Rejected network slices;

[0620] The data radio bearer corresponding to the rejected network slice;

[0621] Number of times network slices were rejected;

[0622] Cells that reject network slicing;

[0623] Reasons for rejecting network slicing;

[0624] The released protocol data unit PDU session;

[0625] Number of times a PDU session is released;

[0626] The network slice corresponding to the released PDU session;

[0627] The number of network slices corresponding to the released PDU session;

[0628] Release the cell ID of the PDU session corresponding to the network slice;

[0629] Release the tracking area code TAC of the cell corresponding to the PDU session of the network slice;

[0630] The cell radio network temporary identifier C-RNTI of the terminal device.

[0631] In some embodiments, the slice-related information is sent in the form of a single report or a list of reports.

[0632] In some embodiments, obtaining the slice-related information occurs by performing at least one of the following processes:

[0633] Register a cell, switch a cell, add a secondary cell, change a secondary cell, establish a PDU session, and modify a PDU session.

[0634] In some implementations, the processor 802 is further configured to:

[0635] Indicates configuration information, which is used to instruct the collection of information related to the slice.

[0636] In some implementations, the configuration information is carried in a radio resource control (RRC) reconfiguration message and / or an RRC recovery message.

[0637] In some embodiments, the configuration information includes one or more of the following information:

[0638] The time when the terminal device collects slice-related information;

[0639] The absolute time information of the access network device sending the configuration information;

[0640] The data radio bearer (DRB) list to be collected by the terminal device;

[0641] The list of network slices to be collected by the terminal device;

[0642] The area scope collected by the terminal device;

[0643] List of public land mobile networks (PLMNs) or independent non-public networks (SNPNs) that are allowed to report slice related information;

[0644] The configuration type for recording slice-related information by the terminal device includes event triggering, which includes changes in the cell where the terminal device is located; network slices are rejected during the terminal device's cell registration process; and the PDU session corresponding to the slice is released during the terminal device's cell handover, secondary cell addition, or secondary cell change process.

[0645] The triggering conditions for the terminal device to report slice-related information include the threshold for the number of rejected network slices and the threshold for the number of released network slice-related PDU sessions.

[0646] In some embodiments, if the configuration information includes a triggering condition for a terminal device to report slice-related information, the slice-related information is reported when the triggering condition for the terminal device to report slice-related information is met.

[0647] In some embodiments, if the configuration information includes the time when the terminal device collects slice-related information, the slice-related information includes slice-related information collected after the timer for collecting slice-related information is started.

[0648] In some implementations, the processor 802 is further configured to:

[0649] First information is obtained, where the first information indicates that slice-related information is available.

[0650] In some embodiments, the first information may be carried in an RRC creation complete message, an RRC recovery complete message, an RRC reconfiguration complete message, or an RRC reestablishment complete message.

[0651] In some embodiments, the slice-related information also includes slice-related information collected by the access network device itself.

[0652] In some implementations, the slice-related information collected by the access network device itself includes at least one or more of the following:

[0653] The network slice corresponding to the released PDU session;

[0654] The number of network slices corresponding to the released PDU session;

[0655] Released PDU session;

[0656] The number of released PDU sessions;

[0657] Release the cell ID of the PDU session corresponding to the network slice;

[0658] The reason why the PDU session corresponding to the network slice is released;

[0659] Tracking area code TAC corresponding to the cell.

[0660] In some implementations, the slice-related information collected by the access network device itself further includes:

[0661] The number of terminal devices activated on each network slice corresponding to the cell within a preset time period, and / or the duration of the PDU session established by the terminal device on each network slice.

[0662] In some implementations, the processor 802 is further configured to:

[0663] Get the average duration of PDU sessions established by terminal devices on each network slice.

[0664] In some embodiments, the average duration is determined based on the sum of the durations of the PDU sessions corresponding to the network slice established by the terminal devices activated under the corresponding network slice and the number of terminal devices activated under the network slice.

[0665] In some implementations, the processor 802 is specifically configured to:

[0666] According to the cell radio network temporary identifier C-RNTI, cell ID and time information of the terminal device, the slice related information collected by the terminal device is correlated and analyzed with the slice related information collected by itself to obtain a correlation analysis result;

[0667] The correlation analysis result is sent to the OAM or core network equipment.

[0668] It should be noted here that the above-mentioned access side device provided by the present disclosure can implement all the method steps corresponding to those implemented by the access side device in the above-mentioned method embodiment, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0669] It should be noted that the division of units in the embodiments of the present disclosure is schematic and is merely a logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of the present disclosure may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0670] If the above-mentioned integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of the present disclosure is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, a server, or an access side device, etc.) or a processor (processor) to execute all or part of the steps of the various embodiments of the present disclosure. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk, and other media that can store program code.

[0671] The embodiment of the present disclosure provides a processor-readable storage medium, which stores a computer program. The computer program is used to enable the processor to execute the information processing method provided by the embodiment of the present disclosure, so that the processor can implement all the steps of the information processing method implemented by the terminal device or the access side device in the above method embodiment, and can achieve the same technical effect. The parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here. Among them, the processor-readable storage medium can be any available medium or data storage device that the processor can access, including but not limited to magnetic storage (such as floppy disk, hard disk, magnetic tape, magneto-optical disk (MO), etc.), optical storage (such as CD, DVD, BD, HVD, etc.), and semiconductor storage (such as ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)), etc.

[0672] One embodiment of the present disclosure further provides a computer program product comprising instructions, wherein the computer program is stored in a storage medium, and at least one processor can read the computer program from the storage medium. When the at least one processor executes the computer program, all steps of the information processing method implemented by the terminal device or the access side device in the above-mentioned method embodiment can be implemented, and the same technical effects can be achieved. The parts and beneficial effects of this embodiment that are the same as those in the method embodiment will not be described in detail here.

[0673] The present disclosure also provides a communication system, including a terminal device and an access-side device. The terminal device and the access-side device are capable of executing the corresponding steps in the above-described information processing method embodiments and achieving the same technical effects. The parts of this embodiment that are identical to the method embodiments and the beneficial effects thereof will not be further detailed herein.

[0674] Those skilled in the art will appreciate that the embodiments of the present disclosure may be provided as methods, systems, or computer program products. Thus, the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Furthermore, the present disclosure may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage and optical storage) containing computer-usable program code.

[0675] The present disclosure is described with reference to the signaling interaction diagrams and / or block diagrams of the methods, devices, and computer program products according to the embodiments of the present disclosure. It should be understood that each process and / or box in the signaling interaction diagram and / or block diagram, as well as the combination of processes and / or boxes in the signaling interaction diagram and / or block diagram, can be implemented by computer-executable instructions. These computer-executable instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one or more processes in the signaling interaction diagram and / or one or more boxes in the block diagram. These processor-executable instructions can also be stored in a processor-readable memory that can guide the computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the processor-readable memory produce an article of manufacture including an instruction device that implements the functions specified in one or more processes in the signaling interaction diagram and / or one or more boxes in the block diagram.

[0676] These processor-executable instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce computer-implemented processing, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the signaling interaction diagram and / or one or more boxes in the block diagram.

[0677] Obviously, those skilled in the art may make various changes and modifications to the present disclosure without departing from the spirit and scope of the present disclosure. Thus, if these modifications and variations of the present disclosure fall within the scope of the claims of the present disclosure and their equivalents, the present disclosure is intended to include these modifications and variations.

Claims

1. An information processing method, wherein: Applied to a terminal device, the method includes: Get slice related information; The slice-related information is sent to the access network device, where the slice-related information indicates the performance of the network slice.

2. The method according to claim 1, wherein The slice-related information includes any one or more of the following: Absolute time information of the access network device sending the configuration information; Relative time relative to the time of receiving the configuration information; Rejected network slices; The data radio bearer corresponding to the rejected network slice; Number of times network slices were rejected; Cells that reject network slicing; Reasons for rejecting network slicing; The released protocol data unit PDU session; Number of times a PDU session is released; The network slice corresponding to the released PDU session; The number of network slices corresponding to the released PDU session; Release the cell ID of the PDU session corresponding to the network slice; Release the tracking area code TAC of the cell corresponding to the PDU session of the network slice; The cell radio network temporary identifier C-RNTI of the terminal device.

3. The method according to claim 1 or 2, wherein: The sending of the slice related information to the access network device includes: sending the slice related information to the access network device in the form of a single report or a report list.

4. The method according to claim 1 or 2, wherein: The acquisition of slice related information occurs in at least one of the following processes: Register a cell, switch a cell, add a secondary cell, change a secondary cell, establish a PDU session, and modify a PDU session.

5. The method according to claim 1 or 2, wherein: The method further includes: receiving configuration information, where the configuration information is used to instruct collection of the slice-related information.

6. The method according to claim 5, wherein: The configuration information is carried in a radio resource control RRC reconfiguration message and / or an RRC recovery message.

7. The method according to claim 5, wherein: The configuration information includes one or more of the following information: The time when the terminal device collects slice related information; Absolute time information of sending the configuration information by the access network device; The data radio bearer DRB list to be collected by the terminal device; A list of network slices to be collected by the terminal device; The area range collected by the terminal device; List of public land mobile networks (PLMNs) or independent non-public networks (SNPNs) that are allowed to report slice related information; The configuration type of the terminal device recording slice related information includes event triggering, and the event triggering includes a change in the cell where the terminal device is located; when the terminal device performs cell registration, a network slice is rejected; when the terminal device performs cell switching, secondary cell addition, or secondary cell change, a PDU session corresponding to a slice is released; The triggering conditions for the terminal device to report slice-related information, including a threshold value for the number of rejected network slices; The threshold for the number of released network slice related PDU sessions.

8. The method according to claim 7, wherein: If the configuration information includes a triggering condition for the terminal device to report slice related information, the sending the slice related information to the access network device includes: When the triggering condition for the terminal device to report slice related information is met, the slice related information is sent to the access network device.

9. The method according to claim 7, wherein: If the configuration information includes the time when the terminal device collects slice related information, the method further includes: The time for the terminal device to collect slice-related information is set to the value of the timer for collecting slice-related information, and the timer is started.

10. The method according to claim 9, wherein: The method further includes: releasing the configuration information when the timer expires, and deleting the slice related information collected within the effective time of the timer after a preset time period; Alternatively, when the reserved memory resources are full, the configuration information is released, and the slice related information collected within the effective time of the timer is deleted after a preset time period.

11. The method according to claim 1 or 2, wherein: Also includes: Send first information to the access network device, where the first information indicates that slice-related information is available.

12. The method according to claim 11, wherein The first information may be carried in an RRC creation complete message, an RRC recovery complete message, an RRC reconfiguration complete message or an RRC reconstruction complete message.

13. An information processing method, wherein: Applicable to access network equipment, including: Obtain slice related information, including slice related information reported by the terminal device; The slice-related information is sent to the operation, maintenance and management OAM and / or core network equipment, where the slice-related information indicates the performance of the network slice.

14. The method according to claim 13, wherein The slice-related information includes any one or more of the following: Absolute time information of the access network device sending the configuration information; Relative time relative to the time of receiving the configuration information; Rejected network slices; The data radio bearer corresponding to the rejected network slice; Number of times network slices were rejected; Cells that reject network slicing; Reasons for rejecting network slicing; The released protocol data unit PDU session; Number of times a PDU session is released; The network slice corresponding to the released PDU session; The number of network slices corresponding to the released PDU session; Release the cell ID of the PDU session corresponding to the network slice; Release the tracking area code TAC of the cell corresponding to the PDU session of the network slice; The cell radio network temporary identifier C-RNTI of the terminal device.

15. The method according to claim 13 or 14, wherein: The slice-related information is sent in the form of a single report or a report list.

16. The method according to claim 13 or 14, wherein: The acquisition of slice related information occurs in at least one of the following processes: Register a cell, switch a cell, add a secondary cell, change a secondary cell, establish a PDU session, and modify a PDU session.

17. The method according to claim 13 or 14, wherein: The method further includes: indicating configuration information, where the configuration information is used to instruct collection of the slice related information.

18. The method according to claim 17, wherein: The configuration information is carried in a radio resource control RRC reconfiguration message and / or an RRC recovery message.

19. The method according to claim 17, wherein The configuration information includes one or more of the following information: The time when the terminal device collects slice related information; Absolute time information of sending the configuration information by the access network device; The data radio bearer DRB list to be collected by the terminal device; A list of network slices to be collected by the terminal device; The area range collected by the terminal device; List of public land mobile networks (PLMNs) or independent non-public networks (SNPNs) that are allowed to report slice related information; The configuration type of the terminal device recording slice related information includes event triggering, and the event triggering includes a change in the cell where the terminal device is located; when the terminal device performs cell registration, a network slice is rejected; when the terminal device performs cell switching, secondary cell addition, or secondary cell change, a PDU session corresponding to a slice is released; The triggering conditions for the terminal device to report slice-related information, including a threshold value for the number of rejected network slices; The threshold for the number of released network slice related PDU sessions.

20. The method according to claim 19, wherein If the configuration information includes a triggering condition for the terminal device to report slice related information, the slice related information is reported when the triggering condition for the terminal device to report slice related information is met.

21. The method according to claim 19, wherein If the configuration information includes the time for the terminal device to collect slice-related information, the slice-related information includes the slice-related information collected after the timer for collecting slice-related information is started.

22. The method according to claim 13 or 14, wherein Also includes: First information is obtained, where the first information indicates that slice-related information is available.

23. The method according to claim 22, wherein The first information may be carried in an RRC creation complete message, an RRC recovery complete message, an RRC reconfiguration complete message or an RRC reconstruction complete message.

24. The method according to claim 13 or 14, wherein The slice-related information also includes slice-related information collected by the access network device itself.

25. The method according to claim 24, wherein The slice-related information collected by the access network device itself includes at least one or more of the following: The network slice corresponding to the released PDU session; The number of network slices corresponding to the released PDU session; Released PDU session; The number of released PDU sessions; Release the cell ID of the PDU session corresponding to the network slice; The reason why the PDU session corresponding to the network slice is released; Tracking area code TAC corresponding to the cell.

26. The method according to claim 25, wherein The slice-related information collected by the access network device itself also includes: the number of terminal devices activated on each network slice corresponding to the cell within a preset time period, and / or the duration of the PDU session established by the terminal device on each network slice.

27. The method according to claim 26, wherein The method further comprises: Obtain the average duration of the PDU sessions established by the terminal device on each network slice.

28. The method according to claim 27, wherein The average duration is determined based on the sum of the durations of the PDU sessions corresponding to the network slice established by the terminal devices activated under the corresponding network slice and the number of terminal devices activated under the network slice.

29. The method according to claim 13 or 14, wherein Sending the slice-related information to the OAM or core network device includes: According to the cell radio network temporary identifier C-RNTI, cell ID and time information of the terminal device, the slice related information collected by the terminal device is correlated and analyzed with the slice related information collected by the terminal device to obtain a correlation analysis result; Send the association analysis result to the OAM or the core network device.

30. A terminal device, wherein: include: memory for storing computer programs; a transceiver for transmitting and receiving data under the control of the processor; A processor is configured to read the computer program in the memory and perform the following operations: Get slice related information; Slice-related information is sent to the access network device, where the slice-related information indicates the performance of the network slice.

31. The terminal device according to claim 30, wherein: The slice-related information includes any one or more of the following information: Absolute time information of the access network device sending the configuration information; Relative time relative to the time of receiving the configuration information; Rejected network slices; The data radio bearer corresponding to the rejected network slice; Number of times network slices were rejected; Cells that reject network slicing; Reasons for rejecting network slicing; The released protocol data unit PDU session; Number of times a PDU session is released; The network slice corresponding to the released PDU session; The number of network slices corresponding to the released PDU session; Release the cell ID of the PDU session corresponding to the network slice; Release the tracking area code TAC of the cell corresponding to the PDU session of the network slice; The cell radio network temporary identifier C-RNTI of the terminal device.

32. The terminal device according to claim 30 or 31, wherein: The processor is configured to: The slice-related information is sent to the access network device in the form of a single report or a report list.

33. The terminal device according to claim 30 or 31, wherein: The acquisition of slice related information occurs in at least one of the following processes: Register a cell, switch a cell, add a secondary cell, change a secondary cell, establish a PDU session, and modify a PDU session.

34. The terminal device according to claim 30 or 31, wherein: The processor is further configured to: Receive configuration information, where the configuration information is used to instruct collection of slice-related information.

35. The terminal device according to claim 34, wherein: The configuration information is carried in a radio resource control RRC reconfiguration message and / or an RRC recovery message.

36. The terminal device according to claim 34, wherein: The configuration information includes one or more of the following information: The time when the terminal device collects slice related information; Absolute time information of sending the configuration information by the access network device; The data radio bearer DRB list to be collected by the terminal device; A list of network slices to be collected by the terminal device; The area range collected by the terminal device; List of public land mobile networks (PLMNs) or independent non-public networks (SNPNs) that are allowed to report slice related information; The configuration type of the terminal device recording slice related information includes event triggering, and the event triggering includes a change in the cell where the terminal device is located; when the terminal device performs cell registration, a network slice is rejected; when the terminal device performs cell switching, secondary cell addition, or secondary cell change, a PDU session corresponding to a slice is released; The triggering conditions for the terminal device to report slice-related information, including a threshold value for the number of rejected network slices; The threshold for the number of released network slice related PDU sessions.

37. The terminal device according to claim 36, wherein: If the configuration information includes a triggering condition for the terminal device to report slice related information, the processor is configured to: When the triggering condition for the terminal device to report slice related information is met, the slice related information is sent to the access network device.

38. The terminal device according to claim 36, wherein: If the configuration information includes the time for the terminal device to collect slice related information, the processor is further configured to: The time for the terminal device to collect slice-related information is set to the value of the timer for collecting slice-related information, and the timer is started.

39. The terminal device according to claim 38, wherein: The processor is further configured to: When the timer expires, the configuration information is released, and the slice related information collected within the validity period of the timer is deleted after a preset time period; Alternatively, when the reserved memory resources are full, the configuration information is released, and the slice related information collected within the effective time of the timer is deleted after a preset time period.

40. The terminal device according to claim 30 or 31, wherein: The processor is further configured to: Send first information to the access network device, where the first information indicates that slice-related information is available.

41. The terminal device according to claim 40, wherein: The first information may be carried in an RRC creation complete message, an RRC recovery complete message, an RRC reconfiguration complete message or an RRC reconstruction complete message.

42. An access network device, wherein: include: memory for storing computer programs; a transceiver for transmitting and receiving data under the control of the processor; A processor is configured to read the computer program in the memory and perform the following operations: Obtain slice related information, including slice related information reported by the terminal device; Send slice-related information to operation, maintenance and management (OAM) and / or core network equipment.

43. The terminal device according to claim 42, wherein: The slice-related information includes any one or more of the following: Absolute time information of the access network device sending the configuration information; Relative time relative to the time of receiving the configuration information; Rejected network slices; The data radio bearer corresponding to the rejected network slice; Number of times network slices were rejected; Cells that reject network slicing; Reasons for rejecting network slicing; The released protocol data unit PDU session; Number of times a PDU session is released; The network slice corresponding to the released PDU session; The number of network slices corresponding to the released PDU session; Release the cell ID of the PDU session corresponding to the network slice; Release the tracking area code TAC of the cell corresponding to the PDU session of the network slice; The cell radio network temporary identifier C-RNTI of the terminal device.

44. The terminal device according to claim 42 or 43, wherein: The slice-related information is sent in the form of a single report or a report list.

45. The terminal device according to claim 42 or 43, wherein: The acquisition of slice related information occurs in at least one of the following processes: Register a cell, switch a cell, add a secondary cell, change a secondary cell, establish a PDU session, and modify a PDU session.

46. The terminal device according to claim 42 or 43, wherein: The processor is further configured to: Indicates configuration information, where the configuration information is used to instruct the collection of slice related information.

47. The terminal device according to claim 46, wherein: The configuration information is carried in a radio resource control RRC reconfiguration message and / or an RRC recovery message.

48. The terminal device according to claim 46, wherein: The configuration information includes one or more of the following information: The time when the terminal device collects slice related information; Absolute time information of sending the configuration information by the access network device; The data radio bearer DRB list to be collected by the terminal device; A list of network slices to be collected by the terminal device; The area range collected by the terminal device; List of public land mobile networks (PLMNs) or independent non-public networks (SNPNs) that are allowed to report slice related information; The configuration type of the terminal device recording slice related information, the configuration type including event triggering, and the event triggering including a change in the cell where the terminal device is located; During the process of the terminal device performing cell registration, a network slice is rejected; during the process of the terminal device performing cell switching, secondary cell addition or secondary cell change, a PDU session corresponding to a slice is released; The triggering conditions for the terminal device to report slice-related information, including a threshold value for the number of rejected network slices; The threshold for the number of released network slice related PDU sessions.

49. The terminal device according to claim 48, wherein: If the configuration information includes a triggering condition for the terminal device to report slice related information, the slice related information is reported when the triggering condition for the terminal device to report slice related information is met.

50. The terminal device according to claim 49, wherein: If the configuration information includes the time for the terminal device to collect slice related information, the slice related information includes slice related information collected after the timer for collecting slice related information is started.

51. The terminal device according to claim 42 or 43, wherein: The processor is further configured to: First information is obtained, where the first information indicates that slice-related information is available.

52. The terminal device according to claim 51, wherein: The first information may be carried in an RRC creation complete message, an RRC recovery complete message, an RRC reconfiguration complete message or an RRC reconstruction complete message.

53. The terminal device according to claim 42 or 43, wherein: The slice-related information also includes slice-related information collected by the access network device itself.

54. The terminal device according to claim 53, wherein: The slice-related information collected by the access network device itself includes at least one or more of the following: The network slice corresponding to the released PDU session; The number of network slices corresponding to the released PDU session; Released PDU session; The number of released PDU sessions; Release the cell ID of the PDU session corresponding to the network slice; The reason why the PDU session corresponding to the network slice is released; Tracking area code TAC corresponding to the cell.

55. The terminal device according to claim 54, wherein: The slice-related information collected by the access network device itself also includes: The number of terminal devices activated on each network slice corresponding to the cell within a preset time period, and / or the duration of the PDU session established by the terminal device on each network slice.

56. The terminal device according to claim 55, wherein: The processor is further configured to: Obtain the average duration of the PDU sessions established by the terminal device on each network slice.

57. The terminal device according to claim 56, wherein: The average duration is determined based on the sum of the durations of the PDU sessions corresponding to the network slice established by the terminal devices activated under the corresponding network slice and the number of terminal devices activated under the network slice.

58. The terminal device according to claim 42 or 43, wherein: The processor is configured to: According to the cell radio network temporary identifier C-RNTI, cell ID and time information of the terminal device, the slice related information collected by the terminal device is correlated and analyzed with the slice related information collected by the terminal device to obtain a correlation analysis result; Send the correlation analysis result to the OAM or core network device.

59. A processor-readable storage medium, wherein: The processor-readable storage medium stores a computer program, and the computer program is used to enable a processor to execute the information processing method according to any one of claims 1 to 12, or to execute the information processing method according to any one of claims 13 to 29.

Images