WO2022021004A1

WO2022021004A1 - Wireless communication method and device

Info

Publication number: WO2022021004A1
Application number: PCT/CN2020/104888
Authority: WO
Inventors: 付喆; 王淑坤; 杨皓睿
Original assignee: Oppo广东移动通信有限公司
Priority date: 2020-07-27
Filing date: 2020-07-27
Publication date: 2022-02-03
Also published as: CN115606247A

Abstract

Provided are a wireless communication method and device. The method comprises: an access network device determining, according to slice information, a result of retrieving a user equipment (UE) context or an access control result. Slice information is taken into consideration in a process of an access network device determining to retrieve an RRC connection, that is, access control is performed on the basis of the slice information, such that where a slice of a terminal device is not supported by the access network device, the terminal device is prevented from releasing an RRC connection resource of a UE after accessing a network, and thus a delay and signaling overheads can be reduced.

Description

Wireless communication method and device

technical field

The embodiments of the present application relate to the field of communication, and more particularly, to wireless communication methods and devices.

Background technique

At present, the access network device only determines whether the retrieval of the user equipment context (retrieve UE context) succeeds or fails according to the user equipment (UE) context, and then determines whether the RRC connection can be recovered.

However, even if the access network device can obtain the user equipment context, the RRC connection may need to be released for other reasons, thereby increasing the delay and signaling overhead.

SUMMARY OF THE INVENTION

Provided are a wireless communication method and device, which avoids acquiring the UE context and then releasing the UE context when the slice of the terminal device is not supported by the access network device, and can reduce time delay and signaling overhead.

In a first aspect, a wireless communication method is provided, including:

The access network device determines a result of restoring the UE context of the user equipment or an access control result according to the slice information.

In a second aspect, an access network device is provided, which is configured to execute the method in the above-mentioned first aspect or each implementation manner thereof. Specifically, the network device includes functional modules for executing the methods in the above-mentioned first aspect or each implementation manner thereof.

In a third aspect, an access network device is provided, including a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory, so as to execute the method in the above-mentioned first aspect or each implementation manner thereof.

In a fourth aspect, a chip is provided, which is used to implement the method in the above-mentioned first aspect or each of its implementation manners. Specifically, the chip includes: a processor for invoking and running a computer program from a memory, so that a device on which the chip is installed executes the method in the first aspect or its respective implementations.

In a fifth aspect, a computer-readable storage medium is provided for storing a computer program, and the computer program causes a computer to execute the method in the above-mentioned first aspect or each of its implementations.

In a sixth aspect, a computer program product is provided, comprising computer program instructions, the computer program instructions cause a computer to perform the method in the first aspect or each of the implementations thereof.

In a seventh aspect, a computer program is provided, which, when run on a computer, causes the computer to execute the method of the above-mentioned first aspect or each of its implementations.

Based on the above technical solutions, the slice information is considered when the access network device determines to restore the RRC connection, that is, the access control is performed based on the slice information. When the slice of the terminal device is not supported by the access network device, all the After the terminal device accesses the network, the RRC connection resources of the UE are released, and further, the delay and signaling overhead can be reduced.

Description of drawings

FIG. 1 is an example of an application scenario of the present application.

2 to 7 are schematic flowcharts of a wireless communication method provided by an embodiment of the present application.

FIG. 8 is a schematic block diagram of an access network device provided by an embodiment of the present application.

FIG. 9 is a schematic block diagram of a communication device provided by an embodiment of the present application.

FIG. 10 is a schematic block diagram of a chip provided by an embodiment of the present application.

detailed description

The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

FIG. 1 is a schematic diagram of an application scenario of an embodiment of the present application.

As shown in FIG. 1 , the communication system 100 may include a terminal device 110 and a network device 120 . The network device 120 may communicate with the terminal device 110 through the air interface. Multi-service transmission is supported between the terminal device 110 and the network device 120 .

It should be understood that the embodiment of the present application only uses the communication system 100 for exemplary description, but the embodiment of the present application is not limited thereto. That is to say, the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: long term evolution (Long Term Evolution, LTE) system, LTE time division duplex (Time Division Duplex, TDD), universal mobile communication system (Universal mobile communication system) Mobile Telecommunication System, UMTS), 5G communication system (also known as New Radio (New Radio, NR) communication system), or future communication systems, etc.

In the communication system 100 shown in FIG. 1 , the network device 120 may be an access network device that communicates with the terminal device 110 . An access network device may provide communication coverage for a particular geographic area, and may communicate with terminal devices 110 (eg, UEs) located within the coverage area.

The network device 120 may be an evolved base station (Evolutional Node B, eNB or eNodeB) in a Long Term Evolution (Long Term Evolution, LTE) system, or a next generation radio access network (Next Generation Radio Access Network, NG RAN) device, Or a base station (gNB) in an NR system, or a wireless controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or the network device 120 can be a relay station, an access point, a vehicle-mounted device, a wearable Devices, hubs, switches, bridges, routers, or network devices in the future evolved Public Land Mobile Network (PLMN).

The terminal device 110 may be any terminal device, which includes, but is not limited to, a terminal device that adopts a wired or wireless connection with the network device 120 or other terminal devices.

For example, the terminal equipment 110 may refer to an access terminal, a user equipment (UE), a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, user agent, or user device. The access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, end devices in 5G networks or end devices in future evolved networks, etc.

The terminal device 110 may be used for device-to-device (Device to Device, D2D) communication.

The wireless communication system 100 may further include a core network device 130 that communicates with the base station, and the core network device 130 may be a 5G core network (5G Core, 5GC) device, for example, an Access and Mobility Management Function (Access and Mobility Management Function). , AMF), another example, authentication server function (Authentication Server Function, AUSF), another example, user plane function (User Plane Function, UPF), another example, session management function (Session Management Function, SMF). Optionally, the core network device 130 may also be an evolved packet core (Evolved Packet Core, EPC) device of an LTE network, for example, a session management function+core network data gateway (Session Management Function+Core Packet Gateway, SMF+PGW- C) Equipment. It should be understood that the SMF+PGW-C can simultaneously implement the functions that the SMF and the PGW-C can implement. In the process of network evolution, the above-mentioned core network equipment may also be called by other names, or a new network entity may be formed by dividing the functions of the core network, which is not limited in this embodiment of the present application.

The various functional units in the communication system 100 may also establish a connection through a next generation network (next generation, NG) interface to implement communication.

For example, the terminal equipment establishes an air interface connection with the access network equipment through the NR interface to transmit user plane data and control plane signaling; the terminal equipment can establish a control plane signaling connection with the AMF through the NG interface 1 (N1 for short); access Network equipment, such as the next generation wireless access base station (gNB), can establish a user plane data connection with the UPF through the NG interface 3 (N3 for short); the access network equipment can establish a control plane signaling with the AMF through the NG interface 2 (N2 for short). connection; UPF can establish a control plane signaling connection with SMF through NG interface 4 (N4 for short); UPF can exchange user plane data with the data network through NG interface 6 (N6 for short); AMF can communicate with SMF through NG interface 11 (N11 for short) The SMF establishes a control plane signaling connection; the SMF can establish a control plane signaling connection with the PCF through the NG interface 7 (N7 for short).

