Communication method and communication apparatus

Abstract

The application provides a communication method and a communication device. A first network element can obtain first REDCAP information from a terminal device and second REDCAP information of a subscription of the terminal device, and determine whether the terminal device is allowed to use a service corresponding to the first REDCAP information according to the first REDCAP information and the second REDCAP information. The first network element is an access network device or a core network device. Based on the scheme, the first network element can verify whether the service corresponding to the first REDCAP information can be used through the subscription REDCAP information of the terminal device, thereby facilitating the terminal device to use only the corresponding service, for example, facilitating the terminal device to use only the first service type of service through the REDCAP access technology, and not to use the second service type of service through the REDCAP access technology.

Description

Technical Field

[0001] This application relates to the field of communications, and more specifically, to a communication method and a communication device. Background Technology

[0002] Fifth-generation (5G) wireless technology is primarily used to address various use cases, categorized as enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC). However, other use cases exist between these main categories, such as industrial sensor networks, video surveillance, and wearable devices. To effectively serve these use cases, reduced-capability (REDCAP) NR terminals have been introduced. Compared to conventional NR terminals, REDCAP terminals offer lower cost and complexity, smaller form factor, and longer battery life. A key challenge for REDCAP terminals is ensuring they can only be used with their designated use cases or services. Summary of the Invention

[0003] This application provides a communication method and a communication device, which helps to ensure that the corresponding terminal device can only use its corresponding service.

[0004] In a first aspect, a communication method is provided, the method comprising: a first network element acquiring first REDCAP information and second REDCAP information subscribed by the terminal device from a terminal device, and determining, based on the first REDCAP information and the second REDCAP information, whether the terminal device is allowed to use the service corresponding to the first REDCAP information.

[0005] Optionally, the first network element is an access network device or a core network device.

[0006] According to the communication method provided in this application, the first network element can verify whether the REDCAP information (i.e., the first REDCAP information) reported by the terminal device can be used through the REDCAP information (i.e., the second REDCAP information) subscribed by the terminal device, thereby helping to ensure that the terminal device can only use its corresponding services.

[0007] In conjunction with the first aspect, in some implementations of the first aspect, the first REDCAP information is used to indicate the REDCAP access technology, and the second information is used to indicate whether the terminal device has subscribed to the REDCAP access technology.

[0008] In this scheme, whether the terminal device is allowed to use the service corresponding to the first REDCAP information refers to whether the terminal device is allowed to establish a connection with the network through REDCAP access technology. Based on this scheme, the first network element can determine whether the terminal device can establish a connection with the network through REDCAP access technology, thereby ensuring that the terminal device can only use its subscribed access technology to establish a connection with the network.

[0009] In conjunction with the first aspect, in some implementations of the first aspect, the first REDCAP information is used to indicate the REDCAP access technology and the first service type, wherein the access technology used by the first service type is the REDCAP access technology, and the second REDCAP information is used to indicate the REDCAP access technology and at least one service type, wherein the access technology used by the at least one service type is the REDCAP access technology.

[0010] In this scheme, whether the terminal device is allowed to use the service corresponding to the first REDCAP information refers to whether the terminal device is allowed to use the service of the first service type through REDCAP access technology. Based on this scheme, the first network element can determine whether the terminal device can use the service of the first service type through REDCAP access technology, thereby ensuring that the terminal device can only use the service of the first service type under REDCAP access technology.

[0011] In conjunction with the first aspect, in some implementations of the first aspect, the first REDCAP information is used to indicate a first type of REDCAP access technology, and the second REDCAP information is used to indicate at least one type of REDCAP access technology, with different types of REDCAP access technologies corresponding to different service types. Specifically, the first type of REDCAP access technology corresponds to a first service type.

[0012] In this scheme, whether the terminal device is allowed to use the service corresponding to the first REDCAP information refers to whether the terminal device is allowed to use the first type of REDCAP access technology, or whether the terminal device is allowed to use the first type of service through the first type of REDCAP access technology, or whether the terminal device is allowed to use the first type of service. Based on this scheme, the first network element can determine whether the terminal device can use the first type of REDCAP access technology, thereby ensuring that the terminal device can only use the first type of REDCAP access technology.

[0013] In conjunction with the first aspect, in some implementations of the first aspect, the first network element sends a first instruction information to the terminal device. The first instruction information is used to indicate that the terminal device is not allowed to use the service corresponding to the first REDCAP information, or to indicate that the terminal device cannot use the service corresponding to the first REDCAP information.

[0014] Optionally, the first indication information includes a reason value, which indicates the reason why the terminal device was rejected.

[0015] In conjunction with the first aspect, in certain implementations of the first aspect, when the first network element is an access network device, the first network element obtains first REDCAP information from the terminal device, including: the first network element receiving a radio resource control (RRC) message from the terminal device, the RRC message including the first REDCAP information; or, the first network element receiving radio capability information from the terminal device and determining the first REDCAP information based on the radio capability information; or, the first network element receiving a first message from an access and mobility management network element, the first message including the first REDCAP information; or, the first network element receiving radio capability information of the terminal device from an access and mobility management network element and determining the first REDCAP information based on the radio capability information.

[0016] Based on any of the above methods, the first network element can obtain the first REDCAP information.

[0017] For example, this RRC message is an RRC connection establishment request message.

[0018] In conjunction with the first aspect, in some implementations of the first aspect, the first network element is an access network device in the second network during the process of the terminal device switching from the first network to the second network.

[0019] For example, the first network can be a fourth-generation (4G) or long-term evolution (LTE) network, and the second network can be a fifth-generation (5G) or new radio (NR) network.

[0020] In conjunction with the first aspect, in some implementations of the first aspect, the first network element acquiring first REDCAP information from the terminal device includes: the first network element receiving radio capability information of the terminal device from an access network device in the first network; and the first network element determining the first REDCAP information based on the radio capability information.

[0021] Furthermore, before the first network element determines the first REDCAP information based on the radio capability information, the method further includes: the first network element receiving REDCAP indication information sent from the access and mobility management network element in the second network, the REDCAP indication information being used to instruct the first network element to determine the first REDCAP information based on the radio capability information.

[0022] Based on this scheme, the first network element can determine the first REDCAP information according to the instructions of the access and mobility management network element in the second network and the radio capability information.

[0023] In conjunction with the first aspect, in certain implementations of the first aspect, the first network element obtaining the subscribed second REDCAP information of the terminal device includes: the first network element sending a request message to the access and mobility management network element based on the first REDCAP information, the request message being used to request the access and mobility management network element to obtain the second REDCAP information from the unified data management network element; and the first network element receiving the second REDCAP information from the access and mobility management network element.

[0024] It should be understood that when the first network element is an access network device in the second network, the access and mobility management network element is an access and mobility management network element in the second network.

[0025] In conjunction with the first aspect, in some implementations of the first aspect, the first network element is the access and mobility management network element.

[0026] In conjunction with the first aspect, in some implementations of the first aspect, the first network element obtaining the first REDCAP information includes: the first network element receiving a non-access stratum (NAS) message from the terminal device, the NAS message including the first REDCAP information; or, the first network element receiving the first REDCAP information from an access network device.

[0027] In conjunction with the first aspect, in some implementations of the first aspect, before the first network element receives the first REDCAP information from the access network device, the method further includes: the first network element sending radio capability information of the terminal device to the access network device, the radio capability information being used by the access network device to determine the first REDCAP information.

[0028] In conjunction with the first aspect, in some implementations of the first aspect, the first network element is the access and mobility management network element in the second network during the handover process of the terminal device from the first network to the second network.

[0029] In conjunction with the first aspect, in some implementations of the first aspect, the first network element acquiring the first REDCAP information includes: the first network element receiving the first REDCAP information from an access network device in the second network, wherein the first REDCAP information is determined by the access network device in the second network based on the radio capability information of the terminal device from the access network device in the first network.

[0030] In conjunction with the first aspect, in some implementations of the first aspect, before the first network element receives the first REDCAP information from the access network device in the second network, the method further includes: the first network element sending REDCAP indication information to the access network device in the second network, the REDCAP indication information being used to instruct the access network device in the second network to determine the first REDCAP information based on the radio capability information.

[0031] In conjunction with the first aspect, in some implementations of the first aspect, the first network element is the session management network element.

[0032] In conjunction with the first aspect, in some implementations of the first aspect, the first network element acquiring the first REDCAP information includes: the first network element receiving the first REDCAP information from the access and mobility management network element.

[0033] In conjunction with the first aspect, in some implementations of the first aspect, the first network element obtains the second REDCAP information by: the first network element sending a request message to the unified data management network element based on the first REDCAP information, the request message being used to request the second REDCAP information; and the first network element receiving the second REDCAP information from the unified data management network element.

[0034] In conjunction with the first aspect, in some implementations of the first aspect, the second REDCAP information is also used to indicate the business characteristic information corresponding to the at least one business type.

[0035] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: the first network element sending third indication information to the terminal device, the third indication information being used to indicate one or more of the following: the terminal device saving the timing advance (TA) value used during the current RRC connection establishment process and using it during the next RRC connection establishment; or, the terminal device reducing the frequency used for neighbor cell measurement; or, the terminal device saving the transmit power used during the current RRC connection establishment process and using it during the next RRC connection establishment.

[0036] For example, when the service characteristic information corresponding to the first service type is the fixed location of the terminal device or the terminal device is used in a video surveillance scenario, the first network element can send third instruction information to optimize the random access, wireless resource management or power control methods of the terminal device through the third instruction information.

[0037] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: a first network element transmitting broadcast information, the broadcast information including REDCAP access technology indication information and optimization indication information, the optimization information indicating whether a terminal device whose access technology is the first radio access technology should enable optimization functions according to the optimization indication information, the optimization functions including one or more of the following: saving the timing advance value (TA) used during the current RRC connection establishment process and using it during the next RRC connection establishment; or reducing the frequency when performing neighbor cell measurements; or saving the transmit power used during the current RRC connection establishment process and using it during the next RRC connection establishment.

[0038] For example, when the service characteristic information corresponding to the first service type is the fixed location of the terminal device or the terminal device is used in a video surveillance scenario, the first network element can send broadcast information to optimize the random access, wireless resource management or power control of the terminal device through the broadcast information.

[0039] In a second aspect, a communication method is provided, comprising: a terminal device sending first REDCAP information; the terminal device receiving indication information sent by a first network element according to the first REDCAP information, the indication information being used to indicate whether the terminal device is allowed to use the service corresponding to the first REDCAP information.

[0040] According to the communication method provided in this application, the first network element can verify whether the first REDCAP information can be used through the REDCAP information subscribed by the terminal device, thereby ensuring that the terminal device can only use its corresponding service.

[0041] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes: the terminal device sending adjusted REDCAP information according to the instruction information, the adjusted REDCAP information being different from the first REDCAP information.

[0042] In conjunction with the second aspect, in some implementations of the second aspect, the terminal device sends first REDCAP information, including: the terminal device sends radio capability information, the radio capability information being used to determine the first REDCAP information.

[0043] In conjunction with the second aspect, in some implementations of the second aspect, the first network element is an access network device.

[0044] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes: the terminal device receiving third indication information from the first network element, the third indication information indicating one or more of the following: the terminal device saves the timing advance (TA) value used during the current RRC connection establishment process and uses it during the next RRC connection establishment; or, the terminal device reduces the frequency used for neighbor cell measurement; or, the terminal device saves the transmit power used during the current RRC connection establishment process and uses it during the next RRC connection establishment.

