Wireless communication method, device, chip, storage medium and program product

By using NAS messages to transmit SPS configuration information between core network devices and terminal devices, the problem of NB-IoT devices being unable to securely receive SPS configurations is solved, thereby improving information security and resource utilization efficiency.

WO2026232585A1PCT designated stage Publication Date: 2026-11-12GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2025/094069
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2025-05-09
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

In existing technologies, NB-IoT devices that support CP CIoT EPS/5GS optimization cannot securely receive SPS configuration information, which leads to malicious attacks on the network and terminal devices, as well as low resource utilization efficiency and high transmission latency.

Method used

The SPS configuration information is transparently transmitted to the terminal device through the core network equipment, and encrypted and protected with NAS messages to avoid direct transmission in AS messages, thus ensuring information security and resource utilization efficiency.

Benefits of technology

It enables secure transmission of SPS configuration information, reduces transmission latency, decreases dynamic scheduling signaling overhead, improves resource utilization efficiency, and optimizes network performance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2025094069_12112026_PF_FP_ABST
    Figure CN2025094069_12112026_PF_FP_ABST
Patent Text Reader

Abstract

Provided in the present application are a wireless communication method, a device, a chip, a storage medium and a program product. The method comprises: a terminal device receiving semi-persistent scheduling (SPS) configuration information sent by a core network device.
Need to check novelty before this filing date? Find Prior Art

Description

A wireless communication method and device, chip, storage medium, and software product Technical Field

[0001] This application relates to the field of communication technology, specifically to a wireless communication method and device, chip, storage medium, and program product. Background Technology

[0002] To better serve periodic business operations, the concept of pre-configured resources has been introduced. Semi-Persistent Scheduling (SPS) is an efficient radio resource allocation mechanism suitable for periodic or predictable data transmission scenarios. SPS configuration information defines how radio resources are periodically pre-allocated to terminal devices, reducing the signaling overhead of dynamic scheduling. Summary of the Invention

[0003] This application provides a wireless communication method and device, a chip, a storage medium, and a program product.

[0004] This application provides a wireless communication method, the method comprising:

[0005] The terminal device receives SPS configuration information sent by the core network device.

[0006] This application provides a wireless communication method, the method comprising:

[0007] The core network equipment sends SPS configuration information to the terminal equipment.

[0008] This application provides a wireless communication method, the method comprising:

[0009] Access network devices receive SPS configuration information sent by core network devices;

[0010] The access network device transmits the SPS configuration information to the terminal device.

[0011] This application provides a terminal device, including:

[0012] The first communication unit is configured to receive SPS configuration information sent by the core network equipment.

[0013] This application provides a core network device, including:

[0014] The second communication unit is configured to send SPS configuration information to the terminal device.

[0015] This application provides an access network device, including:

[0016] The third communication unit is configured to receive SPS configuration information sent by the core network equipment and to transmit the SPS configuration information to the terminal equipment.

[0017] The communication device provided in this application embodiment can be a terminal device, a core network device, or an access network device as described above. The communication device includes a processor and a memory. The memory stores computer programs, and the processor calls and runs the computer programs stored in the memory to execute the aforementioned wireless communication method.

[0018] The chip provided in this application embodiment is used to implement the above-described wireless communication method.

[0019] Specifically, the chip includes a processor for calling and running a computer program from a memory, causing a device equipped with the chip to perform the aforementioned wireless communication method.

[0020] The computer-readable storage medium provided in this application embodiment is used to store a computer program that causes a computer to execute the above-described wireless communication method.

[0021] The computer program product provided in this application includes computer program instructions that cause a computer to execute the above-described wireless communication method.

[0022] The computer program provided in this application embodiment, when run on a computer, causes the computer to execute the above-described wireless communication method.

[0023] Through the above technical solution, the core network equipment sends SPS configuration information to the terminal equipment, enabling the terminal equipment to perform semi-persistent scheduling configuration based on the SPS configuration information. This can reduce transmission latency, reduce the signaling overhead of dynamic scheduling, and improve resource utilization efficiency. Moreover, it can flexibly adapt to different service requirements and optimize network performance. Attached Figure Description

[0024] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0025] Figure 1 is a schematic diagram of a communication architecture provided in an embodiment of this application;

[0026] Figure 2 is a schematic diagram of an optional process for establishing an RRC connection provided in an embodiment of this application;

[0027] Figure 3 is an optional flowchart of the wireless communication method provided in an embodiment of this application;

[0028] Figure 4 is a schematic diagram of an optional wireless communication method provided in an embodiment of this application;

[0029] Figure 5 is a schematic diagram of an optional wireless communication method provided in an embodiment of this application;

[0030] Figure 6 is a schematic diagram of an optional wireless communication method provided in an embodiment of this application;

[0031] Figure 7 is a schematic diagram of an optional wireless communication method provided in an embodiment of this application;

[0032] Figure 8 is a schematic flowchart of an optional wireless communication method provided in an embodiment of this application;

[0033] Figure 9 is a schematic flowchart of an optional wireless communication method provided in an embodiment of this application;

[0034] Figure 10 is a schematic diagram of the composition structure of a terminal device provided in an embodiment of this application;

[0035] Figure 11 is a schematic diagram of the composition structure of a core network device provided in an embodiment of this application;

[0036] Figure 12 is a schematic diagram of the composition structure of an access network device provided in an embodiment of this application;

[0037] Figure 13 is a schematic diagram of the composition structure of a communication device provided in an embodiment of this application;

[0038] Figure 14 is a schematic diagram of the composition structure of a chip provided in an embodiment of this application;

[0039] Figure 15 is a schematic block diagram of a communication system provided in an embodiment of this application. Detailed Implementation

[0040] The technical solutions of the embodiments of this application will now be described with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0041] Figure 1 is a schematic diagram of an application scenario according to an embodiment of this application. As shown in Figure 1, the communication system 100 may include a terminal device 110 and an access network device 120. The access network device 120 can communicate with the terminal device 110 via an air interface. Multi-service transmission is supported between the terminal device 110 and the access network device 120.

[0042] It should be understood that the embodiments of this application are only illustrated by way of example with communication system 100, but the embodiments of this application are not limited thereto. That is to say, the technical solutions of the embodiments of this 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), Evolved Packet System (EPS), Internet of Things (IoT) system, Narrow Band Internet of Things (NB-IoT) system, Consumer Internet of Things (CIoT) system, enhanced Machine-Type Communications (eMTC) system, 5G communication system (also known as New Radio (NR) communication system), 6G communication system, or future communication systems, etc.

[0043] In the communication system 100 shown in Figure 1, the access network device 120 can be a network device that communicates with the terminal device 110. The access network device 120 can provide communication coverage for a specific geographical area and can communicate with the terminal device 110 (e.g., UE) located within that coverage area.

[0044] Access network equipment 120 may be an evolved Node B (eNB or eNodeB) in a Long Term Evolution (LTE) system, a Next Generation Radio Access Network (NG RAN) device, a base station (gNB) in an NR system, a base station in a 6G system, a radio controller in a Cloud Radio Access Network (CRAN), or the access network equipment 120 may be a relay station, access point, vehicle-mounted equipment, wearable device, hub, switch, bridge, router, or access network equipment in a future evolved Public Land Mobile Network (PLMN), etc.

[0045] Terminal device 110 can be any terminal device, including but not limited to terminal devices that are connected to access network device 120 or other terminal devices via wired or wireless connections.

[0046] For example, the terminal device 110 can refer to an access terminal, user equipment (UE), user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, narrowband Internet of Things (NB-IoT) device, wireless communication device, user agent, or user device. The access terminal can be a cellular phone, cordless phone, Session Initiation Protocol (SIP) phone, IoT device, satellite handheld terminal, Wireless Local Loop (WLL) station, Personal Digital Assistant (PDA), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, in-vehicle device, wearable device, terminal device in a 5G network, terminal device in a 6G network, or terminal device in a future evolved network, etc.

[0047] Terminal device 110 can be used for device-to-device (D2D) communication.

[0048] The communication system 100 may also include a core network device 130 that communicates with the access network device 120. The core network device 130 may be a 5G core network (5G Core, 5GC) device. For example, the 5GC device may include Access and Mobility Management Function (AMF) network elements, Location Management Function (LMF) network elements, Unified Data Management (UDM) network elements, Network Exposure Function (NEF) network elements, Application Function (AF) network elements, Network Function (NF) network elements, Home Gateway Mobile Location Center (H-GMLC) network elements, Visited Gateway Mobile Location Center (V-GMLC) network elements, Location Services Client (LCS Client), etc.

[0049] It should be noted that core network device 130 can also be a Mobility Management Entity (MME) in the LTE network, or it can be an Evolved Packet Core (EPC) device in the LTE network, such as a Session Management Function + Core Packet Gateway (SMF+PGW-C) device. It should be understood that SMF+PGW-C can simultaneously implement the functions of both SMF and PGW-C.

[0050] It should also be noted that during network evolution, the aforementioned core network equipment may be called by other names, or new network entities may be formed by dividing the functions of the core network. This application does not impose any restrictions on this.

[0051] Figure 1 exemplarily illustrates an access network device, a core network device, and two terminal devices. Optionally, the communication system 100 may include multiple access network devices, and each access network device may include other numbers of terminal devices within its coverage area. This application embodiment does not limit this.