FIG. 1 exemplarily shows one base station, one core network device and two terminal devices. Optionally, the wireless communication system 100 may include multiple base station devices and the coverage area of each base station may include other numbers of terminals equipment, which is not limited in this embodiment of the present application.

It should be understood that, in the embodiments of the present application, a device having a communication function in the network/system can be referred to as a communication device. Taking the communication system 100 shown in FIG. 1 as an example, the communication device may include a network device 120 and a terminal device 110 with a communication function, and the network device 120 and the terminal device 110 may be the devices described above, which will not be repeated here; The communication device may further include other devices in the communication system 100, such as other network entities such as a network controller and a mobility management entity, which are not limited in this embodiment of the present application.

It should also be understood that the terms "system" and "network" are often used interchangeably herein. The term "and/or" in this article is only an association relationship to describe the associated objects, indicating that there can be three kinds of relationships, for example, A and/or B, it can mean that A exists alone, A and B exist at the same time, and A and B exist independently B these three cases. In addition, the character "/" in this document generally indicates that the related objects are an "or" relationship.

It should be noted that, in this application, the RRC connection state of the terminal device may include RRC_INACTIVE (deactivated) state, RRC_IDLE (idle) state and RRC_CONNECTED (connected) state. In the RRC_IDLE state, mobility is UE-based cell selection reselection, paging is initiated by the Core Network (CN), and the paging area is configured by the CN. There is no UE access stratum (Access Stratum, AS) context on the base station side, nor does an RRC connection exist. In the RRC_CONNECTED state, there is an RRC connection, and the UE AS context exists between the base station and the UE. The location of the UE is known to the network device at the specific cell level. Mobility is the mobility of network device control. Unicast data can be transmitted between the UE and the base station. Under RRC_INACTIVE, mobility is UE-based cell selection reselection, there is a connection between CN-NR, UE AS context exists on a certain base station, paging is triggered by Radio Access Network (RAN), based on The paging area of the RAN is managed by the RAN, and the network equipment knows the location of the UE based on the paging area level of the RAN.

In the process of the terminal device recovering from the RRC deactivated state to the RRC connected state, the requesting serving access network device that receives the RRC recovery request will be involved in the process of requesting a context from the last serving access network device (last serving gNB) . The identifier of the terminal device is carried in the RRC resume request (RRCresumeRequest, or RRCresumeRequest1) message, which identifies the wireless network temporary identifier (Identify Radio Network Temporary Identifier, I-RNTI) I-RNTI. The requesting serving access network device that receives the RRC recovery request determines the identifier of the last serving access network device through the identifier of the terminal device, and requests the last serving access network device to obtain the context. For example, a Retrieve UE context request (Retrieve UE context request) may be sent to the last serving access network device. Finally, the serving access network device may respond with a RETRIEVE UE CONTEXT RESPONSE or a RETRIEVE UE CONTEXT failure.

In other words, after the terminal device sends the RRC resume request (RRCresumeRequest), the requesting serving access network device will send the retrieve UE context request to the last serving access network device. Finally, the service access network device will send RETRIEVE UE CONTEXT RESPONSE(UE context retrieval success) or RETRIEVE UE CONTEXT failure(UE context retrieval failure).

FIG. 2 shows a schematic flowchart of a wireless communication method 200 according to an embodiment of the present application. The method 200 may be executed interactively by a terminal device, a requesting service access network device, a final serving access network device, and an AMF. The terminal equipment shown in FIG. 2 may be the terminal equipment shown in FIG. 1 , and the requesting service access network equipment and the final serving access network equipment shown in FIG. 2 may be the access network equipment shown in FIG. 1 . The AMF shown in FIG. 3 may be the core network device shown in FIG. 1 .

The following describes the process of the terminal device successfully restoring the RRC connection with reference to the method 200 .

As shown in FIG. 2, the method 200 may include some or all of the following:

S210, the terminal device sends an RRCresumeRequest to the requesting serving access network device, and provides an I-RNTI in the resume request, and the I-RNTI may be allocated to the terminal device by the last serving access network device.

S220, if the requesting serving access network device can address the last serving access network device according to the I-RNTI, the requesting serving access network device sends a request for restoring the UE context to the last serving access network device, which is used to request the last serving access network device The network device provides UE context (context), which may also be referred to as UE context data (data).

S230, finally, the serving access network device sends a UE context recovery response to the requesting serving access network device, so as to provide UE context data to the requesting requesting serving access network device.

S240, requesting the serving access network device to send RRC recovery to the terminal device.

S250, the terminal device sends the RRC recovery complete to the requesting serving access network device, so as to complete the recovery of the RRC connection.

S260: If there is downlink data in the last serving access network device, in order to avoid data loss, the requesting serving access network device may send an address indication to the last serving access network device to provide the address of data forwarding to the last serving access network device. access equipment.

S270, requesting the serving access network device to send a path switch request to the AMF to perform a path switch (path switch).

S280, requesting the serving access network device to receive a path switching request response sent by the AMF, so as to complete the path switching.

S290, requesting the serving access network device to trigger the last serving access network device to release UE resources on the last serving access network device.

FIG. 3 shows a schematic flowchart of a wireless communication method 300 according to an embodiment of the present application. The method 300 may be executed interactively by a terminal device, a requesting service access network device, a final serving access network device, and an AMF. The terminal equipment shown in FIG. 3 may be the terminal equipment shown in FIG. 1 , and the requesting service access network equipment and the final serving access network equipment shown in FIG. 3 may be the access network equipment shown in FIG. 1 . The AMF shown in FIG. 3 may be the core network device shown in FIG. 1 .

The following describes the process of the terminal device recovering the failure of the RRC connection with reference to the method 300 .

As shown in FIG. 3, the method 300 may include:

S310, the terminal device sends an RRCresumeRequest to the access network device requesting the service. For example, the I-RNTI is provided in the resume request, and the I-RNTI is the identifier allocated to the terminal device by the last serving access network device.

S320, if the requesting serving access network device can be addressed to the last serving access network device according to the I-RNTI, the requesting serving access network device sends a request for restoring the UE context to the last serving access network device for requesting the last serving access network device The network device provides UE context data.

S330, finally, the service access network device cannot restore or authenticate the UE context data.

S340: Finally, the serving access network device indicates to the requesting requesting serving access network device that the recovery fails.

S350, request the serving access network device to trigger the terminal device to perform rollback, for example, a new RRC connection may be established by sending an RRCsetup.

S360, perform an RRC connection establishment process.

In the method 200 and the method 300, finally, the serving access network device only determines success or failure of retrieving the UE context according to the UE context, without considering the slice information. However, in the actual recovery process, even if the service access network device can obtain the context at the end, it is possible that the current requesting service access network device cannot support the terminal device to access the network or the slicing due to the slicing problem, which will cause the context to be obtained first. The operation of releasing the context afterward increases the delay and signaling overhead.

In the present application, slice information is considered in the process of requesting the serving access network device to restore the RRC connection, so that access control can be performed.

