WO2024041288A1 - Procédé de demande de tranche et dispositif terminal - Google Patents

Procédé de demande de tranche et dispositif terminal Download PDF

Info

Publication number
WO2024041288A1
WO2024041288A1 PCT/CN2023/109170 CN2023109170W WO2024041288A1 WO 2024041288 A1 WO2024041288 A1 WO 2024041288A1 CN 2023109170 W CN2023109170 W CN 2023109170W WO 2024041288 A1 WO2024041288 A1 WO 2024041288A1
Authority
WO
WIPO (PCT)
Prior art keywords
network slice
information
slice
network
rejection
Prior art date
Application number
PCT/CN2023/109170
Other languages
English (en)
Chinese (zh)
Inventor
卫威
Original Assignee
哲库科技(北京)有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 哲库科技(北京)有限公司 filed Critical 哲库科技(北京)有限公司
Publication of WO2024041288A1 publication Critical patent/WO2024041288A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration

Definitions

  • the present application relates to the field of communications, and more specifically, to a slice request method and a terminal device.
  • the fifth generation mobile communication technology (5G, 5th Generation Mobile Communication Technology) system introduces the new feature of network slicing, which is also a representative function of the 5G system; its purpose is to By dividing different network slices and allocating different network resources, such as bandwidth, speed, service quality, etc., different business needs can occupy network resources more reasonably.
  • 5G 5th Generation Mobile Communication Technology
  • a terminal device initiates registration in the network, it needs to first request network slicing; how the terminal device requests network slicing is a technical issue that needs to be solved.
  • Embodiments of the present application provide a slicing request method and a terminal device for requesting network slicing.
  • Embodiments of the present application provide a slicing request method, which includes: a terminal device requests a network slicing based on slicing rejection information based on a Network Slicing Concurrent Registration Group (NSSRG).
  • NSSRG Network Slicing Concurrent Registration Group
  • Embodiments of the present application provide a slice configuration method, which includes: a network device sends slice rejection information based on a network slice concurrent registration group.
  • An embodiment of the present application provides a terminal device, including: a slice request module, configured to request a network slice based on the rejection information of the network slice concurrent registration group.
  • An embodiment of the present application provides a network device, including: a sending module, configured to send rejection information based on network slicing concurrent registration groups.
  • An embodiment of the present application provides a device, including a processor and a memory.
  • the memory is used to store computer programs, and the processor is used to call and run the computer program stored in the memory, so that the device performs the above method.
  • An embodiment of the present application provides a chip for implementing the above method.
  • the chip includes: a processor, configured to call and run a computer program from the memory, so that the device installed with the chip executes the above method.
  • Embodiments of the present application provide a computer-readable storage medium for storing a computer program, which when the computer program is run by a device, causes the device to perform the above method.
  • An embodiment of the present application provides a computer program product, which includes computer program instructions, and the computer program instructions cause a computer to execute the above method.
  • An embodiment of the present application provides a computer program that, when run on a computer, causes the computer to perform the above method.
  • the terminal device can request network slicing based on the NSSRG-based rejection slicing information, thereby realizing network slicing requests in NSSRG units, requesting network slices associated with NSSRG, and realizing precise requests for network slicing.
  • Figure 1 is a schematic diagram of an application scenario according to an embodiment of the present application.
  • Figure 2 is a schematic flow chart of a slice request method 200 according to an embodiment of the present application.
  • Figure 3 is an implementation flow chart according to Embodiment 1 of the present application.
  • Figure 4 is an implementation flow chart according to Embodiment 2 of the present application.
  • Figure 5 is an implementation flow chart according to Embodiment 3 of the present application.
  • Figure 6 is a schematic flow chart of a slice configuration method 600 according to an embodiment of the present application.
  • Figure 7 is a schematic block diagram of a terminal device 700 according to an embodiment of the present application.
  • Figure 8 is a schematic block diagram of a terminal device 800 according to an embodiment of the present application.
  • Figure 9 is a schematic block diagram of a network device 900 according to an embodiment of the present application.
  • Figure 10 is a schematic structural diagram of a communication device 1000 according to an embodiment of the present application.
  • Figure 11 is a schematic structural diagram of a chip 1100 according to an embodiment of the present application.
  • Figure 12 is a schematic block diagram of a communication system 1200 according to an embodiment of the present application.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • WCDMA broadband code division multiple access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • LTE-A Advanced long term evolution
  • NR New Radio
  • NTN Non-Terrestrial Networks
  • UMTS Universal Mobile Telecommunication System
  • WLAN Wireless Local Area Networks
  • WiFi wireless fidelity
  • 5G fifth-generation communication
  • the communication system in the embodiment of the present application can be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, a dual connectivity (Dual Connectivity, DC) scenario, or a standalone (Standalone, SA)Network scene.
  • Carrier Aggregation, CA Carrier Aggregation, CA
  • DC Dual Connectivity
  • SA Standalone
  • the communication system in the embodiment of the present application can be applied to unlicensed spectrum, where the unlicensed spectrum can also be considered as shared spectrum; or, the communication system in the embodiment of the present application can also be applied to licensed spectrum , among which, licensed spectrum can also be considered as non-shared spectrum.
  • the embodiments of this application describe various embodiments in combination with network equipment and terminal equipment.
  • the terminal equipment may also be called user equipment (User Equipment, UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent or user device, etc.
  • User Equipment User Equipment
  • the terminal device can be a station (ST) in the WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, or a personal digital processing unit.
  • ST station
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • the terminal device can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as aircraft, balloons and satellites). superior).
  • the terminal device may be a mobile phone (Mobile Phone), a tablet computer (Pad), a computer with a wireless transceiver function, a virtual reality (Virtual Reality, VR) terminal device, or an augmented reality (Augmented Reality, AR) terminal.
  • Equipment wireless terminal equipment in industrial control, wireless terminal equipment in self-driving, wireless terminal equipment in remote medical, wireless terminal equipment in smart grid , wireless terminal equipment in transportation safety, wireless terminal equipment in smart city, or wireless terminal equipment in smart home, etc.
  • the terminal device may also be a wearable device.
  • Wearable devices can also be called wearable smart devices. It is a general term for applying wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes, etc.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not just hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-sized devices that can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, and those that only focus on a certain type of application function and need to cooperate with other devices such as smartphones.
  • the network device may be a device used to communicate with mobile devices.
  • the network device may be an access point (Access Point, AP) in WLAN, or a base station (Base Transceiver Station, BTS) in GSM or CDMA.
  • BTS Base Transceiver Station
  • it can be a base station (NodeB, NB) in WCDMA, or an evolutionary base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and an NR network network equipment (gNB) or network equipment in the future evolved PLMN network or network equipment in the NTN network, etc.
  • AP Access Point
  • BTS Base Transceiver Station
  • NodeB, NB base station
  • Evolutional Node B, eNB or eNodeB evolution base station
  • gNB NR network network equipment
  • the network device may have mobile characteristics, for example, the network device may be a mobile device.
  • the network device can be a satellite or balloon station.
  • the satellite can be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geosynchronous orbit (geostationary earth orbit, GEO) satellite, a high elliptical orbit (High Elliptical Orbit, HEO) satellite ) satellite, etc.
  • the network device may also be a base station installed on land, water, etc.
  • network equipment can provide services for a cell, and terminal equipment communicates with the network equipment through transmission resources (for example, frequency domain resources, or spectrum resources) used by the cell.
  • the cell can be a network equipment ( For example, the cell corresponding to the base station), the cell can belong to the macro base station, or it can belong to the base station corresponding to the small cell (Small cell).
  • the small cell here can include: urban cell (Metro cell), micro cell (Micro cell), pico cell ( Pico cell), femto cell (Femto cell), etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-rate data transmission services.
  • Figure 1 illustrates a communication system 100.
  • the communication system includes a network device 110 and two terminal devices 120.
  • the communication system 100 may include multiple network devices 110 , and the coverage of each network device 110 may include other numbers of terminal devices 120 , which is not limited in this embodiment of the present application.
  • the communication system 100 may also include other network entities such as Mobility Management Entity (MME), Access and Mobility Management Function (AMF), etc.
  • MME Mobility Management Entity
  • AMF Access and Mobility Management Function
  • network equipment may include access network equipment and core network equipment. That is, the wireless communication system also includes multiple core networks used to communicate with access network equipment.
  • the access network equipment can be a long-term evolution (long-term evolution, LTE) system, a next-generation (mobile communication system) (next radio, NR) system or authorized auxiliary access long-term evolution (LAA- Evolutionary base station (evolutional node B, abbreviated as eNB or e-NodeB) macro base station, micro base station (also known as "small base station"), pico base station, access point (access point, AP), Transmission point (TP) or new generation base station (new generation Node B, gNodeB), etc.
  • LTE long-term evolution
  • NR next-generation
  • LAA- Evolutionary base station evolutional node B, abbreviated as eNB or e-NodeB
  • eNB next-generation
  • NR next-generation
  • LAA- Evolutionary base station evolutional node B, abbre
  • the communication equipment may include network equipment and terminal equipment with communication functions.
  • the network equipment and terminal equipment may be specific equipment in the embodiments of the present application, which will not be described again here; the communication equipment may also include a communication system.
  • Other devices in the network such as network controllers, mobility management entities and other network entities, are not limited in the embodiments of this application.
  • the "instruction” mentioned in the embodiments of this application may be a direct instruction, an indirect instruction, or an association relationship.
  • a indicates B which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B. relation.
  • correlate can mean that there is a direct correspondence or indirect correspondence between the two, it can also mean that there is an associated relationship between the two, or it can mean indicating and being instructed, configuration and being. Configuration and other relationships.
  • the 5G system introduces the new feature of network slicing, which is also a representative function of the 5G system. Its purpose is to divide different network slices in the same network environment and allocate different network resources, such as bandwidth, speed, service quality, etc., so that different business needs can occupy network resources more reasonably.
  • a UE When a UE initiates registration in a public land mobile network (PLMN, public land mobile network), the UE needs to save the available slice information under the network (such as the available network slice selection auxiliary information (Allowed NSSAI, Allowed Network Slice Selection Assistance Information)) and configured slice information (such as configured NSSAI (Configured NSSAI)), or default configured slice information (such as default configured NSSAI (Default Configured NSSAI)), exclude the rejected slices Information (such as rejected NSSAI (Rejected NSSAI)), combined with the UE's own policy, carries the UE requested information in the non-access layer (NAS, Non-Access-Stratum) message (such as registration request (Registration Request)) of the registration request.
  • NAS Non-Access-Stratum
  • the network confirms the configured slicing information (such as configured NSSAI), available slicing information (such as available NSSAI), and rejected slicing information (such as rejected NSSAI) of the UE under the current network based on the requested slicing information, and responds in the registration response Configure this information to the UE in the NAS message (such as request response (Registration Accept)).
  • configured NSSAI such as configured NSSAI
  • available slicing information such as available NSSAI
  • rejected slicing information such as rejected NSSAI
  • Each of the above NSSAI can contain one or more single network slice selection auxiliary information (S-NSSAI, Single NSSAI).
  • S-NSSAI Single NSSAI
  • the UE can then select a specific S-NSSAI available in the current network to initiate a data session based on these configuration information and its own policies.
  • NSSRG Network Slice Simultaneous Registration Group
  • the NSSRG information can contain one or more S-NSSAI associated NSSRG values (NSSRG values for S-NSSAI). This information is further defined in the protocol as shown in Table 2:
  • an S-NSSAI can be associated with one or more NSSRG values to indicate which NSSRGs an S-NSSAI is associated with.
  • NSSRG information is associated with the configuration slice (Configured NSSAI) under the current network. That is to say, all S-NSSAI configured under the current network can each be associated with one or more NSSRGs.
  • the available slices (such as available NSSAI) are a subset of the slices configured in the current network, so each available S-NSSAI is associated with one or more NSSRGs.
  • the slices requested when a user initiates registration are generally associated with the same NSSRG. Therefore, after each successful registration on the network side, the available slices assigned to the user will be associated with the same NSSRG.
  • Each data session initiated by the user can also be associated with a specific NSSRG.
  • Some NSSRG. NSSRG can be used to classify and manage users' slice configurations. Based on specific implementation strategies, users can confirm which associated slices they can use on a specific NSSRG, and then configure the corresponding available slices (such as Allowed NSSAI) to the user. The user can then follow up Data sessions can only be initiated on the corresponding associated NSSRG. Different users can only use the available slices associated with their own available NSSRGs based on their different subscription information, and will not access slices associated with other NSSRGs, thus achieving further refined management of network slices.
  • the current slicing rejection definition is still based on S-NSSAI, that is to say, slicing requests can only be rejected based on specific S-NSSAI. If an S-NSSAI is associated with multiple NSSRGs and the network rejects it within the current protocol framework, it cannot be rejected based on the NSSRGs.
  • the current terminal requests slices on Group 1 when registering, but not on Group 2; if the requested S-NSSAI is associated with both Group 1 and Group 2, Group 2, the network side is rejecting When rejecting the slice request, S-NSSAI will be rejected, which will cause the slices available to the end user on group 2 to also be rejected.
  • the S-NSSAI requested in group 2 will exclude the previously rejected S-NSSAI, so the number of slices currently requested in group 2 will be The number of slices that can actually be requested by group 2 is less than the number, that is, the S-NSSAI that was previously rejected when initiating a slice request on group 1 cannot be requested on group 2. It can be seen that the existing request and reject slices are implemented in units of S-NSSAI, and in fact, fine management of slices based on NSSRG is not achieved.
  • FIG 2 is a schematic flowchart of a slice request method 200 according to an embodiment of the present application. This method can optionally be applied to the system shown in Figure 1, but is not limited thereto. The method includes at least part of the following.
  • the terminal device requests network slicing based on the slicing rejection information based on the network slicing concurrent registration group.
  • embodiments of the present application can implement precise management and requesting network slicing based on NSSRG.
  • the NSSRG-based rejection slice information can be configured by the network side, for example, by the AMF.
  • NSSRG-based reject slice information is carried in extended reject slice information.
  • extended rejected slice information can select auxiliary information (Extended Rejected NSSAI) for extended rejected network slices.
  • the extended deny slice information (such as extended deny NSSAI) may carry one or more NSSRG-based deny slice information, where the NSSRG-based deny slice information may be NSSRG-based S-NSSAI.
  • the extended deny S-NSSAI carrying one or more NSSRG-based slice deny information is shown in Table 4:
  • the value of the list type (Type of list) of the extended deny NSSAI shown in Table 4 is the first value, which is used to indicate that the extended deny NSSAI is an extended deny NSSAI that carries NSSRG-based deny slice information.
  • two types of extended rejection NSSAI have been defined, one of which is a list of rejection S-NSSAI, the value of its list type (Type of list) is 000; the other is to add a backoff timer
  • the duration extension rejects NSSAI, whose Type of list value is 001.
  • the value of the list type (Type of list) (i.e., the above-mentioned first value) can be other than the aforementioned 000 and a value other than 001, for example, the first value is 010.
  • the extended rejected NSSAI proposed in the embodiment of this application carries one or more rejected S-NSSAI based on NSSRG (Rejected S-NSSAI with NSSRG).
  • NSSRG Rejected S-NSSAI with NSSRG
  • its content is as shown in Table 5:
  • Table 5 contains information about S-NSSAI 1 and multiple NSSRG values, indicating that S-NSSAI 1 is rejected when associated with NSSRG 1, associated with NSSRG 2, ... or associated with NSSRG y.
  • NSSRG-based rejection of slice information can achieve accurate management of network slices based on the combined information of S-NSSAI and NSSRG.
  • S-NSSAI A is associated with NSSRG 1 and NSSRG 2; when the terminal device requests S-NSSAI A on NSSRG 1, it is rejected by the network device.
  • the terminal device receives and saves the NSSRG-based rejection slicing information sent by the network device.
  • the NSSRG-based rejection slicing information is sent by the network device.
  • the rejected slice information includes the information of S-NSSAI A and NSSRG 1; later, when the terminal device switches to NSSRG 2, it re-initiates the registration request, because the rejected slice information based on NSSRG only contains the information of S-NSSAI A and NSSRG 1. , but does not contain the information of S-NSSAI A and NSSRG 2, so the terminal device can request the S-NSSAI A on NSSRG 2. It can be seen that the embodiments of the present application are beneficial to accurately controlling the network slice associated with the NSSRG.
  • the slice request method proposed in the embodiment of this application also includes: a terminal device and recording based on Rejection slicing information for NSSRG.
  • the NSSRG-based rejection slicing information can be sent by the network device (such as AMF) through the registration response (Registration Accept) or the configuration update command (Configuration Update Command).
  • the terminal device receives the registration response or the configuration update command, and the registration response or The configuration update command carries the NSSRG-based rejection slicing information.
  • the terminal device can update the previously saved available NSSAI. For example, the terminal device deletes the first S-NSSAI from the available NSSAI; where the first S-NSSAI is associated with the third S-NSSAI.
  • the S-NSSAI of an NSSRG, and the NSSRG-based rejection slice information includes the information of the first S-NSSAI and the first NSSRG.
  • the first NSSRG may be the NSSRG currently requested by the UE.
  • the terminal device can check whether each of the current Allowed S-NSSAI (in the available NSSAI) and its currently associated NSSRG group has been rejected. If so, delete the Allowed S-NSSAI from the Allowed NSSAI. If the S-NSSAI is already associated with an activated PDU session, you can release the PDU session first and then delete the S-NSSAI.
  • the terminal device requests network slicing based on NSSRG-based rejection slicing information, which may include:
  • the terminal device does not request the network slice to be requested associated with the third NSSRG; or,
  • the terminal device requests the network slice to be requested associated with the third NSSRG.
  • the terminal device does not request the S-NSSAI to be requested associated with the third NSSRG; or,
  • the terminal device requests to associate the S-NSSAI to be requested of the third NSSRG.
  • the terminal device may initiate an update registration request, and request the second S-NSSAI associated with the second NSSRG in the update registration request, where the rejection slice information is based on the NSSRG. does not contain the information of the second S-NSSAI and the second NSSRG. That is to say, when the terminal device initiates an update registration request on a certain NSSRG, the requested S-NSSAI and the information of the NSSRG are not included in the NSSRG-based rejection slicing information.
  • Network equipment such as AMF
  • AMF Access Management Function
  • FIG 3 is an implementation flow chart according to Embodiment 1 of the present application, including the following steps:
  • the UE registers under the current PLMN for the first time. At this time, the UE does not have available slices (Allowed NSSAI) and configured slices (Configured NSSAI) records under the current PLMN. The UE uses the default configured slice (Default Configured NSSAI) as the requested slice (Requested NSSAI). ) initiates a registration request.
  • AMF issues available slices (Allowed NSSAI), configured slices (Configured NSSAI), and rejects slices in the registration response (Registration Accept) (such as rejection slice information that is not based on NSSRG in related technologies).
  • This application implements The example proposed rejects slice information based on NSSRG and slice-associated NSSRG information.
  • the NSSRG-based rejection slice information can be carried in the extended rejection NSSAI shown in Table 4.
  • the UE records the above information issued by the AMF. For example, the UE records available slices (Allowed NSSAI), configured slices (Configured NSSAI), rejected slices, rejected slice information based on NSSRG, etc.
  • the UE initiates a registration request again. Based on the above recorded information, when filling in the requested slice (Requested NSSAI), you can check whether the requested S-NSSAI and the NSSRG associated with the S-NSSAI are in the NSSRG-based rejected slice information; If so, the S-NSSAI is not requested; otherwise, the S-NSSAI can be requested.
  • Requested NSSAI the requested S-NSSAI and the NSSRG associated with the S-NSSAI are in the NSSRG-based rejected slice information; If so, the S-NSSAI is not requested; otherwise, the S-NSSAI can be requested.
  • Figure 4 is an implementation flow chart according to Embodiment 2 of the present application, including the following steps:
  • the UE is currently in the registration state, and one or some of the originally available NSSRGs need to be changed to unavailable.
  • the AMF issues a configuration update command (Configuration Update Command) to the UE, which carries the NSSRG-based rejection slice information to be updated.
  • the NSSRG-based rejected slice information can be updated additively, that is, the AMF issues a new NSSRG-based rejected slice list, and new unavailable NSSRG records can be added based on the last one.
  • the UE receives and records the NSSRG-based rejection slice information. Similarly, the UE can also adopt an additive recording method when recording, that is, adding new NSSRG-based rejection slice information on the basis of the original record. Furthermore, the UE checks whether each of the current Allowed S-NSSAI and its currently associated NSSRG group has been rejected. If it is, remove it from Allowed NSSAI. If the S-NSSAI is already associated with an activated PDU session, the PDU session needs to be released locally first.
  • the UE can initiate update registration and include the requested slice (Requested NSSAI) carried in the update registration request. Specifically, the following steps are adopted:
  • the UE can initiate an update registration request with the unrejected slice in the default configuration slice (Default Configured NSSAI).
  • the configuration slices under the current PLMN include S-NSSAI 1, S-NSSAI 2, and S-NSSAI 3.
  • the UE checks whether the information of NSSRG A and S-NSSAI 1 is in the currently saved NSSRG-based rejection slice information.
  • the UE can initiate an update registration request under NSSRG A, and the update registration request carries the identifier of S-NSSAI 1; if the information of NSSRG A and S-NSSAI 1 is in the NSSRG-based rejection slice information, the UE can further search for NSSRG A and S-NSSAI 2; if the information of NSSRG A and S-NSSAI 1, the information of NSSRG A and S-NSSAI 2, the information of NSSRG A and S-NSSAI 3 are not in the rejected slice information based on NSSRG, the UE Step (2) can be performed to continue to search for unrejected slices from the Default Configured NSSAI and initiate an update registration request.
  • the search method can refer to the aforementioned step (1), which will not be described again here.
  • the above describes how the terminal device receives and saves the NSSRG-based rejection slicing information when the originally available NSSRG is changed to unavailable. Specifically, an updated addition method can be used, and the terminal device receives and records the new NSSRG-based rejection slicing information. When the originally unavailable NSSRG is to be changed to be available, the embodiment of the present application can delete all the previously saved NSSRG-based rejected slicing information, and receive and record the new NSSRG-based rejected slicing information.
  • the slice request method proposed in the embodiment of this application also includes:
  • the terminal device receives a configuration update command used to notify changes in network slice subscription information
  • the terminal device clears the NSSRG-based rejected slice information. Specifically, the terminal device may clear locally saved NSSRG-based rejected slicing information.
  • the method may further include: the terminal device initiates an update registration request, and the terminal device receives NSSRG-based rejection slicing information.
  • Figure 5 is an implementation flow chart according to Embodiment 3 of the present application, including the following steps:
  • AMF sends a configuration update command (Configuration Update Command) to the UE for network switching.
  • Configuration Update Command a configuration update command
  • the configuration update command Configuration Update Command
  • the UE clears the current NSSRG-based rejected slice list, and may clear other types of rejected slice lists. UE and initiates update registration.
  • the AMF sends a registration response to the UE, and carries the new available slice (Allowed NSSAI) and the new NSSRG-based rejected slice list in the registration response.
  • the UE receives and records the aforementioned information, such as new available slices (Allowed NSSAI) and a new NSSRG-based rejected slice list.
  • the NSSRG-based slicing rejection information proposed in the embodiments of this application is only effective under the current PLMN.
  • the terminal device changes the PLMN the current NSSRG-based slicing rejection information is deleted.
  • the terminal device when the terminal device deregisters, deletes the NSSRG-based rejection slicing information. For example, the terminal device deletes the currently saved NSSRG-based denied slice list when it shuts down, restarts, enters airplane mode, removes the USIM card, or initiates de-registration on the network side. Afterwards, the terminal device can wait for the AMF to deliver a new list. For example, the terminal device re-initiates a registration request, and the AMF delivers new NSSRG-based rejection slice information in the registration response.
  • FIG. 6 is a schematic flowchart of a slice configuration method 600 according to an embodiment of the present application. The method includes at least part of the following.
  • the network device sends slicing rejection information based on the network slicing concurrent registration group.
  • the network device may include an AMF.
  • the network device sends NSSRG-based slicing rejection information to the terminal device.
  • the NSSRG-based slicing rejection information may include a combination of multiple slicing information and NSSRG, for the terminal device to request network slicing based on the NSSRG-based slicing rejection information. , thereby achieving precise management of network slicing based on NSSRG.
  • the rejected slice information of the NSSRG is carried in the extended rejected slice information.
  • the extended reject slice information includes an extended reject NSSAI
  • the value of the list type of the extended reject NSSAI is the first value.
  • the first value is used to indicate that the extended reject NSSAI is an extended reject NSSAI that carries the reject slice information of the NSSRG.
  • the NSSRG-based rejection slice information includes single network slice selection assistance information S-NSSAI associated with the NSSRG.
  • the network device sends NSSRG-based rejection slicing information, including:
  • the network device sends a registration response or a configuration update command, which carries the NSSRG-based rejection slicing information described in the registration response or configuration update command.
  • the network device when the fourth NSSRG of the terminal device is changed from available to unavailable, the network device sends a configuration update command to the terminal device, and the configuration update command carries the configuration based on the fourth NSSRG. Reject slice information.
  • the network device can use an additive update method to issue new NSSRG-based rejection slicing information; the UE can locally save the basis of the NSSRG-based rejection slicing information. Above, add the new NSSRG-based rejected slicing information.
  • the network device when the fifth NSSRG of the terminal device is changed from unavailable to available, the network device sends a configuration update command to the terminal device, and the configuration update command is used to notify network slice subscription information changes .
  • the network device can notify the UE to delete the originally saved NSSRG-based rejection slice information, and then re-issue a new NSSRG-based rejection slice. information.
  • the method further includes: in the presence of new NSSRG-based rejection slicing information, the network device sends the new NSSRG-based rejection slicing information.
  • FIG. 7 is a schematic block diagram of a terminal device 700 according to an embodiment of the present application.
  • the terminal device 700 may include:
  • the slice request module 710 is configured to request a network slice based on the rejection information of the network slice concurrent registration group (NSSRG).
  • NSSRG-based deny slicing information is configured by the network device.
  • NSSRG-based reject slice information is carried in extended reject slice information.
  • the extended deny slice information includes extended deny network slice selection assistance information (NSSAI), and the value of the list type of the extended deny NSSAI is the first value.
  • NSSAI extended deny network slice selection assistance information
  • the NSSRG-based reject slice information includes NSSRG-based single network slice selection assistance information S-NSSAI.
  • FIG. 8 is a schematic block diagram of a terminal device 800 according to an embodiment of the present application.
  • the terminal device 800 includes one or more features of the terminal device 700 described above.
  • the embodiment of this application also includes:
  • the receiving and information maintenance module 820 is used to receive and record NSSRG-based rejected slice information.
  • the receiving and information maintenance module 820 is configured to receive a registration response or a configuration update command, where the registration response or configuration update command carries the NSSRG-based rejection slicing information.
  • the receiving and information maintenance module 820 is also used to delete the first S-NSSAI from the available NSSAI; wherein the first S-NSSAI is the S-NSSAI associated with the first NSSRG, and the rejection based on the NSSRG
  • the slice information includes information about the first S-NSSAI and the first NSSRG.
  • the slice request module 710 is also configured to initiate an update registration request when the available NSSAI is cleared, and request the second S-NSSAI associated with the second NSSRG in the update registration request, wherein based on the NSSRG The rejected slice information does not contain the information of the second S-NSSAI and the second NSSRG.
  • the receiving and information maintenance module 820 is configured to receive a configuration update command for notifying network slice subscription information changes, and clear the NSSRG-based rejected slice information.
  • the slice request module 710 is used to initiate an update registration request.
  • it also includes:
  • the first deletion module 830 is configured to delete the NSSRG-based rejection slice information when the terminal device 800 changes the PLMN.
  • it also includes:
  • the second deletion module 840 is used to delete the NSSRG-based rejection slice information when the terminal device 800 deregisters.
  • slice request module 710 is used to:
  • the NSSRG-based rejection slice information contains information about the network slice to be requested and the third NSSRG, do not request the network slice to be requested associated with the third NSSRG; or,
  • the request is made to associate the network slice to be requested with the third NSSRG.
  • slice request module 710 is used to:
  • the NSSRG-based rejection slice information contains information about the S-NSSAI to be requested and the third NSSRG, do not request the S-NSSAI to be requested associated with the third NSSRG; or,
  • the NSSRG-based rejection slice information does not contain the information of the S-NSSAI to be requested and the third NSSRG, a request is made to associate the S-NSSAI to be requested of the third NSSRG.
  • the terminal device 800 in the embodiment of the present application can implement the corresponding functions of the terminal device in the foregoing method embodiment.
  • each module (sub-module, unit or component, etc.) in the terminal device 800 please refer to the corresponding description in the above method embodiment, and will not be described again here.
  • the functions described with respect to each module (sub-module, unit or component, etc.) in the terminal device 700 and the terminal device 800 in the embodiment of the application can be implemented by different modules (sub-module, unit or component, etc.), or Can be implemented by the same module (submodule, unit or component, etc.).
  • FIG. 9 is a schematic block diagram of a network device 900 according to an embodiment of the present application.
  • the network device 900 may include:
  • the sending module 910 is configured to send NSSRG-based rejection slice information.
  • NSSRG-based reject slice information is carried in extended reject slice information.
  • the extended deny slice information includes an extended deny NSSAI, and the value of the list type of the extended deny NSSAI is the first value.
  • the NSSRG-based rejection slice information includes single network slice selection assistance information S-NSSAI associated with the NSSRG.
  • the sending module 910 is configured to send a registration response or a configuration update command, where the registration response or configuration update command carries NSSRG-based rejection slicing information.
  • the sending module 910 when the fourth NSSRG of the terminal device is changed from available to unavailable, sends a configuration update command to the terminal device, where the configuration update command carries rejection slice information based on the fourth NSSRG.
  • the sending module 910 when the fifth NSSRG of the terminal device is changed from unavailable to available, sends a configuration update command to the terminal device, and the configuration update command is used to notify the change of network slice subscription information.
  • the sending module 910 is also configured to send new NSSRG-based rejected slicing information if there is new NSSRG-based rejected slicing information.
  • network device 900 includes an AMF.
  • the network device 900 in the embodiment of the present application can implement the corresponding functions of the network device in the foregoing method embodiment.
  • each module (sub-module, unit or component, etc.) in the network device 900 please refer to the corresponding description in the above method embodiment, and will not be described again here.
  • the functions described for each module (sub-module, unit or component, etc.) in the network device 900 of the application embodiment can be implemented by different modules (sub-module, unit or component, etc.), or can be implemented by the same module.
  • Figure 10 is a schematic structural diagram of a communication device 1000 according to an embodiment of the present application.
  • the communication device 1000 includes a processor 1010, and the processor 1010 can call and run a computer program from the memory, so that the communication device 1000 implements the method in the embodiment of the present application.
  • communication device 1000 may also include memory 1020.
  • the processor 1010 can call and run the computer program from the memory 1020, so that the communication device 1000 implements the method in the embodiment of the present application.
  • the memory 1020 may be a separate device independent of the processor 1010, or may be integrated into the processor 1010.
  • the communication device 1000 may further include a transceiver 1030, and the processor 1010 may control the transceiver 1030 to communicate with other devices. Specifically, the communication device 1000 may send information or data to other devices, or receive information sent by other devices. information or data.
  • the transceiver 1030 may include a transmitter and a receiver.
  • the transceiver 1030 may further include an antenna, and the number of antennas may be one or more.
  • the communication device 1000 can be a network device according to the embodiment of the present application, and the communication device 1000 can implement the corresponding processes implemented by the network device in the various methods of the embodiment of the present application. For the sake of simplicity, these processes are not mentioned here. Again.
  • the communication device 1000 can be a terminal device in the embodiment of the present application, and the communication device 1000 can implement the corresponding processes implemented by the terminal device in each method of the embodiment of the present application. For simplicity, in This will not be described again.
  • FIG 11 is a schematic structural diagram of a chip 1100 according to an embodiment of the present application.
  • the chip 1100 includes a processor 1110, and the processor 1110 can call and run a computer program from the memory to implement the method in the embodiment of the present application.
  • chip 1100 may also include memory 1120 .
  • the processor 1110 can call and run the computer program from the memory 1120 to implement the method executed by the terminal device or the network device in the embodiment of the present application.
  • the memory 1120 may be a separate device independent of the processor 1110, or may be integrated into the processor 1110.
  • the chip 1100 may also include an input interface 1130.
  • the processor 1110 can control the input interface 1130 to communicate with other devices or chips. Specifically, it can obtain information or data sent by other devices or chips.
  • the chip 1100 may also include an output interface 1140.
  • the processor 1110 can control the output interface 1140 to communicate with other devices or chips. Specifically, it can output information or data to other devices or chips.
  • the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the network device in the various methods of the embodiment of the present application. For the sake of simplicity, they will not be described again. .
  • the chip can be applied to the terminal device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the terminal device in each method of the embodiment of the present application. For the sake of brevity, details will not be repeated here. .
  • the chips used in network equipment and terminal equipment can be the same chip or different chips.
  • chips mentioned in the embodiments of this application may also be called system-on-chip, system-on-a-chip, system-on-chip or system-on-chip, etc.
  • the processor mentioned above can be a general-purpose processor, a digital signal processor (DSP), an off-the-shelf programmable gate array (FPGA), an application specific integrated circuit (ASIC), or Other programmable logic devices, transistor logic devices, discrete hardware components, etc.
  • DSP digital signal processor
  • FPGA off-the-shelf programmable gate array
  • ASIC application specific integrated circuit
  • the above-mentioned general processor may be a microprocessor or any conventional processor.
  • non-volatile memory may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
  • non-volatile memory can be read-only memory (ROM), programmable ROM (PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically removable memory. Erase electrically programmable read-only memory (EPROM, EEPROM) or flash memory.
  • Volatile memory can be random access memory (RAM).
  • the memory in the embodiment of the present application can also be a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is, memories in embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.
  • FIG. 12 is a schematic block diagram of a communication system 1200 according to an embodiment of the present application.
  • the communication system 1200 includes a terminal device 1210 and a network device 1220.
  • the terminal device 1210 can be used to implement the corresponding functions implemented by the terminal device in the above method
  • the network device 1220 can be used to implement the corresponding functions implemented by the network device in the above method.
  • no further details will be given here.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted over a wired connection from a website, computer, server, or data center (such as coaxial cable, optical fiber, Digital Subscriber Line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) means to transmit to another website, computer, server or data center.
  • the computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center integrated with one or more available media.
  • the available media may be magnetic media (eg, floppy disk, hard disk, magnetic tape), optical media (eg, DVD), or semiconductor media (eg, solid state disk (Solid State Disk, SSD)), etc.
  • the size of the sequence numbers of the above-mentioned processes does not mean the order of execution.
  • the execution order of each process should be determined by its functions and internal logic, and should not be used in the embodiments of the present application.
  • the implementation process constitutes any limitation.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente demande concerne un procédé de demande de tranche et un dispositif terminal. Le procédé de demande de tranche comprend les étapes suivantes : un dispositif terminal demande une tranche de réseau selon des informations de tranche rejetées sur la base d'un groupe d'enregistrement simultané de tranche de réseau (NSSRG). La présente demande peut mettre en œuvre une demande de tranche de réseau.
PCT/CN2023/109170 2022-08-26 2023-07-25 Procédé de demande de tranche et dispositif terminal WO2024041288A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211035415.3 2022-08-26
CN202211035415.3A CN115412434B (zh) 2022-08-26 2022-08-26 一种切片请求方法和终端设备

Publications (1)

Publication Number Publication Date
WO2024041288A1 true WO2024041288A1 (fr) 2024-02-29

Family

ID=84162313

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/109170 WO2024041288A1 (fr) 2022-08-26 2023-07-25 Procédé de demande de tranche et dispositif terminal

Country Status (2)

Country Link
CN (1) CN115412434B (fr)
WO (1) WO2024041288A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115412434B (zh) * 2022-08-26 2024-02-09 哲库科技(北京)有限公司 一种切片请求方法和终端设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109951877A (zh) * 2017-12-20 2019-06-28 华为技术有限公司 一种切片信息更新方法及装置
WO2022027209A1 (fr) * 2020-08-04 2022-02-10 Zte Corporation Procédé, dispositif et produit programme d'ordinateur pour la communication sans fil
CN114521336A (zh) * 2019-09-27 2022-05-20 夏普株式会社 用户装置以及核心网装置
CN115412434A (zh) * 2022-08-26 2022-11-29 哲库科技(北京)有限公司 一种切片请求方法和终端设备

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111031571B (zh) * 2018-10-09 2022-01-14 华为技术有限公司 一种网络切片接入控制的方法及装置
CN111586772B (zh) * 2019-02-18 2021-06-22 华为技术有限公司 一种通信方法及装置
CN112737808A (zh) * 2019-10-28 2021-04-30 中兴通讯股份有限公司 一种网络切片实例配置方法和装置
WO2021091285A1 (fr) * 2019-11-06 2021-05-14 Samsung Electronics Co., Ltd. Procédé et appareil pour commander une tranche de réseau dans un système de communication sans fil
CN113709764B (zh) * 2020-05-21 2023-06-27 华为技术有限公司 一种通信方法及装置
CN111885698B (zh) * 2020-07-22 2023-03-28 Oppo广东移动通信有限公司 网络切片注册方法、装置、终端及存储介质
CN114071576A (zh) * 2020-07-28 2022-02-18 中国联合网络通信集团有限公司 网络切片选择方法、系统、计算机设备及存储介质
CN114302492A (zh) * 2020-09-23 2022-04-08 维沃移动通信有限公司 切片请求方法、终端及网络侧设备
EP4218275A1 (fr) * 2020-09-25 2023-08-02 INTEL Corporation Accès efficace à des tranches de réseau d'opérateur unique
CN114501545A (zh) * 2020-10-26 2022-05-13 中国移动通信有限公司研究院 一种切片信息处理方法、装置、设备和存储介质

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109951877A (zh) * 2017-12-20 2019-06-28 华为技术有限公司 一种切片信息更新方法及装置
CN114521336A (zh) * 2019-09-27 2022-05-20 夏普株式会社 用户装置以及核心网装置
WO2022027209A1 (fr) * 2020-08-04 2022-02-10 Zte Corporation Procédé, dispositif et produit programme d'ordinateur pour la communication sans fil
CN115412434A (zh) * 2022-08-26 2022-11-29 哲库科技(北京)有限公司 一种切片请求方法和终端设备

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
NOKIA, NOKIA SHANGHAI BELL, SHARP: "Network slice simultaneous registration group", 3GPP DRAFT; C1-215816, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. CT WG1, no. E-meeting; 20211011 - 20211015, 30 September 2021 (2021-09-30), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052055100 *
VIVO: "Clarification on the confliction between the NSSRG information IE and the Configured NSSAI IE", 3GPP DRAFT; C1-223847, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. CT WG1, no. E-meeting; 20220512 - 20220520, 5 May 2022 (2022-05-05), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052149274 *

Also Published As

Publication number Publication date
CN115412434B (zh) 2024-02-09
CN115412434A (zh) 2022-11-29

Similar Documents

Publication Publication Date Title
JP7290193B2 (ja) 無線端末及び無線端末における方法
EP4033799B1 (fr) Procédé d'émission par relais, terminal relais et terminal distant
WO2020150876A1 (fr) Procédé d'établissement de session, dispositif terminal et dispositif de réseau
WO2022011618A1 (fr) Procédé de traitement d'informations, dispositif terminal et dispositif de réseau
US20230224797A1 (en) Network access method, terminal device, and network device
WO2024041288A1 (fr) Procédé de demande de tranche et dispositif terminal
WO2022160123A1 (fr) Procédé de sélection de mode d'accès, dispositif terminal et dispositif de réseau
WO2022126641A1 (fr) Procédé de communication sans fil, dispositif terminal, premier dispositif de réseau d'accès et élément de réseau
WO2022021165A1 (fr) Procédé de découverte de relais et terminal
CN116965102A (zh) 无线通信方法、终端设备和网络设备
WO2022099475A1 (fr) Procédé de gestion de session, dispositif terminal et dispositif de réseau
WO2022032539A1 (fr) Procédé de relais et terminal
WO2022183317A1 (fr) Procédé d'obtention d'informations de tranche et dispositif terminal
WO2022147681A1 (fr) Procédé de routage auxiliaire, dispositif terminal et dispositif de réseau
WO2022032453A1 (fr) Procédé d'optimisation de radiomessagerie et dispositif de réseau
WO2023272737A1 (fr) Procédé d'accès, dispositif terminal, élément réseau de gestion unifiée des données et premier élément réseau
WO2022266870A1 (fr) Procédé de communication de liaison latérale, dispositif terminal, dispositif de réseau et système de communication
WO2022160272A1 (fr) Procédé de communication sans fil, dispositif de terminal et dispositif de réseau
WO2022151274A1 (fr) Procédé de radiomessagerie et nœud de réseau
US20230090887A1 (en) Relay communication method and device
WO2022217615A1 (fr) Procédé pour entrer dans un état connecté, et dispositif terminal
WO2023142981A1 (fr) Procédé de communication et dispositif associé
EP4216602A1 (fr) Procédé de communication sans fil, dispositif terminal et dispositif de réseau
WO2023070671A1 (fr) Procédé de traitement de service restreint, dispositif terminal et dispositif de réseau
WO2022170558A1 (fr) Procédé de sélection de réseau, dispositif terminal et dispositif de réseau

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23856378

Country of ref document: EP

Kind code of ref document: A1