[0052] It should be noted that Figure 1 is merely an example illustrating the system to which this application applies. Of course, the method shown in the embodiments of this application can also be applied to other systems. Furthermore, the terms "system" and "network" are often used interchangeably in this document. The term "and / or" in this document merely describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship. It should also be understood that "instruction" mentioned in the embodiments of this application can be a direct instruction, an indirect instruction, or an indication of a related relationship. For example, A instructing B can mean that A directly instructs B, for example, B can be obtained through A; it can also mean that A indirectly instructs B, for example, A instructs C, B can be obtained through C; or it can mean that there is a related relationship between A and B. It should also be understood that "correspondence" mentioned in the embodiments of this application can indicate a direct or indirect correspondence between two things, or an related relationship between two things, or a relationship of instruction and being instructed, configuration and being configured, etc. It should also be understood that the "predefined" or "predefined rules" mentioned in the embodiments of this application can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices, access network devices, and core network devices). This application does not limit the specific implementation method. For example, predefined can refer to those defined in a protocol. It should also be understood that in the embodiments of this application, the "protocol" can refer to standard protocols in the field of communication, such as the LTE protocol, the NR protocol, and related protocols applied to future communication systems. This application does not limit this.

[0053] To facilitate understanding of the technical solutions of the embodiments of this application, the relevant technologies of the embodiments of this application are described below. The following relevant technologies are optional solutions and can be combined with the technical solutions of the embodiments of this application in any way, and they all fall within the protection scope of the embodiments of this application.

[0054] (1) Semi-Persistent Scheduling (SPS).

[0055] To better serve periodic services, the concept of pre-configured resources has been introduced. SPS (Spectrum Spectrum Allocation) is an efficient wireless resource allocation mechanism suitable for periodic or predictable data transmission scenarios. It improves spectrum efficiency by reducing control signaling overhead, making it particularly suitable for services with high latency and reliability requirements (such as voice, video calls, and industrial IoT). The following is a detailed introduction to SPS:

[0056] SPS configuration is handled by the Radio Resource Control (RRC) layer, and includes the following parameters:

[0057] a. Periodicity: Configures the periodicity of downlink or uplink allocation, in subframes. Specifically, the downlink SPS is configured with a downlink semi-static scheduling period, and the uplink SPS is configured with an uplink semi-static scheduling period.

[0058] b. Number of Hybrid Automatic Repeat Request (HARQ) processes (nrofHARQ-Processes): The number of configured HARQ processes.

[0059] c. HARQ Process ID Offset (harq-ProcID-Offset): The offset used to derive the HARQ process ID.

[0060] d. Configured Scheduling-Radio Network Temporary Identity (CS-RNTI): CS-RNTI used for activation, deactivation and retransmission.

[0061] SPS activation is accomplished via Downlink Control Information (DCI) messages on the Physical Downlink Control Channel (PDCCH), and the specific steps are as follows:

[0062] a. Receiving DCI messages: The UE receives DCI messages containing SPS configuration information on the PDCCH.

[0063] b. Verify Cyclic Redundancy Check (CRC): The UE verifies whether the CRC of the DCI message is correct.

[0064] c. Activate SPS: If the CRC verification passes, the UE activates the SPS configuration based on the information in the DCI message.

[0065] The release of SPS can also be accomplished through DCI messages on PDCCH, with the specific steps as follows:

[0066] a. Receiving DCI message: The UE receives a DCI message containing SPS release information on the PDCCH.

[0067] b. Verify CRC: The UE verifies whether the CRC of the DCI message is correct.

[0068] c. Release SPS: If the CRC verification passes, the UE releases the SPS configuration based on the information in the DCI message.

[0069] In this way, by instructing the release of resources through a specific DCI message, the UE stops using the pre-configured resources.

[0070] In one example, the SPS configuration (SPS-config) includes one or more of the following:

[0071] CS-RNTI(semiPersistSchedC-RNTI)

[0072] Downlink SPS configuration (SPS-ConfigDL);

[0073] Uplink SPS configuration (SPS-ConfigUL).

[0074] For downlink SPS configuration, one or more of the following parameters may be included:

[0075] The downlink semi-static scheduling period (semiPersistSchedIntervalDL);

[0076] HARQ process count (numberOfConfSPS-Processes);

[0077] The PUCCH resource list (n1PUCCH-AN-PersistentList) used for HARQ-ACK feedback.

[0078] For uplink SPS configuration, one or more of the following parameters may be included:

[0079] Uplink scheduling period (semiPersistSchedIntervalUL);

[0080] Uplink power control parameters (p0-Persistent).

[0081] For example, here is an example of an SPS configuration:

[0082] SPS-Config::=SEQUENCE{

[0083] semiPersistSchedC-RNTI C-RNTIOPTIONAL,--Need (i.e., CS-RNTI; if CS-RNTI is not configured, SPS cannot be activated via DCI, and resources must be configured directly via RRC in this case)

[0084] ORsps-ConfigDL SPS-ConfigDL OPTIONAL,--Need (Downlink SPS configuration)

[0085] ONsps-ConfigUL SPS-ConfigUL OPTIONAL--Need ON} (Uplink SPS configuration)

[0086] SPS-ConfigDL::=CHOICE{

[0087] release NULL, (Release downlink SPS configuration)

[0088] setup SEQUENCE {(Establish downlink SPS configuration)}

[0089] semiPersistSchedIntervalDL ENUMERATED{

[0090] sf10,sf20,sf32,sf40,sf64,sf80,sf128,sf160,sf320,sf640,spare6,spare5,spare4,spare3,spare2,spare1}, (The period of downlink semi-static scheduling, in subframes)

[0091] numberOfConfSPS-Processes INTEGER(1..8), (Number of HARQ processes (1~8))

[0092] n1PUCCH-AN-PersistentList (Physical Uplink Control Channel (PUCCH) resource list, used for HARQ-ACK feedback)

[0093] ...}}

[0094] Here, the SPS configuration (SPS-config) is sent to the UE via the RRC Connection Reconfiguration message.

[0095] SPS activation conditions: When the UE receives a DCI message containing SPS configuration information and the CRC verification passes, the UE activates the SPS configuration.

[0096] SPS release condition: When the UE receives a DCI message containing SPS release information and the CRC verification passes, the UE releases the SPS configuration.

[0097] SPS Configuration Index: The SPS configuration index (SPS-ConfigIndex) is used to indicate one of several SPS configurations. The information elements of the configuration index are as follows:

[0098] SPS-ConfigIndex-r16::=INTEGER(0..maxNrofSPS-Config-1-r16)

[0099] SPS Configuration List: The SPS configuration list (SPS-ConfigToAddModList) is used to add or modify one or more DL SPS configurations. The information elements of the configuration list are as follows:

[0100] SPS-ConfigToAddModList-r16::=SEQUENCE(SIZE(1..maxNrofSPS-Config-r16))OF SPS-Config

[0101] SPS Release List: The SPS release list (SPS-ConfigToReleaseList) is used to release one or more DL SPS configurations. The information elements of the release list are as follows:

[0102] SPS-ConfigToReleaseList-r16::=SEQUENCE(SIZE(1..maxNrofSPS-Config-r16))OF SPS-ConfigIndex-r16

[0103] Through the above configuration and operation, the LTE system can effectively manage and utilize SPS resources, thereby improving the system's resource utilization and data transmission efficiency.

[0104] (2) Control plane function optimization (Control Plane CIoT EPS / 5GS optimization).

[0105] For example, Figure 2 is an optional flowchart of RRC connection establishment provided in an embodiment of this application. As shown in Figure 2, the process may include:

[0106] S201, Send Random Access Preamble. Here, it can be the terminal device sending the Random Access Preamble to the access network device.

[0107] S202, Send a Random Access Response message. Here, the access network device may send a Random Access Response to the terminal device after receiving the Random Access Preamble.

[0108] S203, Send an RRC Connection Request message (RRCConnectionRequest). This can occur after the terminal device receives a Random Access Response, at which point the terminal device sends the RRCConnectionRequest to the access network device.

[0109] S204, Send RRC Connection Setup Message (RRCConnectionSetup). Here, it can be that after the access network device receives the RRC Connection Request, the access network device sends RRCConnectionSetup to the terminal device.

[0110] S205, send an RRC connection setup complete message (RRCConnectionSetupComplete). Here, it can be the terminal device sending RRCConnectionSetupComplete (incl.UL NAS message) to the access network device.

[0111] In this embodiment, the terminal device can be a UE, and the access network device can be an (ng-)eNB. The core idea of ​​control plane optimization is that data is directly transmitted in the control plane via Non-Access Stratum (NAS) messages, avoiding the establishment and maintenance of the user plane, thus eliminating complex RRC state transitions. For example, from the perspectives of uplink (UL) and downlink (DL), control plane CIoT EPS / 5GS optimization has the following characteristics:

[0112] (i) UL NAS signaling messages or UL NAS messages carrying data can be transmitted in UL RRC container messages (see Figure 2). DL NAS signaling or DL ​​NAS data can be transmitted in DL RRC container messages;

[0113] (ii) For NB-IoT devices:

[0114] ① Reconfiguration of RRC connections is not supported;

[0115] ② Do not use a data radio bearer (DRB);

[0116] ③ Do not use Access Stratum (AS) security;

[0117] ④ During the establishment or reconstruction of an RRC connection, a non-anchored carrier can be configured for all unicast transmissions.

[0118] ⑤ There is no distinction between different data types in AS, such as IP, Non-IP, or Short Message Service (SMS) data types.