It should be understood that the slicing information may be related information of network slicing (slicing), and the network slicing may also be referred to as a slice for short. To facilitate understanding of this solution, an exemplary description of network slicing is given below.

Based on network slicing, multiple services with different requirements can provide lower latency, more targeted, more flexible and more scalable services. For example, Radio Access Network (RAN) slicing can enable application providers to participate in the design, deployment and operation of customized RANs to better support the business of application providers. The terminal device can report the slicing requirement. After receiving the slicing requirement reported by the terminal device, the access network device can select an appropriate MAF according to the slicing requirement reported by the UE to establish a service session between the UE and the network. Because the access network device can only determine the slice information required by the terminal device after receiving the message 5 (MSG5), and the slice information required by the terminal device may not be the slice supported by the requesting service access network device, or although it is a request A slice supported by the serving access network device but the slice is overloaded. In this case, the requesting serving access network device can only send an RRC release (RRCRlease) message to the terminal device after MSG5, so that the terminal device can reselect an appropriate cell. Therefore, it is possible to delay the access of other suitable terminal equipment due to the access of the terminal equipment, and it is also possible to increase the delay of providing the slice service of the terminal equipment.

FIG. 4 shows a schematic flowchart of a wireless communication method 400 according to an embodiment of the present application, and the method 400 may be executed by a requesting serving access network device or a last serving access network device. The requesting serving access network device and the last serving access network device shown in FIG. 4 may be the access network devices shown in FIG. 1 .

S410, the access network device determines a result of restoring the UE context of the user equipment or an access control result according to the slice information.

In other words, the access network device determines an RRC reject message according to the slice information, and the RRC reject message is used to initiate the terminal device to re-establish an RRC connection.

Or, in other words, the access network device determines whether access to the network is permitted according to the slice information.

Or, in other words, the access network device determines the result of the request for restoring the UE context according to the slice information.

When the access network device determines to restore the RRC connection, the slice information is considered, that is, the access control is performed based on the slice information. In the case that the slice of the terminal device is not supported by the access network device, the access of the terminal device is avoided. The network then releases the RRC connection resources of the UE, thereby reducing delay and signaling overhead.

In some embodiments of the present application, the result of restoring the UE context is a UE context restoring response.

In some embodiments of the present application, the restoring UE context response is used to indicate that restoring the UE context is successful, and/or the restoring UE context response is used to indicate that the terminal device can access the network or slice, and/or the The restore UE context response is used to indicate that at least some of the slices of the terminal equipment are supported, and/or the restored UE context response is used to indicate that at least some of the slices of the terminal equipment are not overloaded, and/or Alternatively, the requesting serving access network device may support at least some of the slices of the terminal device.

Of course, the UE context restoration response may also include second indication information and/or a second cause value, and the second indication information and/or the second cause value may be used to indicate at least one of the following: the UE context restoration is successful , and/or the restore UE context response is used to indicate that the terminal device has access to a network or slice, and/or the restore UE context response is used to indicate that at least some of the slices of the terminal device are supported, and /or, the restoring UE context response is used to indicate that at least some of the slices of the terminal device are not overloaded, and/or the requesting serving access network device can support at least some of the slices of the terminal device.

It should be noted that, at least some of the slices of the terminal device may be some of the slices, or all of the slices.

In some embodiments of the present application, the result of restoring the UE context is failure to restore the UE context.

In some embodiments of the present application, the failure to restore the UE context is used to indicate the failure to restore the UE context, and/or the failure to restore the UE context is used to indicate that the terminal device cannot access the network or slice, and/or the the failure to restore the UE context is used to indicate that at least some of the slices of the terminal device are not supported, and/or the failure to restore the UE context is used to indicate that at least some of the slices of the terminal device are overloaded, and /or, the requesting serving access network device does not support at least part of the slices of the terminal device.

For example, the failure to restore the UE context is used to indicate the failure to restore the UE context, and/or the failure to restore the UE context is used to indicate that the terminal device cannot access the network or slice, and/or the failure to restore the UE context is used for Indicates that all slices of the terminal equipment are not supported, and/or the failure to restore the UE context is used to indicate that all slices of the terminal equipment are overloaded, and/or the requesting service access network equipment does not support the terminal equipment of all slices.

In some embodiments of the present application, the failure to restore the UE context includes first indication information and/or a first cause value, and the first indication information and/or the first cause value are used to indicate at least one of the following: UE context acquisition fails, non-UE context authentication fails, non-UE context is not acquired, at least some of the slices of the terminal device are not supported, at least some of the slices of the terminal device are overloaded, and service access is requested The network device does not support at least part of the slices of the terminal device, the RRC reject message and the information used to trigger the requesting serving access network device to send the RRC reject message to the terminal device. Optionally, the RRC rejection message may be an unencrypted and/or integrity-protected message. Optionally, the information used to trigger the requesting serving access network device to send an RRC reject message to the terminal device may be an instruction requesting the serving access network device to generate an RRC reject message, or an anchor (Anchor) access. The network device generates an RRC rejection message and sends it to the terminal device. Explain in the manual

In some embodiments of the present application, the method 400 may further include:

The access network device obtains or sends an RRC reject message.

In some embodiments of the present application, the RRC rejection message is a message generated by the last access network device, or the RRC rejection message is a message sent by the requesting serving access network device according to the last serving access network device. The UE context recovery failure message, the message generated by at least one of the first indication information and the first cause value. In some embodiments of the present application, the RRC rejection message is a message generated by the last serving access network device, and the RRC rejection message is encapsulated in the failure to restore the UE context. In some embodiments of the present application, the RRC rejection message is sent by the requesting serving access network device to the terminal device. In some embodiments of the present application, the RRC rejection message is a message sent by the service requesting access network device to the terminal device after the last serving access network device sends the requesting serving access network device to the terminal device. . In some embodiments of the present application, the RRC rejection message includes the first indication information and/or the first cause value, and the first indication information and/or the first cause value are used to indicate at least one of the following Item: non-UE context acquisition failed, non-UE context authentication failed, non-UE context was not acquired, at least some of the slices of the terminal device are not supported, at least some of the slices of the terminal device are overloaded, request The serving access network device does not support at least part of the slices of the terminal device, the RRC reject message and the information used to trigger the requesting serving access network device to send the RRC reject message to the terminal device. In some embodiments of the present application, the RRC rejection message further includes an identifier of a slice supported by the requesting serving access network device and/or an identifier of a slice that is not overloaded.

In some embodiments of the present application, the slice information includes at least one of the following information:

The first information obtained from the terminal device;

second information obtained from the access management function AMF;

third information obtained from the requesting service access network device; or

Finally, the fourth information stored by the access network device is served.

In some embodiments of the present application, the first information includes information of at least one slice among slices requested, permitted, established, and preconfigured by the terminal device.

In some embodiments of the present application, the first information is a slice identifier.

In some embodiments of the present application, the first information is information obtained by the terminal device from the terminal device through a random access channel RACH process, and/or the first information is an RRC recovery request or RRC Recovery request 1 obtains the information from the terminal device.

In some embodiments of the present application, the second information includes an overload start message or information related to slice overload in the overload start message.

