Wireless communication method and device
By performing access control based on slice information in the access network device, the problem of increased delay and signaling overhead of terminal equipment restoring RRC connection is solved, and more efficient network access is achieved.
Patent Information
- Application Number
- CN202080100923.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-07-27
- Publication Date
- 2024-11-15
- Estimated Expiration
- 2040-07-27
AI Technical Summary
The prior art fails to effectively consider slice information when the terminal device restores RRC connection, resulting in an increase in delay and signaling overhead.
In the access network device, access control is performed based on slice information to avoid releasing the UE's RRC connection resources when the terminal device slice is not supported.
Reduces delay and signaling overhead and improves the access network efficiency of terminal equipment.
Smart Images

Figure CN115606247B_ABST
Abstract
Description
Technical Field
[0001] The embodiments of the present application relate to the field of communications, and more specifically, to wireless communication methods and devices. Background Art
[0002] Currently, the access network device only determines whether the user equipment (UE) context is successfully or failed to be retrieved according to the user equipment (UE) context, and further determines whether the RRC connection can be restored.
[0003] However, even if the access network device is able to obtain the user equipment context, it may be necessary to release the RRC connection due to other reasons, thereby increasing the delay and signaling overhead. Summary of the invention
[0004] Provided are a wireless communication method and device, which avoids acquiring and then releasing the UE context when the slice of the terminal device is not supported by the access network device, thereby reducing latency and signaling overhead.
[0005] In a first aspect, a wireless communication method is provided, comprising:
[0006] The access network device determines the result of restoring the user equipment UE context or the access control result based on the slice information.
[0007] In a second aspect, an access network device is provided, which is used to execute the method in the first aspect or its implementations. Specifically, the network device includes a functional module used to execute the method in the first aspect or its implementations.
[0008] In a third aspect, an access network device is provided, comprising a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the first aspect or its implementations.
[0009] In a fourth aspect, a chip is provided for implementing the method in the first aspect or its implementations. Specifically, the chip includes: a processor for calling and running a computer program from a memory, so that a device equipped with the chip executes the method in the first aspect or its implementations.
[0010] In a fifth aspect, a computer-readable storage medium is provided for storing a computer program, wherein the computer program enables a computer to execute the method in the above-mentioned first aspect or its various implementations.
[0011] In a sixth aspect, a computer program product is provided, comprising computer program instructions, wherein the computer program instructions enable a computer to execute the method in the above-mentioned first aspect or its various implementations.
[0012] In a seventh aspect, a computer program is provided, which, when executed on a computer, enables the computer to execute the method in the first aspect or its various implementations.
[0013] Based on the above technical solution, slice information is taken into consideration when the access network device determines to restore the RRC connection, that is, access control is performed based on the slice information. When the slice of the terminal device is not supported by the access network device, it is avoided that the RRC connection resources of the UE are released after the terminal device accesses the network, thereby reducing latency and signaling overhead. BRIEF DESCRIPTION OF THE DRAWINGS
[0014] Figure 1 This is an example of the application scenario of this application.
[0015] Figures 2 to 7 It is a schematic flowchart of the wireless communication method provided in an embodiment of the present application.
[0016] Figure 8 It is a schematic block diagram of an access network device provided in an embodiment of the present application.
[0017] Fig. 9 It is a schematic block diagram of a communication device provided in an embodiment of the present application.
[0018] Fig.10 It is a schematic block diagram of the chip provided in the embodiment of the present application. DETAILED DESCRIPTION
[0019] The following will describe the technical solutions in the embodiments of the present application in conjunction with the 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 ordinary technicians in this field without creative work are within the scope of protection of this application.
[0020] Figure 1 It is a schematic diagram of an application scenario of an embodiment of the present application.
[0021] like Figure 1 As shown, 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 via an air interface. The terminal device 110 and the network device 120 support multi-service transmission.
[0022] It should be understood that the embodiments of the present application are only exemplified by the communication system 100, but the embodiments of the present application are 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 (LTE) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), 5G communication system (also known as New Radio (NR) communication system), or future communication systems.
[0023] exist Figure 1 In the communication system 100 shown, the network device 120 may be an access network device that communicates with the terminal device 110. The access network device may provide communication coverage for a specific geographical area, and may communicate with the terminal device 110 (eg, UE) located in the coverage area.
[0024] The network device 120 may be an evolved Node B (eNB or eNodeB) in a Long Term Evolution (LTE) system, or a 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 (CRAN), or the network device 120 may be a relay station, an access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, or a network device in a future evolved Public Land Mobile Network (PLMN), etc.
[0025] The terminal device 110 may be any terminal device, including but not limited to a terminal device connected to the network device 120 or other terminal devices by wire or wireless connection.
[0026] For example, the terminal device 110 may refer to an access terminal, a user equipment (UE), a user unit, a user 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, a user agent, or a 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 handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a 5G network, or a terminal device in a future evolution network, etc.
[0027] The terminal device 110 may be used for device-to-device (D2D) communication.
[0028] The wireless communication system 100 may also include a core network device 130 for communicating 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), and for example, an authentication server function (Authentication Server Function, AUSF), and for example, a user plane function (User Plane Function, UPF), and for example, a 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 the LTE network, for example, a session management function + a data gateway (Session Management Function + Core Packet Gateway, SMF + PGW-C) device of the core network. It should be understood that SMF + PGW-C can simultaneously implement the functions that SMF and PGW-C can implement. In the process of network evolution, the above-mentioned core network device may also be called other names, or a new network entity may be formed by dividing the functions of the core network, which is not limited to the embodiments of the present application.
[0029] The functional units in the communication system 100 may also establish connections through next generation (NG) network interfaces to achieve communication.
[0030] For example, the terminal device establishes an air interface connection with the access network device through the NR interface for transmitting user plane data and control plane signaling; the terminal device can establish a control plane signaling connection with the AMF through the NG interface 1 (N1 for short); the access network device, 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 device can establish a control plane signaling connection with the AMF through the NG interface 2 (N2 for short); the UPF can establish a control plane signaling connection with the SMF through the NG interface 4 (N4 for short); the UPF can exchange user plane data with the data network through the NG interface 6 (N6 for short); the AMF can establish a control plane signaling connection with the SMF through the NG interface 11 (N11 for short); the SMF can establish a control plane signaling connection with the PCF through the NG interface 7 (N7 for short).
[0031] Figure 1 A base station, a core network device and two terminal devices are shown exemplarily. Optionally, the wireless communication system 100 may include multiple base station devices and each base station may include another number of terminal devices within its coverage area, which is not limited in the embodiments of the present application.
[0032] It should be understood that all devices with communication functions in the network / system in the embodiments of the present application can be referred to as communication devices. Figure 1 Taking the communication system 100 shown as an example, the communication equipment may include a network device 120 and a terminal device 110 with communication functions. The network device 120 and the terminal device 110 may be the devices described above and will not be repeated here. The communication equipment may also include other devices in the communication system 100, such as a network controller, a mobile management entity and other network entities, which is not limited in the embodiments of the present application.
[0033] It should also be understood that the terms "system" and "network" are often used interchangeably herein. The term "and / or" herein is merely a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " herein generally indicates that the associated objects before and after are in an "or" relationship.
[0034] It should be noted that in the present application, the RRC connection state of the terminal device may include the RRC_INACTIVE (deactivated) state, the RRC_IDLE (idle) state and the RRC_CONNECTED (connected) state. In the RRC_IDLE state, mobility is based on UE 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 (AS) context on the base station side, nor is there an RRC connection. In the RRC_CONNECTED state, there is an RRC connection, and there is a UE AS context between the base station and the UE. The network device knows that the location of the UE is at a specific cell level. Mobility is mobility controlled by the network device. Unicast data can be transmitted between the UE and the base station. In RRC_INACTIVE, mobility is based on UE cell selection reselection, there is a connection between CN-NR, the UE AS context exists on a base station, paging is triggered by the Radio Access Network (RAN), and the paging area based on RAN is managed by RAN. The network device knows that the location of the UE is based on the paging area level of RAN.
[0035] In the process of the terminal device recovering from the RRC deactivated state to the RRC connected state, the process of the requesting service access network device receiving the RRC recovery request requesting the context from the last serving access network device (last serving gNB) is involved. The RRC recovery request (RRCresumeRequest, or, RRCresumeRequest1) message carries the identifier of the terminal device and the Identify Radio Network Temporary Identifier (I-RNTI) I-RNTI. The requesting service 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. The last serving access network device may respond with a Retrieve UE CONTEXT RESPONSE or a Retrieve UE CONTEXT failure.
[0036] In other words, after the terminal device sends an RRC resume request (RRCresumeRequest), the requesting service access network device will send a retrieve UE context request to the last service access network device. The last service access network device will send a RETRIEVE UE CONTEXT RESPONSE (UE context retrieval success) or a RETRIEVE UECONTEXT failure (UE context retrieval failure).
[0037] Figure 2 A schematic flow chart of a wireless communication method 200 according to an embodiment of the present application is shown. The method 200 can be interactively executed by a terminal device, a requesting service access network device, a final service access network device, and an AMF. Figure 2 The terminal device shown in FIG. 1 may be a terminal device such as Figure 1 The terminal equipment shown, Figure 2 The requesting service access network device and the final service access network device shown in FIG. 1 may be as follows: Figure 1 The access network equipment shown. Figure 3 The AMF shown in FIG. 1 may be Figure 1 The core network equipment shown.
[0038] The following describes a process for a terminal device to successfully restore an RRC connection in conjunction with the method 200.
[0039] like Figure 2 As shown, the method 200 may include some or all of the following contents:
[0040] S210, the terminal device sends an RRCresumeRequest to the service access network device requesting the service, and provides an I-RNTI in the resume request. The I-RNTI may be the last one allocated to the terminal device by the service access network device.
[0041] S220, if the requesting service access network device can address the last service access network device according to the I-RNTI, the requesting service access network device sends a restore UE context request to the last service access network device, which is used to request the last service access network device to provide a UE context (context), and the UE context can also be called UE context data (data).
[0042] S230, finally the serving access network device sends a recovery UE context response to the requesting service access network device to provide UE context data to the requesting service access network device.
[0043] S240, requesting the service access network device to send RRC recovery to the terminal device.
[0044] S250, the terminal device sends an RRC recovery completion to the service requesting access network device to complete the recovery of the RRC connection.
[0045] S260, if there is downlink data in the last serving access network device, to avoid data loss, the requesting service access network device may send an address indication to the last serving access network device to provide the last serving access network device with an address for forwarding data.
[0046] S270, request the service access network device to send a path switching request to the AMF to perform path switching (pathswitch).
[0047] S280, requesting the service access network device to receive the path switching request response sent by AMF to complete the path switching.
[0048] S290: Request the serving access network device to trigger the last serving access network device to release UE resources on the last serving access network device.
[0049] Figure 3 A schematic flow chart of a wireless communication method 300 according to an embodiment of the present application is shown. The method 300 can be interactively executed by a terminal device, a requesting service access network device, a final service access network device, and an AMF. Figure 3 The terminal device shown in FIG. 1 may be a terminal device such as Figure 1 The terminal equipment shown, Figure 3 The requesting service access network device and the final service access network device shown in FIG. 1 may be as follows: Figure 1 The access network equipment shown. Figure 3 The AMF shown in FIG. 1 may be Figure 1 The core network equipment shown.
[0050] The following describes the process of a terminal device failing to restore an RRC connection in conjunction with the method 300.
[0051] like Figure 3 As shown, the method 300 may include:
[0052] S310, the terminal device sends an RRCresumeRequest to the service access network device requesting the service. For example, the resume request provides an I-RNTI, which is an identifier last assigned to the terminal device by the service access network device.
[0053] S320: If the requesting service access network device can address the last service access network device according to the I-RNTI, the requesting service access network device sends a restore UE context request to the last service access network device to request the last service access network device to provide UE context data.
[0054] S330: Finally, the service access network device cannot recover or authenticate the UE context data.
[0055] S340, finally, the service access network device indicates the recovery failure to the requesting service access network device.
[0056] S350, requesting the service access network device to trigger the terminal device to perform fallback, for example, a new RRC connection can be established by sending RRCsetup.
[0057] S360, execute RRC connection establishment process.
[0058] In the method 200 and the method 300, the last serving access network device determines whether the retrieve UE context is successful or failed only based on the UE context, without considering the slice information. However, in the actual recovery process, even if the last serving access network device can obtain the context, it is possible that the current requesting serving access network device cannot support the terminal device to access the network or slice due to the slice problem, which results in the operation of obtaining the context first and then releasing the context, increasing the delay and signaling overhead.
[0059] In the present application, slice information is taken into consideration in the process of requesting the service access network device to restore the RRC connection, so that access control can be performed.
[0060] It should be understood that the slicing information may be relevant information of network slicing, and the network slicing may also be referred to as slicing for short. To facilitate the understanding of this solution, an exemplary explanation of network slicing is given below.
[0061] Based on network slicing, multiple services with different requirements can be provided with lower latency, more targeted, greater flexibility and higher scalability services. For example, Radio Access Network (RAN) slicing can enable application providers to participate in the design, deployment and operation of customized RAN to better support the services of application providers. The terminal device can report the slicing requirements. After receiving the slicing requirements reported by the terminal device, the access network device can select the appropriate MAF according to the slicing requirements reported by the UE to establish a service session between the UE and the network. Since the access network device can only determine the slicing information required by the terminal device after receiving message 5 (MSG5), and the slicing information required by the terminal device may not be the slicing supported by the requesting service access network device, or although it is the slicing supported by the requesting service access network device, the slicing is overloaded. In this case, the requesting service access network device can only send an RRC release (RRCRelease) message to the terminal device after MSG5, so that the terminal device reselects a suitable cell. As a result, it is possible that other suitable terminal devices will be delayed in access due to the access of the terminal device, and the delay in providing the slicing service of the terminal device may also be increased.
[0062] Figure 4 A schematic flow chart of a wireless communication method 400 according to an embodiment of the present application is shown. The method 400 may be executed by a requesting service access network device or a last serving access network device. Figure 4 The requesting service access network device and the final service access network device shown in FIG. 1 may be as follows: Figure 1 The access network equipment shown.
[0063] S410, the access network device determines the result of restoring the user equipment UE context or the access control result according to the slice information.
[0064] In other words, the access network device determines the RRC rejection message based on the slice information, and the RRC rejection message is used to trigger the terminal device to re-establish the RRC connection.
[0065] Or, in other words, the access network device determines whether access to the network is allowed based on the slice information.
[0066] Or, in other words, the access network device determines the result of restoring the UE context request based on the slice information.
[0067] Slice information is taken into consideration when the access network device determines to restore the RRC connection, i.e., access control is performed based on the slice information. When the slice of the terminal device is not supported by the access network device, it avoids releasing the RRC connection resources of the UE after the terminal device accesses the network, thereby reducing latency and signaling overhead.
[0068] In some embodiments of the present application, the result of restoring the UE context is a restoring UE context response.
[0069] In some embodiments of the present application, the recovery UE context response is used to indicate that the UE context is successfully restored, and / or, the recovery UE context response is used to indicate that the terminal device can access the network or slice, and / or the recovery UE context response is used to indicate that at least some of the slices of the terminal device are supported, and / or, the recovery 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 service access network device can support at least some of the slices of the terminal device.
[0070] Of course, the recovery UE context response may also include second indication information and / or a second cause value, and the second indication information and / or the second cause value can be used to indicate at least one of the following: the UE context is restored successfully, and / or the recovery UE context response is used to indicate that the terminal device can access the network or slice, and / or the recovery UE context response is used to indicate that at least some of the slices of the terminal device are supported, and / or the recovery 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 service access network device can support at least some of the slices of the terminal device.
[0071] It should be noted that at least some of the slices in the slices of the terminal device may be some of the slices, or all of the slices.
[0072] In some embodiments of the present application, the result of restoring the UE context is a failure to restore the UE context.
[0073] In some embodiments of the present application, 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 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 service access network device does not support at least some of the slices of the terminal device.
[0074] It should be noted that at least some of the slices in the slices of the terminal device may be some of the slices, or all of the slices.
[0075] For example, 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 all slices of the terminal device are not supported, and / or the failure to restore the UE context is used to indicate that all slices of the terminal device are overloaded, and / or the requesting service access network device does not support all slices of the terminal device.
[0076] In some embodiments of the present application, the failure to restore the UE context includes a 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 failure, non-UE context authentication failure, non-UE context 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, the requesting service access network device does not support at least some of the slices of the terminal device, an RRC rejection message, and information for triggering the requesting service access network device to send an RRC rejection message to the terminal device. Optionally, the RRC rejection message may be an unencrypted and / or integrity-protected message. Optionally, the information for triggering the requesting service access network device to send an RRC rejection message to the terminal device may be an indication that the requesting service access network device generates an RRC rejection message, or an indication that an anchor access network device generates an RRC rejection message and sends it to the terminal device. Explain in the specification
[0077] In some embodiments of the present application, the method 400 may further include:
[0078] The access network device obtains or sends an RRC reject message.
[0079] In some embodiments of the present application, the RRC reject message is a message generated by the last access network device, or the RRC reject message is a message generated by the requesting service access network device according to the restore UE context failure message sent by the last service access network device, the first indication information and at least one of the first cause value. In some embodiments of the present application, the RRC reject message is a message generated by the last service access network device, and the RRC reject message is encapsulated in the restore UE context failure. In some embodiments of the present application, the RRC reject message is sent by the requesting service access network device to the terminal device. In some embodiments of the present application, the RRC reject message is sent by the requesting service access network device to the terminal device after the last service access network device sends it to the requesting service access network device. In some embodiments of the present application, the RRC reject 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: non-UE context acquisition failure, non-UE context authentication failure, non-UE context 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, the requesting service access network device does not support at least some of the slices of the terminal device, the RRC reject message, and information used to trigger the requesting service access network device to send an RRC reject message to the terminal device. In some embodiments of the present application, the RRC reject message also includes the slice identifier supported by the requesting service access network device and / or the identifier of the slice that is not overloaded.
[0080] In some embodiments of the present application, the slice information includes at least one of the following information:
[0081] first information obtained from the terminal device;
[0082] second information obtained from the access management function AMF;
[0083] third information obtained from the service requesting access network device; or
[0084] Finally, the fourth information is stored by the service access network device.
[0085] In some embodiments of the present application, the first information includes information of at least one slice among the slices requested, allowed, established, and pre-configured by the terminal device.
[0086] In some embodiments of the present application, the first information is a slice identifier.
[0087] In some embodiments of the present application, the first information is information obtained from the terminal device through a random access channel RACH process, and / or the first information is information obtained from the terminal device through an RRC recovery request or an RRC recovery request 1.
[0088] 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.
[0089] 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 auxiliary information NSSAI list, a slice overload list, a slice overload response, or information used to indicate a reduction in slice traffic load.
[0090] In some embodiments of the present application, the third information includes the first information and / or the second information.
[0091] In some embodiments of the present application, the third information is carried in a restore UE context request message.
[0092] In some embodiments of the present application, the fourth information is information of at least one slice of the slices of the requested, allowed, established, pre-configured, and established terminal device saved by the last serving access network device.
[0093] In some embodiments of the present application, the access network device is a last serving access network device.
[0094] In some embodiments of the present application, the access network device is a service requesting access network device.
[0095] In some embodiments of the present application, the method 400 may further include:
[0096] The requesting service access network device determines whether to trigger a UE context recovery request process.
[0097] In some embodiments of the present application, the identifier of the last serving access network device is an identifier obtained by requesting the serving access network device to parse the identifier Radio Network Temporary I-RNTI reported by the terminal device.
[0098] The wireless communication method of the present application is described below with reference to a specific flowchart.
[0099] Figure 5 A schematic flow chart of a wireless communication method 500 according to an embodiment of the present application is shown. The method 500 can be interactively executed by a terminal device, a requesting service access network device, and a final serving access network device. Figure 5 The terminal device shown in FIG. 1 may be a terminal device such as Figure 1 The terminal equipment shown, Figure 5 The requesting service access network device and the final service access network device shown in FIG. 1 may be as follows: Figure 1 The access network equipment shown.
[0100] like Figure 5 As shown, the method 500 may include:
[0101] S510, the terminal device in the RRC deactivated state sends a radio resource control (RRC) recovery request (RRCResumeRequest or RRCResumeRequest1) to the service requesting access network device. Optionally, the RRC recovery request may include at least one of the following information:
[0102] a). I-RNTI, the I-RNTI may be the last one assigned to the terminal device by the serving access network device.
[0103] b). First information. Optionally, the first information may be a slice identifier. Optionally, the first information may include information about the requested / allowed / established / pre-configured slice of the terminal device.
[0104] S520: If the requesting service access network device can address the last service access network device identifier according to the I-RNTI, the requesting service access network device sends a retrieve UE context request to the last service access network device. Optionally, the retrieve UE context request may include at least one of the following:
[0105] a). The first information obtained from the terminal device.
[0106] b). The second information obtained from the access management function AMF. The second information may also be referred to as non-UE, such as network-level, slice information, or may be information for a terminal device or a slice of the terminal device. The second information may be notified by the AMF to the requesting service access network device. Exemplarily, the second information may be carried in an overload start message, for example, the second information obtained by the requesting service access network device may be a complete overload start message obtained by the requesting service access network device from the AMF, or may 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: an overload start network slice selection auxiliary information NSSAI list (Overload Start NSSAI List), a slice overload list (Slice Overload List), a slice overload response (Slice Overload Response) or information indicating a slice traffic load reduction (Slice Traffic Load Reduction Indication). Optionally, the second information may be obtained in advance, requested at the time, or stored.
[0107] Of course, the first information can be the information notified by the terminal device to the service requesting access network device through the RACH process, or it can be the information notified by the terminal device to the service requesting access network device through RRCResumeRequest or RRCResumeRequest1. Similarly, the slice information can be carried in the retrieve UE context request, or it can be carried in a message different from the retrieve UE context request.
[0108] S530, finally, the service access network device receives the request to restore the UE context, and determines the result of restoring the UE context based on the slice information in the request to restore the UE context. Optionally,
[0109] a). 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 for the terminal device or 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 message, for example, the second information obtained by the requesting service access network device may be the complete overload start message obtained by the requesting service access network device from the AMF, or may be only at least part of the information related to the slice overload in the overloadstart message. Optionally, the overload start message may include at least one of the following: an overload start network slice selection auxiliary information NSSAI list (Overload Start NSSAI List), a slice overload list (Slice Overload List), a slice overload response (Slice Overload Response) or information indicating a reduction in slice traffic load (Slice Traffic Load Reduction Indication). Optionally, the second information may be obtained in advance, requested at the time, or stored.
[0110] b) The third information obtained from the service requesting access network device, for example, the first information and the second information.
[0111] Optionally, the second information in a) and the second information in the third information may be the same or different.
[0112] c) The fourth information stored by the last serving access network device. For example, the information of at least one slice of the slices of the terminal device requested, allowed, established, preconfigured, or established stored by the last serving access network device.
[0113] S540, the last serving access network device sends a retrieve UE context response to the requesting service access network device. For example, the last serving access network device determines whether the terminal device can access the network or whether at least one of the slices of the terminal device is accepted / not overloaded based on the retrieve UE context request. If the terminal device can access the network or all slices of the slices of the terminal device or at least one slice is accepted / not overloaded, the last serving access network device sends a retrieve UE context response to the requesting service access network device. Optionally, the role, meaning and specific contents of the retrieve UE context response can be found in the description of method 400. To avoid repetition, they will not be repeated here.
[0114] S550, the requesting service access network device performs subsequent operations, such as sending a RRCResume message to the UE.
[0115] In method 500, the service access network device can finally determine whether the terminal device can access the network or whether at least part of the slices of the terminal device are supported based on the slice information, and then send a restore UE context response to the service access network device requesting service only when it is determined that the terminal device can access the network or at least part of the slices of the terminal device are supported. Based on this, it is avoided that the UE context is restored and then released when the slice of the terminal device is not supported, which can reduce latency and signaling overhead.
[0116] Figure 6 A schematic flow chart of a wireless communication method 600 according to an embodiment of the present application is shown. The method 600 can be interactively executed by a terminal device, a requesting service access network device, and a final serving access network device. Figure 6 The terminal device shown in FIG. 1 may be a terminal device such as Figure 1 The terminal equipment shown, Figure 6 The requesting service access network device and the final service access network device shown in FIG. 1 may be as follows: Figure 1 The access network equipment shown.
[0117] like Figure 6 As shown, the method 600 may include:
[0118] S610, the terminal device in the RRC deactivated state sends a radio resource control (RRC) recovery request (RRCResumeRequest or RRCResumeRequest1) to the service requesting access network device. Optionally, the RRC recovery request may include at least one of the following information:
[0119] a). I-RNTI, the I-RNTI may be the last one assigned to the terminal device by the serving access network device.
[0120] b). First information. Optionally, the first information may be a slice identifier. Optionally, the first information may include information about the requested / allowed / established / pre-configured slice of the terminal device.
[0121] S620: If the requesting service access network device can address the last service access network device identifier according to the I-RNTI, the requesting service access network device sends a retrieve UE context request to the last service access network device. Optionally, the retrieve UE context request may include at least one of the following:
[0122] a). The first information obtained from the terminal device.
[0123] b). The second information obtained from the access management function AMF. The second information may also be referred to as non-UE, such as network-level, slice information, or may be information for a terminal device or a slice of the terminal device. The second information may be notified by the AMF to the requesting service access network device. Exemplarily, the second information may be carried in an overload start message, for example, the second information obtained by the requesting service access network device may be a complete overload start message obtained by the requesting service access network device from the AMF, or may 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: an overload start network slice selection auxiliary information NSSAI list (Overload Start NSSAI List), a slice overload list (Slice Overload List), a slice overload response (Slice Overload Response) or information indicating a slice traffic load reduction (Slice Traffic Load Reduction Indication). Optionally, the second information may be obtained in advance, requested at the time, or stored.
[0124] Of course, the first information can be the information notified by the terminal device to the service requesting access network device through the RACH process, or it can be the information notified by the terminal device to the service requesting access network device through RRCResumeRequest or RRCResumeRequest1. Similarly, the slice information can be carried in the retrieve UE context request, or it can be carried in a message different from the retrieve UE context request.
[0125] S630, finally, the service access network device receives the request to restore the UE context, and determines the result of restoring the UE context based on the slice information in the request to restore the UE context.
[0126] a). 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 for the terminal device or 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 message, for example, the second information obtained by the requesting service access network device may be the complete overload start message obtained by the requesting service access network device from the AMF, or may be only at least part of the information related to the slice overload in the overloadstart message. Optionally, the overload start message may include at least one of the following: an overload start network slice selection auxiliary information NSSAI list (Overload Start NSSAI List), a slice overload list (Slice Overload List), a slice overload response (Slice Overload Response) or information indicating a reduction in slice traffic load (Slice Traffic Load Reduction Indication). Optionally, the second information may be obtained in advance, requested at the time, or stored.
[0127] b) The third information obtained from the service requesting access network device, for example, the first information and the second information.
[0128] Optionally, the second information in a) and the second information in the third information may be the same or different.
[0129] c) The fourth information stored by the last serving access network device. For example, the information of at least one slice of the slices of the terminal device requested, allowed, established, preconfigured, or established stored by the last serving access network device.
[0130] S640, the last serving access network device sends a retrieve UE context failure to the requesting service access network device. For example, the last serving access network device determines whether the terminal device can access the network or whether at least one of the slices of the terminal device is accepted / not overloaded based on the request to recover the UE context. If the terminal device cannot access the network or at least one of the slices of the terminal device or all the slices are not accepted / overloaded, the last serving access network device sends a retrieve UE context failure to the requesting service access network device. Optionally, the role, meaning and specific contents of the UE context recovery failure can be found in the description of method 400. To avoid repetition, they will not be repeated here.
[0131] S650, the requesting service 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 first indication information or the first cause value. Optionally, the RRC rejection message also includes a slice identifier supported by the requesting service access network device and / or an identifier of a slice that is not overloaded.
[0132] In the method 600, the last 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 a retrieve UE context failure to the UE. Based on this, it is avoided that the UE context is restored and then released when the slice of the terminal device is not supported, which can reduce latency and signaling overhead.
[0133] Figure 7 A schematic flow chart of a wireless communication method 700 according to an embodiment of the present application is shown. The method 700 can be interactively executed by a terminal device and a service requesting access network device. Figure 7 The terminal device shown in FIG. 1 may be a terminal device such as Figure 1 The terminal equipment shown, Figure 6 The request service access network device shown in FIG. 1 may be as follows: Figure 1 The access network equipment shown.
[0134] like Figure 7As shown, the method 700 may include:
[0135] S710, the terminal device in the RRC deactivated state sends a radio resource control (RRC) recovery request (RRCResumeRequest or RRCResumeRequest1) to the service requesting access network device. Optionally, the RRC recovery request may include at least one of the following information:
[0136] a). I-RNTI, the I-RNTI may be the last one assigned to the terminal device by the serving access network device.
[0137] b). First information. Optionally, the first information may be a slice identifier. Optionally, the first information may include information about the requested / allowed / established / pre-configured slice of the terminal device.
[0138] S720, requesting the service access network device to receive the RRC recovery request, and determining the access control result based on the slice information, whether to send a request to restore the UE context and at least one of the results of restoring the UE context. Optionally, the request to restore the UE context may include at least one of the following:
[0139] a). The first information obtained from the terminal device.
[0140] 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 for the terminal device or the slice of the terminal device. The second information may be notified by the AMF to the requesting service access network device. Exemplarily, the second information may be carried in an overload start message, for example, the second information obtained by the requesting service access network device may be the complete overload start message obtained by the requesting service access network device from the AMF, or may be only at least part of the information related to the slice overload in the overloadstart message. Optionally, the overload start message may include at least one of the following: an overload start network slice selection auxiliary information NSSAI list (Overload Start NSSAI List), a slice overload list (Slice Overload List), a slice overload response (Slice Overload Response) or information indicating a reduction in slice traffic load (Slice Traffic Load Reduction Indication). Optionally, the second information may be obtained in advance, requested at the time, or stored.
[0141] S730, if the service access network device is requested to determine that at least one of the slices of the terminal device is accessible / not overloaded, the service access network device is requested to send an RRC resume (RRCresume) message to the UE, or, after obtaining the restore UE context response message, sends an RRCresume message to the UE; and / or, if the service access network device is requested to determine that at least one of the slices of the UE is not accessible / overloaded, the service access network device is requested to send an RRCReject message to the UE, or, after obtaining the restore UE context response / failure message, sends an RRCReject message to the UE; and / or, if the service access network device is requested to determine that at least one of the slices of the terminal device is not accessible / overloaded, the service access network device is requested to determine that the request to restore the context fails, or determines that the request to restore the context fails after obtaining the restore UE context response / failure message.
[0142] S740: If the requesting service access network device determines that at least one of the UE slices can be accessed, and if the requesting service access network device can address the last service access network device identifier according to the I-RNTI, the requesting service access network device sends a retrieve UE context request to the last service access network device. The last service access network device receives the retrieve UE context request message and determines the result of retrieving UE context. Optionally, the last service access network device receives the retrieve UE context request message and determines the result of retrieving UE context according to the slice information.
[0143] In method 700, the service access network device can determine whether the terminal device can access the network or whether at least part of the slices of the terminal device are supported based on the slice information. For example, when it is determined that the network cannot be accessed or at least part of the slices of the terminal device are not supported, an RRC rejection message is sent to 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 latency and signaling overhead.
[0144] In other words, the requesting service access network device determines whether to send RRCReject to the UE based on the slice information. For example, if the requesting service access network device determines that the slice of the terminal device is inaccessible, such as the slice of the terminal device is overloaded, the requesting service access network device sends RRCreject to the terminal device. Otherwise, the requesting service access network device executes the subsequent normal process, that is, the requesting service access network device executes the send retrieve UE context Request to the last service access network device, etc. This is equivalent to determining whether to send RRCreject to the terminal device through a non-interactive confirmation access method when the requesting service access network device can obtain the slice information of the terminal device. Based on this, it avoids restoring the UE context and then releasing the UE context when the slice of the terminal device is not supported, which can reduce latency and signaling overhead.
[0145] It should be understood that in various method embodiments of the present application, the size of the sequence number of each process does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application. For example, the above S730 and S740 can be executed at the same time, or S730 can be executed first and then S740, or S740 can be executed first and then S730.
[0146] The preferred embodiments of the present application are described in detail above in conjunction with the accompanying drawings. However, the present application is not limited to the specific details in the above embodiments. Within the technical concept of the present application, the technical solution of the present application can be subjected to a variety of simple modifications, and these simple modifications all belong to the protection scope of the present application. For example, the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, the present application will not further explain various possible combinations. For another example, the various different embodiments of the present application can also be arbitrarily combined, as long as they do not violate the ideas of the present application, they should also be regarded as the contents disclosed in the present application.
[0147] 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 a first direction from a site to a user device of a cell, and "uplink" is used to indicate that the transmission direction of signals or data is a second direction from a user device of a cell to a site. For example, "downlink signal" indicates that the transmission direction of the signal is a first direction. In addition, in the embodiments of the present application, the term "and / or" is merely a description of the association relationship of associated objects, indicating that three relationships may exist. 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 article generally indicates that the previously associated objects are in an "or" relationship.
[0148] Combination of the above Figures 1 to 7 , describes in detail the method embodiment of the present application, and the following is combined with Figures 8 to 10 , describe in detail the device embodiments of the present application.
[0149] Figure 8 It is a schematic block diagram of an access network device 800 according to an embodiment of the present application.
[0150] like Figure 8 As shown, the access network device 800 may include:
[0151] Processing unit 810 is used to determine the result of restoring the user equipment UE context or the access control result based on the slice information.
[0152] In some embodiments of the present application, the result of restoring the UE context is a restoring UE context response.
[0153] In some embodiments of the present application, the recovery UE context response is used to indicate that the UE context is successfully restored, and / or, the recovery UE context response is used to indicate that the terminal device can access the network or slice, and / or the recovery UE context response is used to indicate that at least some of the slices of the terminal device are supported, and / or, the recovery 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 service access network device can support at least some of the slices of the terminal device.
[0154] In some embodiments of the present application, the result of restoring the UE context is a failure to restore the UE context.
[0155] In some embodiments of the present application, 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 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 service access network device does not support at least some of the slices of the terminal device.
[0156] In some embodiments of the present application, the failure to restore the UE context includes a 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 failure, non-UE context authentication failure, non-UE context 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, the requesting service access network device does not support at least some of the slices of the terminal device, an RRC rejection message, and information used to trigger the requesting service access network device to send an RRC rejection message to the terminal device.
[0157] In some embodiments of the present application, the access network device further includes:
[0158] The communication unit is used to obtain or send an RRC rejection message.
[0159] In some embodiments of the present application, the RRC reject message is a message generated by the last access network device, or the RRC reject message is a message generated by the requesting service access network device based on the UE context recovery failure message, the first indication information and at least one of the first cause value sent by the last service access network device.
[0160] In some embodiments of the present application, 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 the UE context.
[0161] In some embodiments of the present application, the RRC rejection message is a message sent by the requesting service access network device to the last service access network device.
[0162] 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: non-UE context acquisition failure, non-UE context authentication failure, non-UE context 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, the requesting service access network device does not support at least some of the slices of the terminal device, an RRC rejection message, and information used to trigger the requesting service access network device to send an RRC rejection message to the terminal device.
[0163] In some embodiments of the present application, the RRC rejection message also includes a slice identifier supported by the requested service access network device and / or an identifier of a slice that is not overloaded.
[0164] In some embodiments of the present application, the slice information includes at least one of the following information:
[0165] first information obtained from the terminal device;
[0166] second information obtained from the access management function AMF;
[0167] third information obtained from the service requesting access network device; or
[0168] Finally, the fourth information is stored by the service access network device.
[0169] In some embodiments of the present application, the first information includes information of at least one slice among the slices requested, allowed, established, and pre-configured by the terminal device.
[0170] In some embodiments of the present application, the first information is a slice identifier.
[0171] In some embodiments of the present application, the first information is information obtained from the terminal device through a random access channel RACH process, and / or the first information is information obtained from the terminal device through an RRC recovery request or an RRC recovery request 1.
[0172] 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.
[0173] 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 auxiliary information NSSAI list, a slice overload list, a slice overload response, or information used to indicate a reduction in slice traffic load.
[0174] In some embodiments of the present application, the third information includes the first information and / or the second information.
[0175] In some embodiments of the present application, the third information is carried in a restore UE context request message.
[0176] In some embodiments of the present application, the fourth information is information of at least one slice of the slices of the requested, allowed, established, pre-configured, and established terminal device saved by the last serving access network device.
[0177] In some embodiments of the present application, the access network device is a last serving access network device.
[0178] In some embodiments of the present application, the access network device is a service requesting access network device.
[0179] In some embodiments of the present application, the processing unit 810 is further configured to:
[0180] Determine whether to trigger the restore UE context request procedure.
[0181] In some embodiments of the present application, the identifier of the last serving access network device is an identifier obtained by requesting the serving access network device to parse the identifier Radio Network Temporary I-RNTI reported by the terminal device.
[0182] It should be understood that the device embodiment and the method embodiment may correspond to each other, and similar descriptions may refer to the method embodiment. Specifically, Figure 8 The access network device 800 shown may correspond to the corresponding subject in the method 200 to the method 700 of the embodiment of the present application, such as the request service access network device or the last service access network device. And the aforementioned and other operations and / or functions of each unit in the access network device 800 are respectively to implement Figures 2 to 7 For the sake of brevity, the corresponding processes in each method are not repeated here.
[0183] The communication device of the embodiment of the present application is described above from the perspective of functional modules in conjunction with the accompanying drawings. It should be understood that the functional modules can be implemented in hardware form, can also be implemented by software instructions, and can also be implemented by a combination of hardware and software modules.
[0184] Specifically, each step of the method embodiment in the embodiment of the present application can be completed by the hardware integrated logic circuit and / or software instructions in the processor. The steps of the method disclosed in the embodiment of the present application can be directly reflected as being executed by a hardware decoding processor, or being executed by a combination of hardware and software modules in the decoding processor.
[0185] Optionally, the software module may be located in a mature storage medium in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, a register, etc. 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 embodiment in combination with its hardware.
[0186] For example, the processing unit and the communication unit mentioned above may be implemented by a processor and a transceiver, respectively.
[0187] Fig. 9 It is a schematic structural diagram of a communication device 900 according to an embodiment of the present application.
[0188] like Fig. 9 As shown, the communication device 900 may include a processor 910 .
[0189] The processor 910 may call and run a computer program from the memory to implement the method in the embodiment of the present application.
[0190] Please continue to see Fig. 9 , the communication device 900 may further include a memory 920 .
[0191] 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 method in the embodiment 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.
[0192] Please continue to see Fig. 9 , the communication device 900 may further include a transceiver 930 .
[0193] The processor 910 may control the transceiver 930 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices. The transceiver 930 may include a transmitter and a receiver. The transceiver 930 may further include an antenna, and the number of antennas may be one or more.
[0194] It should be understood that the various components in the communication device 900 are connected via a bus system, wherein the bus system includes not only a data bus but also a power bus, a control bus and a status signal bus.
[0195] It should also be understood that the communication device 900 may be a terminal device of the 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 embodiment of the present application, that is, the communication device 900 of the embodiment of the present application may correspond to the access network device 800 in the embodiment of the present application. For example, the communication device 900 may correspond to executing the corresponding subjects in the methods 200 to 700 according to the embodiments of the present application, and for the sake of brevity, it will not be repeated here.
[0196] In addition, a chip is also provided in an embodiment of the present application.
[0197] For example, the chip may be an integrated circuit chip with signal processing capabilities, and can implement or execute the methods, steps, and logic diagrams disclosed in the embodiments of the present application. The chip may also be called a system-level chip, a system chip, a chip system, or a system-on-chip chip, etc. Optionally, the chip can be applied to various communication devices, so that the communication device equipped with the chip can execute the methods, steps, and logic diagrams disclosed in the embodiments of the present application.
[0198] Fig.10 is a schematic structural diagram of a chip 1000 according to an embodiment of the present application.
[0199] like Fig.10 As shown, the chip 1000 includes a processor 1010 .
[0200] The processor 1010 may call and run a computer program from the memory to implement the method in the embodiment of the present application.
[0201] Please continue to see Fig.10 , the chip 1000 may further include a memory 1020 .
[0202] The processor 1010 may call and run a computer program from the memory 1020 to implement the method in the embodiment of the present application. The memory 1020 may be used to store indication 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.
[0203] Please continue to see Fig.10 , the chip 1000 may further include an input interface 1030 .
[0204] The processor 1010 may control the input interface 1030 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.
[0205] Please continue to see Fig.10 , the chip 1000 may further include an output interface 1040 .
[0206] The processor 1010 may control the output interface 1040 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.
[0207] 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 requesting service access network device in the various methods of the embodiments of the present application, and can also implement the corresponding processes implemented by the final service access network device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.
[0208] It should also be understood that the various components in the chip 1000 are connected via a bus system, wherein the bus system includes not only a data bus but also a power bus, a control bus and a status signal bus.
[0209] The processors mentioned above may include but are not limited to:
[0210] General-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, etc.
[0211] The processor can be used to implement or execute the methods, steps and logic block diagrams disclosed in the embodiments of the present application. The steps of the method disclosed in the embodiments of the present application can be directly embodied as a hardware decoding processor, or a combination of hardware and software modules in the decoding processor. The software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an erasable programmable memory, a register, etc. The storage medium is located in a memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
[0212] The memory mentioned above includes but is not limited to:
[0213] Volatile memory and / or non-volatile memory. Among them, the non-volatile memory can be read-only memory (ROM), programmable ROM (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM) or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM bus random access memory (DR RAM).
[0214] It should be noted that the memory described herein is intended to include these and any other suitable types of memory.
[0215] In an embodiment of the present application, a computer-readable storage medium is further provided for storing computer programs. The computer-readable storage medium stores one or more programs, and the one or more programs include instructions, which, when executed by a portable electronic device including multiple application programs, enable the portable electronic device to execute the methods of the embodiments shown in methods 200 to 700.
[0216] 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 the sake of brevity, they are not repeated here.
[0217] 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 the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.
[0218] A computer program product is also provided in an embodiment of the present application, including a computer program.
[0219] 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 the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.
[0220] 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 the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.
[0221] The present application also provides a computer program in an embodiment. When the computer program is executed by a computer, the computer can execute the methods in the embodiments shown in method 200 to method 700.
[0222] Optionally, the computer program can be applied to the network device in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the network device in the various methods in the embodiments of the present application. For the sake of brevity, they are not described here.
[0223] In addition, the embodiment of the present application also provides a communication system, which may include the terminal device and the network device involved above to form a communication system as follows: Figure 1 The communication system 100 shown is not described in detail for the sake of brevity. It should be noted that the term "system" and the like in this document may also be referred to as "network management architecture" or "network system" and the like.
[0224] It should also be understood that the terms used in the embodiments of the present application and the appended claims are for the purpose of describing specific embodiments only and are not intended to limit the embodiments of the present application.
[0225] For example, as used in the embodiments of the present application and the appended claims, the singular forms "a," "said," "above," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
[0226] Those skilled in the art will appreciate 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. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the embodiments of the present application.
[0227] If implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in the embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory, a random access memory, a magnetic disk or an optical disk.
[0228] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0229] In several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other ways.
[0230] For example, the division of units or modules or components in the device embodiment described above is only a logical function division, and there may be other division methods in actual implementation. For example, multiple units or modules or components can be combined or integrated into another system, or some units or modules or components can be ignored or not executed.
[0231] For another example, the units / modules / components described above as separation / display components may or may not be physically separated, that is, they may be located in one place, or they may be distributed on 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.
[0232] Finally, it should be noted that the mutual coupling or direct coupling or communication connection shown or discussed above may be an indirect coupling or communication connection through some interfaces, devices or units, which may be electrical, mechanical or other forms.
[0233] The above contents are only specific implementation methods of the embodiments of the present application, but the protection scope of the embodiments of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or replacements within the technical scope disclosed in the embodiments of the present application, which should be included in the protection scope of the embodiments of the present application. Therefore, the protection scope of the embodiments of the present application shall be based on the protection scope of the claims.
Claims
1. A wireless communication method, characterized in that: include: In the process of restoring the radio resource control RRC connection, the access network device determines the result of restoring the user equipment UE context according to the slice information; The slice information includes first information obtained from the terminal device and second information obtained from the access management function AMF; The first information includes a slice identifier of at least one slice among the slices requested, allowed, established, and preconfigured by the terminal device; The second information includes an overload start message or information related to slice overload in the overload start message; The overload start message includes 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 information used to indicate a reduction in slice traffic load.
2. The method according to claim 1, characterized in that The result of restoring the UE context is a restore UE context response.
3. The method according to claim 2, characterized in that The recovery UE context response is used to indicate that the UE context is successfully restored, and / or the recovery UE context response is used to indicate that the terminal device can access the network or slice, and / or the recovery UE context response is used to indicate that at least some of the slices of the terminal device are supported, and / or the recovery 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 service access network device can support at least some of the slices of the terminal device.
4. The method according to claim 1, characterized in that: The result of restoring the UE context is failure to restore the UE context.
5. The method according to claim 4, characterized in that 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 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 service access network device requested does not support at least some of the slices of the terminal device.
6. The method according to claim 4, characterized in that 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 failure, non-UE context authentication failure, non-UE context 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, the requesting service access network device does not support at least some of the slices of the terminal device, an RRC rejection message, and information used to trigger the requesting service access network device to send an RRC rejection message to the terminal device.
7. The method according to claim 1, characterized in that The method further comprises: The access network device obtains or sends an RRC reject message.
8. The method according to claim 7, characterized in that The RRC reject message is a message generated by the last access network device, or the RRC reject message is a message generated by the requesting service access network device based on at least one of the UE context recovery failure message, the first indication information and the first cause value sent by the last service access network device.
9. The method according to claim 7, characterized in that: 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 the UE context.
10. The method according to claim 7, characterized in that The RRC rejection message is a message that the requesting service access network device sends to the last service access network device.
11. The method according to claim 7, characterized in that The RRC rejection message 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 failure, non-UE context authentication failure, non-UE context 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, the requesting service access network device does not support at least some of the slices of the terminal device, an RRC rejection message, and information used to trigger the requesting service access network device to send an RRC rejection message to the terminal device.
12. The method according to claim 11, characterized in that The RRC rejection message also includes the slice identifier supported by the requested service access network device and / or the identifier of the slice that is not overloaded.
13. The method according to claim 1, characterized in that The slice information includes at least one of the following information: The third information obtained from the service access network device requesting the service; Finally, the fourth information is stored by the service access network device.
14. The method according to claim 1, characterized in that The first information is information obtained from the terminal device through a random access channel RACH process, and / or the first information is information obtained from the terminal device through an RRC recovery request.
15. The method according to claim 13, characterized in that The third information includes the first information and / or the second information.
16. The method according to claim 13, characterized in that The third information is carried in the restore UE context request message.
17. The method according to claim 13, characterized in that The fourth information is information of at least one slice among the slices of the requested, allowed, established, pre-configured, and established terminal device saved by the last serving access network device.
18. The method according to any one of claims 1 to 17, characterized in that The access network device is the last serving access network device.
19. The method according to any one of claims 1 to 17, characterized in that The access network device is a service requesting access network device.
20. The method according to claim 19, characterized in that The method further comprises: The requesting service access network device determines whether to trigger a UE context recovery request process.
21. The method according to claim 18, characterized in that The identifier of the last serving access network device is an identifier obtained by requesting the serving access network device to resolve the identifier Radio Network Temporary Identifier I-RNTI reported by the terminal device.
22. An access network device, characterized in that: include: A processing unit, configured to determine a result of restoring a user equipment UE context according to the slice information during the process of restoring a radio resource control RRC connection; The slice information includes first information obtained from the terminal device and second information obtained from the access management function AMF; The first information includes a slice identifier of at least one slice among the slices requested, allowed, established, and preconfigured by the terminal device; The second information includes an overload start message or information related to slice overload in the overload start message; The overload start message includes 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 information used to indicate a reduction in slice traffic load.
23. The access network device according to claim 22, characterized in that: The result of restoring the UE context is a restore UE context response.
24. The access network device according to claim 23, characterized in that: The recovery UE context response is used to indicate that the UE context is successfully restored, and / or the recovery UE context response is used to indicate that the terminal device can access the network or slice, and / or the recovery UE context response is used to indicate that at least some of the slices of the terminal device are supported, and / or the recovery 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 service access network device can support at least some of the slices of the terminal device.
25. The access network device according to claim 22, characterized in that: The result of restoring the UE context is failure to restore the UE context.
26. The access network device according to claim 25, characterized in that: 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 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 service access network device requested does not support at least some of the slices of the terminal device.
27. The access network device according to claim 25, characterized in that: 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 failure, non-UE context authentication failure, non-UE context 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, the requesting service access network device does not support at least some of the slices of the terminal device, an RRC rejection message, and information used to trigger the requesting service access network device to send an RRC rejection message to the terminal device.
28. The access network device according to claim 22, characterized in that: The access network equipment also includes: The communication unit is used to obtain or send an RRC rejection message.
29. The access network device according to claim 28, characterized in that: The RRC reject message is a message generated by the last access network device, or the RRC reject message is a message generated by the requesting service access network device based on at least one of the UE context recovery failure message, the first indication information and the first cause value sent by the last service access network device.
30. The access network device according to claim 28, characterized in that: 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 the UE context.
31. The access network device according to claim 28, characterized in that: The RRC rejection message is a message that the requesting service access network device sends to the last service access network device.
32. The access network device according to claim 28, characterized in that: The RRC rejection message 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 failure, non-UE context authentication failure, non-UE context 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, the requesting service access network device does not support at least some of the slices of the terminal device, an RRC rejection message, and information used to trigger the requesting service access network device to send an RRC rejection message to the terminal device.
33. The access network device according to claim 32, characterized in that: The RRC rejection message also includes the slice identifier supported by the requested service access network device and / or the identifier of the slice that is not overloaded.
34. The access network device according to claim 22, characterized in that: The slice information includes at least one of the following information: The third information obtained from the service access network device requesting the service; Finally, the fourth information is stored by the service access network device.
35. The access network device according to claim 22, characterized in that: The first information is information obtained from the terminal device through a random access channel RACH process, and / or the first information is information obtained from the terminal device through an RRC recovery request.
36. The access network device according to claim 34, characterized in that: The third information includes the first information and / or the second information.
37. The access network device according to claim 34, characterized in that: The third information is carried in the restore UE context request message.
38. The access network device according to claim 34, characterized in that: The fourth information is information of at least one slice among the slices of the requested, allowed, established, pre-configured, and established terminal device saved by the last serving access network device.
39. The access network device according to any one of claims 22 to 38, characterized in that: The access network device is the last serving access network device.
40. The access network device according to any one of claims 22 to 38, characterized in that: The access network device is a service requesting access network device.
41. The access network device according to claim 40, characterized in that: The processing unit is also used for: Determine whether to trigger the restore UE context request procedure.
42. The access network device according to claim 39, characterized in that: The identifier of the last serving access network device is an identifier obtained by requesting the serving access network device to resolve the identifier Radio Network Temporary Identifier I-RNTI reported by the terminal device.
43. A network device, characterized in that: include: A processor, a memory and a transceiver, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method according to any one of claims 1 to 21.
44. A chip, characterized in that: include: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 21.
45. A computer-readable storage medium, characterized in that Used to store a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 21.
46. A computer program product, characterized in that The method comprises computer program instructions which cause a computer to execute the method as claimed in any one of claims 1 to 21.