[0119] In short, in the 3rd Generation Partnership Project (3GPP) research on Support Voice via GEO (Geostationary Satellite Earth Orbit, GEO), NB-IoT devices can access the communication system via GEO satellites to use voice call services. To support Voice via GEO services, SPS (Single Message Support) can be used to reduce control signaling overhead and improve resource efficiency. Voice services are extremely sensitive to latency and jitter, with GEO call transmission latency being particularly severe. SPS can reduce transmission latency to some extent because it reduces the signaling interactions required for each transmission. However, for NB-IoT devices that only support CP CIoT EPS / 5GS optimization, they do not support RRC Connection Reconfiguration. Therefore, SPS-Config cannot be sent in the RRC Connection Reconfiguration message; instead, it needs to be provided to the UE in other AS (RRC) messages. However, since NB-IoT devices that only support CP CIoT EPS / 5GS optimization do not support AS layer security, it is very insecure to directly provide SPS configuration information to the UE in the AS message. This will leak the network's configuration information to the UE, thereby making the UE and the network vulnerable to malicious attacks.

[0120] Based on this, this application provides a wireless communication method. For NB IoT devices that only support CP CIoT optimization, the access network device can send SPS configuration information to the core network device, and then the core network device can send it to the UE through NAS messages. This ensures that the SPS configuration information can be encrypted and protected for integrity by the NAS security context, so that the SPS configuration information can be securely transmitted to the UE.

[0121] To facilitate understanding of the technical solutions of the embodiments of this application, the technical solutions of this application are described in detail below through specific embodiments. The above-mentioned related technologies are optional solutions and can be arbitrarily combined with the technical solutions of the embodiments of this application, all of which fall within the protection scope of the embodiments of this application. The embodiments of this application include at least some of the following contents.

[0122] This application provides a wireless communication method, as shown in FIG3, which may include the following steps:

[0123] S301. The terminal device receives SPS information sent by the core network device. Alternatively, the core network device sends SPS configuration information to the terminal device.

[0124] It should be understood that SPS configuration information is a set of resource management parameters sent by the network side to the terminal device via RRC signaling in a wireless communication system, used to achieve pre-allocated resource scheduling for periodic services. Specifically, SPS configuration information is a wireless resource scheduling mechanism used to optimize resource allocation efficiency for periodic services (such as Voice over Long-Term Evolution (VoLTE) and periodic IoT reporting).

[0125] It should also be understood that SPS configuration information defines how radio resources are periodically pre-allocated to terminal devices to reduce the signaling overhead of dynamic scheduling. For example, SPS configuration information may include one or more of the following parameters: periodicity, number of HARQ processes, HARQ process ID offset, and CS-RNTI.

[0126] This application provides a wireless communication method, as shown in FIG4, which may include the following steps:

[0127] S401. The core network device sends SPS configuration information to the access network device. Alternatively, the access network device receives the SPS configuration information sent by the core network device.

[0128] S402. The access network device transmits the SPS configuration information transparently to the terminal device. Alternatively, the terminal device receives the SPS configuration information transparently transmitted by the access network device.

[0129] In this embodiment, the core network device sends SPS configuration information to the terminal device, enabling the terminal device to perform semi-persistent scheduling configuration based on the SPS configuration information. This reduces transmission latency, reduces signaling overhead for dynamic scheduling, and improves resource utilization efficiency. Furthermore, it can flexibly adapt to different service requirements and optimize network performance.

[0130] In this embodiment of the application, when the core network device sends the SPS configuration information to the terminal device, the establishment and maintenance of the user plane (e.g., DRB) is not required, thereby eliminating the complex RRC state transition process.

[0131] The wireless communication method shown in Figure 3 or Figure 4 will now be described.

[0132] In some embodiments, SPS configuration information is carried in the NAS message sent to the terminal device.

[0133] In this embodiment of the application, NAS messages can ensure that the network side (such as access network equipment and core network equipment) securely provides SPS configuration information to the terminal equipment.

[0134] In this embodiment, the terminal device can be an NB-IoT device, such as an NB-IoT device that only supports CP CIoT EPS / 5GS optimization. However, for NB-IoT devices that only support CP CIoT EPS / 5GS optimization, they do not support RRC Connection Reconfiguration, so they cannot send SPS configuration information in the RRC Connection Reconfiguration message. Instead, the SPS configuration information needs to be provided to the terminal device in other AS messages (RRC messages). However, since NB-IoT devices that only support CP CIoT EPS / 5GS optimization do not support AS layer security, directly providing the SPS configuration information to the terminal device in the AS message is highly insecure, as it would leak network-side configuration information about the terminal device, leading to malicious attacks on both the terminal device and the network.

[0135] In this scenario, SPS configuration information can be sent to NB-IoT devices that only support CP CIoT EPS / 5GS optimization via NAS messages. The NAS messages can be protected by a NAS security context, ensuring the secure transmission of the SPS configuration information to the end device.

[0136] In some embodiments, the core network equipment may include one of the following: a mobility management network element, a session management network element, and a policy control network element. In the embodiments of this application, the mobility management network element may be the MME in an LTE network, or the AMF in a 5G core network, or even the mobility management network element in a 6G network; no limitation is made here.

[0137] In this embodiment of the application, when the mobility management network element is an MME, it can be implemented in an LTE network, thereby improving the applicability of the solution.

[0138] In the embodiments of this application, the session management network element can be a Packet Data Network Gateway (PDN Gateway, abbreviated as PGW) + Serving Gateway (SGW) in the EPC device, or it can be a Session Management Function (SMF) network element in the 5G core network, and no limitation is made here.

[0139] In the embodiments of this application, the policy control network element can be the Policy and Charging Rules Function (PCRF) in the EPC device, or it can be the Policy Control Function (PCF) in the 5G core network, and no limitation is made here.

[0140] In some embodiments, SPS configuration information may be carried in the NAS message as one or more of the following:

[0141] Messages during the registration process;

[0142] Messages related to location updates;

[0143] Go to the registration process for related messages;

[0144] Messages during the service request process;

[0145] Safe mode command message.

[0146] In one possible implementation, the SPS configuration information may be carried in one or more of the following NAS messages: messages during the registration process, messages related to location updates, messages related to the deregistration process, messages during the service request process, etc.

[0147] In this embodiment of the application, the messages during the registration process may include one or more of the following: Attach Accept, Attach Reject, Registration Accept, and Registration Reject. Attach Accept serves as the network side's confirmation response to the terminal device's initial attach request, completing the terminal device registration; Attach Reject serves as the network's rejection of the terminal device's attach request; Registration Accept serves as the network side's confirmation message sent to the terminal device after receiving the terminal device's registration request; and Registration Reject serves as the network side's rejection of the registration request initiated by the terminal device.

[0148] In this embodiment of the application, the location update-related message may include one or more of the following: Tracking Area Update Accept (TAU Accept) and Tracking Area Update Reject (TAU Reject). TAU Accept confirms the location update request from the terminal device and maintains the terminal device's registration status; TAU Reject rejects the UE's location update request.

[0149] In this embodiment of the application, messages related to the deregistration process may include one or more of the following: Detach Accept, Detach Request, Deregistration Request, and Deregistration Accept. Specifically, Detach Request initiates the release of the connection between the terminal device and the network; Detach Accept confirms the completion of the connection release; Deregistration Request initiates a deregistration request between the terminal device and the network; and Deregistration Accept confirms that the deregistration request of the terminal device has been accepted by the network.

[0150] In this embodiment of the application, the messages during the service request process may include one or more of the following: Service Accept and Service Reject. Service Accept allows the terminal device to use a specific service; Service Reject rejects the terminal device's service request.

[0151] In this implementation, core network equipment may include mobility management elements (such as MME or AMF). When the mobility management element configures SPS for the terminal device, if the terminal device only supports CP CIoT EPS / 5GS optimization and does not support AS layer security, the mobility management element can send the SPS configuration information to the terminal device in a downlink NAS message. This NAS message may contain one or more of the following: UE identification information (e.g., TMSI and / or GUTI); SPS configuration information (e.g., SPS-config).

[0152] For example, when the downlink NAS message includes one or more of the messages described above such as Attach Accept, Attach Reject, TAU Accept, TAU Reject, Detach Accept, and Detach Request, the mobility management network element can be the MME. When the downlink NAS message includes one or more of the messages described above such as Registration Accept, Registration Reject, Deregistration Request, Deregistration Accept, Service Accept, and Service Reject, the mobility management network element can be the AMF. When the downlink NAS message includes a registration acceptance or rejection message for the 6G network, the mobility management network element can be the 6G MM.

[0153] In this way, the terminal device can configure semi-persistent scheduling based on the received SPS configuration information.

[0154] In another possible implementation, SPS configuration information can also be carried in the Security Mode Command message.

[0155] In this embodiment of the application, the core network equipment may also include a mobility management network element (such as MME or AMF). In this case, the mobility management network element may provide SPS configuration information to the terminal device in the Security Mode Command message.

[0156] In this embodiment, when the core network device establishes a NAS security context for the terminal device, it can simultaneously send SPS configuration information to the terminal device in the Security Mode Command message. This allows the terminal device to configure semi-persistent scheduling based on the SPS configuration information in the Security Mode Command message.

[0157] In some embodiments, SPS configuration information may be contained in a first session management (SM) container, wherein the first SM container is carried in a NAS message sent to the terminal device.

[0158] In this embodiment of the application, the core network device can send SPS configuration information to the terminal device through the first SM container in the NAS message.

[0159] In this scenario, core network equipment may include session management network elements (such as PGW+SGW or SMF in EPC). At this point, the session management network element... For the SMF side, the SMF sends the first SM container to the AMF, and the AMF sends the first SM container in a NAS message to the terminal device.

[0160] It should also be noted that when the SMF does not need to communicate with the terminal device through the AMF, the SPS configuration information can be directly sent to the terminal device as an Information Elements (IE) in a message with a security mechanism.