In some embodiments of the present application, the overload start message may include at least one of the following: an overload start network slice selection assistance information NSSAI list, a slice overload list, a slice overload response, or information indicating a reduction in slice traffic load .

In some embodiments of the present application, the third information includes the first information and/or the second information.

In some embodiments of the present application, the third information is carried in a UE context recovery request message.

In some embodiments of the present application, the fourth information is at least one slice among the slices of the requested, allowed, established, preconfigured, and previously established terminal equipment saved by the last serving access network device Information.

In some embodiments of the present application, the access network device is the last serving access network device.

In some embodiments of the present application, the access network device is a requesting service access network device.

The requesting serving access network device determines whether to trigger a UE context recovery request procedure.

In some embodiments of the present application, the identifier of the last serving access network device is an identifier obtained by parsing the requesting serving access network device based on the identification wireless network temporary identifier I-RNTI reported by the terminal device.

The wireless communication method of the present application will be described below with reference to specific flowcharts.

FIG. 5 shows a schematic flowchart of a wireless communication method 500 according to an embodiment of the present application. The method 500 may be interactively executed by a terminal device, a requesting service access network device, and a final serving access network device. The terminal equipment shown in FIG. 5 may be the terminal equipment shown in FIG. 1 , and the requesting service access network equipment and the final serving access network equipment shown in FIG. 5 may be the access network equipment shown in FIG. 1 .

As shown in FIG. 5, the method 500 may include:

S510, the terminal device in the RRC deactivated state sends a radio resource control (Radio Resource Control, RRC) recovery request (RRCResumeRequest or RRCResumeRequest1) to the requesting serving access network device. Optionally, the RRC recovery request may include at least one of the following information:

a). I-RNTI, the I-RNTI may be allocated to the terminal device by the last serving access network device.

b). First information. Optionally, the first information may be a slice identifier. Optionally, the first information may include requested/allowed/established/preconfigured slice information of the terminal device.

S520, if the requesting serving access network device can be addressed to the last serving access network device identifier according to the I-RNTI, the requesting serving access network device sends a restore UE context request (retrieve UE context request) to the last serving access network device. Optionally, the request for restoring the UE context may include at least one of the following:

a). The above-mentioned first information obtained from the terminal device.

b). The second information obtained from the access management function AMF. The second information may also be referred to as non-UE (non-UE), such as network-level, slice information, or may be information about a terminal device or a slice of the terminal device. The second information may be notified by the AMF to the access network device requesting the service. Exemplarily, the second information may be carried in an overload start (overload start) message, for example, the second information obtained by the requesting service access network device may be the complete overload obtained by the requesting service access network device from the AMF. The start message can also be only at least part of the information related to slice overload in the overload start message. Optionally, the overload start message may include at least one of the following: overload start network slice selection auxiliary information NSSAI list (Overload Start NSSAI List), slice overload list (Slice Overload List), slice overload response (Slice Overload Response) or Information used to indicate slice traffic load reduction (Slice Traffic Load Reduction Indication). Optionally, the second information may be acquired in advance, may be acquired by request at the time, or may be stored.

Certainly, the first information may be information notified by the terminal device to the access network device requesting a service through the RACH process, or information notified by the terminal device to the access network device requesting a service through RRCResumeRequest or RRCResumeRequest1. Similarly, the slice information may be carried in the retrieve UE context request, or may be carried in a message different from the retrieve UE context request.

S530: Finally, the serving access network device receives the request for restoring the UE context, and determines a result of restoring the UE context based on the slice information in the request for restoring the UE context. optional,

a) The second information obtained from the access management function AMF; the second information may also be called non-UE (non-UE), such as network level, slice information, or may be for terminal equipment or all information about the slice of the terminal device. The second information may be notified by the AMF to the last serving access network device. Exemplarily, the second information may be carried in an overload start (overload start) message, for example, the second information obtained by the requesting service access network device may be the complete overload obtained by the requesting service access network device from the AMF. The start message can also be only at least part of the information related to slice overload in the overload start message. Optionally, the overload start message may include at least one of the following: overload start network slice selection auxiliary information NSSAI list (Overload Start NSSAI List), slice overload list (Slice Overload List), slice overload response (Slice Overload Response) or Information used to indicate slice traffic load reduction (Slice Traffic Load Reduction Indication). Optionally, the second information may be acquired in advance, may be acquired by request at the time, or may be stored.

b). The third information obtained from the device requesting the service access network. For example, the above-mentioned first information and the above-mentioned second information.

Optionally, the second information in a) and the second information in the third information may be the same or different.

c). The fourth information stored by the last service access network device. For example, the information of at least one slice of the slices of the terminal equipment that is requested, allowed, established, pre-configured, and once established by the last serving access network equipment.

S540, the last serving access network device sends a resume UE context response (retrieve UE context response) to the requesting serving access network device. For example, the last serving access network device determines, based on the restore UE context request, whether the terminal device can access the network or whether at least one of the slices of the terminal device is accepted/not overloaded, if the terminal device The device can access the network or all or at least one of the slices of the terminal device are accepted/not overloaded, and the last serving access network device sends a restore UE context response (retrieve to the requesting serving access network device) UE context response). Optionally, reference may be made to the description for method 400 for the function, meaning and specific content of the UE context recovery response, which will not be repeated here in order to avoid repetition.

S550, the requesting serving access network device performs subsequent operations, such as sending an RRCResume message to the UE.

In the method 500, finally, the serving access network device may determine, based on the slice information, whether the terminal device can access the network or whether at least part of the slice of the terminal device is supported, and then determine whether the terminal device can access the network or all the slices of the terminal device are supported. The UE context recovery response is sent to the requesting serving access network device only when at least part of the slices of the terminal device are supported. Based on this, it is avoided to restore the UE context and then release the UE context when the slice of the terminal device is not supported, which can reduce delay and signaling overhead.

FIG. 6 shows a schematic flowchart of a wireless communication method 600 according to an embodiment of the present application. The method 600 may be executed interactively by a terminal device, a requesting service access network device, and finally a serving access network device. The terminal equipment shown in FIG. 6 may be the terminal equipment shown in FIG. 1 , and the requesting service access network equipment and the final serving access network equipment shown in FIG. 6 may be the access network equipment shown in FIG. 1 . .

As shown in FIG. 6, the method 600 may include:

S610: The terminal device in the RRC deactivated state sends a radio resource control (Radio Resource Control, RRC) recovery request (RRCResumeRequest or RRCResumeRequest1) to the requesting serving access network device. Optionally, the RRC recovery request may include at least one of the following information:

S620, if the requesting serving access network device can be addressed to the last serving access network device identifier according to the I-RNTI, the requesting serving access network device sends a restore UE context request (retrieve UE context request) to the last serving access network device. Optionally, the request for restoring the UE context may include at least one of the following:

a). The above-mentioned first information obtained from the terminal device.

S630: Finally, the serving access network device receives the request for restoring the UE context, and determines a result of restoring the UE context based on the slice information in the request for restoring the UE context. optional,