[0045] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes: the terminal device receiving broadcast information from the first network element, the broadcast information including REDCAP access technology indication information and optimization indication information, the optimization information indicating whether the terminal device using REDCAP access technology should enable optimization function according to the optimization indication information, the optimization function including one or more of the following: saving the timing advance (TA) value used in the current RRC connection establishment process and using it in the next RRC connection establishment; or reducing the frequency when performing neighbor cell measurements; or saving the transmit power used in the current RRC connection establishment process and using it in the next RRC connection establishment.

[0046] Thirdly, a communication system is provided, comprising: a first network element and a second network element; the second network element sending first REDCAP information of a terminal device to the first network element; the first network element obtaining second REDCAP information subscribed by the terminal device based on the first REDCAP information; and the first network element determining whether to allow the terminal device to use the service corresponding to the first REDCAP information based on the first REDCAP information and the second REDCAP information.

[0047] According to the communication system provided in this application, the first network element can verify whether the first REDCAP information can be used through the REDCAP information subscribed by the terminal device, thereby ensuring that the terminal device can only use its corresponding service.

[0048] In conjunction with the third aspect, in some implementations of the third aspect, the second network element is an access and mobility management network element, and the first network element is an access network device; or, the second network element is an access network device, and the first network element is an access and mobility management network element; or, the second network element is an access and mobility management network element, and the first network element is a session management network element; or, the second network element is an access network device in the first network during the handover process of the terminal device from the first network to the second network, and the first network element is an access network device in the second network.

[0049] In conjunction with the third aspect, in some implementations of the third aspect, the system further includes a unified data management network element; and the first network element obtains the second REDCAP information of the terminal device based on the first REDCAP information, including: the first network element obtains the second REDCAP information from the unified data management network element based on the first REDCAP information.

[0050] Fourthly, a communication apparatus is provided, comprising modules or units for performing the methods of the first to second aspects or any possible implementation thereof.

[0051] Fifthly, an apparatus is provided, including a processor. The processor is coupled to a memory and is configured to execute instructions in the memory to cause the apparatus to perform the methods described in the first to second aspects or any possible implementation thereof. Optionally, the apparatus further includes a memory. Optionally, the apparatus further includes interface circuitry, to which the processor is coupled.

[0052] A sixth aspect provides a processor, comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive signals through the input circuit and transmit signals through the output circuit, causing the processor to execute the methods of the first aspect to the second aspect or any possible implementation thereof.

[0053] In specific implementation, the processor can be a chip, the input circuit can be an input pin, the output circuit can be an output pin, and the processing circuit can be a transistor, gate circuit, flip-flop, and various logic circuits. The input signal received by the input circuit can be received and input by, for example, but not limited to, a receiver, and the signal output by the output circuit can be output to, for example, but not limited to, a transmitter and transmitted by the transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as the input circuit and the output circuit at different times. This application does not limit the specific implementation of the processor and various circuits.

[0054] A seventh aspect provides a processing apparatus including a processor and a memory. The processor is configured to read instructions stored in the memory and to receive signals via a receiver and transmit signals via a transmitter to execute the methods of the first aspect to the second aspect or any of the possible implementations of the first aspect to the second aspect.

[0055] Optionally, the processor may be one or more, and the memory may be one or more.

[0056] Alternatively, the memory can be integrated with the processor, or the memory can be set separately from the processor.

[0057] In specific implementation, the memory can be a non-transitory memory, such as read-only memory (ROM), which can be integrated with the processor on the same chip or set on different chips. The embodiments of this application do not limit the type of memory or the way the memory and processor are set.

[0058] The processing device in the seventh aspect above can be a chip. The processor can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, integrated circuit, etc. When implemented in software, the processor can be a general-purpose processor that reads software code stored in memory. The memory can be integrated into the processor or located outside the processor and exist independently.

[0059] Eighthly, a computer program product is provided, comprising: a computer program (also referred to as code or instructions) that, when run, causes a computer to perform the methods described in the first, second, or ninth aspects, or any possible implementation of the first to second aspects.

[0060] Ninth aspect, a computer-readable medium is provided that stores a computer program (also referred to as code or instructions) that, when executed on a computer, causes the computer to perform the methods of the first to second aspects or any possible implementation thereof. Attached Figure Description

[0061] Figure 1 This is a schematic diagram of a communication system provided in this application;

[0062] Figure 2 This is a schematic diagram of another communication system provided in this application;

[0063] Figure 3 This is a schematic flowchart of a communication method provided in this application;

[0064] Figure 4 This is a schematic flowchart of another communication method provided in this application;

[0065] Figure 5 This is a schematic flowchart of a communication method provided in this application;

[0066] Figure 6 This is a schematic flowchart of another communication method provided in this application;

[0067] Figure 7 This is a schematic flowchart of a communication method provided in this application;

[0068] Figure 8 This is a schematic flowchart of another communication method provided in this application;

[0069] Figure 9 This is a schematic block diagram of a communication device provided in this application;

[0070] Figure 10 This is a schematic block diagram of an access network device provided in this application;

[0071] Figure 11 This is a schematic block diagram of a terminal device provided in this application;

[0072] Figure 12 This is a schematic block diagram of a communication device provided in this application. Detailed Implementation

[0073] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0074] The technical solutions of this application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) system, 5th Generation (5G) system, New Radio (NR) system, or other communication systems that may emerge in the future.

[0075] Figure 1 An architecture diagram of the system 100 that can be applied to this application is shown. For example... Figure 1As shown, the system 100 may include one or more of the following devices: terminal device 101, access network device 102, user plane network element 103, data network 104, access and mobility management network element 105, session management network element 106, policy control network element 107, application network element 108, unified data management network element 109, and network openness network element 110.

[0076] Terminal device 101 can be user equipment (UE), a user, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user equipment. For example, it can be a mobile phone, tablet computer, computer with wireless transceiver capabilities, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical care, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, etc. Terminal device 101 can also be a device or circuit structure installed in the above-mentioned various devices, such as a chip or chip system.

[0077] The terminal device in this application may refer to a REDCAP terminal device, or a low-capacity terminal device, a reduced-capacity terminal device, a REDCAP UE, a Reduced Capacity UE, a narrow-band NR (NB-NR) UE, etc.

[0078] Optionally, the terminal device in this application has one or more of the following features:

[0079] 1. Bandwidth Capability. Bandwidth capability can be expressed as the maximum baseband bandwidth processing capacity. For example, the terminal device in this application supports a bandwidth of no more than 40MHz.

[0080] 2. Number of transmit and receive antennas. For example, the terminal device in this application may support 2 receive and 1 transmit (2 receiving antennas and 1 transmitting antenna), or 1 receive and 1 transmit (1 receiving antenna and 1 transmitting antenna).

[0081] 3. Maximum uplink transmit power. For example, the maximum uplink transmit power of the terminal device in this application can be 4 dBm. A value within 20dBm.

[0082] 4. Protocol Version. The terminal device in this application may be a terminal device of NR version 17 (release-17, Rel-1) or a later version of NR Rel-17.

[0083] 5. Carrier aggregation capability. For example, the terminal device in this application does not support carrier aggregation, or it supports carrier aggregation, but the maximum number of carrier aggregations supported at the same time is less than the maximum number of carrier aggregations supported at the same time by terminal devices with traditional, normal, or high capabilities (also referred to as legacy terminal devices or normal terminal devices).

[0084] 6. Duplex capability. For example, the terminal device in this application supports half-duplex frequency division duplexing (FDD).

[0085] 7. Data processing time capability. For example, the minimum latency between the terminal device in this application receiving downlink data and sending feedback on the downlink data is greater than the minimum latency between the terminal device with conventional, normal, or high capabilities receiving downlink data and sending feedback on the downlink data; and / or, the minimum latency between the terminal device in this application sending uplink data and receiving feedback on the uplink data is greater than the minimum latency between the terminal device with conventional, normal, or high capabilities sending uplink data and receiving feedback on the uplink data.

[0086] 8. Processing Capability. For example, the baseband processing capability of the terminal device in this application is lower than that of a conventional, normal, or high-capability terminal device. The baseband processing capability may include at least one of the following: the maximum number of multiple-input multiple-output (MIMO) layers supported by the terminal device during data transmission; the number of hybrid automatic repeat request (HARQ) processes supported by the terminal device; and the maximum transmission block size (TBS) supported by the terminal device.

[0087] 9. Uplink and / or downlink peak transmission rates. Peak transmission rate refers to the maximum data transmission rate that a terminal device can achieve per unit time (e.g., per second). The uplink peak rate supported by the terminal device in this application may be lower than the uplink peak rate supported by conventional, normal, or high-capacity terminal devices, and / or the downlink peak rate supported by the terminal device in this application may be lower than the downlink peak rate supported by conventional, normal, or high-capacity terminal devices.

[0088] 10. Buffer size. The buffer can be understood as the total size of the Layer 2 (L2) buffer, or the total number of soft channel bits that HARQ processing can use.

[0089] Access network device 102: It can manage radio resources, provide access services for terminal devices, and thus complete the forwarding of control signals and user data between terminal devices and the core network.

[0090] Access network equipment can include transmission reception points (TRPs), evolved NodeBs (eNBs or eNodeBs) in LTE systems, home base stations (e.g., home evolved NodeBs or home Node Bs, HNBs), base band units (BBUs), radio controllers, relay stations, access points, vehicle-mounted equipment, wearable devices in cloud radioaccess network (CRAN) scenarios, next-generation NodeBs (gNBs) in 5G mobile communication systems, and access network equipment and access points (APs) in future evolved public land mobile networks (PLMNs).

[0091] User plane element 103: mainly responsible for data packet routing and forwarding.

[0092] Data network 104: This can be a carrier service, internet access, or a third-party service, such as IP Multimedia Service (IMS) or the internet. The data network may include an application server (AS), which is a software framework that provides an environment for applications to run, offering services such as security, data, transaction support, load balancing, and large-scale distributed system management. Terminal devices obtain application messages by communicating with the AS.

[0093] Access and Mobility Management Element 105: Primarily responsible for mobility management in mobile networks, such as user location updates, user registration networks, and user handover.

[0094] Session Management Element 106: Primarily responsible for session management in mobile networks, such as session establishment, modification, and release. Specific functions include assigning IP addresses to users and selecting user plane network elements that provide packet forwarding capabilities.

[0095] Policy control network element 107: responsible for providing policies to access and mobility management network elements and session management network elements, such as quality of service (QoS) policies and slice selection policies.

[0096] Application Element 108: Responsible for providing services to the 3GPP network and interacting with policy control elements to perform policy control, etc.

[0097] Unified Data Management Network Element 109: Used to store user data, such as contract information and authentication / authorization information.

[0098] Network Open Element 110: Provides frameworks, authentication and interfaces related to open network capabilities, and facilitates the transfer of information between 5G system network functions and other network functions.

[0099] It should be understood that the aforementioned devices or network elements can be devices with corresponding functions, or internal software / hardware modules (such as chips). It should also be understood that any device or network element involved in this application can be implemented in software or a combination of software and hardware.

[0100] In one example Figure 1 The system 100 shown can be Figure 2 The 5G system shown is illustrated. It should be understood that system 100 can also be a 4G system or other systems, and this application does not limit it in this regard.

[0101] Figure 2 This is a schematic diagram of a 5G system architecture. In this system architecture diagram, [the following is related to...] Figure 1 The network elements with the same labels in the attached diagram are Figure 1 The naming conventions of the corresponding network elements in the current 5G system. See also... Figure 2The 5G system architecture may include one or more of the following network elements: UE 101, (radio)access network (RAN) 102, user plane function (UPF) 103, data network (DN) 104, access and mobility management function (AMF) 105, session management function (SMF) 106, policy control function (PCF) 107, application function (AF) 108, unified data management (UDM) 109, and network exposure function 110.