[0161] In this embodiment, since NAS is a message between the mobility management network element and the terminal device, it can be directly described as the core network device sending SPS configuration information to the terminal device. Furthermore, SMF may not store the SPS configuration information in the SM container; instead, it can be sent to the terminal device as a new IE.

[0162] In some embodiments, NAS messages may include messages related to a Protocol Data Unit (PDU) session.

[0163] In this embodiment, the session management network element may include SGW, PGW, or SMF, etc. The SM container may be included in one or more NAS messages such as PDU session establishment accept, PDU session modification command, and PDU session release command.

[0164] In this embodiment, the Session Management Network (SMN) element can add SPS configuration information to the SM container and send it to the UE via a downlink NAS message. The SM container is sent from the SMN element to the Mobility Management Network (MMN) element, then from the MMN element to the access network device, and finally from the access network device to the terminal device. Furthermore, for future 6G networks, if a Service Based Interface (SBI) N2 architecture is supported, the SM container may also be sent from the SMN element to the access network device via the SBI interface, and then from the access network device to the terminal device.

[0165] In this way, the terminal device configures semi-persistent scheduling based on the SPS configuration information received from the N1 NAS container.

[0166] In some embodiments, SPS configuration information may be included in a first UE policy. The first UE policy is carried in a NAS message.

[0167] In this embodiment of the application, the core network device sends the SPS configuration information to the terminal device through the first UE policy in the NAS message.

[0168] In this scenario, core network equipment may include policy control network elements (such as PCRF or PCF in EPC). On the PCF side, the PCF sends the first UE policy to the AMF, and the AMF sends the first UE policy to the terminal device in a NAS message. It should also be noted that when the PCF does not need to communicate with the terminal device through the AMF, the SPS configuration information can be directly carried as an IE in a message with security mechanisms.

[0169] In this embodiment, since the NAS can be a message between the mobility management network element and the terminal device, it can be directly described as the core network device sending SPS configuration information to the terminal device. Furthermore, the PCF may not place the SPS configuration information in the UE policy; in this case, it can be sent to the terminal device as a new IE.

[0170] In some embodiments, a NAS message may include one or more of the following:

[0171] Messages during the registration process;

[0172] Messages during the service request process;

[0173] Messages related to PDU sessions;

[0174] Downlink NAS transmission message.

[0175] In the embodiments of this application, the messages during the registration process may include one or more of the following: Attach Request, Attach Accept, Registration Accept, and Registration Request; the messages during the service request process may include one or more of the following: Service Request and Service Accept, without limitation.

[0176] In this embodiment of the application, PCF provides UE policy to the terminal device during the UE configuration update process. The NAS message here can also be a downlink NAS transport message.

[0177] In one example, the interface for an access network device (e.g., a base station) may include an N2 interface and / or an N3 interface. The N2 interface connects to the AMF (Access and Mobility Management Function) and is used to transmit UE context, NAS messages, mobility management, etc.; the N3 interface connects to the User Plane Function (UPF) and is used only for user data forwarding (GTP-U tunnel).

[0178] In one example, the interface for SMF / PCF may include one or more of the following interfaces: N11 interface, N7 interface, and N15 interface. The N11 interface is located between AMF and SMF and is used for session management signaling (e.g., PDU session establishment); the N7 interface is located between SMF and PCF and is used for policy control (e.g., Quality of Service (QoS) rule issuance); and the N15 interface is located between AMF and PCF and is used for mobility-related policies (e.g., UE location policies).

[0179] It is understood that this application also provides a wireless communication method, as shown in FIG5, which may include the following steps:

[0180] S501. The core network equipment receives SPS configuration information sent by the access network equipment. Alternatively, it can be said that the access network equipment sends SPS configuration information to the core network equipment.

[0181] In this embodiment of the application, the access network device sends SPS configuration information to the core network device. In addition to the SPS configuration information, the access network device can also send the associated UE identification information to the core network device.

[0182] In some embodiments, the SPS configuration information may be included in a first message sent by the access network device. The first message may also include a first identifier, which is used to identify the terminal device. That is, the SPS configuration information may be included in a first message sent by the access network device to the core network device. The first message may include the first identifier and the SPS configuration information.

[0183] In this application embodiment, the first identifier may include one or more of the following UE identification information (UE ID): Temporary Mobile Subscriber Identity (TMSI), Globally Unique Temporary UE Identity (GUTI), and Subscription Permanent Identifier (SUPI).

[0184] In some embodiments, the first message may include one or more of the following:

[0185] Initial UE message;

[0186] Initial UE context establishment response;

[0187] Uplink NAS transmission;

[0188] Messages related to PDU sessions;

[0189] Messages related to the handover process;

[0190] Messages related to access network device configuration updates;

[0191] Messages related to resource status reports.

[0192] In this application embodiment, PDU session-related messages may include one or more of the following: PDU session request and PDU session establishment; handover process-related messages may include one or more of the following: handover request and path switch request; access network equipment configuration update-related messages may include: eNB / gNB configuration update; resource status report-related messages may include: resource status reporting, and no limitations are imposed here.

[0193] In this embodiment, when Handover Required triggers a handover process (e.g., inter-base station handover) and requests core network equipment to coordinate resources, the base station provides SPS configuration information to the core network equipment; for example, the source eNB sends Handover Required → MME. Path Switch Request is sent by the new base station to notify the core network of SPS configuration after handover; for example, the target eNB sends Path Switch Request → MME. Specifically, Handover Required → N2 can be sent from the source gNB to the AMF; Path Switch Request → N2 can be sent from the target gNB to the AMF.

[0194] In this embodiment, the PDN Connectivity Request in 4G corresponds to the PDU Session Establishment in 5G; in this case, the receiving end can be an AMF or an SMF. Bearer / PDU Session Modification / Release is a session modification or release command initiated by the core network device, which is executed by the access network device and confirmed in response. When the access network device reports its own configuration and status to the core network device, it reports the SPS configuration via eNB / gNB Configuration Update; in this case, the receiving end can be an MME. Resource Status Reporting carries SPS configuration information when reporting radio resource usage statistics; in this case, the receiving end can be an MME.

[0195] In one possible implementation, when the core network equipment includes a mobility management element (such as MME or AMF), if the access network equipment configures SPS for the terminal equipment and the terminal equipment only supports CP CIoT EPS / 5GS optimization but not AS layer security, the access network equipment can send the SPS configuration information to the mobility management element. This message may include: UE identification information (e.g., TMSI, GUTI); and SPS configuration information (e.g., SPS-config). The SPS configuration information may be included in one or more messages such as the initial UE message and the initial UE context setup request and sent to the mobility management element.

[0196] In other words, under this implementation, the mobility management network element sends the SPS configuration information to the terminal device via NAS messages. The first message in this case can be an initial UE message, an initial UE context setup request, or other messages that do not involve the PDU session. Thus, after receiving the SPS configuration information from the access network device provided to the terminal device, the mobility management network element can send the SPS configuration information to the terminal device in a downlink NAS message.

[0197] In some embodiments, the access network device sends SPS configuration information and UE identification information to the mobility management network element. At this time, the signaling message carrying SPS configuration information may include one or more of the following: initial UE message, initial UE context setup response, uplink NAS transport, PDU session request, etc.

[0198] In this embodiment, when the terminal device powers on for the first time and attempts to connect to the network, it first sends an initial UE message. The Initial UE Message typically contains an Attach message or a Service Request message as its NAS layer payload. That is, when the terminal device initiates an Attach procedure, the access network device encapsulates the Attach message in the Initial UE Message and then sends it to the core network device. When the terminal device initiates a Service Request procedure, the access network device encapsulates the Service Request message in the Initial UE Message and then sends it to the core network device.

[0199] After receiving the initial UE message, the access network device performs a series of processes, including verifying the UE's identity and allocating resources, before sending an initial UE context establishment response to the terminal device. This response may include one or more of the following: an allocated Temporary Identifier (TAI), an allocated Temporary Mobile Subscriber Identity (TMSI), an allocated Temporary Cell Identifier (TCI), and security parameters. Upon receiving the initial UE context establishment response, the terminal device can use this information to complete the security authentication process and then begin normal data transmission. This process involves multiple message exchanges, including RRC connection establishment and secure mode commands.

[0200] In other words, under this implementation, the mobility management network element sends the SPS configuration information to the terminal device in the Security Mode Command message. In this case, the first message can be any of the above-mentioned messages.

[0201] In another possible implementation, where the core network equipment includes session management network elements (such as PGW+SGW or SMF in EPC), the first message may include a second SM container, and the SPS configuration information is contained in the second SM container.

[0202] In this embodiment of the application, for the SMF side, the access network device (such as a base station) sends a second SM container (containing SPS configuration information) to the AMF, and the AMF sends the second SM container along with the N11 interface message to the SMF; then the SMF sends the SPS configuration information to the terminal device.

[0203] In this embodiment, the access network device can send an N2 SM message to the session management network element through the mobility management network element. This message may include one or more of the following parameters: (a) UE identification information; and (b) SPS configuration information. The UE identification information may include one or more of the Temporary Mobile Subscriber Identity (TMSI) and the Globally Unique Temporary UE Identity (GUTI). The SPS configuration information may include SPS configuration (SPS-config). After receiving the N2 SM message, the session management network element can add the SPS configuration information to the SM container and send it to the UE via a downlink NAS message. The SM container is sent from the session management network element to the mobility management network element, then from the mobility management network element to the access network device, and finally from the access network device to the terminal device.