S640, the last serving access network device sends a recovery UE context failure (retrieve UE context failure) to the requesting serving access network device. For example, the last serving access network device determines, based on the restore UE context request, whether the terminal device can access the network or whether at least one of the slices of the terminal device is accepted/not overloaded, if the terminal device The device cannot access the network or at least one or all of the slices of the terminal device are not accepted/overloaded, and the last serving access network device sends the requesting serving access network device to the requesting serving access network device. UE context failure). Optionally, for the function, meaning and specific content of the failure to restore the UE context, reference may be made to the description in the method 400 , which is not repeated here to avoid repetition.

S650, the requesting serving access network device performs subsequent operations, such as sending an RRC rejection message to the UE. For example, the RRC rejection message may carry the above-mentioned first indication information or the above-mentioned first cause value. Optionally, the RRC rejection message further includes an identifier of a slice supported by the requesting serving access network device and/or an identifier of a slice that is not overloaded.

In the method 600, finally the serving access network device determines the result of restoring the UE context according to the slice information. If the last serving access network device determines that the UE slice is inaccessible or the slice of the terminal device is overloaded, the last serving access network device sends retrieve UE context failure to the UE. Based on this, it is avoided to restore the UE context and then release the UE context when the slice of the terminal device is not supported, which can reduce delay and signaling overhead.

FIG. 7 shows a schematic flowchart of a wireless communication method 700 according to an embodiment of the present application, and the method 700 may be executed interactively by a terminal device and a device requesting a service access network. The terminal device shown in FIG. 7 may be the terminal device shown in FIG. 1 , and the access network device that requests the service shown in FIG. 6 may be the access network device shown in FIG. 1 .

As shown in FIG. 7, the method 700 may include:

S710, the terminal device in the RRC deactivated state sends a radio resource control (Radio Resource Control, RRC) recovery request (RRCResumeRequest or RRCResumeRequest1) to the requesting serving access network device. Optionally, the RRC recovery request may include at least one of the following information:

S720, requesting the serving access network device to receive the RRC recovery request, and determine the access control result based on the slice information, whether to send at least one of a request for recovering the UE context and a result for recovering the UE context. Optionally, the request for restoring the UE context may include at least one of the following:

a). The above-mentioned first information obtained from the terminal device.

b). The second information obtained from the access management function AMF; the second information may also be referred to as non-UE (non-UE), such as network level, slice information, and may also be for terminal equipment or all information about the slice of the terminal device. The second information may be notified by the AMF to the access network device requesting the service. Exemplarily, the second information may be carried in an overload start (overload start) message, for example, the second information obtained by the requesting service access network device may be the complete overload obtained by the requesting service access network device from the AMF. The start message can also be only at least part of the information related to slice overload in the overload start message. Optionally, the overload start message may include at least one of the following: overload start network slice selection auxiliary information NSSAI list (Overload Start NSSAI List), slice overload list (Slice Overload List), slice overload response (Slice Overload Response) or Information used to indicate slice traffic load reduction (Slice Traffic Load Reduction Indication). Optionally, the second information may be acquired in advance, may be acquired by request at the time, or may be stored.

S730, if the requesting serving access network device determines that at least one of the slices of the terminal device can be accessed/is not overloaded, request the serving access network device to send an RRC resume (RRCresume) message to the UE, or, after obtaining a resume UE context response After the message, send an RRCresume message to the UE; and/or, if the requesting serving access network device determines that at least one of the UE slices cannot be accessed/overloaded, the requesting serving access network device sends an RRCReject message to the UE, or, in After obtaining the UE context recovery response/failure message, send an RRCReject message to the UE; and/or, if the requesting service access network device determines that at least one of the slices of the terminal device cannot be accessed/overloaded, request service access The network device determines that the request to restore the context fails, or determines that the request to restore the context fails after acquiring the UE context restore response/failure message.

S740, if the requesting serving access network device determines that at least one of the UE slices can be accessed, and if the requesting serving access network device can address the last serving access network device identifier according to the I-RNTI, request the serving access network The device sends a retrieve UE context request to the last serving access network device. Finally, the serving access network device receives the retrieve UE context request message and determines the result of the retrieve UE context. Optionally, finally, the serving access network device receives the retrieve UE context request message, and determines the result of the retrieve UE context according to the slice information.

In method 700, the requesting service access network device may determine, based on the slice information, whether the terminal device can access the network or whether at least part of the slice of the terminal device is supported. For example, further sending an RRC reject message to the terminal device when it is determined that an inaccessible network or at least part of the slice of the terminal device is not supported. Based on this, it is avoided to restore the UE context and then release the UE context when the slice of the terminal device is not supported, which can reduce delay and signaling overhead.

In other words, the requesting serving access network device determines whether to send an RRCReject to the UE according to the slice information. For example, if the requesting serving access network device determines that the slice of the terminal device is inaccessible, for example, the slice of the terminal device is overloaded, the requesting serving access network device sends an RRCreject to the terminal device. Otherwise, request the serving access network device to perform subsequent normal procedures, that is, request the serving access network device to perform sending retrieve UE context Request to the last serving access network device, etc. It is equivalent to determining whether to send an RRCreject to the terminal device by means of non-interactive access confirmation in the case that the requesting serving access network device can obtain the information of the slice of the terminal device. Based on this, it is avoided to restore the UE context and then release the UE context when the slice of the terminal device is not supported, which can reduce delay and signaling overhead.

It should be understood that in the various method embodiments of the present application, the size of the sequence numbers of the above-mentioned processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic, and should not be implemented in the present application. The implementation of the examples constitutes no limitation. For example, the above S730 and S740 may be performed simultaneously, or S730 may be performed first and then S740 may be performed, or S740 may be performed first and then S730 may be performed.

The preferred embodiments of the present application have been described in detail above with reference to the accompanying drawings. However, the present application is not limited to the specific details of the above-mentioned embodiments. Within the scope of the technical concept of the present application, various simple modifications can be made to the technical solutions of the present application. These simple modifications all belong to the protection scope of the present application. For example, the specific technical features described in the above-mentioned specific embodiments can be combined in any suitable manner unless they are inconsistent. In order to avoid unnecessary repetition, this application does not describe any possible combination. State otherwise. For another example, the various embodiments of the present application can also be combined arbitrarily, as long as they do not violate the idea of the present application, they should also be regarded as the content disclosed in the present application.

In addition, in the embodiments of the present application, the terms "downlink" and "uplink" are used to indicate the transmission direction of signals or data, wherein "downlink" is used to indicate that the transmission direction of signals or data is from the site to the user equipment of the cell In the first direction, "uplink" is used to indicate that the transmission direction of the signal or data is the second direction sent from the user equipment of the cell to the site. For example, "downlink signal" indicates that the transmission direction of the signal is the first direction. In addition, in this embodiment of the present application, the term "and/or" is only an association relationship for describing associated objects, indicating that there may be three kinds of relationships. Specifically, A and/or B can represent three situations: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character "/" in this document generally indicates that the related objects are an "or" relationship.

The method embodiments of the present application are described in detail above with reference to FIGS. 1 to 7 , and the apparatus embodiments of the present application are described in detail below with reference to FIGS. 8 to 10 .

FIG. 8 is a schematic block diagram of an access network device 800 according to an embodiment of the present application.