[0102] It should be understood that Figure 2 The names given to each network element are merely names and do not limit the function of the element itself. In different networks, these network elements may have other names, and this embodiment does not impose specific limitations on this. For example, in a 6G network, some or all of the above network elements may use the terminology from 5G, or they may have other names. Similarly, Figure 2 The interface between network elements shown is only an example. In 5G networks and other future networks, the interface between network elements may not be the interface shown in the figure. This application does not limit this.

[0103] It should also be understood that the embodiments of this application are not limited to those described above. Figure 2 In the system architecture shown. For example, a communication system to which this application can be applied may include more or fewer network elements or devices. Figure 2 The devices or network elements in the network can be hardware, software based on function, or a combination of both. Figure 2 Devices or network elements within the network can communicate with each other through other devices or network elements.

[0104] 5G wireless technology is primarily used to address various use cases, categorized as enhanced mobile broadband (eMBB), ultra-reliable and low-latency communication (URLLC), and massive machine-type communication (mMTC). However, other use cases exist alongside these main ones, such as industrial sensor networks, video surveillance, and wearable devices. To effectively serve these use cases, reduced-capability (REDCAP) NR terminals have been introduced. Compared to conventional NR terminals, REDCAP terminals offer lower cost and complexity, smaller form factor, and longer battery life. A key challenge for REDCAP terminals is ensuring they can only be used with their designated use cases or services.

[0105] In view of this, this application provides a communication method in which an access network device or a core network device can determine whether a terminal device can use the service corresponding to the REDCAP information it reports (i.e., the first REDCAP information), thereby helping to ensure that the terminal device can only use the corresponding service. The solution provided by this application is described below.

[0106] Figure 3 This is a schematic flowchart of a communication method provided in this application. The method 300 may include steps S310 to S330, which will be described below.

[0107] S310, the first network element obtains REDACP information from the terminal device, i.e., the first REDACP information.

[0108] In this application, the first REDACP information can be sent proactively by other network elements to the first network element, or it can be sent by other network elements to the first network element after receiving a request from the first network element, or it can be determined by the first network element itself. Examples will be provided in methods 400 to 800 below.

[0109] S320, the first network element obtains the REDCAP information of the terminal device, that is, the second REDCAP information.

[0110] The first network element can obtain the subscription information of the terminal device from the unified data management network element. The subscription information of the terminal device includes the second REDCAP information. Alternatively, the first network element can obtain the second REDCAP information from the subscription information of the terminal device from the unified data management network element. The second REDCAP information may be information that was already stored in the unified data management network element when the terminal device signed up, or it may be information sent by the application network element to the unified data management network element through the capability open interface.

[0111] S330, the first network element determines whether to allow the terminal device to use the service corresponding to the first REDCAP information based on the first REDCAP information and the second REDCAP information.

[0112] In the first implementation, the first REDCAP information is used to indicate the REDCAP access technology. Correspondingly, the second REDCAP information is used to indicate the access technology subscribed to by the terminal device, or the second REDCAP information is used to indicate whether the terminal device has subscribed to the REDCAP access technology.

[0113] If the terminal device's subscribed access technology includes REDCAP access technology, or if the terminal device has subscribed to REDCAP access technology, then the terminal device is allowed to use the service corresponding to the first REDCAP information, that is, the terminal device is allowed to use REDCAP access technology to establish a connection with the network. If the terminal device's subscribed access technology does not include REDCAP access technology, or if the terminal device has not subscribed to REDCAP access technology, then the terminal device is not allowed to use the service corresponding to the first REDCAP information, that is, the terminal device is not allowed to use REDCAP access technology to establish a connection with the network.

[0114] In both the first and second implementation methods described below, REDCAP access refers to a "simplified" version of NR technology, or Reduced Capability NR, developed by 5G NR to adapt to the massive network access of IoT terminals. This aims to meet the network connectivity needs of IoT terminal devices in three scenarios: video surveillance, industrial sensor networks, and wearable devices, or similar needs in other scenarios. In other words, in both the first and second implementation methods, it can be assumed that REDCAP terminals corresponding to different scenarios or use cases can establish connections to the network through REDCAP access technology. For example, REDCAP terminals for video surveillance, industrial sensor networks, and wearable devices can all establish connections to the network through REDCAP access technology.

[0115] For example, if the terminal device is a wearable device, and the wearable device has subscribed to REDCAP access technology, it can be allowed to establish a connection with the network through REDCAP access technology. If the wearable device has subscribed to narrowband Internet of Things (NB-IoT) access technology, it is not allowed to establish a connection with the network through REDCAP access technology.

[0116] In the second implementation, the first REDCAP information is used to indicate the REDCAP access technology and the first service type, wherein the access technology used by the first service type is the REDCAP access technology. Correspondingly, the second REDCAP information is used to indicate the REDCAP access technology and at least one service type, wherein the access technology used by the at least one service type is the REDCAP access technology.

[0117] If the at least one service type includes the first service type, then the terminal device is allowed to use the service corresponding to the first REDCAP information, that is, the terminal device is allowed to use REDCAP access technology to access the service of the first service type. If the at least one service type does not include the first service type, then the terminal device is not allowed to use the service corresponding to the first REDCAP information, that is, the terminal device is not allowed to use REDCAP access technology to access the service of the first service type.

[0118] For example, if the first service type is video surveillance service, and the at least one service type also includes video surveillance service, then the terminal device is allowed to access the video surveillance service using REDCAP access technology. If the first service type is video surveillance, and the at least one service type is wearable service, then the terminal device is not allowed to access the video surveillance service using REDCAP access technology.

[0119] In the third implementation, the first REDCAP information is used to indicate a first type of REDCAP access technology, and correspondingly, the second REDCAP information is used to indicate at least one type of REDCAP access technology. Different types of REDCAP access technologies correspond to different service types.

[0120] If the at least one type of REDCAP access technology includes the first type of REDCAP access technology, then the terminal device is allowed to use the service corresponding to the first REDCAP information, that is, the terminal device is allowed to use the first type of REDCAP access technology to access the service corresponding to the first type of REDCAP access technology. If the at least one type of REDCAP access technology does not include the first type of REDCAP access technology, then the terminal device is not allowed to use the service corresponding to the first REDCAP information, that is, the terminal device is not allowed to use the first type of REDCAP access technology to access the service corresponding to the first type of REDCAP access technology.

[0121] In this implementation, different scenarios or use cases can be considered to correspond to different REDCAP access technologies, or different REDCAP access technologies can be considered to indicate different scenarios or use cases. For example, the first type of REDCAP access technology corresponds to video surveillance scenarios, the second type of REDCAP access technology corresponds to industrial sensor networks, and the third type of REDCAP access technology corresponds to wearable scenarios. REDCAP terminals used in video surveillance scenarios, such as surveillance cameras, can use the first type of REDCAP access technology; REDCAP terminals used in industrial sensor networks, such as temperature sensors and pressure sensors, can use the second type of REDCAP access technology; and wearable devices such as smart bracelets and smartwatches can use the third type of REDCAP access technology.

[0122] For example, if the terminal device is a surveillance camera and the surveillance camera is subscribed to the first type of REDCAP access technology, then the terminal device is allowed to access video surveillance services using the first type of REDCAP access technology.

[0123] In this application, business, business type, scenario, use case, and use case information can be interchanged.

[0124] According to the method provided in this application, the terminal device can report the access technology and / or service type to the first network element (access network equipment or core network equipment). The first network element uses the subscription information of the terminal device to verify the access technology and / or service type reported by the terminal device to determine whether the terminal device can use the reported access technology and / or service type. This helps to ensure that the terminal device can only use its corresponding service.

[0125] In the above scheme, the first network element can be either an access network device or a core network device. The following examples illustrate the scheme provided in this application in more detail, using the first network element as an access network device, an access and mobility management network element, a session management network element, an access network device in the second network during the handover process from the first network to the second network, and an access and mobility management network element in the second network during the handover process from the first network to the second network.

[0126] Figure 4 This is a schematic flowchart of a communication method provided in this application. Method 400 is an example where the first network element is an access network device; the method 400 is described below.

[0127] S401, the access network device obtains the first REDCAP information.

[0128] The access network device can obtain this first REDCAP information in several ways. Examples are given below.

[0129] Method 1

[0130] The terminal device can carry first REDCAP information in the RRC message sent to the access network device.

[0131] For example, this RRC message is an RRC connection establishment request message.

[0132] Method 2

[0133] The terminal device can send its radio capability information to the access network device, and the access network device can determine the first REDCAP information based on the radio capability information. For example, the radio capability information can carry the first REDCAP information. Alternatively, the access network device can determine the first REDCAP information based on parameters in the radio capability information. For instance, the access network device can determine the REDCAP information used by the terminal device based on parameters such as the corresponding access frequency point in the radio capability information and use it as the first REDCAP information.

[0134] For example, this method can be applied to the case of the terminal device being registered for the first time upon power-on.

[0135] Method 3

[0136] The terminal device can send its radio capability information to the access network device, and the access network device can send the radio capability information to the access and mobility management network element. After an RRC connection is established between the terminal device and the access network device, the access network device can request the radio capability information from the access and mobility management network element. Upon receiving the request, the access and mobility management network element returns the radio capability information to the access network device. The access network device can determine the first REDCAP information based on the radio capability information. For details on how the access network device determines the first REDCAP information based on the radio capability information, please refer to the description in Method 2; it will not be repeated here.

[0137] For example, in this application, the access and mobility management network element can put the wireless capability information of the terminal device in a container, which only stores the wireless capability information of the terminal device and does not view the contents of the wireless capability information of the terminal device.

[0138] Method 4

[0139] The terminal device can send first REDCAP information to the access and mobility management network element (AMI) via NAS messages. The AMI can then forward the received first REDCAP information to the access network device. For example, after receiving a NAS message, the AMI can proactively send the first REDCAP information from the NAS message to the access network device. Alternatively, when the access network device requests the first REDCAP information, the AMI can forward the received first REDCAP information to the access network device.

[0140] For example, the NAS message could be a registration request message.

[0141] For example, the access and mobility management network element can send the first REDCAP information to the access network device via the N2 message. N2 is the interface between the access and mobility management network element and the access network device. If the name of this interface changes, the message name will also change accordingly.

[0142] S402, the access network device sends a first request message to the access and mobility management network element based on the first REDCAP information. Correspondingly, the access and mobility management network element receives the first request message sent by the terminal device.

[0143] For example, the first request message is used to instruct the access and mobility management network element to obtain the subscription information of the terminal device from the unified data management network element, wherein the subscription information includes second REDCAP information. For instance, the first request message may include the identity information of the terminal device, such as a subscription permanent identifier (SUPI).

[0144] Furthermore, the first request message may also include a fourth instruction message, which instructs the access and mobility management network element to obtain only the second REDCAP information from the unified data management network element, without obtaining other subscription information of the terminal device.

[0145] S403, the access and mobility management network element sends a second request message to the unified data management network element based on the first request message from the access network device.

[0146] It should be understood that the content of the first request message and the second request message may be the same, but this application does not limit this. For example, if the first request message includes the fourth instruction information, the second request message may not include the fourth instruction information.

[0147] S404, the unified data management network element sends the subscription information or second REDCAP information of the terminal device to the access and mobility management network element. Correspondingly, the access and mobility management network element receives the subscription information or second REDCAP information of the terminal device.