[0204] In this embodiment, for future 6G networks, if a Service Based Interface (SBI) N2 architecture is supported, the SM container may also be sent to the access network device via the SBI interface through a session management network element, and then sent to the terminal device by the access network device. The session management network element can be an SGW, PGW, or SMF, etc. The SM container may be included in one or more NAS messages related to the PDU session: PDU session establishment accept, PDU session modification command, and PDU session release command.

[0205] In other words, under this implementation, the session management network element sends the SPS configuration information to the terminal device through the SM container in the NAS message. In this case, the first message can be a PDU session request or other message involving the PDU session.

[0206] In another possible implementation, where the core network equipment includes policy control network elements (such as PCRF or PCF in EPC), the first message may include a second UE policy, and the SPS configuration information is included in the second UE policy.

[0207] In this embodiment of the application, on the SMF side, the access network device (such as a base station) sends a second UE policy (containing SPS configuration information) to the AMF, and the AMF sends the second UE policy in the N15 interface message to the PCF; then the PCF sends the SPS configuration information to the terminal device.

[0208] In this embodiment, the access network device sends SPS configuration information to the core network device. Besides the SPS configuration information, the access network device may also send associated UE identification information to the AMF. For example, the SPS configuration information is carried and sent to the AMF in one or more of the following second messages:

[0209] (a) Initial Context Setup Request: This message is sent to the AMF when 5G-RG or W-AGF needs to establish an initial context. This message may contain necessary configuration information and security context.

[0210] (b) Uplink NAS Transport: Used to transmit uplink NAS messages from 5G-RG or W-AGF. For example, 5G-RG or W-AGF might use this message to send a Registration Complete message to AMF;

[0211] (c) PDU Session Request: When a PDU session needs to be established or modified, the 5G-RG or W-AGF will send this message to the AMF. This message contains the relevant parameters of the PDU session.

[0212] In the process involving Initial Context Setup Request, NAS messages are used for interaction between the terminal device and core network devices (such as AMF, MME, etc.), while access network devices (such as base stations gNB, eNB, etc.) only transmit these messages transparently. For example, in a 5G network, the NAS messages involved in this process may include one or more of the following: Registration Request, Registration Accept, Service Request, Security Mode Complete, etc.; in a 4G network, the NAS messages involved in this process may include: Attach Request, Attach Accept, PDN Connectivity Request.

[0213] In this embodiment, the AMF sends the SPS configuration information and associated UE identification information to the PCF. These parameters can be sent to the PCF via one or more of the following messages:

[0214] (a) Npcf_UEPolicyControl_Create Request: When the AMF needs to create a new UE policy association, it sends this request message to the PCF and provides the relevant UE context parameters;

[0215] (b) Npcf_UEPolicyControl_Update Notify: When the AMF detects certain triggering conditions (such as changes in service area restrictions), it sends this notification message to the PCF to update the UE policy association.

[0216] (c)Npcf_AMPolicyControl_Update Notify: When the AMF receives new access and mobility control policy information, it will send this information to the PCF via this notification message.

[0217] In this embodiment, the PCF can add SPS configuration information to the UE policy and provide it to the terminal device. The PCF sends the UE policy and UE ID to the AMF via the Namf_Communication_N1N2MessageTransfer message, and the AMF then transmits the UE policy to the terminal device through the access network equipment.

[0218] In other words, under this implementation, the policy control network element sends the SPS configuration information to the terminal device through the UE policy in the NAS message. At this time, the first message may include one or more of the following: initial UE context setup request, uplink NAS transport, and PDU session request. In this way, the terminal device performs semi-persistent scheduling configuration based on the SPS configuration information received in the UE policy.

[0219] The communication method provided in the embodiments of this application will be described in detail below with reference to specific application scenarios.

[0220] To ensure that the network securely provides SPS configuration information to the UE, this solution proposes to send the SPS configuration to NB-IoT devices that only support CP CIoT EPS / 5GS optimization via NAS messages. The NAS messages can be protected by the NAS security context, thereby ensuring the secure transmission of SPS messages to the UE.

[0221] Example 1: The access network device sends the SPS configuration information to the mobility management network element, and the mobility management network element sends the SPS configuration information to the UE through NAS messages.

[0222] In some embodiments, assuming the terminal device is a UE, the access network device is a base station or a radio access network (RAN), and the core network device is a mobility management (MM) network element, as shown in Figure 6, the implementation process of Embodiment 1 includes the following steps:

[0223] S601, Send SPS configuration information. Here, the RAN sends SPS configuration information to the mobility management network element.

[0224] S602, SPS configuration information is sent via NAS message. Here, the mobility management network element sends SPS configuration information to the UE via NAS message.

[0225] As shown in Figure 6, the access network device can send the SPS configuration information for the UE to the mobility management network element, which then sends it to the UE in a UL NAS message. The mobility management network element can be an MME, AMF, or a 6G mobility management network element.

[0226] When the access network device configures SPS for the UE, if the UE only supports CP CIoT EPS / 5GS optimization and does not support AS layer security, the access network device can send the SPS configuration information to the mobility management network element. The message contains one or more of the following parameters: (a) UE identification information, such as one or more of TMSI, GUTI, etc.; (b) SPS configuration information, such as SPS-config.

[0227] In this embodiment of the application, SPS configuration information can be included in one or more messages such as initial UE message and initial UE context setup response and sent to the mobility management network element.

[0228] In this embodiment of the application, after the mobility management network element receives the SPS configuration message provided to the UE by the access network device, it can send the SPS configuration information to the UE in a downlink NAS message. For example, the downlink NAS message may include one or more of the following messages: Attach accept / Attach reject, TAU accept / TAU reject, detach accept, detach request, registration accept, registration reject, deregistration request, deregistration accept, service accept, service reject, and 6G registration acceptance or rejection message.

[0229] In this embodiment of the application, when the mobility management network element is an MME, the NAS message may include one or more of the following: Attach accept / Attach reject, TAU accept / TAU reject, detach accept, detach request.

[0230] In this embodiment of the application, when the mobility management network element is an AMF, the NAS message may include one or more of the following: registration accept, registration reject, deregistration request, deregistration accept, service accept, and service reject.

[0231] In this embodiment of the application, when the mobility management network element is 6G MM, the NAS message may include one or more of the following: 6G registration acceptance or rejection message.

[0232] In this way, the UE configures semi-persistent scheduling based on the received SPS configuration.

[0233] Example 2: The access network device sends the SPS configuration information to the session management network element. The session management network element sends the SPS configuration information to the mobility management network element through the SM container. Then, the mobility management network element sends the SM container to the UE in the NAS message.

[0234] In some embodiments, assuming the terminal device is a UE, the access network device is a RAN, and the core network device is a Session Management (SM) network element, as shown in Figure 7, the implementation process of Embodiment 2 includes the following steps:

[0235] S701, Send SPS configuration information. Here, the RAN sends SPS configuration information to the session management network element, which can be done by the RAN sending SPS configuration information to the session management network element through the mobility management network element.

[0236] S702, SPS configuration information is sent via the SM container. Here, the SPS configuration information is contained within the SM container. This can be achieved by the Session Management Network element sending the SM container to the Mobility Management Network element, which then carries the SM container in a NAS message and sends it to the RAN, which finally sends it to the UE.

[0237] As shown in Figure 7, the access network device can send SPS configuration information to the session management network element, which then sends it to the mobility management network element through the SM container. The mobility management network element then sends it to the UE through the SM container in the DL NAS message.

[0238] In this embodiment of the application, the access network device sends an N2 SM message to the session management network element through the mobility management network element, which may include one or more of the following parameters: (a) UE identification information; (b) SPS configuration information.

[0239] In this embodiment, after receiving the N2 SM message, the session management network element adds the SPS configuration information therein to the SM container and sends it to the UE via a downlink NAS message. The SM container is sent by the session management network element to the mobility management network element, then by the mobility management network element to the access network device, and finally by the access network device to the UE. For future 6G networks, if the SBI N2 architecture is supported, the SM container may also be sent by the session management network element to the access network device via the SBI interface, and then by the access network device to the UE. The session management network element can be an SGW, PGW, SMF, etc. The SM container is a dedicated container used to carry session management-related parameters (such as SPS configuration information) in the NAS message. For example, the SM container can be included in one or more NAS messages related to the PDU session: PDU session establishment accept, PDU session modification command, and PDU session release command. In this way, the UE performs semi-persistent scheduling configuration based on the SPS configuration information received from the N1 NAS container.

[0240] Example 3: The access network device sends the SPS configuration information to the policy control network element. The policy control network element sends the SPS configuration information to the mobility management network element through the UE policy. Then, the mobility management network element sends the UE policy in the NAS message to the UE.

[0241] In some embodiments, assuming the terminal device is a UE, the access network device is a RAN, and the core network device is a policy control network element, as shown in Figure 8, the implementation process of Embodiment 3 includes the following steps:

[0242] S801, Send SPS configuration information. Here, the RAN sends SPS configuration information to the PCF, which can be done through the mobility management network element.

[0243] S802, SPS configuration information is sent via UE policy. Here, the SPS configuration information is included in the UE policy. This can be achieved by the PCF sending the UE policy to the mobility management network element, the mobility management network element then sending the UE policy in a NAS message to the RAN, and finally the RAN sending it to the UE.

[0244] As shown in Figure 8, the access network device can provide SPS configuration information to the PCF, which then sends it to the mobility management network element via UE policy. The mobility management network element then sends the SPS configuration information to the UE via UE policy in the NAS message.