As shown in FIG. 8 , the access network device 800 may include:

The processing unit 810 is configured to determine, according to the slice information, a result of restoring the user equipment UE context or an access control result.

In some embodiments of the present application, the failure to restore the UE context includes first indication information and/or a first cause value, and the first indication information and/or the first cause value are used to indicate at least one of the following: UE context acquisition fails, non-UE context authentication fails, non-UE context is not acquired, at least some of the slices of the terminal device are not supported, at least some of the slices of the terminal device are overloaded, and service access is requested The network device does not support at least part of the slices of the terminal device, the RRC reject message and the information used to trigger the requesting serving access network device to send the RRC reject message to the terminal device.

In some embodiments of the present application, the access network device further includes:

The communication unit is used to obtain or send an RRC rejection message.

In some embodiments of the present application, the RRC rejection message is a message generated by the last access network device, or the RRC rejection message is a message sent by the requesting serving access network device according to the last serving access network device. A message generated by at least one of the UE context recovery failure message, the first indication information, and the first cause value.

In some embodiments of the present application, the RRC rejection message is a message generated by the last serving access network device, and the RRC rejection message is encapsulated in the failure to restore the UE context.

In some embodiments of the present application, the RRC rejection message is a message sent by the requesting serving access network device to the last serving access network device.

In some embodiments of the present application, the RRC rejection message includes the first indication information and/or the first cause value, and the first indication information and/or the first cause value are used to indicate at least one of the following Item: non-UE context acquisition failed, non-UE context authentication failed, non-UE context was not acquired, at least some of the slices of the terminal device are not supported, at least some of the slices of the terminal device are overloaded, request The serving access network device does not support at least part of the slices of the terminal device, the RRC reject message and the information used to trigger the requesting serving access network device to send the RRC reject message to the terminal device.

In some embodiments of the present application, the RRC rejection message further includes an identifier of a slice supported by the requesting serving access network device and/or an identifier of a slice that is not overloaded.

The first information obtained from the terminal device;

second information obtained from the access management function AMF;

Finally, the fourth information stored by the access network device is served.

In some embodiments of the present application, the processing unit 810 is further configured to:

Determine whether to trigger the restore UE context request procedure.

It should be understood that the apparatus embodiments and the method embodiments may correspond to each other, and similar descriptions may refer to the method embodiments. Specifically, the access network device 800 shown in FIG. 8 may correspond to a corresponding subject performing methods 200 to 700 in the embodiments of the present application, such as a requesting service access network device or a last serving access network device. Moreover, the aforementioned and other operations and/or functions of each unit in the access network device 800 are respectively to implement the corresponding processes in each method in FIG. 2 to FIG. 7 , and are not repeated here for brevity.

The communication device of the embodiments of the present application is described above from the perspective of functional modules with reference to the accompanying drawings. It should be understood that the functional modules can be implemented in the form of hardware, can also be implemented by instructions in the form of software, and can also be implemented by a combination of hardware and software modules.

Specifically, the steps of the method embodiments in the embodiments of the present application may be completed by hardware integrated logic circuits in the processor and/or instructions in the form of software, and the steps of the methods disclosed in conjunction with the embodiments of the present application may be directly embodied as hardware The execution of the decoding processor is completed, or the execution is completed by a combination of hardware and software modules in the decoding processor.

Optionally, the software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, and other storage media mature in the art. The storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps in the above method embodiments in combination with its hardware.

For example, the processing unit and the communication unit referred to above may be implemented by a processor and a transceiver, respectively.

FIG. 9 is a schematic structural diagram of a communication device 900 according to an embodiment of the present application.

As shown in FIG. 9 , the communication device 900 may include a processor 910 .

The processor 910 may call and run a computer program from the memory to implement the methods in the embodiments of the present application.

Continuing to refer to FIG. 9 , the communication device 900 may further include a memory 920 .

The memory 920 may be used to store indication information, and may also be used to store codes, instructions, etc. executed by the processor 910 . The processor 910 may call and run a computer program from the memory 920 to implement the methods in the embodiments of the present application. The memory 920 may be a separate device independent of the processor 910 , or may be integrated in the processor 910 .

Continuing to refer to FIG. 9 , the communication device 900 may also include a transceiver 930 .

The processor 910 may control the transceiver 930 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices. Transceiver 930 may include a transmitter and a receiver. The transceiver 930 may further include antennas, and the number of the antennas may be one or more.

It should be understood that each component in the communication device 900 is connected through a bus system, wherein the bus system includes a power bus, a control bus and a status signal bus in addition to a data bus.

It should also be understood that the communication device 900 may be a terminal device of this embodiment of the present application, and the communication device 900 may implement the corresponding processes implemented by the requesting service access network device in each method of the embodiments of the present application, that is to say, this The communication device 900 in the embodiment of the application may correspond to the access network device 800 in the embodiment of the application. For example, the communication device 900 may correspond to the corresponding subject in executing the method 200 to the method 700 according to the embodiment of the present application, which is not repeated here for brevity.

In addition, the embodiment of the present application also provides a chip.

For example, the chip may be an integrated circuit chip, which has a signal processing capability, and can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The chip may also be referred to as a system-on-chip, a system-on-chip, a system-on-a-chip, or a system-on-a-chip, or the like. Optionally, the chip can be applied to various communication devices, so that the communication device installed with the chip can execute the methods, steps and logic block diagrams disclosed in the embodiments of the present application.

FIG. 10 is a schematic structural diagram of a chip 1000 according to an embodiment of the present application.

As shown in FIG. 10 , the chip 1000 includes a processor 1010 .

The processor 1010 may call and run a computer program from the memory to implement the methods in the embodiments of the present application.

Please continue to refer to FIG. 10 , the chip 1000 may further include a memory 1020 .

The processor 1010 may call and run a computer program from the memory 1020 to implement the methods in the embodiments of the present application. The memory 1020 may be used to store instruction information, and may also be used to store codes, instructions, etc. executed by the processor 1010 . The memory 1020 may be a separate device independent of the processor 1010 , or may be integrated in the processor 1010 .

Please continue to refer to FIG. 10 , the chip 1000 may further include an input interface 1030 .

The processor 1010 can control the input interface 1030 to communicate with other devices or chips, and specifically, can obtain information or data sent by other devices or chips.

Please continue to refer to FIG. 10 , the chip 1000 may further include an output interface 1040 .

The processor 1010 can control the output interface 1040 to communicate with other devices or chips, and specifically, can output information or data to other devices or chips.

It should be understood that the chip 1000 can be applied to the access network device in the embodiments of the present application, for example, the chip can implement the corresponding processes implemented by the access network device requesting the service in each method of the embodiments of the present application, and can also implement the present application. For the sake of brevity, the corresponding processes implemented by the last serving access network device in each method of the application embodiments will not be repeated here.

It should also be understood that various components in the chip 1000 are connected through a bus system, wherein the bus system includes a power bus, a control bus and a status signal bus in addition to a data bus.

The processors referred to above may include, but are not limited to:

General-purpose processor, Digital Signal Processor (DSP), Application Specific Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic devices, discrete gates Or transistor logic devices, discrete hardware components, and so on.