[0148] Specifically, upon request from the access and mobility management network element, the unified data management network element can retrieve the second REDCAP information from the subscription information of the terminal device and then send the second REDCAP information to the access and mobility management network element. Alternatively, upon request from the access and mobility management network element, the unified data management network element can send the subscription information of the terminal device, including the second REDCAP information, to the access and mobility management network element.

[0149] S405, the access and mobility management network element sends a second REDCAP message or the subscription information of the terminal device to the access network equipment. Correspondingly, the access network equipment receives the second REDCAP message or the subscription information of the terminal device.

[0150] S406, the access network device determines whether to allow the terminal device to use the service corresponding to the first REDCAP information based on the first REDCAP information and the second REDCAP information.

[0151] This step is the same as S330, and you can refer to S330.

[0152] Optionally, the method may further include:

[0153] S407a, the access network device sends a first indication message to the terminal device. Correspondingly, the terminal device receives the first indication message. The first indication message indicates that the terminal device is not allowed to use the service corresponding to the first REDCAP information, or that the terminal device cannot use the service corresponding to the first REDCAP information.

[0154] If, in S406, the access network device determines that the terminal device is not allowed to use the service corresponding to the first REDCAP information, it can send a first indication message to the terminal device, indicating that the terminal device cannot use the service corresponding to the first REDCAP information.

[0155] For example, the first indication information may include a reason value, which indicates the reason why the terminal device is rejected, that is, the reason why the terminal device is not allowed to use the service corresponding to the first REDCAP information. For example, the reason value indicates that the terminal device has not subscribed to the REDCAP access technology. For example, the reason value indicates that the terminal device is illegally / unauthorized to use the service of the first service type.

[0156] For example, the first indication information or the reason value can be carried in an RRC reject or RRC release message.

[0157] Optionally, the method may further include:

[0158] S408a, the terminal device sends the adjusted REDCAP information to the access network equipment.

[0159] After receiving the first instruction information, the terminal device can report the adjusted REDCAP information to the access network equipment. The access network equipment can then determine whether to allow the terminal device to use the service corresponding to the adjusted REDCAP information.

[0160] For example, if the adjusted REDCAP information can indicate the REDCAP access technology and the second service type, and the second service type uses the REDCAP access technology, and the second REDCAP information indicates the REDCAP access technology and the second service type, then the terminal device is allowed to use the service corresponding to the adjusted REDCAP information.

[0161] Optionally, the method may further include:

[0162] S409a, the terminal device initiates a mobility update process to update the wireless capability information of the terminal device, thereby updating the first REDCAP information.

[0163] That is, the terminal device sends the adjusted REDCAP information to the access network device by updating the terminal device's wireless capability information.

[0164] It should be understood that either S408a or S409a can be implemented.

[0165] Optionally, the method may further include:

[0166] S407b, the access network device sends a second indication message to the terminal device, the second indication message indicating that the terminal device is allowed to use the service corresponding to the first REDCAP information. Accordingly, the terminal device receives the second indication message.

[0167] If, in S406, the access network device determines that the terminal device is allowed to use the service corresponding to the first REDCAP information, then it can send the second instruction information to the terminal device.

[0168] Alternatively, if in S406 the access network device determines that the terminal device is allowed to use the service corresponding to the first REDCAP information, and the first service type indicated by the first REDCAP information represents a higher access priority, then the access network device can send second indication information to the terminal device. For example, if the access network device determines that the terminal device is allowed to use the service corresponding to the first REDCAP information, and the first service type indicated by the first REDCAP information is a wearable service, then the access network device can send second indication information to the terminal device. For instance, the second indication information can be carried via an RRC receive message.

[0169] It should be understood that either S407a or S407b can be implemented.

[0170] According to the communication method provided in this application, the terminal device can report first REDCAP information to the access network device. After the access network device obtains the REDCAP information subscribed to by the terminal device (i.e., second REDCAP information), it verifies the first REDCAP information to determine whether the terminal device can use the service corresponding to the first REDCAP information. This helps to ensure that the terminal device can only use its corresponding service.

[0171] Figure 5 This is a schematic flowchart of a communication method provided in this application. Method 500 is an example where the first network element is an access and mobility management network element; the method 500 is described below.

[0172] S501, the access and mobility management network element obtains the first REDCAP information.

[0173] Access and mobility management network elements can obtain first REDCAP information in various ways. Examples are given below.

[0174] Method 1

[0175] The terminal device can send a NAS message to the access and mobility management network element, and the NAS message can carry the first REDCAP information. Therefore, the access and mobility management network element can obtain the first REDCAP information by receiving the NAS message.

[0176] For example, the NAS message could be a registration request message.

[0177] Method 2

[0178] The access network device can send the first REDCAP information to the access and mobility management network element.

[0179] For example, the first REDCAP information on the access network device side can be sent by the terminal device to the access network device via an RRC message.

[0180] For example, the first REDCAP information on the access network device side can be determined by the access network device based on the wireless capability information of the terminal device sent by the terminal device. For instance, during the initial registration process of the terminal device upon power-on, the terminal device can send its wireless capability information to the access network device (possibly at the request of the access network device). How the access network device determines the first REDCAP information based on the wireless capability information of the terminal device sent by the terminal device can be referred to Method 2 in Method 400, and will not be elaborated here.

[0181] For example, the first REDCAP information on the access network device side can be determined by the access network device based on the radio capability information of the terminal device obtained from the access and mobility management network element. Specifically, the terminal device can send its radio capability information to the access network device, and the access network device can send the radio capability information to the access and mobility management network element. After the terminal device completes an RRC connection with the access network device, the access network device can request the radio capability information from the access and mobility management network element. After receiving the request from the access network device, the access and mobility management network element returns the radio capability information to the access network device. The access network device can determine the first REDCAP information based on the radio capability information and send the first REDCAP information to the access and mobility management network element. For details on how the access network device determines the first REDCAP information based on the radio capability information, please refer to the description in Method 2, which will not be repeated here.

[0182] In steps S502-S503, the access and mobility management network element sends a second request message to the unified data management network element based on the first REDCAP information, requesting the second REDCAP information or the subscription information of the terminal device. The unified data management network element, based on the request from the access and mobility management network element, returns the second REDCAP information or the subscription information of the terminal device to the access and mobility management network element.

[0183] Steps S502 to S503 are the same as S403 to S404, and can be referred to S403 to S404, so they will not be repeated here.

[0184] S504, the access and mobility management network element determines whether to allow the terminal device to use the service corresponding to the first REDCAP information based on the first REDCAP information and the second REDCAP information.

[0185] This step is the same as S330, and you can refer to S330.

[0186] Optionally, the method may further include:

[0187] S505a, the access and mobility management network element sends a first indication message to the terminal device, the first indication message indicating that the terminal device is not allowed to use the service corresponding to the first REDCAP information. Accordingly, the terminal device receives the first indication message.

[0188] If, in S504, the access and mobility management network element determines that the terminal device is not allowed to use the service corresponding to the first REDCAP information, then it can send the first instruction information to the terminal device.

[0189] For example, the first indication information may include a reason value indicating the reason why the terminal device was rejected. For instance, the reason value may indicate that the terminal device has not subscribed to REDACP access technology. Or, the reason value may indicate that the terminal device is illegally / unauthorized to use the services of the first service type.

[0190] For example, the first indication information or the reason value can be carried in a NAS reject message. For instance, the NAS reject message could be a NAS registration rejection message.

[0191] Optionally, the method may further include:

[0192] S506a, the terminal device sends the adjusted REDCAP information to the access and mobility management network element.

[0193] After receiving the first instruction information, the terminal device can report the adjusted REDCAP information to the access network equipment. Then, the access network equipment sends the adjusted REDCAP information to the access and mobility management network element. The access and mobility management network element can determine whether to allow the terminal device to use the service corresponding to the adjusted REDCAP information.

[0194] For example, the adjusted REDCAP information can indicate the REDCAP access technology and the second service type. The second service type uses the REDCAP access technology. If the second REDCAP information indicates the REDCAP access technology and the second service type, then the terminal device is allowed to use the service corresponding to the adjusted REDCAP information.

[0195] Optionally, the method may further include:

[0196] S507a, the terminal device initiates a mobility update process to update the wireless capabilities of the terminal device, thereby updating the first REDCAP information.

[0197] That is, the terminal device sends adjusted REDCAP information to the access network device by updating its radio capability information. The access network device can then send the adjusted REDCAP information to the access and mobility management network element (AMI), which can determine whether to allow the terminal device to use the service corresponding to the adjusted REDCAP information. It should be understood that either S506a or S507a can be executed.

[0198] Optionally, the method may further include:

[0199] In S505b, the access and mobility management network element sends a second indication message to the terminal device, the second indication message indicating that the terminal device is permitted to use the service corresponding to the first REDCAP information. Accordingly, the terminal device receives the second indication message.

[0200] If, in S504, the access and mobility management network element determines that the terminal device is permitted to use the service corresponding to the first REDCAP information, then it can send the second instruction information to the terminal device.

[0201] For example, the second instruction information can be carried via a NAS receive message.

[0202] It should be understood that either S505a or S506b can be implemented.

[0203] According to the communication method provided in this application, the access and mobility management network element can obtain the first REDCAP information, and after obtaining the REDCAP information subscribed to by the terminal device (i.e., the second REDCAP information), it can verify the first REDCAP information to determine whether the terminal device can use the service corresponding to the first REDCAP information. This helps to ensure that the terminal device can only use its corresponding service.

[0204] Figure 6 This is a schematic flowchart of a communication method provided in this application. Method 600 is an example where the first network element is a session management network element; the method 600 is described below.

[0205] S601, the session management network element obtains the first REDCAP information.

[0206] Specifically, the access and mobility management network element can send the first REDCAP information to the session management network element. For details on how the access and mobility management network element obtains the first REDCAP information, please refer to the description of S501 in method 500; it will not be repeated here.

[0207] S602, the session management network element sends a third request message to the unified data management network element.

[0208] For example, the content of the third request message can be the same as the content of the first request message or the second request message described above. For details, please refer to the description of steps S402 and S403 in method 400, which will not be repeated here.

[0209] S603, the unified data management network element returns second REDCAP information or the terminal device's subscription information to the session management network element according to the request of the terminal device. Correspondingly, the session management network element receives the second REDCAP information or the terminal device's subscription information. The terminal device's subscription information includes the second REDCAP information.

[0210] S604, the session management network element determines whether to allow the terminal device to use the service corresponding to the first REDCAP information based on the first REDCAP information and the second REDCAP information.

[0211] This step is the same as S330, and you can refer to S330.

[0212] Optionally, the method may further include:

[0213] S605a, the session management network element sends a first indication message to the terminal device, the first indication message indicating that the terminal device is not allowed to use the service corresponding to the first REDCAP information. Accordingly, the terminal device receives the first indication message.

[0214] If, in S604, the session management network element determines that the terminal device is not allowed to use the service corresponding to the first REDCAP information, it can send the first indication information to the access and mobility management network element. For example, the access and mobility management network element can carry the first indication information in the NAS message sent to the terminal device.

[0215] For example, the first indication information may include a reason value indicating the reason why the terminal device was rejected. For instance, the reason value may indicate that the terminal device has not subscribed to REDACP access technology. Or, the reason value may indicate that the terminal device is illegally / unauthorized to use the services of the first service type. For example, the first indication information or the reason value may be carried in a NAS SM rejection message. For example, the NAS rejection message may be a PDU session establishment rejection message.