[0245] In this embodiment, the access network device sends SPS configuration information to the AMF. In addition to the SPS configuration information, the access network device also sends the associated UE identification information to the AMF. The SPS configuration information can be carried in one or more of the following second messages and sent to the AMF: Initial Context Setup Request, Uplink NAS Transport, and PDU Session Request.

[0246] The following sections will explain the Initial Context Setup Request, Uplink NAS Transport, and PDU Session Request:

[0247] Initial Context Setup Request: This message is sent to the AMF when 5G-RG or W-AGF needs to establish an initial context. This message can contain the necessary configuration information and security context.

[0248] Uplink NAS Transport: Used to transmit uplink NAS messages from 5G-RG or W-AGF. For example, 5G-RG or W-AGF might use this message to send a Registration Complete message to AMF;

[0249] PDU Session Request: When a PDU session needs to be established or modified, the 5G-RG or W-AGF will send this message to the AMF. This message contains the relevant parameters of the PDU session.

[0250] In this embodiment of the application, the AMF sends the SPS configuration information and the associated UE identification information to the PCF. The parameters can be sent to the PCF through one or more of the following third messages: Npcf_UEPolicyControl_Create Request, Npcf_UEPolicyControl_Update Notify, and Npcf_AMPolicyControl_Update Notify.

[0251] The following sections will explain Npcf_UEPolicyControl_Create Request, Npcf_UEPolicyControl_Update Notify, and Npcf_AMPolicyControl_Update Notify respectively:

[0252] Npcf_UEPolicyControl_Create Request: When the AMF needs to create a new UE policy association, it sends this request message to the PCF and provides the relevant UE context parameters.

[0253] Npcf_UEPolicyControl_Update Notify: When the AMF detects certain triggering conditions (such as changes in service area restrictions), it sends this notification message to the PCF to update the UE policy association.

[0254] Npcf_AMPolicyControl_Update Notify: When the AMF receives new access and mobility control policy information, it sends this information to the PCF via this notification message.

[0255] In this embodiment, the PCF adds SPS configuration information to the UE policy container and provides it to the UE. The PCF sends the UE policy container and UE ID (SUPI) to the AMF via the Namf_Communication_N1N2MessageTransfer message, and the AMF transparently transmits the UE policy container to the UE through the base station. The UE configures semi-persistent scheduling based on the SPS configuration information received in the UE policy container.

[0256] Example 4: The access network device sends the SPS configuration information to the mobility management network element, and the mobility management network element sends the SPS configuration information to the UE in the Security Mode Command message.

[0257] In some embodiments, assuming the terminal device is a UE, the access network device is a RAN, and the core network device is a mobility management (MM) network element, as shown in Figure 9, the implementation process of Embodiment 4 includes the following steps:

[0258] S901, Send SPS configuration information. Here, the RAN sends SPS configuration information to the mobility management network element.

[0259] S902, SPS configuration information is sent via Security Mode Command message. Here, the mobility management network element can send SPS configuration information to the UE via Security Mode Command message.

[0260] As shown in Figure 9, the access network device can send SPS configuration information to the mobility management network element, and the mobility management network element can provide the SPS configuration information to the UE in the Security Mode Command message.

[0261] In this embodiment of the application, the access network device sends SPS configuration information and UE identification information to the mobility management network element. The signaling message carrying SPS configuration information may include one or more of the following fourth messages: initial UE message, initial UE context setup response, Uplink NAS Transport, PDU Session Request, etc.

[0262] In this embodiment, when establishing a NAS security context for a UE, the mobility management network element can simultaneously send SPS configuration information to the UE in a Security Mode Command message. This allows the UE to configure semi-persistent scheduling based on the SPS configuration information in the Security Mode Command message.

[0263] In summary, in this embodiment, for NB IoT devices that only support CP CIoT optimization, the access network device can send SPS configuration information to the core network device, which then sends it to the UE via NAS messages. This ensures that the SPS configuration information can be encrypted and protected for integrity by the NAS security context. Specifically, the SPS configuration information can be sent to the UE by the mobility management network element via the N1 NAS container or SMC; or by the session management network element via the SM container; or by the policy control network element via the UE policy container.

[0264] The wireless communication method provided in this embodiment ensures that the network securely provides SPS configuration information to the UE, avoiding malicious attacks on both the UE and the network due to the leakage of network configuration messages to the UE. The SPS configuration information is sent to NB-IoT devices that only support CP CIoT EPS / 5GS optimization via NAS messages, and these NAS messages are protected by a NAS security context, thus ensuring the secure transmission of the SPS configuration information to the UE.

[0265] The preferred embodiments of this application have been described in detail above with reference to the accompanying drawings. However, this application is not limited to the specific details of the above embodiments. Within the scope of the technical concept of this application, various simple modifications can be made to the technical solutions of this application, and these simple modifications all fall within the protection scope of this application. For example, the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. To avoid unnecessary repetition, this application will not describe the various possible combinations separately. Furthermore, various different embodiments of this application can also be arbitrarily combined, as long as they do not violate the spirit of this application, they should also be considered as the content disclosed in this application. Moreover, without conflict, the various embodiments and / or the technical features in the various embodiments described in this application can be arbitrarily combined with the prior art, and the resulting technical solutions should also fall within the protection scope of this application.

[0266] It should also be understood that in the various method embodiments of this application, the sequence number of each process does not imply the order of execution. 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 embodiments of this application. Furthermore, in the embodiments of this application, the terms "downlink," "uplink," and "sidelink" are used to indicate the transmission direction of signals or data. "Downlink" indicates that the transmission direction of signals or data is a first direction from the site to the user equipment in the cell; "uplink" indicates that the transmission direction of signals or data is a second direction from the user equipment in the cell to the site; and "sidelink" indicates that the transmission direction of signals or data is a third direction from user equipment 1 to user equipment 2. For example, "downlink signal" indicates that the transmission direction of the signal is the first direction. Additionally, in the embodiments of this application, the term "and / or" is merely a description of the association relationship between related objects, indicating that three relationships can exist. Specifically, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0267] Based on the foregoing embodiments, this application provides corresponding communication devices.

[0268] Figure 10 is a schematic diagram of the composition structure of a terminal device provided in an embodiment of this application. As shown in Figure 10, the terminal device 1000 includes:

[0269] The first communication unit 1001 is configured to receive SPS configuration information sent by the core network equipment.

[0270] In some embodiments, the SPS configuration information is carried in a non-access stratum (NAS) message sent to the terminal device.

[0271] In some embodiments, the core network equipment includes one of the following:

[0272] Mobility management network elements;

[0273] Session management network element;

[0274] Policy control network element.

[0275] In some embodiments, the SPS configuration information is carried in one or more of the following NAS messages:

[0276] Messages during the registration process;

[0277] Messages related to location updates;

[0278] Go to the registration process for related messages;

[0279] Messages during the service request process;

[0280] Safe mode command message.

[0281] In some embodiments, the SPS configuration information is contained in a first SM container, which carries the NAS message sent to the terminal device.

[0282] In some embodiments, the NAS message includes messages related to the PDU session.

[0283] In some embodiments, the SPS configuration information is included in a first UE policy, which is carried in a NAS message.

[0284] In some embodiments, the NAS message includes one or more of the following:

[0285] Messages during the registration process;

[0286] Messages during the service request process;

[0287] Messages related to PDU sessions;

[0288] Downlink NAS transmission message.

[0289] In some embodiments, the first communication unit in the terminal device may be implemented by a transceiver in the terminal device.

[0290] Figure 11 is a schematic diagram of the composition structure of the core network device provided in an embodiment of this application. As shown in Figure 11, the core network device 1100 includes:

[0291] The second communication unit 1101 is configured to send semi-persistent scheduling (SPS) configuration information to the terminal device.

[0292] In some embodiments, the SPS configuration information is carried in the NAS message sent to the terminal device.

[0293] In some embodiments, the core network equipment includes one of the following:

[0294] Mobility management network elements;

[0295] Session management network element;

[0296] Policy control network element.

[0297] In some embodiments, the SPS configuration information is carried in one or more of the following NAS messages:

[0298] Messages during the registration process;

[0299] Messages related to location updates;

[0300] Go to the registration process for related messages;

[0301] Messages during the service request process;

[0302] Safe mode command message.

[0303] In some embodiments, the SPS configuration information is contained in a first SM container, which carries the NAS message sent to the terminal device.

[0304] In some embodiments, the NAS message includes messages related to the PDU session.

[0305] In some embodiments, the SPS configuration information is included in a first UE policy, which is carried in a NAS message.

[0306] In some embodiments, the NAS message includes one or more of the following:

[0307] Messages during the registration process;

[0308] Messages during the service request process;

[0309] Messages related to PDU sessions;

[0310] Downlink NAS transmission message.

[0311] In some embodiments, the second communication unit 1101 is further configured to receive the SPS configuration information sent by the access network device.

[0312] In some embodiments, the SPS configuration information is included in a first message sent by the access network device, and the first message further includes a first identifier, which is used to identify the terminal device.

[0313] In some embodiments, the first message includes a second SM container, and the SPS configuration information is contained in the second SM container.

[0314] In some embodiments, the first message includes a second UE policy, and the SPS configuration information is included in the second UE policy.

[0315] In some embodiments, the first message includes one or more of the following:

[0316] Initial UE message;

[0317] Initial UE context establishment response;

[0318] Uplink NAS transmission;

[0319] Messages related to PDU sessions;

[0320] Messages related to the handover process;

[0321] Messages related to access network device configuration updates;

[0322] Messages related to resource status reports.

[0323] In some embodiments, the second communication unit in the core network device may be implemented by a transceiver in the core network device.