The processor may be used to implement or execute the methods, steps, and logical block diagrams disclosed in the embodiments of this application. The steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software module may be located in random access memory, flash memory, read-only memory, programmable read-only memory or erasable programmable memory, registers and other storage media mature in the art. The storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware.

The memory mentioned above includes but is not limited to:

Volatile memory and/or non-volatile memory. Wherein, the non-volatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically programmable read-only memory (Erasable PROM, EPROM). Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory. Volatile memory may be Random Access Memory (RAM), which acts as an external cache. By way of illustration and not limitation, many forms of RAM are available, such as Static RAM (SRAM), Dynamic RAM (DRAM), 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 link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM).

It should be noted that the memory described herein is intended to include these and any other suitable types of memory.

Embodiments of the present application also provide a computer-readable storage medium for storing a computer program. The computer-readable storage medium stores one or more programs including instructions that, when executed by a portable electronic device including a plurality of application programs, enable the portable electronic device to perform methods 200 through 700 The method of the illustrated embodiment.

Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For brevity, here No longer.

Optionally, the computer-readable storage medium can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application. , and are not repeated here for brevity.

The embodiments of the present application also provide a computer program product, including a computer program.

Optionally, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in each method of the embodiments of the present application. Repeat.

Optionally, the computer program product can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application, in order to It is concise and will not be repeated here.

A computer program is also provided in the embodiments of the present application. When the computer program is executed by a computer, the computer can execute the methods of the embodiments shown in method 200 to method 700 .

Optionally, the computer program can be applied to the network device in the embodiments of the present application. When the computer program is run on the computer, it causes the computer to execute the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity. , and will not be repeated here.

In addition, an embodiment of the present application further provides a communication system, which may include the above-mentioned terminal equipment and network equipment to form a communication system 100 as shown in FIG. 1 , which is not repeated here for brevity. It should be noted that the terms "system" and the like in this document may also be referred to as "network management architecture" or "network system" and the like.

It should also be understood that the terms used in the embodiments of the present application and the appended claims are only for the purpose of describing specific embodiments, and are not intended to limit the embodiments of the present application.

For example, as used in the embodiments of this application and the appended claims, the singular forms "a," "the," "above," and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. meaning.

Those skilled in the art can realize that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled persons may use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of the embodiments of the present application.

If implemented in the form of a software functional unit and sold or used as a stand-alone product, it may be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of the present application can be embodied in the form of software products in essence, or the parts that make contributions to the prior art or the parts of the technical solutions, and the computer software products are stored in a storage medium , including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the embodiments of the present application. The aforementioned storage medium includes: a U disk, a removable hard disk, a read-only memory, a random access memory, a magnetic disk or an optical disk and other media that can store program codes.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the above-described systems, devices and units may refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods may be implemented in other manners.

For example, the division of units, modules or components in the apparatus embodiments described above is only a logical function division, and other division methods may be used in actual implementation. For example, multiple units, modules or components may be combined or integrated. To another system, or some units or modules or components can be ignored, or not implemented.

For another example, the above-mentioned units/modules/components described as separate/display components may or may not be physically separated, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units/modules/components may be selected according to actual needs to achieve the purpose of the embodiments of the present application.

Finally, it should be noted that the mutual coupling or direct coupling or communication connection shown or discussed above may be through some interfaces, indirect coupling or communication connection of devices or units, which may be electrical, mechanical or other forms .

The above contents are only specific implementations of the embodiments of the present application, but the protection scope of the embodiments of the present application is not limited thereto. Changes or substitutions should all be covered within the protection scope of the embodiments of the present application. Therefore, the protection scope of the embodiments of the present application should be subject to the protection scope of the claims.

Claims

A wireless communication method, comprising:

The access network device determines a result of restoring the UE context of the user equipment or an access control result according to the slice information.
The method according to claim 1, wherein the result of restoring the UE context is a UE context restoring response.
The method according to claim 2, wherein the restoring UE context response is used to indicate that restoring the UE context is successful, and/or the restoring UE context response is used to indicate that the terminal device can access the network or slice, and /or the restoring UE context response is used to indicate that at least some of the slices of the terminal device are supported, and/or the restored UE context response is used to indicate that at least some of the slices of the terminal device are not supported The overload, and/or the requesting serving access network device may support at least some of the slices of the terminal device.
The method according to claim 1, wherein the result of restoring the UE context is failure to restore the UE context.
The method according to claim 4, wherein the failure to restore the UE context is used to indicate a failure to restore the UE context, and/or the failure to restore the UE context is used to indicate that the terminal device cannot access the network or slice, and /or, the failure to restore the UE context is used to indicate that at least part of the slices in the terminal device are not supported, and/or the failure to restore the UE context is used to indicate that at least part of the slices of the terminal device are not supported The slices are overloaded, and/or the requesting serving access network device does not support at least some of the slices of the terminal device.
The method according to claim 4 or 5, wherein the failure to restore the UE context includes first indication information and/or a first cause value, and the first indication information and/or the first cause value are used to indicate At least one of the following: non-UE context acquisition fails, non-UE context authentication fails, non-UE context is not acquired, at least some of the slices of the terminal device are not supported, and at least some of the slices of the terminal device are not supported. Overload, the requesting serving access network device does not support at least part of the slices of the terminal device, an RRC reject message and information used to trigger the requesting serving access network device to send an RRC reject message to the terminal device.
The method according to any one of claim 1, wherein the method further comprises:

The access network device obtains or sends an RRC reject message.
The method according to claim 7, wherein the RRC rejection message is a message generated by the last access network device, or the RRC rejection message is a request for the serving access network device to request the serving access network according to the last serving access network device. A message generated by at least one of the UE context restoration failure message, the first indication information, and the first cause value sent by the device.
The method according to claim 7, wherein the RRC rejection message is a message generated by the last serving access network device, and the RRC rejection message is encapsulated in the failure to restore the UE context.
The method according to claim 7, wherein the RRC rejection message is a message sent by the requesting serving access network device to the last serving access network device.
The method according to any one of claims 7 to 10, wherein the RRC rejection message includes the first indication information and/or the first cause value, the first indication information and/or The first cause value is used to indicate at least one of the following: non-UE context acquisition fails, non-UE context authentication fails, non-UE context is not acquired, at least some of the slices of the terminal device are not supported, the terminal device At least some of the slices of the requesting service access network are overloaded, the requesting serving access network device does not support at least some of the slices of the terminal device, an RRC reject message and a RRC reject message for triggering the requesting serving access network device to send an RRC reject to the terminal device message information.
The method according to claim 11, wherein the RRC rejection message further comprises an identifier of a slice supported by the requesting serving access network device and/or an identifier of a slice that is not overloaded.
The method according to any one of claims 1 to 12, wherein the slice information includes at least one of the following information:

The first information obtained from the terminal device;

second information obtained from the access management function AMF;

third information obtained from the requesting service access network device; or