[0216] Optionally, the method may further include:

[0217] S606a, the terminal device sends the adjusted REDCAP information to the access network equipment, and the access network equipment sends the adjusted REDCAP information to the session management network element through the access and mobility management network element.

[0218] After receiving the first indication information, the terminal device can report the adjusted REDCAP information to the access network equipment. The access network equipment then sends the adjusted REDCAP information to the session management network element through the access and mobility management network element. The session management network element can determine whether to allow the terminal device to use the service corresponding to the adjusted REDCAP information. For example, the adjusted REDCAP information may indicate the REDCAP access technology and the second service type. If the second service type uses the REDCAP access technology, and the second REDCAP information indicates both the REDCAP access technology and the second service type, then the terminal device is allowed to use the service corresponding to the adjusted REDCAP information.

[0219] Optionally, the method may further include:

[0220] S607a, the terminal device initiates a mobility update process to update the wireless capabilities of the terminal device, thereby updating the first REDCAP information.

[0221] That is, the terminal device sends the adjusted REDCAP information to the access network device by updating its radio capability information. The access network device can send the adjusted REDCAP information to the session management element through the access and mobility management element, and the session management element can determine whether to allow the terminal device to use the service corresponding to the adjusted REDCAP information.

[0222] It should be understood that either S606a or S607a can be implemented.

[0223] Optionally, the method may further include:

[0224] In S605b, the session management network element sends a second indication message to the terminal device, the second indication message indicating that the terminal device is allowed to use the service corresponding to the first REDCAP information. Accordingly, the terminal device receives the second indication message.

[0225] If, in S604, the session management network element determines that the terminal device is allowed to use the service corresponding to the first REDCAP information, then the second instruction information can be sent to the terminal device.

[0226] For example, the second instruction information can be carried in the accept message established through the PDU session.

[0227] It should be understood that either S605a or S606b can be implemented.

[0228] According to the communication method provided in this application, the session management network element can obtain the first REDCAP information, and after obtaining the REDCAP information subscribed to by the terminal device (i.e., the second REDCAP information), it can verify the first REDCAP information to determine whether the terminal device can use the service corresponding to the first REDCAP information. This helps to ensure that the terminal device can only use its corresponding service.

[0229] Figure 7 This is a schematic flowchart of a communication method provided in this application. Method 700 is an example of a first network element being an access and mobility management network element in a second network during the handover process of a terminal device from a first network to a second network. Exemplarily, the first network can be a 4G or LTE network, and the second network can be a 5G or NR network, but this application does not limit it to these possibilities.

[0230] For ease of understanding and description, the access network devices in the second network are referred to as "target access network devices," and the access network devices in the first network are referred to as "source access network devices." The access and mobility management network elements in the second network are referred to as "target access and mobility management network elements," and the access network devices in the first network are referred to as "source access and mobility management network elements." For example, the target access network device can be the gNB shown in the figure, and the source access network device can be the eNB shown in the figure; the target access and mobility management network element can be the AMF shown in the figure, and the source and target access and mobility management network elements can be the MME shown in the figure. The method 700 is described below.

[0231] S701, the source access network device sends a handover request message to the target access network device. Correspondingly, the target access network device receives the handover request message from the source access network device. The handover request message includes the radio capability information of the terminal device.

[0232] Regarding how the source access network device obtains the wireless capability information of the terminal device, you can refer to the description of the access network device obtaining the wireless capability information of the terminal device in step S401. However, it should be understood that at this time, the access and mobility management network element should be the access and mobility management network element in the first network, such as the MME.

[0233] It should be understood that in the case of switching between different systems, the process that needs to be executed before step S701 can refer to existing technologies, such as TS 23.502 Clause 4.111.2.2, which will not be described in detail here.

[0234] S702, when the target access and mobility management network element determines that the terminal device is undergoing a system handover, such as when it determines that the terminal is switching from LTE to 5G, it can send REDCAP indication information to the target access network device. Accordingly, the target access network device receives the REDCAP indication information.

[0235] The REDCAP indication information is used to instruct the target access network device to determine the first REDCAP information based on the wireless capability information of the terminal device.

[0236] It should be understood that 702 can be executed before or after S701, and the embodiments of this application do not limit this.

[0237] S703, the target access network device determines the first REDCAP information based on the wireless capability information of the terminal device.

[0238] Optionally, the target access network device may determine the first REDCAP information from the terminal radio capability information based on the REDCAP indication information sent by the access and mobility management network element.

[0239] Regarding how the target access network device determines the first REDCAP information based on the wireless capability information of the terminal device, please refer to the relevant description in Method 2 of step S401 for the access network device determining the first REDCAP information based on the wireless capability information of the terminal device, which will not be repeated here.

[0240] In this embodiment, step S702 is optional. That is, the target access network device can determine the first REDCAP information based on the REDCAP indication information sent by the target access and mobility management network element, or it can determine the first REDCAP information independently.

[0241] S704, after determining the first REDCAP information, the target access network device sends the first REDCAP information to the target access and mobility management network element. Correspondingly, the target access and mobility management network element receives the first REDCAP information.

[0242] In steps S705-S706, the target access and mobility management network element sends a second request message to the unified data management network element. Based on the request from the target access and mobility management network element, the unified data management network element returns second REDCAP information or the subscription information of the terminal device to the target access and mobility management network element.

[0243] For example, the content of the second request message here can be the same as the content of the second request message described above. For details, please refer to the description of steps S402 and S403 in method 400, which will not be repeated here.

[0244] S707, the target access and mobility management network element determines whether to allow the terminal device to use the service corresponding to the first REDCAP information based on the first REDCAP information and the second REDCAP information.

[0245] This step is the same as S330, and you can refer to S330.

[0246] Optionally, the method may further include:

[0247] S708a, the target access and mobility management network element sends a first indication information to the source access and mobility management network element. The first indication information is used to disallow the terminal device from using the service corresponding to the first REDCAP information. Accordingly, the source access and mobility management network element receives the first indication information.

[0248] If, in S707, the target access and mobility management network element determines that the terminal device is not allowed to use the service corresponding to the first REDCAP information, then it can send the first instruction information to the terminal device.

[0249] For example, the first indication information may include a reason value indicating the reason why the terminal device was rejected. For instance, the reason value may indicate that the terminal device has not subscribed to REDACP access technology. Or, the reason value may indicate that the terminal device is illegally / unauthorized to use the services of the first service type. Optionally, the method may further include one or more of the following steps:

[0250] S709a, the source access and mobility management network element sends a handover failure message to the source access network device. Correspondingly, the source access network device receives this handover failure message. This handover failure message indicates that the handover has failed.

[0251] S710a, the source access network device may reselect the target access network device or trigger the terminal device to update its wireless capability information based on the handover failure information.

[0252] Optionally, the method may further include:

[0253] In step S708b, the target access and mobility management network element sends a second indication information to the source access and mobility management network element. This second indication information indicates that the terminal device is permitted to use the service corresponding to the first REDCAP information. Correspondingly, the source access and mobility management network element receives the second indication information.

[0254] If, in S707, the target access and mobility management network element determines that the terminal device is permitted to use the service corresponding to the first REDCAP information, then a second instruction information can be sent to the source access and mobility management network element.

[0255] It should be understood that S708a and 708b can be implemented either.

[0256] According to the communication method provided in this application, during the inter-system handover process, the target access and mobility management network element can obtain the first REDCAP information. After obtaining the REDCAP information subscribed to by the terminal device (i.e., the second REDCAP information), it can verify the first REDCAP information to determine whether the terminal device can use the service corresponding to the first REDCAP information. This helps to ensure that the terminal device can only use its corresponding service. Figure 8 This is a schematic flowchart of a communication method provided in this application. The method 800 is an example where the first network element is a target access network device in the second network during the handover process from a first network to a second network by a terminal device. The first network can be a 4G or LTE network, and the second network can be a 5G or NR network, but this application does not limit this.

[0257] For ease of understanding and description, the access network devices in the second network will be referred to as "target access network devices," and the access network devices in the first network will be referred to as "source access network devices." The access and mobility management network elements in the second network will be referred to as "target access and mobility management network elements," and the access network devices in the first network will be referred to as "source access and mobility management network elements." For example, the target access network device can be the gNB shown in the figure, and the source access network device can be the eNB shown in the figure; the target access and mobility management network element can be the AMF shown in the figure, and the source and target access and mobility management network elements can be the MME shown in the figure.

[0258] S801~S803 are the same as S801~S803, and can be referred to as S801~S803.

[0259] S804, the target access network device sends a first request message to the target access and mobility management network element.

[0260] For example, the content of the first request message here can be the same as the content of the first request message described above. For details, please refer to the description of steps S402 and S403 in method 400, which will not be repeated here.

[0261] In steps S805-S806, the target access and mobility management network element sends a second request message to the unified data management network element to request second REDCAP information or the subscription information of the terminal device. Based on the request from the target access and mobility management network element, the unified data management network element returns the second REDCAP information or the subscription information of the terminal device to the target access and mobility management network element.

[0262] It should be understood that the content of the first request message and the second request message may be the same, but this application does not limit this. For example, if the first request message includes the fourth instruction information, the second request message may not include the fourth instruction information.

[0263] It should be noted that step S804 is optional. In one approach, after the target access and mobility management network element (MACN) determines that the terminal device is undergoing an inter-system handover, the MACN may request second REDCAP information or the terminal device's subscription information from the unified data management network element (UDN). In another approach, after receiving the first request message from the target access network device, the MACN then requests second REDCAP information or the terminal device's subscription information from the UDN.

[0264] S807, the target access and mobility management network element sends the second REDCAP information or the subscription information of the terminal device to the target access network device. Correspondingly, the target access network device receives the second REDCAP information or the subscription information of the terminal device. The subscription information of the terminal device includes the second REDCAP information.

[0265] S808, the target access network device determines whether to allow the terminal device to use the service corresponding to the first REDCAP information based on the first REDCAP information and the second REDCAP information.

[0266] This step is the same as S330, and you can refer to S330.

[0267] It should be understood that S805~S808 are similar to S403~S406, and S403~S406 can be referenced.

[0268] Optionally, the method may further include:

[0269] S809a, the target access network device sends a handover rejection message to the source access network device.

[0270] If, in S808, the target access network device determines that it does not allow the terminal device to communicate with the target access network device, it can send a handover rejection message to the source access network device.

[0271] Optionally, the method may further include:

[0272] S810a, the source access network device sends a first indication message to the terminal device, the first indication message indicating that the terminal device is not allowed to use the service corresponding to the first REDCAP information. Accordingly, the terminal device receives the first indication message.

[0273] After receiving a handover rejection message, the source access network device can send a first indication message to the terminal device, indicating that the terminal device is not allowed to use the service corresponding to the first REDCAP information.

[0274] For example, the first indication information may include a reason value indicating the reason why the terminal device is rejected. For instance, the reason value indicates that the terminal device has not subscribed to the REDACP access technology. For instance, the reason value indicates that the terminal device is illegally / unauthorized to use the first service type. S811a, the source access network device performs a reselection of the target access network device or triggers the terminal device to update its radio capability information based on the handover rejection message.

[0275] It should be understood that either S810a or S811a can be implemented.

[0276] Optionally, the method may further include:

[0277] S809b: The target access network device sends a handover execution message to the source access network device.

[0278] If, in S808, the target access network device determines that it allows the terminal device to communicate with the target access network device, then a handover execution message can be sent to the source access network device.