[0324] Figure 12 is a schematic diagram of the composition structure of the access network device provided in an embodiment of this application. As shown in Figure 12, the access network device 1200 includes:

[0325] The third communication unit 1201 is configured to receive semi-persistent scheduling (SPS) configuration information sent by the core network device and to transmit the SPS configuration information to the terminal device.

[0326] In some embodiments, the SPS configuration information is carried in a non-access stratum (NAS) message sent to the terminal device.

[0327] In some embodiments, the core network equipment includes one of the following:

[0328] Mobility management network elements;

[0329] Session management network element;

[0330] Policy control network element.

[0331] In some embodiments, the SPS configuration information is carried in one or more of the following NAS messages:

[0332] Messages during the registration process;

[0333] Messages related to location updates;

[0334] Go to the registration process for related messages;

[0335] Messages during the service request process;

[0336] Safe mode command message.

[0337] In some embodiments, the SPS configuration information is contained in a first SM container, which carries the NAS message sent to the terminal device.

[0338] In some embodiments, the NAS message includes messages related to the PDU session.

[0339] In some embodiments, the SPS configuration information is included in a first UE policy, which is carried in a NAS message.

[0340] In some embodiments, the NAS message includes one or more of the following:

[0341] Messages during the registration process;

[0342] Messages during the service request process;

[0343] Messages related to PDU sessions;

[0344] Downlink NAS transmission message.

[0345] In some embodiments, the third communication unit 1201 is further configured to send the SPS configuration information to the core network device.

[0346] In some embodiments, the SPS configuration information is included in a first message sent by the access network device, and the first message further includes a first identifier, which is used to identify the terminal device.

[0347] In some embodiments, the first message includes a second SM container, and the SPS configuration information is contained in the second SM container.

[0348] In some embodiments, the first message includes a second UE policy, and the SPS configuration information is included in the second UE policy.

[0349] In some embodiments, the first message includes one or more of the following:

[0350] Initial UE message;

[0351] Initial UE context establishment response;

[0352] Uplink NAS transmission;

[0353] Messages related to PDU sessions;

[0354] Messages related to the handover process;

[0355] Messages related to access network device configuration updates;

[0356] Messages related to resource status reports.

[0357] In some embodiments, the third communication unit in the access network device may be implemented by a transceiver in the access network device.

[0358] Those skilled in the art should understand that the description of the communication device in the embodiments of this application can be understood with reference to the description of the communication method in the embodiments of this application.

[0359] Figure 13 is a schematic diagram of the composition structure of a communication device provided in an embodiment of this application. The communication device may be a terminal device, a core network device, or an access network device. The communication device 1300 shown in Figure 13 may include a processor 1310, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0360] Optionally, as shown in FIG13, the communication device 1300 may further include a memory 1320. The processor 1310 may retrieve and run computer programs from the memory 1320 to implement the methods described in the embodiments of this application.

[0361] The memory 1320 can be a separate device independent of the processor 1310, or it can be integrated into the processor 1310.

[0362] Optionally, as shown in FIG13, the communication device 1300 may further include a transceiver 1330, and the processor 1310 may control the transceiver 1330 to communicate with other devices. Specifically, it may send information or data to other devices or receive information or data sent by other devices.

[0363] The transceiver 1330 may include a transmitter and a receiver. The transceiver 1330 may further include an antenna, and the number of antennas may be one or more.

[0364] Optionally, the communication device 1300 may specifically be a terminal device in the embodiments of this application, and the communication device 1300 may implement the corresponding processes implemented by the terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0365] Optionally, the communication device 1300 may specifically be the core network device in the embodiments of this application, and the communication device 1300 may implement the corresponding processes implemented by the core network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0366] Optionally, the communication device 1300 may specifically be an access network device in the embodiments of this application, and the communication device 1300 may implement the corresponding processes implemented by the access network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0367] Figure 14 is a schematic diagram of the chip structure according to an embodiment of this application. The chip 1400 shown in Figure 14 includes a processor 1410, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0368] Optionally, as shown in FIG14, chip 1400 may further include memory 1420. Processor 1410 may retrieve and run computer programs from memory 1420 to implement the methods in the embodiments of this application.

[0369] The memory 1420 can be a separate device independent of the processor 1410, or it can be integrated into the processor 1410.

[0370] Optionally, the chip 1400 may also include an input interface 1430. The processor 1410 can control the input interface 1430 to communicate with other devices or chips; specifically, it can acquire information or data sent by other devices or chips.

[0371] Optionally, the chip 1400 may also include an output interface 1440. The processor 1410 can control the output interface 1440 to communicate with other devices or chips, specifically, to output information or data to other devices or chips.

[0372] Optionally, the chip can be applied to the terminal device in the embodiments of this application, and the chip can implement the corresponding processes implemented by the terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0373] Optionally, the chip can be applied to the core network device in the embodiments of this application, and the chip can implement the corresponding processes implemented by the core network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0374] Optionally, the chip can be applied to the access network device in the embodiments of this application, and the chip can implement the corresponding processes implemented by the access network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0375] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0376] This application also provides a computer storage medium storing one or more programs, which can be executed by one or more processors to implement the methods in this application.

[0377] Figure 15 is a schematic block diagram of a communication system provided in an embodiment of this application. As shown in Figure 15, the communication system 1500 includes a terminal device 1510, an access network device 1520, and a core network device 1530.

[0378] The terminal device 1510 can be used to implement the corresponding functions implemented by the terminal device in the above method, the access network device 1520 can be used to implement the corresponding functions implemented by the access network device in the above method, and the core network device 1530 can be used to implement the corresponding functions implemented by the core network device in the above method. For the sake of brevity, they will not be described in detail here.

[0379] It should be understood that the processor in the embodiments of this application may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor described above can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0380] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0381] It should be understood that the above-described memory is exemplary and not a limiting description. For example, the memory in the embodiments of this application may also be 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 dynamic random access memory (SLDRAM), and direct memory bus RAM (DR RAM), etc. That is to say, the memory in the embodiments of this application is intended to include, but is not limited to, these and any other suitable types of memory.

[0382] This application also provides a computer-readable storage medium for storing computer programs.

[0383] Optionally, the computer-readable storage medium can be applied to the terminal device in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0384] Optionally, the computer-readable storage medium can be applied to the access network device in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the access network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0385] Optionally, the computer-readable storage medium can be applied to the core network device in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the core network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0386] This application also provides a computer program product, including computer program instructions.

[0387] Optionally, the computer program product can be applied to the terminal device in the embodiments of this application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the terminal device in the various methods of the embodiments of this application. For the sake of brevity, they will not be described in detail here.

[0388] Optionally, the computer program product can be applied to the access network device in the embodiments of this application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the access network device in the various methods of the embodiments of this application. For the sake of brevity, they will not be described in detail here.

[0389] Optionally, the computer program product can be applied to the core network device in the embodiments of this application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the core network device in the various methods of the embodiments of this application. For the sake of brevity, they will not be described in detail here.

[0390] This application also provides a computer program.

[0391] Optionally, the computer program can be applied to the terminal device in the embodiments of this application. When the computer program is run on the computer, it causes the computer to execute the corresponding processes implemented by the terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0392] Optionally, the computer program can be applied to the access network device in the embodiments of this application. When the computer program is run on a computer, it causes the computer to execute the corresponding processes implemented by the access network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0393] Optionally, the computer program can be applied to the core network device in the embodiments of this application. When the computer program is run on a computer, it causes the computer to execute the corresponding processes implemented by the core network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0394] Those skilled in the art will recognize that the units and algorithm steps of the various examples 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 implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0395] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0396] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0397] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0398] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0399] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0400] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A wireless communication method, the method comprising: The terminal device receives the semi-persistent scheduling (SPS) configuration information sent by the core network device.

2. The method according to claim 1, wherein, The SPS configuration information is carried in the non-access stratum (NAS) message sent to the terminal device.

3. The method according to claim 1 or 2, wherein, The core network equipment includes one of the following: Mobility management network elements; Session management network element; Policy control network element.

4. The method according to any one of claims 1 to 3, wherein, The SPS configuration information is carried in one or more of the following NAS messages: Messages during the registration process; Messages related to location updates; Go to the registration process for related messages; Messages during the service request process; Safe mode command message.

5. The method according to any one of claims 1 to 4, wherein, The SPS configuration information is contained in the first session management (SM) container, which carries the NAS message sent to the terminal device.

6. The method according to claim 5, wherein, The NAS messages include messages related to the PDU session.

7. The method according to any one of claims 1 to 6, wherein, The SPS configuration information is contained in the first UE policy, which is carried in the NAS message.

8. The method according to claim 7, wherein, The NAS message includes one or more of the following: Messages during the registration process; Messages during the service request process; Messages related to PDU sessions; Downlink NAS transmission message.

9. A wireless communication method, comprising: The core network equipment sends semi-persistent scheduling (SPS) configuration information to the terminal equipment.

10. The method according to claim 9, wherein, The SPS configuration information is carried in the non-access stratum (NAS) message sent to the terminal device.

11. The method according to claim 9 or 10, wherein, The core network equipment includes one of the following: Mobility management network elements; Session management network element; Policy control network element.

12. The method according to any one of claims 9 to 11, wherein, The SPS configuration information is carried in one or more of the following NAS messages: Messages during the registration process; Messages related to location updates; Go to the registration process for related messages; Messages during the service request process; Safe mode command message.

13. The method according to any one of claims 9 to 12, wherein, The SPS configuration information is contained in the first session management (SM) container, which carries the NAS message sent to the terminal device.

14. The method according to claim 13, wherein, The NAS messages include messages related to the PDU session.