Finally, the fourth information stored by the access network device is served.
The method according to claim 13, wherein the first information comprises information of at least one slice among the slices requested, allowed, established, and preconfigured by the terminal device.
The method according to claim 13, wherein the first information is a slice identifier.
The method according to claim 13, wherein the first information is information obtained by the terminal equipment from the terminal equipment through a random access channel RACH process, and/or the first information is obtained through RRC Recovery request or RRC recovery request 1 information obtained from the terminal device.
The method according to claim 13, wherein the second information comprises an overload start message or information related to slice overload in the overload start message.
The method according to claim 17, wherein the overload start message can include at least one of the following: an overload start network slice selection auxiliary information NSSAI list, a slice overload list, a slice overload response, or an indication of slice traffic. Load reduction information.
The method according to claim 13, wherein the third information includes the first information and/or the second information.
The method according to claim 13, wherein the third information is carried in a UE context recovery request message.
The method according to claim 13, wherein the fourth information is in the slice of the requested, allowed, established, preconfigured, and established terminal equipment saved by the last serving access network equipment information of at least one slice.
The method according to any one of claims 1 to 21, wherein the access network device is the last serving access network device.
The method according to any one of claims 1 to 21, wherein the access network device is a requesting service access network device.
The method of claim 23, wherein the method further comprises:

The requesting serving access network device determines whether to trigger a UE context recovery request procedure.
The method according to any one of claims 22 to 25, wherein the identification of the last serving access network device is a request for the serving access network device to resolve based on the identification wireless network temporary identifier I-RNTI reported by the terminal device obtained identification.
An access network device, characterized in that it includes:

The processing unit is configured to determine, according to the slice information, a result of restoring the UE context of the user equipment or an access control result.
The access network device according to claim 26, wherein the result of restoring the UE context is a UE context restoring response.
The access network device according to claim 27, wherein the UE context recovery response is used to indicate that the UE context recovery is successful, and/or the UE context recovery response is used to indicate that the terminal device can access the network or slices, and/or the restore UE context response is used to indicate that at least some of the slices of the terminal device are supported, and/or the restore UE context response is used to indicate that at least some of the slices of the terminal device are supported Some of the slices are not overloaded, and/or at least some of the slices of the terminal device may be supported by the requesting serving access network device.
The access network device according to claim 26, wherein the result of restoring the UE context is failure to restore the UE context.
The access network device according to claim 29, wherein the failure to restore the UE context is used to indicate a failure to restore the UE context, and/or the failure to restore the UE context is used to indicate that the terminal device cannot access the network or Slices, and/or the failure to restore the UE context is used to indicate that at least part of the slices in the terminal equipment are not supported, and/or the failure to restore the UE context is used to indicate that the terminal equipment is in the slices At least some of the slices are overloaded, and/or the requesting serving access network device does not support at least some of the slices of the terminal device.
The access network device according to claim 29 or 30, wherein the failure to restore the UE context comprises first indication information and/or a first cause value, and the first indication information and/or the first cause value It is used to indicate at least one of the following: the non-UE context acquisition fails, the non-UE context authentication fails, the non-UE context is not acquired, at least some of the slices of the terminal device are not supported, and the slices of the terminal device are not supported. At least some of the slices are overloaded, the requesting serving access network device does not support at least some of the slices of the terminal device, an RRC reject message, and information for triggering the requesting serving access network device to send an RRC reject message to the terminal device.
The access network device according to any one of claims 26 to 31, wherein the access network device further comprises:

The communication unit is used to obtain or send an RRC rejection message.
The access network device according to claim 32, wherein the RRC rejection message is a message generated by the last access network device, or, the RRC rejection message is a request for the service access network device according to the last service The message is generated by at least one of the UE context restoration failure message, the first indication information and the first cause value sent by the access network device.
The access network device according to claim 32, wherein the RRC reject message is a message generated by the last serving access network device, and the RRC reject message is encapsulated in the failure to restore UE context.
The access network device according to claim 32, wherein the RRC rejection message is a message sent by the requesting serving access network device to the last serving access network device.
The access network device according to any one of claims 32 to 35, wherein the RRC rejection message includes the first indication information and/or the first cause value, the first indication information and/or the first cause value is used to indicate at least one of the following: the non-UE context acquisition fails, the non-UE context authentication fails, the non-UE context is not acquired, at least some of the slices of the terminal device are not supported, so at least some of the slices of the terminal equipment are overloaded, the requesting serving access network equipment does not support at least some of the slices of the terminal equipment, the RRC reject message and the RRC rejection message are used to trigger the requesting serving access network equipment to send the terminal equipment to the terminal equipment. Send RRC reject message information.
The access network device according to claim 36, wherein the RRC rejection message further comprises an identifier of a slice supported by the requesting serving access network device and/or an identifier of a slice that is not overloaded.
The access network device according to any one of claims 26 to 37, wherein the slice information includes at least one of the following information:

The first information obtained from the terminal device;

second information obtained from the access management function AMF;

third information obtained from the requesting service access network device; or

Finally, the fourth information stored by the access network device is served.
The access network device according to claim 38, wherein the first information comprises information of at least one slice among the slices requested, allowed, established, and preconfigured by the terminal device.
The access network device according to claim 38, wherein the first information is a slice identifier.
The access network device according to claim 38, wherein the first information is information obtained by the terminal device from the terminal device through a random access channel RACH process, and/or the first information The information obtained from the terminal device through the RRC recovery request or RRC recovery request 1.
The access network device according to claim 38, wherein the second information comprises an overload start message or information related to slice overload in the overload start message.
The access network device according to claim 42, wherein the overload start message can include at least one of the following: an overload start network slice selection auxiliary information NSSAI list, a slice overload list, a slice overload response or a Information indicating a reduction in slice traffic load.
The access network device according to claim 38, wherein the third information includes the first information and/or the second information.
The access network device according to claim 38, wherein the third information is carried in a UE context recovery request message.
The access network device according to claim 38, wherein the fourth information is the requested, allowed, established, preconfigured, and previously established terminal devices saved by the last serving access network device Information about at least one of the slices.
The access network device according to any one of claims 26 to 46, wherein the access network device is the last serving access network device.
The access network device according to any one of claims 26 to 46, wherein the access network device is a requesting service access network device.
The access network device according to claim 48, wherein the processing unit is further configured to:

Determine whether to trigger the restore UE context request procedure.
The access network device according to any one of claims 47 to 49, wherein the identifier of the last serving access network device is the wireless network temporary identifier I based on the identifier reported by the terminal device for requesting the serving access network device. - The identifier obtained by RNTI parsing.
A network device, characterized in that it includes:

A processor, a memory and a transceiver, the memory for storing a computer program, the processor for invoking and running the computer program stored in the memory to perform the method of any one of claims 1 to 25.
A chip, characterized in that it includes:

A processor for invoking and running a computer program from a memory, so that a device on which the chip is installed executes the method as claimed in any one of claims 1 to 25.
A computer-readable storage medium, characterized by being used for storing a computer program, the computer program causing a computer to execute the method according to any one of claims 1 to 25.
A computer program product comprising computer program instructions, the computer program instructions causing a computer to perform the method of any one of claims 1 to 25.
A computer program, characterized in that the computer program causes a computer to perform the method according to any one of claims 1 to 25.