[0279] In step S810b, the source access network device sends a second indication message to the terminal device. The second indication message indicates that the terminal device is permitted to use the service corresponding to the first REDCAP information. Accordingly, the terminal device receives the second indication message.

[0280] After receiving the handover execution message, the source access network device can know that the target access network device allows the terminal device to use the service corresponding to the first REDCAP information, and thus can send the second instruction information to the terminal device.

[0281] According to the communication method provided in this application, during inter-system handover, the target access network device can obtain first REDCAP information. After obtaining the REDCAP information subscribed to by the terminal device (i.e., second REDCAP information), it can verify the first REDCAP information to determine whether the terminal device can use the service corresponding to the first REDCAP information. This helps ensure that the terminal device can only use its corresponding service. Optionally, the second REDCAP information is also used to indicate service characteristic information corresponding to the at least one service type. For example, when indicating the REDCAP access technology and at least one service type, the second REDCAP information can also indicate the service characteristic information corresponding to the at least one service type. For example, the service characteristic information may be mobility information and / or energy-saving requirements, etc.

[0282] In method 400, when the access network device determines that the terminal device is allowed to use the service corresponding to the first REDCAP information, the access network device can also obtain the service feature information corresponding to the first service type based on the second REDCAP information.

[0283] In method 500, when the access and mobility management network element determines that the terminal device is allowed to use the service corresponding to the first REDCAP information, the access and mobility management network element can also obtain the service feature information corresponding to the first service type based on the second REDCAP information, and can send the service feature information corresponding to the first service type to the access network device.

[0284] In method 600, when the session management network element determines that the terminal device is allowed to use the service corresponding to the first REDCAP information, the session management network element can also obtain the service feature information corresponding to the first service type based on the second REDCAP information, and can send the service feature information corresponding to the first service type to the access network device.

[0285] Optionally, as an embodiment of this application, after the access network device obtains the service characteristic information corresponding to the first service type or after the access network device learns the service type of the terminal device, the access network device may send third indication information to the terminal device. The third indication information is used to indicate one or more of the following:

[0286] The terminal device saves the timing advance (TA) value used during the current RRC connection establishment process and uses it during the next RRC connection establishment; or,

[0287] The terminal device reduces the frequency of neighbor cell measurements; or,

[0288] The terminal device saves the transmit power used during the establishment of this RRC connection and uses it during the establishment of the next RRC connection.

[0289] For example, when the service characteristic information corresponding to the first service type is the fixed location of the terminal device or the terminal device is used in a video surveillance scenario, the access network device can send third instruction information.

[0290] Optionally, as an embodiment of this application, after the access network device obtains the service characteristic information or service type corresponding to the first service type, the access network device may send broadcast information. This broadcast information includes REDCAP access technology indication information and optimization indication information. The optimization information indicates whether a terminal device using the first wireless access technology should enable optimization functions according to the optimization indication information. The optimization functions include one or more of the following:

[0291] Save the timing advance (TA) value used during this RRC connection establishment process and use it in the next RRC connection establishment; or,

[0292] Reduce the frequency of neighbor cell measurements; or,

[0293] Save the transmit power used during this RRC connection establishment process and use it during the next RRC connection establishment.

[0294] For example, when the service characteristic information corresponding to the first service type is the fixed location of the terminal device or the terminal device is used in a video surveillance scenario, the access network device can send broadcast information.

[0295] It should be understood that the explanations or descriptions of the various terms appearing in the embodiments of this application can be referenced or interpreted in each embodiment, and are not limited thereto.

[0296] It should also be understood that, in the various embodiments of this application, the sequence numbers of the above processes do not imply the order of execution; the execution order of each process should be determined by its function and internal logic. The various numerical numbers or sequence numbers involved in the above processes are merely for descriptive convenience and should not constitute any limitation on the implementation process of the embodiments of this application.

[0297] In addition, the method described above mainly involves REDCAP technology, but it should be understood that this method can also be extended to other technologies, such as 6G or 6.5G technology.

[0298] The above text combined Figures 3 to 8 The method provided in this application has been described, and the apparatus provided in this application will now be described.

[0299] Figure 9This is a schematic block diagram of the communication device provided in this application. Figure 9 As shown, the communication device 2000 may include a transceiver unit 2100 and a processing unit 2200.

[0300] The transceiver unit 2100 may include a transmitting unit and / or a receiving unit. The transceiver unit 2100 may be a transceiver (including a transmitter and / or receiver), an input / output interface (including input and / or output interfaces), pins, or circuitry, etc. The transceiver unit 2100 can be used to perform the transmitting and / or receiving steps in the above method embodiments. The processing unit 2200 may be a processor (may include one or more), a processing circuit with processor functions, etc., and can be used to perform other steps in the above method embodiments besides transmitting and receiving.

[0301] Optionally, the communication device may further include a storage unit, which may be a memory, an internal storage unit (e.g., a register, a cache, etc.), or an external storage unit (e.g., a read-only memory, a random access memory, etc.). The storage unit is used to store instructions, and the processing unit 2200 executes the instructions stored in the storage unit to cause the communication device to perform the aforementioned method.

[0302] In one design, the communication device 2000 may correspond to the first network element in the above method embodiments, such as the first network element in method 300, the access network device in method 400, the access and mobility management network element in method 500, the session management network element in method 600, the target access and mobility management network element in method 700, or the target access network device in method 800, and may perform the operations performed by the first network element.

[0303] Specifically, the transceiver unit 2100 is used to acquire first REDCAP information from the terminal device and second REDCAP information subscribed by the terminal device; the processing unit 2200 is used to determine, based on the first REDCAP information and the second REDCAP information, whether to allow the terminal device to use the service corresponding to the first REDCAP information.

[0304] Optionally, the first REDCAP information is used to indicate the REDCAP access technology, and the second REDCAP information is used to indicate whether the terminal device has subscribed to the REDCAP access technology.

[0305] Optionally, the first REDCAP information is used to indicate the REDCAP access technology and the first service type, wherein the access technology used by the first service type is the REDCAP access technology, and the second REDCAP information is used to indicate the REDCAP access technology and at least one service type, wherein the access technology used by the at least one service type is the REDCAP access technology.

[0306] Optionally, the first REDCAP information is used to indicate a first type of REDCAP access technology, and the second REDCAP information is used to indicate at least one type of REDCAP access technology, with different types of REDCAP access technologies corresponding to different service types.

[0307] Optionally, the transceiver unit 2100 is further configured to send a first indication information to the terminal device, the first indication information being used to indicate that the terminal device cannot use the service corresponding to the first REDCAP information.

[0308] Optionally, the first indication information includes a reason value, which indicates the reason why the terminal device was rejected.

[0309] Optionally, the device 2000 is an access network device.

[0310] Optionally, the transceiver unit 2100 is specifically configured to receive a Radio Resource Control (RRC) message from the terminal device, the RRC message including the first REDCAP information.

[0311] Optionally, the transceiver unit 2100 is specifically used to receive wireless capability information from the terminal device; the processing unit 2200 is specifically used to determine the first REDCAP information based on the wireless capability information.

[0312] Optionally, the transceiver unit 2100 is specifically configured to receive a first message from an access and mobility management network element, the first message including the first REDCAP information.

[0313] Optionally, the transceiver unit 2100 is specifically configured to receive radio capability information of the terminal device from the access and mobility management network element; the processing unit 2200 is specifically configured to determine the first REDCAP information based on the radio capability information.

[0314] Optionally, the device 2000 is an access network device in the second network during the process of the terminal device switching from the first network to the second network.

[0315] Optionally, the transceiver unit 2100 is specifically used to receive the wireless capability information of the terminal device from the access network device in the first network; the transceiver unit 2200 is specifically used to determine the first REDCAP information based on the wireless capability information.

[0316] Optionally, the transceiver unit 2100 is further configured to receive REDCAP indication information sent from the access and mobility management network element in the second network, wherein the REDCAP indication information is used to instruct the device 2000 to determine the first REDCAP information based on the radio capability information.

[0317] Optionally, the transceiver unit is further configured to: send request information to the access and mobility management network element based on the first REDCAP information, wherein the request information is used to request the access and mobility management network element to obtain the second REDCAP information from the unified data management network element; and receive the second REDCAP information from the access and mobility management network element.

[0318] Optionally, the device 2000 is an access and mobility management network element.

[0319] Optionally, the transceiver unit 2100 is specifically configured to receive a NAS message from the terminal device, the NAS message including the first REDCAP information; or, receive the first REDCAP information from the access network device.

[0320] Optionally, the transceiver unit 2100 is further configured to send the wireless capability information of the terminal device to the access network device, wherein the wireless capability information is used by the access network device to determine the first REDCAP information.

[0321] Optionally, the device 2000 is an access and mobility management network element in the second network during the handover process of the terminal device from the first network to the second network.

[0322] Optionally, the transceiver unit 2100 is specifically configured to receive the first REDCAP information from the access network device in the second network, wherein the first REDCAP information is determined by the access network device in the second network based on the wireless capability information of the terminal device from the access network device in the first network.

[0323] Optionally, the transceiver unit 2100 is further configured to send REDCAP indication information to the access network device in the second network, the REDCAP indication information being used to instruct the access network device in the second network to determine the first REDCAP information based on the radio capability information.

[0324] Optionally, the device 2000 is a session management network element.

[0325] Optionally, the transceiver unit 2100 is specifically used to receive the first REDCAP information from the access and mobility management network element.

[0326] Optionally, the transceiver unit 2100 is specifically configured to: send request information to the unified data management network element based on the first REDCAP information, wherein the request information is used to request the second REDCAP information; and receive the second REDCAP information from the unified data management network element.

[0327] Optionally, the second REDCAP information is also used to indicate the service characteristic information corresponding to the at least one service type.

[0328] Optionally, the transceiver unit 2100 is further configured to send third indication information to the terminal device, the third indication information being used to indicate one or more of the following: the terminal device saves the timing advance (TA) value used during the current RRC connection establishment process and uses it during the next RRC connection establishment; or, the terminal device reduces the frequency when performing neighbor cell measurements; or, the terminal device saves the transmit power used during the current RRC connection establishment process and uses it during the next RRC connection establishment.

[0329] Optionally, the transceiver unit 2100 is further configured to transmit broadcast information, the broadcast information including REDCAP access technology indication information and optimization indication information, the optimization information indicating whether a terminal device whose access technology is REDCAP access technology should enable optimization function according to the optimization indication information, the optimization function including one or more of the following: saving the timing advance value (TA) used in the current RRC connection establishment process and using it in the next RRC connection establishment; or reducing the frequency when performing neighbor cell measurement; or saving the transmit power used in the current RRC connection establishment process and using it in the next RRC connection establishment.

[0330] It should be understood that the transceiver unit 2100 and the processing unit 2200 can also perform other operations performed by the corresponding first network element in the above-mentioned corresponding methods, which will not be described in detail here.

[0331] In another design, the communication device 2000 can correspond to the terminal device in the above method embodiments and can perform the operations performed by the terminal device.

[0332] Specifically, the transceiver unit 2100 is configured to: send first REDCAP information; receive indication information from a first network element, wherein the indication information is used to indicate whether the device 2000 is allowed to use the service corresponding to the first REDCAP information; the transceiver unit 2100 is further configured to: send adjusted REDCAP information according to the indication information, wherein the adjusted REDCAP information is different from the first REDCAP information.

[0333] Optionally, the first network element is an access network device.