15. The method according to any one of claims 9 to 14, wherein, The SPS configuration information is contained in the first UE policy, which is carried in the NAS message.

16. The method according to claim 15, wherein, The NAS message includes one or more of the following: Messages during the registration process; Messages during the service request process; Messages related to PDU sessions; Downlink NAS transmission message.

17. The method according to any one of claims 9 to 16, wherein, The method further includes: The core network device receives the SPS configuration information sent by the access network device.

18. The method according to claim 17, wherein, The SPS configuration information is included in a first message sent by the access network device. The first message also includes a first identifier, which is used to identify the terminal device.

19. The method according to claim 18, wherein, The first message includes a second SM container, and the SPS configuration information is contained in the second SM container.

20. The method according to claim 18, wherein, The first message includes a second UE policy, and the SPS configuration information is contained in the second UE policy.

21. The method according to any one of claims 18 to 20, wherein, The first message includes one or more of the following: Initial UE message; Initial UE context establishment response; Uplink NAS transmission; Messages related to PDU sessions; Messages related to the handover process; Messages related to access network device configuration updates; Messages related to resource status reports.

22. A wireless communication method, the method comprising: The access network device receives the semi-persistent scheduling (SPS) configuration information sent by the core network device; The access network device transmits the SPS configuration information to the terminal device.

23. The method according to claim 22, wherein, The SPS configuration information is carried in the non-access stratum (NAS) message sent to the terminal device.

24. The method according to claim 22 or 23, wherein, The core network equipment includes one of the following: Mobility management network elements; Session management network element; Policy control network element.

25. The method according to any one of claims 22 to 24, wherein, The SPS configuration information is carried in one or more of the following NAS messages: Messages during the registration process; Messages related to location updates; Go to the registration process for related messages; Messages during the service request process; Safe mode command message.

26. The method according to any one of claims 22 to 25, wherein, The SPS configuration information is contained in the first session management (SM) container, which carries the NAS message sent to the terminal device.

27. The method according to claim 26, wherein, The NAS messages include messages related to the PDU session.

28. The method according to any one of claims 22 to 27, wherein, The SPS configuration information is contained in the first UE policy, which is carried in the NAS message.

29. The method according to claim 28, wherein, The NAS message includes one or more of the following: Messages during the registration process; Messages during the service request process; Messages related to PDU sessions; Downlink NAS transmission message.

30. The method according to any one of claims 22 to 29, wherein, The method further includes: The access network device sends the SPS configuration information to the core network device.

31. The method according to claim 30, wherein, The SPS configuration information is included in a first message sent by the access network device. The first message also includes a first identifier, which is used to identify the terminal device.

32. The method according to claim 31, wherein, The first message includes a second SM container, and the SPS configuration information is contained in the second SM container.

33. The method according to claim 31, wherein, The first message includes a second UE policy, and the SPS configuration information is contained in the second UE policy.

34. The method according to any one of claims 31 to 33, wherein, The first message includes one or more of the following: Initial UE message; Initial UE context establishment response; Uplink NAS transmission; Messages related to PDU sessions; Messages related to the handover process; Messages related to access network device configuration updates; Messages related to resource status reports.

35. A terminal device, the terminal device comprising: The first communication unit is configured to receive SPS configuration information sent by the core network equipment.

36. The terminal device according to claim 35, wherein, The SPS configuration information is carried in the non-access stratum (NAS) message sent to the terminal device.

37. The terminal device according to claim 35 or 36, wherein, The core network equipment includes one of the following: Mobility management network elements; Session management network element; Policy control network element.

38. The terminal device according to any one of claims 35 to 37, wherein, The SPS configuration information is carried in one or more of the following NAS messages: Messages during the registration process; Messages related to location updates; Go to the registration process for related messages; Messages during the service request process; Safe mode command message.

39. The terminal device according to any one of claims 35 to 38, wherein, The SPS configuration information is contained in the first session management (SM) container, which carries the NAS message sent to the terminal device.

40. The terminal device according to claim 39, wherein, The NAS messages include messages related to the PDU session.

41. The terminal device according to any one of claims 35 to 40, wherein, The SPS configuration information is contained in the first UE policy, which is carried in the NAS message.

42. The terminal device according to claim 41, wherein, The NAS message includes one or more of the following: Messages during the registration process; Messages during the service request process; Messages related to PDU sessions; Downlink NAS transmission message.

43. A core network device, the core network device comprising: The second communication unit is configured to send SPS configuration information to the terminal device.

44. The core network equipment according to claim 43, wherein, The SPS configuration information is carried in the non-access stratum (NAS) message sent to the terminal device.

45. The core network equipment according to claim 43 or 44, wherein, The core network equipment includes one of the following: Mobility management network elements; Session management network element; Policy control network element.

46. ​​The core network equipment according to any one of claims 43 to 45, wherein, The SPS configuration information is carried in one or more of the following NAS messages: Messages during the registration process; Messages related to location updates; Go to the registration process for related messages; Messages during the service request process; Safe mode command message.

47. The core network equipment according to any one of claims 43 to 46, wherein, The SPS configuration information is contained in the first session management (SM) container, which carries the NAS message sent to the terminal device.

48. The core network equipment according to claim 47, wherein, The NAS messages include messages related to the PDU session.

49. The core network equipment according to any one of claims 43 to 48, wherein, The SPS configuration information is contained in the first UE policy, which is carried in the NAS message.

50. The core network equipment according to claim 49, wherein, The NAS message includes one or more of the following: Messages during the registration process; Messages during the service request process; Messages related to PDU sessions; Downlink NAS transmission message.

51. The core network equipment according to any one of claims 43 to 50, wherein, The second communication unit is further configured to receive the SPS configuration information sent by the access network device.

52. The core network equipment according to claim 51, wherein, The SPS configuration information is included in a first message sent by the access network device. The first message also includes a first identifier, which is used to identify the terminal device.

53. The core network equipment according to claim 52, wherein, The first message includes a second SM container, and the SPS configuration information is contained in the second SM container.

54. The core network equipment according to claim 52, wherein, The first message includes a second UE policy, and the SPS configuration information is contained in the second UE policy.

55. The core network equipment according to any one of claims 52 to 54, wherein, The first message includes one or more of the following: Initial UE message; Initial UE context establishment response; Uplink NAS transmission; Messages related to PDU sessions; Messages related to the handover process; Messages related to access network device configuration updates; Messages related to resource status reports.

56. An access network device, the access network device comprising: The third communication unit is configured to receive SPS configuration information sent by the core network equipment; And to transmit the SPS configuration information to the terminal device.

57. The access network device according to claim 56, wherein, The SPS configuration information is carried in the non-access stratum (NAS) message sent to the terminal device.

58. The access network device according to claim 56 or 57, wherein, The core network equipment includes one of the following: Mobility management network elements; Session management network element; Policy control network element.

59. The access network device according to any one of claims 56 to 58, wherein, The SPS configuration information is carried in one or more of the following NAS messages: Messages during the registration process; Messages related to location updates; Go to the registration process for related messages; Messages during the service request process; Safe mode command message.

60. The access network device according to any one of claims 56 to 59, wherein, The SPS configuration information is contained in the first session management (SM) container, which carries the NAS message sent to the terminal device.

61. The access network device according to claim 60, wherein, The NAS messages include messages related to the PDU session.

62. The access network device according to any one of claims 56 to 61, wherein, The SPS configuration information is contained in the first UE policy, which is carried in the NAS message.

63. The access network device according to claim 62, wherein, The NAS message includes one or more of the following: Messages during the registration process; Messages during the service request process; Messages related to PDU sessions; Downlink NAS transmission message.

64. The access network device according to any one of claims 56 to 63, wherein, The third communication unit is further configured to send the SPS configuration information to the core network device.

65. The access network device according to claim 64, wherein, The SPS configuration information is included in a first message sent by the access network device. The first message also includes a first identifier, which is used to identify the terminal device.

66. The access network device according to claim 65, wherein, The first message includes a second SM container, and the SPS configuration information is contained in the second SM container.

67. The access network device according to claim 65, wherein, The first message includes a second UE policy, and the SPS configuration information is contained in the second UE policy.

68. The access network device according to any one of claims 65 to 67, wherein, The first message includes one or more of the following: Initial UE message; Initial UE context establishment response; Uplink NAS transmission; Messages related to PDU sessions; Messages related to the handover process; Messages related to access network device configuration updates; Messages related to resource status reports.

69. A communication device, the communication device comprising: Memory, used to store computer programs; A processor, connected to the memory, is configured to invoke and run a computer program stored in the memory to perform the method as described in any one of claims 1 to 8, or the method as described in any one of claims 9 to 21, or the method as described in any one of claims 22 to 34.

70. A chip, comprising: A processor for retrieving and running a computer program from memory, causing a device having the chip mounted to perform the method as claimed in any one of claims 1 to 8, or the method as claimed in any one of claims 9 to 21, or the method as claimed in any one of claims 22 to 34.

71. A computer-readable storage medium for storing a computer program, the execution of which causes the computer to perform the method as claimed in any one of claims 1 to 8, or the method as claimed in any one of claims 9 to 21, or the method as claimed in any one of claims 22 to 34.

72. A computer program product comprising computer program instructions, the execution of which causes a computer to perform the method as claimed in any one of claims 1 to 8, or the method as claimed in any one of claims 9 to 21, or the method as claimed in any one of claims 22 to 34.

73. A computer program, the execution of which causes a computer to perform the method as claimed in any one of claims 1 to 8, or the method as claimed in any one of claims 9 to 21, or the method as claimed in any one of claims 22 to 34.