[0334] Optionally, the transceiver unit 2100 is further configured to receive third indication information from the first network element, the third indication information being used to indicate one or more of the following: the device 2000 saves the timing advance (TA) value used during the current RRC connection establishment process and uses it during the next RRC connection establishment; or, the device 2000 reduces the frequency when performing neighbor cell measurements; or, the device 2000 saves the transmit power used during the current RRC connection establishment process and uses it during the next RRC connection establishment.

[0335] Optionally, the transceiver unit 2100 is further configured to receive broadcast information from the first network element, the broadcast information including REDCAP access technology indication information and optimization indication information, the optimization information indicating whether the device 2000, whose access technology is REDCAP access technology, should enable the optimization function according to the optimization indication information, the optimization function including one or more of the following: saving the timing advance value (TA) used in the current RRC connection establishment process and using it in the next RRC connection establishment; or reducing the frequency when performing neighbor cell measurements; or saving the transmit power used in the current RRC connection establishment process and using it in the next RRC connection establishment.

[0336] It should be understood that the transceiver unit 2100 and the processing unit 2200 can also perform other operations performed by the terminal device in the above method embodiments, which will not be described in detail here.

[0337] In another design, the communication device 2000 can correspond to the unified data management network element in the above method embodiments, and can perform the operations performed by the unified data management network element.

[0338] It should be understood that the above division of units is only a functional division, and there may be other division methods in actual implementation.

[0339] It should also be understood that the above processing unit can be implemented in hardware, software, or a combination of both.

[0340] It should also be understood that when the communication device 2000 is an access network device, the transceiver unit 2100 in the communication device can correspond to Figure 10 The RRU 3100 in the access network device 2000 shown in the figure, the processing unit 2200 in the communication device can correspond to Figure 10 The BBU 3200 in the access network device 2000 shown is illustrated. When the communication device 2000 is a chip configured in the access network device, the transceiver unit 2100 in the communication device can be an input / output interface.

[0341] It should also be understood that when the communication device 2000 is a terminal device, the transceiver unit 2100 in the communication device 2000 can correspond to Figure 11 The transceiver 4002 in the terminal device 4000 shown in the diagram, and the processing unit 2200 in the communication device 2000 may correspond to Figure 11 The processor 4001 in the terminal device 4000 shown in the figure.

[0342] Figure 10 This is a structural schematic diagram of the access network device provided in the embodiments of this application, such as a structural schematic diagram of a base station. The access network device 3000 can implement the functions of the access network device in the above method embodiments.

[0343] As shown in the figure, the access network device 3000 may include one or more radio frequency units, such as a remote radio unit (RRU) 3100 and one or more baseband units (BBUs) (also referred to as distributed units (DUs)) 3200. The RRU 3100 may be referred to as a transceiver unit or communication unit, and... Figure 9 The corresponding transceiver unit 2100 in the middle.

[0344] Optionally, the transceiver unit 3100 can also be referred to as a transceiver, transceiver circuit, or transceiver, etc., and may include at least one antenna 3101 and a radio frequency unit 3102. Optionally, the transceiver unit 3100 may include a receiving unit and a transmitting unit, whereby the receiving unit may correspond to a receiver (or receiver circuit), and the transmitting unit may correspond to a transmitter (or transmitter circuit). The RRU 3100 is mainly used for transmitting and receiving radio frequency signals and converting radio frequency signals to baseband signals. The BBU 3200 is mainly used for baseband processing and base station control, etc. The RRU 3100 and BBU 3200 may be physically installed together or physically separated, i.e., a distributed base station.

[0345] The BBU 3200 is the control center of the base station, also known as the processing unit, and can communicate with... Figure 9The processing unit 2200 in the above-mentioned method is mainly used to complete baseband processing functions, such as channel coding, multiplexing, modulation, spreading, etc. For example, the BBU (processing unit) can be used to control the base station to execute the operation process of the access network equipment in the above-mentioned method embodiment.

[0346] In one example, the BBU 3200 can be composed of one or more single boards. Multiple boards can collectively support a single access standard wireless access network (such as an LTE network), or they can each support different access standards wireless access networks (such as LTE, 5G, or other networks). The BBU 3200 also includes a memory 3201 and a processor 3202. The memory 3201 is used to store necessary instructions and data. The processor 3202 is used to control the base station to perform necessary actions, such as controlling the base station to execute the operation procedures related to the access network device in the above method embodiments. The memory 3201 and processor 3202 can serve one or more single boards. That is, each single board can have its own memory and processor, or multiple single boards can share the same memory and processor. Furthermore, each single board can also have necessary circuitry.

[0347] It should be understood that Figure 10 The access network device 3000 shown can implement the various processes involved in the access network device in the foregoing method embodiments. The operation or function of each module in the access network device 3000 is to implement the corresponding processes in the above method embodiments. For details, please refer to the description in the above method embodiments; to avoid repetition, detailed descriptions are appropriately omitted here.

[0348] The BBU 3200 described above can be used to perform the actions implemented internally by the access network device as described in the preceding method embodiments, while the RRU 3100 can be used to perform the transmission and reception actions of the access network device as described in the preceding method embodiments. Please refer to the descriptions in the preceding method embodiments for details, which will not be repeated here.

[0349] Figure 11 This is a schematic diagram of the structure of a terminal 4000 provided in an embodiment of this application. As shown in the figure, the terminal 4000 includes a processor 4001 and a transceiver 4002. Optionally, the terminal 4000 may also include a memory 4003. The processor 4001, transceiver 4002, and memory 4003 can communicate with each other through internal connection paths to transmit control and / or data signals. The memory 4003 is used to store computer programs, and the processor 4001 is used to call and run the computer program from the memory 4003 to control the transceiver 4002 to send and receive signals.

[0350] The processor 4001 and memory 4003 described above can be combined into a processing device 4004. The processor 4001 executes the program code stored in the memory 4003 to achieve the above functions. It should be understood that the processing device 4004 shown in the figure is only an example. In a specific implementation, the memory 4003 may also be integrated into the processor 4001 or independent of the processor 4001. This application does not limit this.

[0351] The aforementioned terminal 4000 may also include an antenna 4010 for transmitting uplink data or uplink control signaling output by transceiver 4002 via wireless signals.

[0352] It should be understood that Figure 11 The terminal 4000 shown can realize the functions that the terminal device involved in the foregoing method embodiments can realize. The operation or function of each module in the terminal 4000 is to implement the corresponding process in the above method embodiments. For details, please refer to the description in the above method embodiments. To avoid repetition, detailed descriptions are appropriately omitted here.

[0353] Optionally, the terminal 4000 may also include a power supply 4005 for providing power to various devices or circuits in the terminal.

[0354] In addition, to make the terminal more functional, the terminal 4000 may also include one or more of the following: an input unit 4006, a display unit 4007, an audio circuit 4008, a camera 4009, and a sensor 4011. The audio circuit may also include a speaker 40081, a microphone 40082, etc.

[0355] It should be understood that the processing device 4004 or processor 4001 can be a chip. For example, the processing device 4004 or processor 4001 can be a field-programmable gate array (FPGA), a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an off-the-shelf FPGA, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, a system-on-chip (SoC), a central processing unit (CPU), a network processor (NP), a digital signal processing circuit (DSP), a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips. A general-purpose processor can be a microprocessor or any conventional processor. The steps of the method 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 module can reside in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. This 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.

[0356] The memory in this application (such as memory 4003) 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 dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0357] Figure 12 This is a schematic block diagram of a communication device 5000 provided in an embodiment of this application. Any network element involved in this application, such as access network equipment, first network element, terminal device, etc., can be provided by... Figure 12 The communication device shown is used to achieve this.

[0358] It should be understood that the communication device 5000 can be a physical device, a component of a physical device (e.g., an integrated circuit, a chip, etc.), or a functional module within a physical device.

[0359] like Figure 12As shown, the communication device 5000 includes one or more processors 5001. The processor 5001 can store execution instructions for performing the methods of the embodiments of this application. Optionally, the processor 5001 can call an interface to implement receiving and transmitting functions. The interface can be a logical interface or a physical interface, without limitation. For example, the interface can be a transceiver circuit or an interface circuit. The transceiver circuit or interface circuit used to implement receiving and transmitting functions can be separate or integrated together. The aforementioned transceiver circuit or interface circuit can be used for reading and writing code / data, or it can be used for transmitting or relaying signals.

[0360] Optionally, the interface can be implemented using a transceiver. Optionally, the communication device 5000 may also include a transceiver 5003. The transceiver 5003 may be referred to as a transceiver unit, transceiver, transceiver circuit, or transceiver, etc., and is used to implement transceiver functions.

[0361] Optionally, the communication device 5000 may further include a memory 5002. This application embodiment does not specifically limit the deployment location of the memory 5002; the memory may be integrated into the processor or may be independent of the processor. In the case where the communication device 5000 does not include a memory, the communication device 5000 only needs to have processing capabilities, and the memory can be deployed in other locations (e.g., a cloud system).

[0362] The processor 5001, memory 5002 and transceiver 5003 communicate with each other through internal connection paths to transmit control and / or data signals.

[0363] It is understood that, although not shown, the communication device 5000 may also include other devices, such as input devices, output devices, batteries, etc.

[0364] Optionally, in some embodiments, the memory 5002 may store execution instructions for performing the methods of the embodiments of this application. The processor 5001 may execute the instructions stored in the memory 5002 in conjunction with other hardware (e.g., transceiver 5003) to complete the steps of the method execution shown herein. For specific working processes and beneficial effects, please refer to the description in the method embodiments herein.

[0365] The methods disclosed in the embodiments of this application can be applied to, or implemented by, processor 5003. Processor 5003 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the method can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The aforementioned processor 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 manifested as execution by a hardware decoding processor, or execution by a combination of hardware and software modules in the decoding processor. The software module can reside in a mature storage medium in the field, such as random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory, electrically erasable programmable memory, or registers. This storage medium is located in memory, and the processor reads instructions from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0366] According to the method provided in the embodiments of this application, this application also provides a computer program product, which includes: computer program code, which, when run on a computer, causes the computer to execute the method of any network element (e.g., access network device, first network element, terminal device, or unified data management network element) in any of the aforementioned method embodiments.

[0367] According to the method provided in the embodiments of this application, this application also provides a computer-readable medium storing program code, which, when run on a computer, causes the computer to perform the method of any network element in any of the foregoing method embodiments.

[0368] According to the method provided in the embodiments of this application, this application also provides a system that includes one or more of the following: an access network device, a session management network element, an access and mobility management network element, or a unified data management network element.

[0369] This application also provides a processing apparatus, including a processor and an interface; the processor is used to execute the method in any of the above method embodiments.

[0370] It should be understood that the aforementioned processing device can be a chip. For example, the processing device can be a field-programmable gate array (FPGA), a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, a system on-chip (SoC), a central processing unit (CPU), a network processor (NP), a digital signal processing circuit (DSP), a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips. It can implement or execute the various 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 module can reside in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. This 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.

[0371] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

[0372] The terms “component,” “module,” “system,” etc., used in this specification are used to refer to computer-related entities, hardware, firmware, combinations of hardware and software, software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program, or a computer. As illustrated, applications running on computing devices and computing devices can both be components. One or more components may reside in a process or execution thread, and components may be located on a single computer or distributed among two or more computers. Furthermore, these components can be executed from various computer-readable media on which various data structures are stored. Components can communicate, for example, via local or remote processes based on signals having one or more data packets (e.g., data from two components interacting with another component between a local system, a distributed system, or a network, such as the Internet interacting with other systems via signals).

[0373] It should be understood that the term "embodiment" used throughout this specification means that a specific feature, structure, or characteristic related to an embodiment is included in at least one embodiment of this application. Therefore, various embodiments throughout this specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments.

[0374] It should be understood that in the embodiments of this application, the designations "first", "second", etc. are only for distinguishing different objects, such as different network devices, and do not constitute a limitation on the scope of the embodiments of this application. The embodiments of this application are not limited thereto.

[0375] It should also be understood that in this application, “when…”, “if” and “if” all refer to the network element making a corresponding processing under certain objective circumstances, and are not time-limited, nor do they require the network element to make a judgment when it is implemented, nor do they mean that there are other limitations.

[0376] It should also be understood that in this application, "at least one" means one or more, and "more than one" means two or more.

[0377] It should also be understood that in the embodiments of this application, "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information.

[0378] It should also be understood that the term "and / or" in this article is merely a description of 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 article generally indicates that the preceding and following related objects have an "or" relationship.

[0379] In this application, expressions such as "the item includes one or more of the following: A, B, and C" generally mean, unless otherwise specified, that the item can be any one of the following: A; B; C; A and B; A and C; B and C; A, B and C; A and A; A, A and A; A, A and B; A, A and C, A, B and B; A, C and C; B and B, B, B and B, B, B and C, C and C; C, C and C, and other combinations of A, B, and C. The above example uses three elements, A, B, and C, to illustrate the possible entries for the item. When expressed as "the item includes at least one of the following: A, B, ..., and X," that is, when the expression contains more elements, then the applicable entries for the item can also be obtained according to the aforementioned rules.

[0380] 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.

[0381] 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.

[0382] 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.

[0383] 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.

[0384] 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.

[0385] 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.

[0386] 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 communication method, characterized in that, include: The first network element obtains the first low-capability REDCAP information from the terminal device; The first network element obtains the second REDCAP information signed by the terminal device; The first network element determines, based on the first REDCAP information and the second REDCAP information, whether to allow the terminal device to use the service corresponding to the first REDCAP information, wherein... The first REDCAP information is used to indicate the REDCAP access technology and a first service type, wherein the first service type uses the REDCAP access technology. The second REDCAP information is used to indicate the REDCAP access technology and at least one service type, wherein the at least one service type uses the REDCAP access technology. or, The first REDCAP information is used to indicate a first type of REDCAP access technology, and the second REDCAP information is used to indicate at least one type of REDCAP access technology. Different types of REDCAP access technologies correspond to different service types.

2. The method as described in claim 1, characterized in that, The method further includes: The first network element sends a first indication message to the terminal device, the first indication message being used to indicate that the terminal device is not allowed to use the service corresponding to the first REDCAP information.

3. The method as described in claim 2, characterized in that, The first indication information includes a reason value, which indicates the reason why the terminal device was rejected.

4. The method according to any one of claims 1 to 3, characterized in that, The first network element is an access network device.

5. The method as described in claim 4, characterized in that, The first network element acquires first REDCAP information from the terminal device, including: The first network element receives a Radio Resource Control (RRC) message from the terminal device, the RRC message including the first REDCAP information; or, The first network element receives radio capability information from the terminal device and determines the first REDCAP information based on the radio capability information; or, The first network element receives a first message from the access and mobility management network element, the first message including the first REDCAP information; or, The first network element receives radio capability information of the terminal device from the access and mobility management network element, and determines the first REDCAP information based on the radio capability information.

6. The method according to any one of claims 1 to 3, characterized in that, The first network element is the access network device in the second network during the process of the terminal device switching from the first network to the second network.

7. The method as described in claim 6, characterized in that, The first network element acquires first REDCAP information from the terminal device, including: The first network element receives wireless capability information of the terminal device from the access network equipment in the first network. The first network element determines the first REDCAP information based on the wireless capability information.

8. The method as described in claim 7, characterized in that, Before the first network element determines the first REDCAP information based on the radio capability information, the method further includes: The first network element receives REDCAP indication information sent from the access and mobility management network element in the second network. The REDCAP indication information is used to instruct the first network element to determine the first REDCAP information based on the radio capability information.

9. The method as described in claim 6, characterized in that, The first network element obtains the second REDCAP information subscribed by the terminal device, including: The first network element sends a request message to the access and mobility management network element based on the first REDCAP information. The request message is used to request the access and mobility management network element to obtain the second REDCAP information from the unified data management network element. The first network element receives the second REDCAP information from the access and mobility management network element.

10. The method according to any one of claims 1 to 3, characterized in that, The first network element is the access and mobility management network element.

11. The method as described in claim 10, characterized in that, The first network element acquires first REDCAP information from the terminal device, including: The first network element receives a NAS message from the terminal device, the NAS message including the first REDCAP information; or, The first network element receives the first REDCAP information from the access network device.

12. The method as described in claim 11, characterized in that, Before the first network element receives the first REDCAP information from the access network device, the method further includes: The first network element sends the wireless capability information of the terminal device to the access network device, and the wireless capability information is used by the access network device to determine the first REDCAP information.

13. The method according to any one of claims 1 to 3, characterized in that, The first network element is the access and mobility management network element in the second network during the process of the terminal device switching from the first network to the second network.

14. The method as described in claim 13, characterized in that, The first network element acquires first REDCAP information from the terminal device, including: The first network element receives the first REDCAP information from the access network device in the second network. The first REDCAP information is determined by the access network device in the second network based on the wireless capability information of the terminal device from the access network device in the first network.

15. The method as described in claim 14, characterized in that, Before the first network element receives the first REDCAP information from the access network device in the second network, the method further includes: The first network element sends REDCAP indication information to the access network device in the second network. The REDCAP indication information is used to instruct the access network device in the second network to determine the first REDCAP information based on the radio capability information.

16. The method according to any one of claims 1 to 3, characterized in that, The first network element is the session management network element.

17. The method as described in claim 16, characterized in that, The first network element acquires first REDCAP information from the terminal device, including: The first network element receives the first REDCAP information from the access and mobility management network element.

18. The method as described in claim 14, characterized in that, The first network element obtains the second REDCAP information signed by the terminal device, including: The first network element sends a request message to the unified data management network element based on the first REDCAP information, the request message being used to request the second REDCAP information; The first network element receives the second REDCAP information from the unified data management network element.

19. The method as described in claim 1, characterized in that, The second REDCAP information is also used to indicate the service characteristic information corresponding to the at least one service type.

20. The method as described in claim 4, characterized in that, The method further includes: The first network element sends a third indication message to the terminal device, the third indication message being used to indicate one or more of the following: The terminal device saves the timing advance (TA) value used during the current Radio Resource Control (RRC) connection establishment process and uses it during the next RRC connection establishment; or... The terminal device reduces the frequency of neighbor cell measurements; or... The terminal device saves the transmit power used during the establishment of this RRC connection and uses it during the establishment of the next RRC connection.

21. The method as described in claim 4, characterized in that, The method further includes: The first network element sends broadcast information, which includes REDCAP access technology indication information and optimization indication information. The optimization indication information indicates whether a terminal device using REDCAP access technology should enable optimization functions according to the optimization indication information. The optimization functions include one or more of the following: Save the timing advance (TA) value used during the current Radio Resource Control (RRC) connection establishment process and use it during the next RRC connection establishment; or... Reduce the frequency of neighbor cell measurements; or, Save the transmit power used during this RRC connection establishment process and use it during the next RRC connection establishment.

22. A communication method, characterized in that, include: The terminal device sends the first low-capability REDCAP information; The terminal device receives an indication message from a first network element based on the first REDCAP information and the second REDCAP information subscribed by the terminal device. The indication message indicates whether the terminal device is allowed to use the service corresponding to the first REDCAP information. The first REDCAP information is used to indicate the REDCAP access technology and a first service type, wherein the access technology used by the first service type is the REDCAP access technology. The second REDCAP information is used to indicate the REDCAP access technology and at least one service type, wherein the at least one service type uses the REDCAP access technology. or, The first REDCAP information is used to indicate a first type of REDCAP access technology, and the second REDCAP information is used to indicate at least one type of REDCAP access technology. Different types of REDCAP access technologies correspond to different service types.

23. The method as described in claim 22, characterized in that, The method further includes: The terminal device sends adjusted REDCAP information according to the instruction information, and the adjusted REDCAP information is different from the first REDCAP information.

24. The method as described in claim 22 or 23, characterized in that, The first network element is an access network device.

25. The method as described in claim 24, characterized in that, The method further includes: The terminal device receives third indication information from the first network element, the third indication information being used to indicate one or more of the following: The terminal device saves the timing advance (TA) value used during the current Radio Resource Control (RRC) connection establishment process and uses it during the next RRC connection establishment; or... The terminal device reduces the frequency of neighbor cell measurements; or... The terminal device saves the transmit power used during the establishment of this RRC connection and uses it during the establishment of the next RRC connection.

26. The method as described in claim 24, characterized in that, The method further includes: The terminal device receives broadcast information from the first network element. The broadcast information includes REDCAP access technology indication information and optimization indication information. The optimization indication information indicates whether the terminal device using REDCAP access technology should enable optimization functions according to the optimization indication information. The optimization functions include one or more of the following: Save the timing advance (TA) value used during the current Radio Resource Control (RRC) connection establishment process and use it during the next RRC connection establishment; or... Reduce the frequency of neighbor cell measurements; or, Save the transmit power used during this RRC connection establishment process and use it during the next RRC connection establishment.

27. A communication system, characterized in that, include: First network element and second network element; The second network element sends the terminal device's first low capability REDCAP information to the first network element; The first network element obtains the second REDCAP information subscribed by the terminal device based on the first REDCAP information; The first network element determines, based on the first REDCAP information and the second REDCAP information, whether to allow the terminal device to use the service corresponding to the first REDCAP information, wherein... The first REDCAP information is used to indicate the REDCAP access technology and a first service type, wherein the first service type uses the REDCAP access technology. The second REDCAP information is used to indicate the REDCAP access technology and at least one service type, wherein the at least one service type uses the REDCAP access technology. or, The first REDCAP information is used to indicate a first type of REDCAP access technology, and the second REDCAP information is used to indicate at least one type of REDCAP access technology. Different types of REDCAP access technologies correspond to different service types.

28. The system as claimed in claim 27, characterized in that, The second network element is an access and mobility management network element, and the first network element is an access network device; or, The second network element is an access network device, and the first network element is an access and mobility management network element; or, The second network element is an access and mobility management network element, and the first network element is a session management network element; or, The second network element is the access network device in the first network during the process of the terminal device switching from the first network to the second network, and the first network element is the access network device in the second network.

29. The system as described in claim 27 or 28, characterized in that, The system also includes a unified data management network element; And, the first network element obtains the second REDCAP information based on the first REDCAP information, including: The first network element obtains the second REDCAP information from the unified data management network element based on the first REDCAP information.

30. A communication device, characterized in that, Includes units for implementing the method as described in any one of claims 1 to 21.

31. A communication device, characterized in that, Includes units for implementing the method as described in any one of claims 22 to 26.

32. A communication device, characterized in that, include: A processor coupled to a memory for storing a program or instructions which, when executed by the processor, cause the apparatus to perform the method as claimed in any one of claims 1 to 21, or the method as claimed in any one of claims 22 to 26.

33. A readable storage medium having a computer program or instructions stored thereon, characterized in that, When the computer program or instructions are executed, they cause the computer to perform the method as described in any one of claims 1 to 21, or the method as described in any one of claims 22 to 26.

34. A computer program product, characterized in that, Includes computer program instructions that cause a computer to perform: the method as claimed in any one of claims 1 to 21, or the method as claimed in any one of claims 22 to 26.

Images