Communication method and related apparatus
The target reader role of the terminal device is determined through the access network device, which solves the problem of low communication reliability of IoT terminal devices and realizes efficient data transmission in the environment energy-enabled IoT architecture.
Patent Information
- Application Number
- PCT/CN2024/095359
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-27
- Filing Date
- 2024-05-25
- Publication Date
- 2024-12-05
AI Technical Summary
When the IoT terminal device is a reader, the communication reliability is low, especially in the environment energy-enabled IoT architecture, it is difficult for the terminal device to effectively determine and execute the target reader role, resulting in poor data transmission quality.
Determine the target reader role of the terminal device through the access network device, obtain its authorized reader role, and select the most suitable target reading from the authorized reader role based on factors such as the capability information and link status of the terminal device, and select the most suitable target reading from the authorized reader role based on factors such as the capability information and link status of the terminal device. to improve communication reliability.
It improves the communication reliability of IoT terminal devices, ensures the quality and reliability of data transmission, and is suitable for environmental energy-enabled terminal devices in IoT architectures.
Smart Images

Figure CN2024095359_05122024_PF_FP_ABST
Abstract
Description
Communication method and related device
[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on May 27, 2023, with application number 202310613361.2, and priority to the Chinese patent application entitled “Communication Methods and Related Devices,” all contents of which are incorporated by reference into this application. Technical Field
[0002] The present application relates to the field of communication technology, and in particular to a communication method and related devices. Background Art
[0003] The Internet of Things (IoT) stands for "the Internet of Everything." One type of IoT network is the Ambient Power-enabled Internet of Things (AmbientIoT or A-IoT). The Ambient Power-enabled IoT architecture can include passive, semi-passive, semi-active, and active terminals, readers, and servers. Passive, semi-passive, semi-active, and active terminals are ultra-low-power terminal devices that can extract energy from the environment to maintain normal operation. For example, the radio electromagnetic waves transmitted by the reader (which can be a carrier signal) can serve as the energy source and carrier signal for the passive, semi-passive, semi-active, and active terminals. Passive, semi-passive, semi-active, and active terminals transmit data by backscattering the carrier signal transmitted by the reader. The server is used to send instructions, such as data read or data write instructions, to enable the reader to communicate with the passive, semi-passive, semi-active, and active terminals, thereby achieving the purpose of identifying targets and exchanging data. The reader can be an access network device or a terminal device. Currently, when a terminal device is used as a reader, there may be a problem of low communication reliability.
[0004] Summary of the Invention
[0005] The present application provides a communication method and related devices, which can improve communication reliability.
[0006] In a first aspect, the present application provides a communication method performed by a communication device, which may be an access network device or a module within the access network device. In this method, the access network device determines a target reader role for a terminal device and sends first information to the terminal device. The first information instructs the terminal device to perform the target reader role.
[0007] In the present application, the access network device can indicate the target reader role to the terminal device according to the communication requirements, so that the terminal device can perform the target reader role, which is beneficial to the reliability of communication.
[0008] In a possible implementation, determining the target reader role of the terminal device includes:
[0009] Obtaining one or more reader roles authorized for the terminal device;
[0010] A target reader role of the terminal device is determined from the authorized one or more reader roles.
[0011] In this implementation, the access network device may first obtain the authorized reader role of the terminal device, and then determine the target reader role from the authorized reader roles, which is beneficial to improving communication reliability.
[0012] In a possible implementation, obtaining one or more reader roles authorized for the terminal device includes:
[0013] One or more reader roles authorized for the terminal device are received from the first core network device.
[0014] In this implementation, the first core network device can determine one or more authorized reader roles for the terminal device based on the terminal device's capability information and / or its subscription data, and send this information to the access network device. This network-side approach, combining the terminal device's capability information and subscription data to determine the authorized reader role to implement the target reader role, better meets actual needs.
[0015] In a possible implementation, obtaining one or more reader roles authorized for the terminal device includes:
[0016] Determining one or more reader roles authorized for the terminal device according to second information; the second information includes one or more of the following information: capability information of the terminal device and / or subscription data of the terminal device;
[0017] The capability information of the terminal device indicates the reader roles supported by the terminal device, and the contract data of the terminal device indicates the reader roles that the terminal device is allowed to serve as.
[0018] In this implementation, the access network device itself can determine one or more reader roles authorized for the terminal device based on the second information. This is easy to implement, enhances the diversity of the solution implementation, and has high applicability.
[0019] In one possible implementation, the method further includes:
[0020] The one or more reader roles authorized for the terminal device are sent to the first core network device, so that the first core network device sends the one or more reader roles authorized for the terminal device to the terminal device.
[0021] In this implementation, when the access network device determines the authorized reader role, the access network device can send the terminal device's authorized reader role to the access network device for subsequent transmission to the terminal device. Once the terminal device learns its authorized reader role, it can send a first request message to the access network device, requesting to be assigned the first reader role. Consequently, the access network device can subsequently determine the target reader role based on the first request message, resulting in high applicability.
[0022] In one possible implementation, the method further includes:
[0023] Acquire third information; the third information includes one or more of the following information: capability information of the terminal device, a first request message from the terminal device, a link status between the access network device and the Internet of Things terminal, or a wireless resource status of the access network device; wherein the capability information of the terminal device indicates a reader role supported by the terminal device, and the first request message is used to request to serve as the first reader role;
[0024] The determining the target reader role of the terminal device from the one or more authorized reader roles includes:
[0025] The target reader role is determined from the one or more authorized reader roles according to the third information.
[0026] Under this implementation mode, the access network device can specifically determine the target reader role from the authorized reader roles based on the third information (such as link status, wireless resource status), which is more in line with communication requirements, improves the accuracy of the determined target reader role, and thus improves the reliability of communication.
[0027] In a possible implementation, determining the target reader role of the terminal device from the one or more authorized reader roles according to the third information includes:
[0028] determining the reader role supported by the terminal device indicated by the capability information of the terminal device among the one or more authorized reader roles as the target reader role; or,
[0029] determining the first reader role among the one or more authorized reader roles as the target reader role; or,
[0030] When the uplink budget between the access network device and the Internet of Things terminal is lower than the downlink budget, and the authorized one or more reader roles include an uplink auxiliary reader, determining the target reader role as an uplink auxiliary reader; or,
[0031] When a downlink budget between the access network device and the Internet of Things terminal is lower than an uplink budget, and the authorized one or more reader roles include a downlink auxiliary reader, the target reader role is determined to be a downlink auxiliary reader.
[0032] Under this implementation, when the downlink quality of the IoT terminal is poor and the IoT terminal cannot successfully receive downlink data directly through the access network device, if the target reader role that the terminal device can perform is an auxiliary reader or a downlink auxiliary reader, then the access network device can first send the downlink data of the IoT terminal to the terminal device, and the terminal device forwards the downlink data to the IoT terminal at a closer distance, thereby ensuring the quality of the downlink transmission. Alternatively, when the uplink quality of the IoT terminal is poor and the IoT terminal cannot successfully send uplink data to the access network device directly through the access network device, if the target reader role that the terminal device can perform is an auxiliary reader or an uplink auxiliary reader, then the IoT terminal can first send the uplink data of the IoT terminal to the terminal device at a closer distance, and the terminal device forwards the uplink data to the access network device, thereby ensuring the quality of the uplink transmission.
[0033] In a possible implementation, determining the target reader role of the terminal device includes:
[0034] Acquire fourth information; the fourth information includes one or more of the following information: capability information of the terminal device, subscription data of the terminal device, a first request message from the terminal device, a link status between the access network device and the Internet of Things terminal, or a wireless resource status of the access network device; wherein the capability information of the terminal device indicates a reader role supported by the terminal device, and the first request message is used to request to serve as the first reader role;
[0035] The target reader role is determined according to the fourth information.
[0036] In this implementation manner, the access network device can directly determine the target reader role based on the fourth information, which has strong operability.
[0037] In one possible implementation, the method further includes:
[0038] receiving capability information of the terminal device sent by a first core network device, where the first core network device supports Internet of Things service management; or
[0039] Receive capability information of the terminal device sent by the terminal device.
[0040] In this implementation, the terminal device can send / forward / transparently transmit the terminal device's capability information to the first core network device (e.g., AMF) via the access network device. The first core network device then sends the parsed terminal device capability information to the access network device, which is beneficial for forward compatibility of the protocol. Alternatively, the terminal device can directly send the terminal device capability information to the access network device, increasing the diversity of the solution implementation.
[0041] In a possible implementation, the receiving capability information of the terminal device sent by the first core network device includes:
[0042] During the registration process, a context request or a terminal device capability check request sent by the first core network device is received, where the context request or the terminal device capability check request includes capability information of the terminal device.
[0043] Under this implementation method, when the capability information of the terminal device is sent by the first core network device to the access network device, the capability information of the terminal device can be carried in an existing message, such as a context request (such as a context establishment request, a context modification request) or a terminal device capability check request, thereby improving the applicability of the solution.
[0044] In one possible implementation, the method further includes:
[0045] receiving first indication information from the terminal device, where the first indication information indicates that the terminal device supports an Internet of Things service;
[0046] A first core network device that supports the management of the Internet of Things service is selected according to the first indication information.
[0047] In this implementation mode, the terminal device can send a first indication message to the access network device so that the access network device selects a first core network device (such as AMF) that supports the management of the Internet of Things service based on the first indication information.
[0048] In one possible implementation, the method further includes:
[0049] When the first cell accessed by the terminal device supports the Internet of Things service, the first core network device is selected according to the first cell accessed by the terminal device, and the first core network device supports the management of the Internet of Things service.
[0050] In one possible implementation, the method further includes:
[0051] Broadcast second indication information, wherein the second indication information indicates that the first cell supports the Internet of Things service, or the second indication information indicates that one or more cells of the access network device support the Internet of Things service, so that the terminal device accesses the first cell supporting the Internet of Things service according to the second indication information, and the one or more cells include the first cell.
[0052] In one possible implementation, the method further includes:
[0053] Send resource configuration information to the terminal device, where the resource configuration information includes one or more of the following information: frequency information, frequency band information, transmission power, transmission bandwidth, transmission rate, or execution duration; the resource configuration information is used by the terminal device to perform the target reader role.
[0054] In a possible implementation, after sending the first information to the terminal device, the method further includes:
[0055] Fifth information is received from the terminal device, where the fifth information indicates whether the terminal device accepts to perform the target reader role.
[0056] In this implementation, after the terminal device receives the first information indicating the target reader role, the terminal device may also feed back to the access network device whether the fifth information indicating whether the target reader role is accepted, thereby improving the integrity of the solution.
[0057] In a possible implementation, the target reader role or the one or more reader roles authorized by the terminal device include the following roles: auxiliary reader, uplink auxiliary reader, downlink auxiliary reader, reader, or reader providing carrier assistance.
[0058] In one possible implementation, the first core network device includes an access management device, a tag management device, an environmental energy acquisition Internet of Things management device, a unified data management device, a user data storage device, a network capability exposure device, a policy control device, or a session management device.
[0059] In a second aspect, the present application provides a communication method performed by a communication device, which may be a terminal device or a module within the terminal device. In this method, the terminal device sends a first request message to an access network device, the first request message being used to request a first reader role; and the terminal device receives first information from the access network device, the first information instructing the terminal device to perform a target reader role.
[0060] In one possible implementation, the method further includes:
[0061] Receiving one or more reader roles authorized for the terminal device from the first core network device;
[0062] The first reader role is determined according to one or more reader roles authorized for the terminal device.
[0063] In one possible implementation, the method further includes:
[0064] The capability information of the terminal device is sent to the access network device, where the capability information of the terminal device indicates reader capabilities supported by the terminal device, and the capability information of the terminal device is used to determine the target reader role.
[0065] In one possible implementation, the method further includes:
[0066] A first indication message is sent to the access network device, where the first indication message indicates that the terminal device supports the Internet of Things service; the first indication message is used to determine the first core network device that supports the management of the Internet of Things service.
[0067] In a possible implementation, the cell accessed by the terminal device is a second cell, and the second cell does not support the Internet of Things service;
[0068] The method further comprises:
[0069] receiving second indication information from the access network device, where the second indication information indicates that the first cell supports the Internet of Things service, or the second indication information indicates that one or more cells of the access network device support the Internet of Things service, where the one or more cells include the first cell;
[0070] Perform cell reselection or cell switching according to the second indication information to access the first cell.
[0071] In this implementation, the second indication information may be carried in the system information broadcast. The terminal device may select to access a cell supporting the Internet of Things service (eg, the first cell) according to the Internet of Things service supported broadcast by the access network device.
[0072] In a possible implementation, the cell accessed by the terminal device is a second cell of the access network device, and the second cell does not support the Internet of Things service;
[0073] The method further comprises:
[0074] Receiving at least one cell identifier from the first core network device, where the cell corresponding to the at least one cell identifier is a cell supporting the Internet of Things service under the access network device, and the cell corresponding to the at least one cell identifier includes the first cell;
[0075] Perform cell reselection or cell handover according to the at least one cell identifier to access the first cell.
[0076] In this implementation mode, the terminal device can reselect / choose / switch to a cell supporting the Internet of Things service (for example, the first cell) from the cells supporting the Internet of Things service sent by the first core network device.
[0077] In a possible implementation, the cell accessed by the terminal device is a second cell, and all cells under the access network device where the second cell is located do not support the Internet of Things service;
[0078] The method further comprises:
[0079] Receiving at least one cell identifier from the first core network device, where the cell corresponding to the at least one cell identifier is a cell supporting the Internet of Things service under the access network device, and the cell corresponding to the at least one cell identifier includes the first cell;
[0080] Perform cell reselection or cell handover according to the at least one cell identifier to access the first cell.
[0081] In one possible implementation, the method further includes:
[0082] Receive resource configuration information from the access network device, the resource configuration information including one or more of the following information: frequency information, frequency band information, transmission power, transmission bandwidth, transmission rate, or execution duration; the resource configuration information is used by the terminal device to execute the target reader role.
[0083] In a possible implementation, after receiving the first information from the access network device, the method further includes:
[0084] Sending fifth information to the access network device, where the fifth information indicates whether the terminal device accepts to execute the target reader role.
[0085] In a possible implementation, the target reader role or the one or more reader roles authorized by the terminal device include the following roles: auxiliary reader, uplink auxiliary reader, downlink auxiliary reader, reader, or reader providing carrier assistance.
[0086] In one possible implementation, the first core network device includes an access management device, a tag management device, an environmental energy acquisition Internet of Things management device, a unified data management device, a user data storage device, a network capability exposure device, a policy control device, or a session management device.
[0087] In a third aspect, the present application provides a communication method performed by a communication device, which may be a first core network device or a module within the first core network device. In the method, the first core network device obtains one or more reader roles authorized for a terminal device; the first core network device sends the one or more authorized reader roles to the terminal device; and the one or more authorized reader roles are used to determine a target reader role.
[0088] In a possible implementation, obtaining one or more reader roles authorized by the terminal device includes:
[0089] Determine one or more reader roles authorized for the terminal device based on the capability information of the terminal device and / or the contract data of the terminal device, where the capability information of the terminal device indicates the reader capabilities supported by the terminal device, and the contract data of the terminal device indicates the reader roles that the terminal device is allowed to serve.
[0090] In one possible implementation, the method further includes:
[0091] Sending one or more reader roles authorized for the terminal device to the access network device.
[0092] In a possible implementation, obtaining one or more reader roles authorized by the terminal device includes:
[0093] Receive one or more reader roles authorized for the terminal device from the access network device.
[0094] In a possible implementation, before receiving the one or more reader roles authorized for the terminal device from the access network device, the method further includes:
[0095] Send the capability information of the terminal device to the access network device.
[0096] In one possible implementation, the method further includes:
[0097] The capability information is received from the terminal device.
[0098] In one possible implementation, the method further includes:
[0099] At least one cell identifier is sent to the terminal device, where the cell corresponding to the at least one cell identifier includes a first cell, and the cell corresponding to the at least one cell identifier is a cell that supports the Internet of Things service. The at least one cell identifier is used for cell reselection or cell switching to facilitate the terminal device to access the first cell.
[0100] In a possible implementation, the first core network device is a first core network device that supports the Internet of Things service.
[0101] In a possible implementation, the target reader role or the one or more reader roles authorized by the terminal device include the following roles: auxiliary reader, uplink auxiliary reader, downlink auxiliary reader, reader, or reader providing carrier assistance.
[0102] In one possible implementation, the first core network device includes an access management device, a tag management device, an environmental energy acquisition Internet of Things management device, a unified data management device, a user data storage device, a network capability exposure device, a policy control device, or a session management device.
[0103] In a fourth aspect, the present application provides a communication method performed by a communication device, which may be a first core network device or a module within the first core network device. In the method, the first core network device obtains one or more reader roles authorized for a terminal device; the first core network device sends the one or more reader roles authorized for the terminal device to an access network device; and the one or more authorized reader roles are used to determine a target reader role.
[0104] In a possible implementation, obtaining one or more reader roles authorized by the terminal device includes:
[0105] Determine one or more reader roles authorized for the terminal device based on the capability information of the terminal device and / or the contract data of the terminal device, where the capability information of the terminal device indicates the reader capabilities supported by the terminal device, and the contract data of the terminal device indicates the reader roles that the terminal device is allowed to serve.
[0106] In one possible implementation, the method further includes:
[0107] The capability information is received from the terminal device.
[0108] In one possible implementation, the method further includes:
[0109] Receive the subscription data of the terminal device from the second core network device.
[0110] In one possible implementation, the method further includes:
[0111] One or more reader roles authorized for the terminal device are sent to the terminal device.
[0112] In one possible implementation, the method further includes:
[0113] At least one cell identifier is sent to the terminal device, where the cell corresponding to the at least one cell identifier includes a first cell, and the cell corresponding to the at least one cell identifier is a cell that supports the Internet of Things service. The at least one cell identifier is used for cell reselection or cell switching to facilitate the terminal device to access the first cell.
[0114] In a possible implementation, the first core network device is a first core network device that supports the Internet of Things service.
[0115] In a possible implementation, the target reader role or the one or more reader roles authorized by the terminal device include the following roles: auxiliary reader, uplink auxiliary reader, downlink auxiliary reader, reader, or reader providing carrier assistance.
[0116] In one possible implementation, the first core network device includes an access management device, a tag management device, an environmental energy acquisition Internet of Things management device, a unified data management device, a user data storage device, a network capability exposure device, a policy control device, or a session management device.
[0117] In one possible implementation, the second core network device includes a unified data management device, a user data storage device, a network capability exposure device, a policy control device, a session management device, a tag management device, an environmental energy enabling Internet of Things device, an environmental energy acquisition Internet of Things terminal management device or an authentication service device.
[0118] In a fifth aspect, the present application provides a communication device, which may be an access network device or a module in the access network device. The communication device includes:
[0119] a processing unit, configured to determine a target reader role of the terminal device;
[0120] The transceiver unit is configured to send first information to the terminal device, wherein the first information instructs the terminal device to perform the target reader role.
[0121] In a possible implementation, when determining the target reader role of the terminal device, the processing unit is configured to:
[0122] Obtaining one or more reader roles authorized for the terminal device;
[0123] A target reader role of the terminal device is determined from the authorized one or more reader roles.
[0124] In a possible implementation, when obtaining one or more reader roles authorized for the terminal device, the processing unit:
[0125] The one or more reader roles authorized for the terminal device are received from the first core network device through the transceiver unit.
[0126] In a possible implementation, when obtaining the one or more reader roles authorized for the terminal device, the processing unit is configured to:
[0127] Determining one or more reader roles authorized for the terminal device according to second information; the second information includes one or more of the following information: capability information of the terminal device and / or subscription data of the terminal device;
[0128] The capability information of the terminal device indicates the reader roles supported by the terminal device, and the contract data of the terminal device indicates the reader roles that the terminal device is allowed to serve as.
[0129] In a possible implementation, the transceiver unit is configured to:
[0130] The one or more reader roles authorized for the terminal device are sent to the first core network device, so that the first core network device sends the one or more reader roles authorized for the terminal device to the terminal device.
[0131] In a possible implementation, the processing unit is configured to:
[0132] Acquire third information; the third information includes one or more of the following information: capability information of the terminal device, a first request message from the terminal device, a link status between the access network device and the Internet of Things terminal, or a wireless resource status of the access network device; wherein the capability information of the terminal device indicates a reader role supported by the terminal device, and the first request message is used to request to serve as the first reader role;
[0133] The target reader role is determined from the one or more authorized reader roles according to the third information.
[0134] In a possible implementation, when determining the target reader role of the terminal device from the one or more authorized reader roles according to the third information, the processing unit is configured to:
[0135] determining the reader role supported by the terminal device indicated by the capability information of the terminal device among the one or more authorized reader roles as the target reader role; or,
[0136] determining the first reader role among the one or more authorized reader roles as the target reader role; or,
[0137] When the uplink budget between the access network device and the Internet of Things terminal is lower than the downlink budget, and the authorized one or more reader roles include an uplink auxiliary reader, determining the target reader role as an uplink auxiliary reader; or,
[0138] When a downlink budget between the access network device and the Internet of Things terminal is lower than an uplink budget, and the authorized one or more reader roles include a downlink auxiliary reader, the target reader role is determined to be a downlink auxiliary reader.
[0139] In a possible implementation, when determining the target reader role of the terminal device, the processing unit is configured to:
[0140] Acquire fourth information; the fourth information includes one or more of the following information: capability information of the terminal device, subscription data of the terminal device, a first request message from the terminal device, a link status between the access network device and the Internet of Things terminal, or a wireless resource status of the access network device; wherein the capability information of the terminal device indicates a reader role supported by the terminal device, and the first request message is used to request to serve as the first reader role;
[0141] The target reader role is determined according to the fourth information.
[0142] In a possible implementation, the transceiver unit is configured to:
[0143] receiving capability information of the terminal device sent by a first core network device, where the first core network device supports Internet of Things service management; or
[0144] Receive capability information of the terminal device sent by the terminal device.
[0145] In a possible implementation, when receiving the capability information of the terminal device sent by the first core network device, the transceiver unit is configured to:
[0146] During the registration process, a context request or a terminal device capability check request sent by the first core network device is received, where the context request or the terminal device capability check request includes capability information of the terminal device.
[0147] In a possible implementation, the transceiver unit is further configured to receive first indication information from the terminal device, where the first indication information indicates that the terminal device supports an Internet of Things service;
[0148] The processing unit is further used to select a first core network device that supports the management of the Internet of Things service based on the first indication information.
[0149] In a possible implementation, the processing unit is configured to:
[0150] When the first cell accessed by the terminal device supports the Internet of Things service, the first core network device is selected according to the first cell accessed by the terminal device, and the first core network device supports the management of the Internet of Things service.
[0151] In a possible implementation, the transceiver unit is configured to:
[0152] Broadcast second indication information, wherein the second indication information indicates that the first cell supports the Internet of Things service, or the second indication information indicates that one or more cells of the access network device support the Internet of Things service, so that the terminal device accesses the first cell supporting the Internet of Things service according to the second indication information, and the one or more cells include the first cell.
[0153] In a possible implementation, the transceiver unit is configured to:
[0154] Send resource configuration information to the terminal device, where the resource configuration information includes one or more of the following information: frequency information, frequency band information, transmission power, transmission bandwidth, transmission rate, or execution duration; the resource configuration information is used by the terminal device to perform the target reader role.
[0155] In a possible implementation, after sending the first information to the terminal device, the transceiver unit is further configured to:
[0156] Fifth information is received from the terminal device, where the fifth information indicates whether the terminal device accepts to perform the target reader role.
[0157] In a possible implementation, the target reader role or the one or more reader roles authorized by the terminal device include the following roles: auxiliary reader, uplink auxiliary reader, downlink auxiliary reader, reader, or reader providing carrier assistance.
[0158] In one possible implementation, the first core network device includes an access management device, a tag management device, an environmental energy acquisition Internet of Things management device, a unified data management device, a user data storage device, a network capability exposure device, a policy control device, or a session management device.
[0159] In a sixth aspect, the present application provides a communication device, which may be a terminal device or a module in a terminal device. The communication device includes:
[0160] A transceiver unit, configured to send a first request message to the access network device, wherein the first request message is used to request to serve as a first reader role;
[0161] The transceiver unit is configured to receive first information from an access network device, where the first information instructs the terminal device to perform a target reader role.
[0162] In a possible implementation, the transceiver unit is further configured to receive one or more reader roles authorized for the terminal device from the first core network device;
[0163] The processing unit is further configured to determine the first reader role according to one or more reader roles authorized for the terminal device.
[0164] In a possible implementation, the transceiver unit is configured to:
[0165] The capability information of the terminal device is sent to the access network device, where the capability information of the terminal device indicates reader capabilities supported by the terminal device, and the capability information of the terminal device is used to determine the target reader role.
[0166] In a possible implementation, the transceiver unit is configured to:
[0167] A first indication message is sent to the access network device, where the first indication message indicates that the terminal device supports the Internet of Things service; the first indication message is used to determine the first core network device that supports the management of the Internet of Things service.
[0168] In a possible implementation, the cell accessed by the terminal device is a second cell, and the second cell does not support the Internet of Things service;
[0169] The transceiver unit is further configured to receive second indication information from the access network device, where the second indication information indicates that the first cell supports the Internet of Things service, or the second indication information indicates that one or more cells of the access network device support the Internet of Things service, where the one or more cells include the first cell;
[0170] The processing unit is further configured to perform cell reselection or cell switching according to the second indication information to access the first cell.
[0171] In a possible implementation, the cell accessed by the terminal device is a second cell of the access network device, and the second cell does not support the Internet of Things service;
[0172] The transceiver unit is further configured to:
[0173] Receiving at least one cell identifier from the first core network device, where the cell corresponding to the at least one cell identifier is a cell supporting the Internet of Things service under the access network device, and the cell corresponding to the at least one cell identifier includes the first cell;
[0174] Perform cell reselection or cell handover according to the at least one cell identifier to access the first cell.
[0175] In a possible implementation, the cell accessed by the terminal device is a second cell, and all cells under the access network device where the second cell is located do not support the Internet of Things service;
[0176] The processing unit is further configured to receive at least one cell identifier from the first core network device, where the cell corresponding to the at least one cell identifier is a cell supporting the Internet of Things service under the access network device, and the cell corresponding to the at least one cell identifier includes the first cell;
[0177] The processing unit is further configured to perform cell reselection or cell handover according to the at least one cell identifier to access the first cell.
[0178] In a possible implementation, the transceiver unit is further configured to:
[0179] Receive resource configuration information from the access network device, the resource configuration information including one or more of the following information: frequency information, frequency band information, transmission power, transmission bandwidth, transmission rate, or execution duration; the resource configuration information is used by the terminal device to execute the target reader role.
[0180] In a possible implementation, after receiving the first information from the access network device, the transceiver unit is further configured to:
[0181] Sending fifth information to the access network device, where the fifth information indicates whether the terminal device accepts to execute the target reader role.
[0182] In a possible implementation, the target reader role or the one or more reader roles authorized by the terminal device include the following roles: auxiliary reader, uplink auxiliary reader, downlink auxiliary reader, reader, or reader providing carrier assistance.
[0183] In one possible implementation, the first core network device includes an access management device, a tag management device, an environmental energy acquisition Internet of Things management device, a unified data management device, a user data storage device, a network capability exposure device, a policy control device, or a session management device.
[0184] In a seventh aspect, the present application provides a communication device, which may be a first core network device or a module in the first core network device. The communication device includes:
[0185] A processing unit, configured to obtain one or more reader roles authorized by the terminal device;
[0186] The transceiver unit is configured to send one or more reader roles authorized by the terminal device to the terminal device; the one or more authorized reader roles are used to determine a target reader role.
[0187] In a possible implementation, when acquiring the one or more reader roles authorized by the terminal device, the processing unit is configured to:
[0188] Determine one or more reader roles authorized for the terminal device based on the capability information of the terminal device and / or the contract data of the terminal device, where the capability information of the terminal device indicates the reader capabilities supported by the terminal device, and the contract data of the terminal device indicates the reader roles that the terminal device is allowed to serve.
[0189] In a possible implementation, the transceiver unit is configured to:
[0190] Sending one or more reader roles authorized for the terminal device to the access network device.
[0191] In a possible implementation, the acquiring of one or more reader roles authorized by the terminal device, the processing unit is configured to:
[0192] The transceiver unit receives one or more reader roles authorized for the terminal device from the access network device.
[0193] In a possible implementation, before receiving the one or more reader roles authorized for the terminal device from the access network device, the transceiver unit is configured to:
[0194] Send the capability information of the terminal device to the access network device.
[0195] In a possible implementation, the transceiver unit is configured to:
[0196] The capability information is received from the terminal device.
[0197] In a possible implementation, the transceiver unit is configured to:
[0198] At least one cell identifier is sent to the terminal device, where the cell corresponding to the at least one cell identifier includes a first cell, and the cell corresponding to the at least one cell identifier is a cell that supports the Internet of Things service. The at least one cell identifier is used for cell reselection or cell switching to facilitate the terminal device to access the first cell.
[0199] In a possible implementation, the first core network device is a first core network device that supports the Internet of Things service.
[0200] In a possible implementation, the target reader role or the one or more reader roles authorized by the terminal device include the following roles: auxiliary reader, uplink auxiliary reader, downlink auxiliary reader, reader, or reader providing carrier assistance.
[0201] In one possible implementation, the first core network device includes an access management device, a tag management device, an environmental energy acquisition Internet of Things management device, a unified data management device, a user data storage device, a network capability exposure device, a policy control device, or a session management device.
[0202] In an eighth aspect, the present application provides a communication device, which may be a first core network device or a module in the first core network device. The communication device includes:
[0203] A processing unit, configured to obtain one or more reader roles authorized by the terminal device;
[0204] The transceiver unit is configured to send one or more reader roles authorized for the terminal device to the access network device; the one or more authorized reader roles are used to determine a target reader role.
[0205] In a possible implementation, when acquiring one or more reader roles authorized by the terminal device, the processing unit is configured to:
[0206] Determine one or more reader roles authorized for the terminal device based on the capability information of the terminal device and / or the contract data of the terminal device, where the capability information of the terminal device indicates the reader capabilities supported by the terminal device, and the contract data of the terminal device indicates the reader roles that the terminal device is allowed to serve.
[0207] In a possible implementation, the transceiver unit is further configured to:
[0208] The capability information is received from the terminal device.
[0209] In a possible implementation, the transceiver unit is further configured to:
[0210] Receive the subscription data of the terminal device from the second core network device.
[0211] In a possible implementation, the transceiver unit is further configured to:
[0212] One or more reader roles authorized for the terminal device are sent to the terminal device.
[0213] In a possible implementation, the transceiver unit is further configured to:
[0214] At least one cell identifier is sent to the terminal device, where the cell corresponding to the at least one cell identifier includes a first cell, and the cell corresponding to the at least one cell identifier is a cell that supports the Internet of Things service. The at least one cell identifier is used for cell reselection or cell switching to facilitate the terminal device to access the first cell.
[0215] In a possible implementation, the first core network device is a first core network device that supports the Internet of Things service.
[0216] In a possible implementation, the target reader role or the one or more reader roles authorized by the terminal device include the following roles: auxiliary reader, uplink auxiliary reader, downlink auxiliary reader, reader, or reader providing carrier assistance.
[0217] In one possible implementation, the first core network device includes an access management device, a tag management device, an environmental energy acquisition Internet of Things management device, a unified data management device, a user data storage device, a network capability exposure device, a policy control device, or a session management device.
[0218] In one possible implementation, the second core network device includes a unified data management device, a user data storage device, a network capability exposure device, a policy control device, a session management device, a tag management device, an environmental energy enabling Internet of Things device, an environmental energy acquisition Internet of Things terminal management device or an authentication service device.
[0219] In a ninth aspect, the present application provides a communication device, which includes a processor, and the processor is used to execute a computer program so that the communication device performs the method as described in any one of the first aspect, the second aspect, the third aspect, or the fourth aspect.
[0220] In one possible design, the communication device may be a chip that implements the method in the first aspect, the second aspect, the third aspect, or the fourth aspect, or a device including a chip.
[0221] In one possible design, the communication device further includes a transceiver, and the processor is coupled to the transceiver.
[0222] In one possible design, the communication device further includes a memory. The processor is coupled to the memory, the memory stores a computer program, and the processor is further configured to call the computer program in the memory.
[0223] In the tenth aspect, the present application provides a communication device, which includes a processor and an interface circuit, the interface circuit being used to receive signals from other communication devices outside the communication device and transmit them to the processor or send signals from the processor to other communication devices outside the communication device, and the processor being used to implement a method as described in any one of the first aspect, the second aspect, the third aspect, or the fourth aspect through a logic circuit or executing code instructions.
[0224] In the eleventh aspect, the present application provides a computer-readable storage medium, which stores a computer program or instruction. When the computer program or instruction is executed by a computer, it implements the method as described in any one of the first aspect, the second aspect, the third aspect, or the fourth aspect.
[0225] In a twelfth aspect, the present application provides a computer program product, which, when read and executed by a computer, enables the computer to execute any one of the methods in the first aspect, the second aspect, the third aspect, or the fourth aspect.
[0226] In the thirteenth aspect, the present application provides a communication system, which includes a terminal device and an access network device, the access network device is used to implement the method described in any one of the first aspects above, the terminal device can be used to implement the method described in any one of the second aspects above, and the first core network device is used to implement the method described in any one of the third or fourth aspects above.
[0227] The beneficial effects of the fifth to thirteenth aspects can be referred to the beneficial effects of the first to fourth aspects, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS
[0228] FIG1 is a schematic diagram of the architecture of a communication system used in an embodiment of the present application;
[0229] FIG2 is another schematic diagram of the architecture of a communication system used in an embodiment of the present application;
[0230] FIG3 is a schematic diagram of an architecture of a protocol stack applicable to the present application;
[0231] FIG4 is another schematic diagram of the architecture of the protocol stack applicable to the present application;
[0232] FIG5 is a flow chart of a communication method provided in an embodiment of the present application;
[0233] FIG6 is another flow chart of the communication method provided in an embodiment of the present application;
[0234] FIG7 is another schematic flow chart of a communication method according to an embodiment of the present application;
[0235] FIG8 is another flow chart of a communication method according to an embodiment of the present application;
[0236] FIG9 is a schematic structural diagram of a possible communication device provided in an embodiment of the present application;
[0237] FIG10 is a schematic structural diagram of a possible communication device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0238] The specific embodiments of the present application are further described in detail below with reference to the accompanying drawings.
[0239] The terms "first" and "second" and the like in the specification, claims, and drawings of this application are used to distinguish between different objects, not to describe a particular order. Furthermore, the terms "including" and "having," and any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus comprising a series of steps or elements is not limited to the listed steps or elements, but may optionally include steps or elements not listed, or may optionally include other steps or elements inherent to the process, method, product, or apparatus.
[0240] References herein to "embodiments" mean that a particular feature, structure, or characteristic described in connection with the embodiments may be included in at least one embodiment of the present application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor does it constitute an independent or alternative embodiment that is mutually exclusive of other embodiments. It is understood, both explicitly and implicitly, by those skilled in the art that the embodiments described herein may be combined with other embodiments.
[0241] In the present application, "at least one (item)" refers to one or more, "more than one" refers to two or more, "at least two (items)" refers to two or three and more than three, and "and / or" is used to describe the association relationship of associated objects, indicating that there may be three relationships. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.
[0242] To better understand the embodiments of the present application, the following first introduces the system architecture involved in the embodiments of the present application:
[0243] Please refer to Figure 1, which is a schematic diagram of the architecture of the communication system applied in the embodiment of the present application. As shown in Figure 1, the communication system 1000 includes a (radio) access network ((radio) access network, (R)AN) 100 and a core network (core network, CN) 200. Optionally, the communication system 1000 may also include the Internet 300. RAN 100 includes at least one RAN node (such as 110a and 110b in Figure 1, collectively referred to as 110) and at least one terminal (such as 120a-120j in Figure 1, collectively referred to as 120). RAN 100 may also include other RAN nodes, such as wireless relay equipment and / or wireless backhaul equipment (not shown in Figure 1). The terminal 120 is connected to the RAN node 110 wirelessly. The RAN node 110 is connected to the core network 200 wirelessly or wiredly. The core network device in the core network 200 and the RAN node 110 in the RAN 100 may be different physical devices, or may be the same physical device that integrates core network logical functions and radio access network logical functions.
[0244] The RAN 100 may be a cellular system related to the Third Generation Partnership Project (3GPP), such as a 4G or 5G mobile communication system, or a future-oriented evolutionary system (such as a 6G mobile communication system). The RAN 100 may also be an open access network (O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) system. The RAN 100 may also be a communication system that integrates two or more of the above systems.
[0245] RAN node 110, which can be referred to as access network equipment, RAN entity, or access node, forms part of a communication system and facilitates wireless access for terminals. Multiple RAN nodes 110 in communication system 1000 can be of the same type or different types. In some scenarios, the roles of RAN node 110 and terminal 120 are relative. For example, network element 120i in Figure 1 can be a helicopter or drone, which can be configured as a mobile base station. For terminal 120j accessing RAN 100 via network element 120i, network element 120i is a base station; however, for base station 110a, network element 120i is a terminal. RAN node 110 and terminal 120 are sometimes referred to as communication devices. For example, base stations 110a and 110b in Figure 1 can be understood as communication devices with base station functionality, and terminals 120a-120j can be understood as communication devices with terminal functionality.
[0246] In one possible scenario, a RAN node may be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next generation NodeB (gNB), a next generation base station in a sixth generation (6G) mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system. A RAN node may be a macro base station (such as 110a in FIG1 ), a micro base station or an indoor station (such as 110b in FIG1 ), a relay node or a donor node, or a wireless controller in a CRAN scenario. Optionally, a RAN node may also be a server, a wearable device, a vehicle or an onboard device. For example, an access network device in vehicle to everything (V2X) technology may be a road side unit (RSU). All or part of the functions of the RAN node in this application may also be implemented by software functions running on hardware, or by virtualized functions instantiated on a platform (such as a cloud platform). The RAN node in this application may also be a logical node, a logical module or software that can implement all or part of the RAN node functions.
[0247] In another possible scenario, multiple RAN nodes collaborate to assist the terminal in achieving wireless access, and different RAN nodes respectively implement part of the functions of the base station. For example, the RAN node can be a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). The CU and DU can be set separately, or they can be included in the same network element, such as a baseband unit (BBU). The RU can be included in a radio frequency device or radio frequency unit, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).
[0248] In different systems, CU (or CU-CP and CU-UP), DU or RU may also have different names, but those skilled in the art can understand their meanings. For example, in the ORAN system, CU may also be called O-CU (Open CU), DU may also be called O-DU, CU-CP may also be called O-CU-CP, CU-UP may also be called O-CU-UP, and RU may also be called O-RU. For the convenience of description, this application uses CU, CU-CP, CU-UP, DU and RU as examples for description. Any unit of CU (or CU-CP, CU-UP), DU and RU in this application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.
[0249] A terminal can be referred to as a terminal device, user equipment (UE), mobile station, mobile terminal, mobile equipment (ME), access terminal, subscriber unit, subscriber station, mobile station, remote station, remote terminal, user terminal, wireless communication device, user agent, or user device. Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), the Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearable, smart transportation, and smart city. Terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, and more. Optionally, the terminal can be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a terminal device in a 5G network, or a terminal device in a future evolved public land mobile network (PLMN) or a non-terrestrial network (NTN), etc. It can also be an end device, a logical entity, an intelligent device, such as a mobile phone, an intelligent terminal and other terminal devices, or a server, a gateway, a base station, a controller and other communication equipment.
[0250] The core network may include one or more functional entities (also known as functional network elements, functions, network elements, entities, core network devices, or devices, etc.), such as network slice selection function (NSSF), network exposure function (NEF), network function repository function (NRF), policy control function (PCF), unified data management (UDM), access and mobility management function (AMF), authentication server function / authentication service function (AUSF), session management function (SMF), user data repository (UDR), user plane function (UPF), tag management function (TMF), etc.
[0251] Optionally, the communication system 1000 may include a server, such as a service requester, that is, a server or application function (AF) that issues instructions, or may be called an operation requester or a third party, etc.
[0252] The following is an introduction to the functions of each device:
[0253] The access and mobility management function (which may be referred to as access and mobility management equipment, access and mobility management function entity, access and mobility management function network element, mobile management equipment, access management equipment, mobile management network element, mobile management entity or AMF, etc.) is a type of core network equipment. The device can be used to manage the access control and mobility of the user equipment. In actual applications, it includes the access and mobility management function in the mobility management entity (MME) in the network framework in long term evolution (LTE), and adds access management functions. Specifically, it can be responsible for the registration, mobility management, tracking area update process, reachability detection, selection of session management network element, mobile state transition management, etc. of the user equipment. For example, in 5G, the access and mobility management network element can be an AMF network element. In future communications, such as 6G, the access and mobility management network element can still be an AMF network element, or have other names, which are not limited in this application. When the access and mobility management network element is an AMF network element, the AMF can provide Namf services.
[0254] The tag management function (which may be called a tag management device, IoT management function (IMF), IoT terminal management function, ambient IoT management function (AITMF), ambient IoT management device, ambient IoT function (AIoTF), ambient IoT terminal management function, ambient IoT management function or TMF, etc.) is used to perform functions such as management of IoT terminals (or ambient IoT terminals), IoT terminal data processing, and IoT terminal data routing. It can parse instructions from the service requester (or application function), determine the reader to execute the instructions based on the instructions, instruct the reader to perform IoT terminal operations or instruct the reader to perform the random access process of the IoT terminal; receive data from the IoT terminal through the reader, optionally perform IoT terminal data processing, and send IoT terminal data to the service requester.
[0255] The user plane function (also known as user plane equipment or UPF) is a type of core network equipment. This equipment is responsible for forwarding and receiving user data from user devices. It receives user data from the data network and transmits it to the user device via access network elements. The user plane function network element also receives user data from the user device via access network elements and forwards it to the data network. The transmission resources and scheduling functions provided by the user plane function network element to the user device are managed and controlled by the session management function network element.
[0256] The session management function (which may be called a session management device or SMF, etc.) is a type of core network device. This device can be used to be responsible for the session management of the user equipment (including the establishment, modification and release of the session), the selection and reselection of the user plane function network element, the Internet Protocol (IP) address allocation of the user equipment, and the quality of service (QoS) control. For example, in 5G, the session management network element may be a session management function (SMF) network element. In future communication systems, such as 6G, the session management network element may still be an SMF network element, or have other names, which are not limited in this application. When the session management network element is an SMF network element, the SMF can provide Nsmf services.
[0257] The authentication service function (which may be referred to as an authentication service network element, authentication service device, AUSF, etc.) is used to perform authentication, that is, authentication between the UE and the operator network. After receiving an authentication request initiated by a subscriber, the authentication service function network element may authenticate and / or authorize the subscriber through the authentication information and / or authorization information stored in the unified data management network element, or generate authentication and / or authorization information of the subscriber through the unified data management network element. The authentication service function network element may feedback authentication information and / or authorization information to the subscriber.
[0258] In one possible implementation, the authentication service function network element may be co-located with the unified data management network element. In a 5G communication system, the authentication service function network element may be an authentication server function (AUSF) network element. In future communication systems, the unified data management may still be AUSF, or may have other names, which are not limited in the embodiments of the present application.
[0259] Unified data management function (which may be referred to as a unified data management device, a unified data management network element, a data management device, a unified data management entity or UDM, etc.). Among them, the unified data management network element is used to process terminal device identification, access authentication, registration and mobility management, etc. In a 5G communication system, unified data management can be a UDM or a unified data management device. In future communication systems, unified data management can also be a UDM network element, or it can have other names, which are not limited in the embodiments of this application. The unified data management device can be a core network device. The unified data management device can be a control plane device.
[0260] The user data storage function (also known as user database device, user database entity, user database network element, user data storage device, or UDR) can be understood as the name of the unified data storage network element in the 5G architecture. The user database mainly includes the following functions: access to subscription data, policy data, application data, and other types of data.
[0261] Network exposure function (NEF) (also known as network exposure device, network exposure function entity, network exposure function network element, network capability exposure function entity, network capability exposure function device, network capability exposure function network element, network capability exposure device, etc.) is mainly used to support the exposure of capabilities and events, such as securely opening the services and capabilities provided by 3GPP network functions to the outside world.
[0262] The policy control function (PCF) (which can be called policy control network element, policy control function network element, policy control device, policy control function entity, etc.) is mainly responsible for providing a unified policy framework for network behavior management, providing policy rules for control plane functions, and obtaining registration information related to policy decisions.
[0263] Operation requester (or business requester or third party): can be a server or application function. In the embodiment of the present application, the operation requester can be understood as a device that sends an operation instruction, for example, the operation requester can be a server (server) or an A-IoT server or an application function (AF) or other device that sends an operation instruction. The operation requester can correspond to a certain type of user, and this type of user can include enterprises, tenants, third parties or companies, without restriction. Among them, the operation requester corresponding to a certain type of user can be understood as the operation requester belonging to this type of user and being managed by this type of user.
[0264] The reader interacts with the IoT terminal through a radio frequency signal or a wireless signal. This application uses a tag as an example to illustrate the IoT terminal (or IoT device, or IoT terminal, etc.), but this application is not limited to the device form of the IoT terminal being a tag, and the entire text is as such. It should be understood that this application does not limit the name of the reader. The reader can also be named a reader-writer or other names, that is, it can be understood that the names of the reader and the reader-writer are interchangeable. The reader here has the functions involved in the reader in this application, such as the reader having the function of performing the operations described in this application on the IoT terminal (such as a tag) (such as obtaining tag information, inventory operation, read operation, write operation or invalidation operation or message interaction operation with the tag, etc.), having the function of obtaining billing-related information and / or billing information, and sending billing information to the CHF. In one possible implementation, the reader can send instructions to the IoT terminal (such as a tag) (such as sending instructions to a server or application function or instructions to a core network device), or the reader can send information from the IoT terminal (such as a tag) to the core network device, server or application function. In one possible implementation, a reader can retrieve information stored in a designated IoT terminal (e.g., a tag) based on instructions issued by a core network device or server. For example, in an inventory operation (or perhaps an inventory management operation), the reader retrieves the tag's identification information; this identification information can be the tag's unique identifier or a temporary identifier. For example, in a read operation, the reader reads data from the tag's storage area. Optionally, in some cases where information stored in the tag needs to be rewritten, the reader can also have a write function. For example, in a write operation, the reader writes data to the tag's storage area. Furthermore, the reader can also perform an invalidation operation on the tag. After the invalidation operation is performed, the tag becomes invalid and cannot be used to perform operations such as obtaining tag information, inventory operations, read operations, message exchange operations with the tag, or write operations. In one possible implementation, the inability to obtain tag information after a tag is invalidated can be understood as meaning that after a tag is invalidated, the reader cannot obtain tag information from the invalidated tag. In another possible implementation, the inability to exchange messages with the tag after a tag is invalidated can be understood as meaning that after a tag is invalidated, the reader cannot exchange messages with the invalidated tag. In this application, the reader can be a terminal device such as UE, or an access network device, a pole station, eNodeB, gNodeB, an integrated access and backhaul (IAB) node, etc. This application does not limit the form of the reader.
[0265] The policy control function (also known as the policy control device or PCF) is primarily responsible for providing a unified policy framework for network behavior management, establishing policy rules for control plane functions, and obtaining registration information related to policy decisions. It should be noted that these functional units can operate independently or be combined to implement certain control functions, such as access control and mobility management functions such as terminal device access authentication, security encryption, and location registration, as well as session management functions such as establishing, releasing, and changing user plane transmission paths.
[0266] It should be noted that the core network equipment in this application can execute processes related to the Internet of Things business, such as tag access management, security authentication, instruction transmission, Internet of Things terminal (such as tag) management and other functions. In one possible implementation, the Internet of Things terminal (such as tag) management is performed by enhancing the access management device (such as AMF). In another possible implementation, the Internet of Things terminal (such as tag) management is performed by a new function (such as TMF, AITMF or AIoTF), and the function can be connected to the access network device, which is equivalent to the access network device having an interface with the function; or the function can be connected to the access network device through AMF. At this time, the topological position in the network is equivalent to the existing SMF or PCF. From the deployment point of view, the new function (such as TMF, AITMF or AIoTF) can be co-deployed with AMF.
[0267] It should be noted that the above functional entity is merely a name, and the name itself does not limit the entity. Unless otherwise specified, different descriptions can be interchanged. For example, the session management function may be replaced by "session management function entity" or another name, and the session management function entity may also correspond to an entity that includes other functions in addition to the session management function. For another example, the user plane function may be replaced by "user plane function entity" or another name, and the user plane function entity may also correspond to an entity that includes other functions in addition to the user plane function. This is a unified description here and will not be repeated below.
[0268] It should be noted that in actual deployment, different functions or network elements can be co-located. For example, the access and mobility management network element can be co-located with the session management network element; and the session management network element can be co-located with the user plane network element. When two network elements are co-located, the interaction between the two network elements provided in the embodiments of the present application becomes an internal operation of the co-located network element or can be omitted.
[0269] It should be noted that the message names between network elements or the names of parameters in the messages in the following embodiments of the present application are only examples, and other names may be used in specific implementations. The embodiments of the present application do not make specific limitations on this.
[0270] In this application, "sending information to...(terminal)" can be understood as the destination end of the information being the terminal. This can include sending information to the terminal directly or indirectly. "Receiving information from...(terminal)" or "receiving information from (terminal)..." can be understood as the source end of the information being the terminal, which can include receiving information from the terminal directly or indirectly. The information may be processed as necessary between the source end and the destination end of the information transmission, such as format changes, etc., but the destination end can understand the valid information from the source end. Similar expressions in this application can be understood similarly and will not be repeated here.
[0271] The following is an explanation of the relevant technical features involved in the embodiments of the present application. It should be noted that these explanations are intended to make the embodiments of the present application easier to understand and should not be regarded as limiting the scope of protection claimed by the present application.
[0272] 1. Ambient IoT power-enabled IoT (Ambient IoT or A-IoT)
[0273] A-IoT is also known as the ambient energy harvesting Internet of Things or the passive Internet of Things (P-IoT), that is, some network nodes can be passive, semi-passive, semi-active, or active. Passive and semi-passive terminals can communicate through reflected carriers, that is, they need to rely on an external carrier source to communicate. Passive terminals can have energy storage capacitors or not. If they do not have energy storage capacitors, they need to rely on the external environment to obtain energy for communication, such as radio frequency energy. For semi-passive terminals, they can have power amplifiers, so that the communication distance is improved compared to passive terminals. For semi-passive terminals, they usually have energy storage capacitors, which can store energy in the environment, such as solar energy, radio power, etc. in the capacitors. For active terminals (active devices), they can actively generate carriers (or can be understood as having carrier recovery capabilities). They do not need to rely on external carrier sources for communication, so they can have active communication capabilities. In one possible implementation, they can also have energy storage capacitors and can obtain energy through solar energy, radio frequency, wind energy, hydropower, or tidal energy, with no restrictions on the energy acquisition method. These nodes do not have their own power supply devices or rely on batteries, but instead obtain energy from the environment to support data perception, transmission, and distributed computing. The nodes can also store the energy they obtain. The environmental energy-enabled IoT architecture can include IoT terminals (such as passive, semi-passive, semi-active, and active terminals), readers, servers, and optionally core network equipment. IoT terminals can be in the form of tags or any other terminal form, without restriction. Readers can be access network devices, such as base stations, pole stations, micro base stations, macro stations, relay points (such as integrated access and backhaul nodes (IAB nodes), mobile base stations, etc. Readers can also be terminal devices, such as mobile phones, IoT devices, handheld readers, and other devices.
[0274] 2. Terminal device as reader
[0275] In Ambient IoT, when the terminal device acts as a reader, the reader roles it can perform mainly include the following four types: 1. Reader (the reader in this application refers to a reader that integrates the functions of an auxiliary reader, a downlink auxiliary reader, an uplink auxiliary reader, and a reader that provides carrier assistance, that is, a functionally integrated reader); 2. Downlink auxiliary reader; 3. Uplink auxiliary reader; 4. A reader that provides carrier assistance; 5. Auxiliary reader. In one possible implementation, the downlink auxiliary reader and the uplink auxiliary reader can be collectively referred to as auxiliary readers. Optionally, with the development of communication technology, the reader role may subsequently include other types, which are not limited here. The following is a detailed introduction to the five types of readers based on Figure 2.
[0276] In this application, the reader role can be understood as or replaced by a reader function or a reader type. The execution reader role can be replaced by executing a reader function or acting as a reader.
[0277] For example, the terminal device shown in (a) of FIG2 performs the role of a functionally integrated reader, which can communicate directly with the IoT terminal (i.e., the tag in (a) of FIG2). Under this architecture, the terminal device needs to have a communication protocol stack (such as radio resource control (RRC), medium access control (MAC), and physical (PHY)) with the IoT terminal, as shown in FIG3. At the same time, as a reader, the terminal device also needs to communicate with core network devices such as AMF or TMF (for example, through non-access stratum (NAS) or A-IoT instructions), so that it can interact with the IoT terminal to send downlink data or obtain uplink data according to the instructions of the core network device. Under this architecture, although the access network device (such as the base station) does not need to communicate directly with the IoT terminal, the wireless resources for communication between the terminal device and the IoT terminal are controlled and scheduled by the base station.
[0278] The terminal device shown in Figure 2(b) performs the role of a downlink auxiliary reader, which can assist the downlink communication of the IoT terminal (i.e., the tag in Figure 2(b)). Under this architecture, the terminal device needs to have a communication protocol stack (RRC, MAC, PHY) with the IoT terminal, as shown in Figure 4. This protocol stack is consistent with the protocol stack used for communication between the terminal device and the IoT terminal in Figure 3. The only difference is whether the communication between the terminal device and the network can directly connect to the core network equipment (such as the AMF / TMF in Figure 3) to transmit IoT services (such as supporting the recognition of A-IoT commands) or is responsible for relaying uplink and downlink data under the control of the access network equipment (such as the base station). Therefore, the difference between Figure 2(b) and Figure 2(a) is that the terminal device is only responsible for relaying the downlink data of the IoT terminal; for uplink data, the IoT terminal can send it directly to the base station. This architecture is typically used when the downlink quality of an IoT terminal is poor and the IoT terminal cannot successfully receive downlink data directly from the base station. Instead, the base station can first send the IoT terminal's downlink data to the terminal device, which then forwards the downlink data to the IoT terminal at a closer distance, thus ensuring the quality of downlink transmission. Therefore, the base station can determine whether the terminal device needs to assist in forwarding downlink data based on the current communication quality with the IoT terminal. Core network equipment does not need to participate in transmission path decisions. In this architecture, communication between the terminal device and the IoT terminal is triggered by the base station, and the radio resources used for this communication are controlled and scheduled by the base station.
[0279] The terminal device shown in Figure 2 (c) performs the role of an uplink auxiliary reader, which can assist the uplink communication of the IoT terminal (i.e., the tag in Figure 2 (c)). The only difference between Figure 2 (c) and Figure 2 (b) is that one assists in downlink communication and the other assists in uplink communication. The scenario applicable to Figure 2 (c) is that, contrary to Figure 2 (b), when the uplink quality of the IoT terminal is poor and the IoT terminal cannot successfully send uplink data to the base station directly through the access network device (such as the base station), the uplink data of the IoT terminal can be sent to a terminal device at a closer distance first, and the terminal device forwards the uplink data to the base station, thereby ensuring the quality of the uplink transmission. Under this architecture, the communication protocol stack that the terminal device needs to support, the communication mechanism between the terminal device and the base station and the core network, etc. are all consistent with Figure 2 (b) and will not be repeated here.
[0280] The terminal device shown in Figure 2 (d) performs the role of a reader that provides carrier assistance. It can only assist in providing carriers to the IoT terminal (i.e., the tag in Figure 2 (d)) without participating in the forwarding of uplink or downlink data. In this case, the terminal device does not need to support special communication protocols (i.e., the terminal device does not need to support the RRC, MAC, and PHY protocols for communicating with IoT terminals). It only needs to support the transmission of carriers in a specific frequency band (i.e., as long as the terminal supports communication in a certain frequency band, it supports the carrier provision function that the terminal device needs to perform under this architecture).
[0281] 3. Community selection
[0282] Before a terminal device initiates the registration process to access the network, it must perform network selection and cell selection. The terminal device selects a specific PLMN based on resource configuration information (e.g., a network selection list) and performs cell selection based on cell selection criteria. For example, the terminal device performs measurements required for cell selection (e.g., signal quality), detects and synchronizes to broadcast channels, and receives and processes broadcast messages. For example, a cell broadcasts one or more PLMN IDs in a system message. The terminal device determines the appropriate cell based on the network selection list, signal quality, and other factors.
[0283] 4. Residential areas supporting IoT services
[0284] A cell supporting IoT services (or ambient energy-enabled IoT services, or ambient energy-harvested IoT services) can be an independent logical cell, or a non-independent logical cell, i.e., IoT services and cellular services share a common logical cell. An access network device may have one or more cells, all of which may support IoT services, none of which may support IoT services, or some of which may not support IoT services.
[0285] It should be noted that if an access network device can support multiple cells, some of which support IoT services and some do not, then the access network device has the ability to select the first core network device (such as AMF) that supports IoT services based on A-IoT indication information (such as the first indication information), and process RRC, N2 messages, resource scheduling, etc. related to IoT services.
[0286] It should be noted that if an access network device can support multiple cells, and none of the multiple cells support IoT services, then the access network device does not have the ability to select the first core network device (such as AMF) that supports IoT services based on A-IoT indication information (such as the first indication information), and process RRC, N2 messages, resource scheduling, etc. related to IoT services.
[0287] It should be noted that the N2 message can be understood as a next generation application protocol (NGAP) message.
[0288] 5. AN message (AN meg)
[0289] During the registration process, the AN message may include AN parameters and NAS messages (eg, registration requests). For the access network device, it may parse the AN parameters and forward the NAS registration message.
[0290] This application uses tags as an example to illustrate the Internet of Things terminal (or called Internet of Things device, IoT terminal, etc.), but this application is not limited to the device form of the Internet of Things terminal as a tag, the full text is as follows. The reader performs non-contact two-way data communication through wireless radio frequency, and uses wireless radio frequency to read and write electronic tags or radio frequency cards (Tags), so as to achieve the purpose of identifying targets and exchanging data. It works in two ways. One is that when the tag enters the effective recognition range of the reader, it receives the radio frequency signal emitted by the reader, and uses the energy obtained by the induced current to emit the information stored in the chip (corresponding to passive tags and semi-passive tags); the other is that the tag can store part of the electrical energy through solar energy or other means, so that it can actively send a signal of a certain frequency (this can also be called a semi-active or active tag). The reader receives the information, decodes it, and sends it to the central information system for relevant data processing.
[0291] The communication method and communication device provided by this application are described in detail below:
[0292] Please refer to Figure 5, which is a flow chart of a communication method provided by an embodiment of the present application. As shown in Figure 5, the communication method includes the following steps S500 to S502. The execution subject of the method shown in Figure 5 can be a communication device, or a chip in the communication device. Here, the communication device can specifically be an access network device or a terminal device or a first core network device. Exemplarily, the first core network device can be AMF, UDM, UDR, NEF, PCF, SMF, TMF, AIoTF, AITMF or AUSF, etc. It should be noted that Figure 5 is a schematic flow chart of an embodiment of the method of the present application, showing the detailed communication steps or operations of the method, but these steps or operations are only examples. The embodiment of the present application can also perform other operations or variations of the various operations in Figure 5. In addition, the various steps in Figure 5 can be executed in a different order from that presented in Figure 5, and it is possible that not all operations in Figure 5 need to be executed. Among them:
[0293] S501: The access network device determines the target reader role of the terminal device.
[0294] In some feasible implementations, the access network device determining the target reader role of the terminal device can be understood as: the access network device obtains one or more authorized reader roles of the terminal device and determines the target reader role of the terminal device from the one or more authorized reader roles. Exemplarily, the target reader role may include one or more reader roles.
[0295] It should be understood that, in one implementation, the access network device obtaining the one or more authorized reader roles of the terminal device can be understood as: the access network device determining the one or more authorized reader roles of the terminal device based on second information, where the second information includes one or more of the following information: capability information of the terminal device and / or subscription data of the terminal device. That is, the access network device can determine the one or more authorized reader roles of the terminal device based on the capability information of the terminal device, or the subscription data of the terminal device, or both the capability information of the terminal device and the subscription data of the terminal device. The capability information of the terminal device indicates the reader roles supported by the terminal device, and the subscription data of the terminal device indicates the reader roles that the terminal device is permitted to serve. In other words, the access network device can determine the one or more authorized reader roles of the terminal device based on the second information. Optionally, in this implementation, when the access network device determines the one or more authorized reader roles of the terminal device based on the second information, the access network device can send the one or more authorized reader roles to the first core network device, so that the first core network device can send the one or more authorized reader roles to the terminal device, and the terminal device can then send a first request message to the access network device based on the received authorized reader roles. It is understandable that after the terminal device receives the authorized one or more reader roles sent by the first core network device, the terminal device can send a first request message to the access network device based on the authorized one or more reader roles. In one possible implementation, the first request message is used to request the execution of the first reader role. Exemplarily, the first reader role is one or more reader roles among the authorized one or more reader roles.
[0296] Exemplarily, in Ambient IoT, the reader roles supported by the terminal device indicated by the capability information of the terminal device may be one or more roles of an uplink assisted (e.g., Ambient IoT UL assisted reader) reader, a downlink assisted (e.g., Ambient IoT DL assisted) reader, an assisted reader (e.g., Ambient IoT assisted reader), a reader (e.g., Ambient IoT reader), or a reader providing carrier assistance (Ambient IoT CW assisted), etc. Among them, the uplink assisted reader and the downlink assisted reader may be collectively referred to as an assisted reader (Ambient IoT assisted reader), or a one-way (Ambient IoT one-way) reader, or a unidirectional assisted (unidirectional assisted) reader, etc., without limitation herein.
[0297] Optionally, in another possible implementation, the capabilities of different reader roles may be backward compatible. For example, a terminal device that supports a reader may support an uplink auxiliary reader, a downlink auxiliary reader, an auxiliary reader, and a carrier-providing auxiliary reader. For another example, a terminal device that supports an auxiliary reader may support an uplink auxiliary reader and a downlink auxiliary reader. In other words, the reader role supported by the terminal device indicated by the capability information of the terminal device in this application may be the reader role with the highest capability. Therefore, after the access network device obtains the capability information of the terminal device, the access network device may consider that the terminal device supports both the reader role with the highest capability indicated by the capability information and other roles with lower capabilities. In other words, the reader role supported by the terminal device indicated by the capability information of the terminal device is not the same as the one indicated by the capability information, and may also include other readers that the terminal device is compatible with.
[0298] In one possible implementation, the capability information of the terminal device may be included in (or contained in, or carried in) a NAS message (such as a registration request), and specifically may be carried in the UE radio capability (UEradio capability) or UE mobility management core network capability (UEMMCoreNetworkCapability) field of the registration request. This method of carrying the capability information of the terminal device described in this application through an existing field in the existing signaling is conducive to forward compatibility of the protocol. It should be noted that the capability information of the terminal device is reported by the terminal device (that is, the capability information of the terminal device comes from the terminal device, or the source of the capability information of the terminal device is the terminal device). When the capability information of the terminal device is reported in a NAS message (such as a registration request), the terminal device may forward / transmit the registration request to the first core network device through the access network device, and after the first core network device parses the capability information of the terminal device, the first core network device sends the capability information of the terminal device to the access network device. It is understandable that during the registration process, the first core network device can carry the terminal device capability information in a context request (such as a context establishment request or a context modification request) or in a terminal device capability check request (UEradio capability check request) to send to the access network device.
[0299] In another possible implementation, after completing the registration process, the terminal device may send the terminal device's capability information to the first core network device via a NAS message. The first core network device sends the terminal device's capability information to the access network device via an N2 message (e.g., a context modification request or a terminal device capability check request).
[0300] Optionally, the terminal device's capability information may be carried in AN parameters (e.g., AN parameters in an AN message). Therefore, when the access network device receives the AN message or AN parameters, it can directly parse the terminal device's capability information without having to pass through the first core network device and then send it to the access network device.
[0301] The reader role that the terminal device is allowed to act as indicated by the contract data of the above-mentioned terminal device may be one or more roles of an uplink auxiliary reader, a downlink auxiliary reader, an auxiliary reader, a reader, or a reader providing carrier assistance. The contract data may explicitly indicate the reader role that the terminal device is allowed to act as, for example, the contract data directly includes one or more roles of an uplink auxiliary reader, a downlink auxiliary reader, an auxiliary reader, a reader, or a reader providing carrier assistance. Exemplarily, the contract data may include one or more information elements of a reader role (e.g., readerrole), a reader type (readertype), or a reader capability (readercapability) to indicate the reader that the terminal device is allowed to act as.
[0302] Optionally, the reader role that the terminal device is allowed to act as indicated by the contract data of the terminal device may not be the same as the one indicated by the contract data display, and may also include other readers that the terminal device is compatible with, or it can be understood that the reader role that the terminal device is allowed to act as indicated by the contract data can be downward compatible, or it can be understood that the reader role that the terminal device is allowed to act as indicated by the contract data is the reader role with the highest capability, and in fact, the reader role that the terminal device is allowed to act as may also include other roles with lower capabilities. For example, if the reader role that the terminal device is allowed to act as indicated by the contract data of the terminal device is a reader, then it can be determined that the reader roles that the terminal device is actually allowed to act as may include an uplink auxiliary reader, a downlink auxiliary reader, an auxiliary reader, and a carrier-providing auxiliary reader, etc.
[0303] Optionally, the contract data may indicate the reader role that the terminal device is allowed to act as by indicating the slice and / or data network name (DNN), which is not limited here. This application does not limit the fields, formats, encodings, structures, etc. that indicate the reader role that the terminal device is allowed to act as in the contract data. Among them, the contract data of the terminal device can be stored in the second core network device, for example, the second core network device can be UDM, UDR, NEF, PCF, SMF, TMF, AIoTF, AITMF or AUSF, etc. The first core network device can obtain the contract data of the terminal device from the second core network device and send it to the access network device.
[0304] In another implementation, the access network device obtaining the one or more reader roles authorized for the terminal device can be understood as: the access network device receives the one or more reader roles authorized for the terminal device from the first core network device. That is, the authorized one or more reader roles are determined by the first core network device and sent to the access network device. It is understandable that when the authorized one or more reader roles are determined by the first core network device, the first core network device can specifically determine the authorized one or more reader roles based on the capability information of the terminal device, or the contract data of the terminal device, or the capability information of the terminal device and the contract data of the terminal device. Generally speaking, under this implementation, the first core network no longer needs to send the contract data of the terminal device to the access network device.
[0305] For example, taking the example of the first core network device determining one or more reader roles authorized for the terminal device based on the capability information of the terminal device, assuming that the capability information of the terminal device indicates that the reader roles supported by the terminal device are uplink auxiliary reader and reader providing carrier assistance, then the first core network device can determine that the reader roles authorized for the terminal device are uplink auxiliary reader and reader providing carrier assistance.
[0306] In one possible implementation, the capabilities of different reader roles may be backward compatible. For example, a terminal device that supports a reader may support an uplink auxiliary reader, a downlink auxiliary reader, an auxiliary reader, and a carrier-providing auxiliary reader. For another example, a terminal device that supports an auxiliary reader may support an uplink auxiliary reader and a downlink auxiliary reader. That is to say, the reader role supported by the terminal device indicated by the capability information of the terminal device in this application may be the reader role with the highest capability. Therefore, after the first core network device obtains the capability information of the terminal device, the first core network device may deem that the terminal device supports both the reader role with the highest capability indicated by the capability information and other roles with lower capabilities. In other words, the reader role supported by the terminal device indicated by the capability information of the terminal device is not the same as the one indicated by the capability information, and may also include other readers that the terminal device is compatible with.
[0307] For example, taking the example of a first core network device determining one or more reader roles authorized for a terminal device based on the capability information of the terminal device, assuming that the capability information of the terminal device indicates that the terminal device supports the reader role of reader, the first core network device may determine that the terminal device is authorized to use a reader role of reader, an auxiliary reader, or a reader providing carrier assistance. The auxiliary reader may include an uplink auxiliary reader and a downlink auxiliary reader.
[0308] For example, taking the example of the first core network device determining one or more reader roles authorized for the terminal device based on the contract data of the terminal device, assuming that the contract data of the terminal device indicates that the terminal device is allowed to serve as an uplink auxiliary reader and a downlink auxiliary reader, then the first core network device can determine that the reader roles authorized for the terminal device are an uplink auxiliary reader and a downlink auxiliary reader.
[0309] In one possible implementation, the reader role that the terminal device is allowed to serve as indicated by the contract data of the terminal device may not be the same as the one indicated by the contract data display, and may also include other readers that the terminal device is compatible with.
[0310] For example, taking the example of a first core network device determining one or more authorized reader roles of a terminal device based on the subscription data of the terminal device, assuming that the subscription data of the terminal device indicates that the terminal device is allowed to have a reader role of reader, the first core network device may determine that the authorized reader roles of the terminal device include reader, auxiliary reader, or reader providing carrier assistance. The auxiliary reader may include an uplink auxiliary reader and a downlink auxiliary reader.
[0311] For example, taking the example of the first core network device determining one or more authorized reader roles based on the capability information of the terminal device and the contract data of the terminal device, assuming that the capability information of the terminal device indicates that the reader roles supported by the terminal device are uplink auxiliary reader and reader providing carrier assistance, and the contract data of the terminal device indicates that the terminal device is allowed to serve as an uplink auxiliary reader and a downlink auxiliary reader, then the first core network device can determine that the authorized reader role of the terminal device is an uplink auxiliary reader.
[0312] Optionally, when the authorized reader role is determined by the first core network device, the first core network device can send the determined authorized reader role to the terminal device so that the terminal device can send a first request message to the access network device based on the authorized reader role.
[0313] It should be understood that the access network device determines the target reader role of the terminal device from one or more authorized reader roles, which can be understood as follows: the access network device obtains third information and determines the target reader role from one or more authorized reader roles based on the third information. The third information includes one or more of the following information: capability information of the terminal device, a first request message from the terminal device, the link status between the access network device and the IoT terminal device, or the wireless resource status of the access network device. The first request message is used to request to act as the first reader role. Generally speaking, the first reader role requested by the terminal device can be an uplink auxiliary reader, a downlink auxiliary reader, an auxiliary reader, a reader, or a carrier-providing auxiliary reader. The link status between the access network device and the IoT terminal (such as a tag) includes information such as packet loss rate, delay, jitter, congestion status, uplink budget, and downlink budget. The wireless resource status of the access network device includes information such as wireless resource utilization, idle rate, spectrum efficiency, and spectrum utilization.
[0314] Exemplarily, when the third information is the capability information of the terminal device, the access network device may determine the reader role supported by the terminal device as indicated by the capability information of the terminal device among the authorized one or more reader roles as the target reader role. For example, assuming that the authorized one or more reader roles include an uplink auxiliary reader and a downlink auxiliary reader, and the capability information of the terminal device indicates that the reader role supported by the terminal device is an uplink auxiliary reader, then the access network device may determine that the target reader role is an uplink auxiliary reader. For another example, assuming that the authorized one or more reader roles include an uplink auxiliary reader, a downlink auxiliary reader, and a carrier-providing auxiliary reader, and the capability information of the terminal device indicates that the reader roles supported by the terminal device are an uplink auxiliary reader and a carrier-providing auxiliary reader, then the access network device may determine that the target reader role is an uplink auxiliary reader and a carrier-providing auxiliary reader.
[0315] In another example, when the third information is a first request message from a terminal device, the access network device may determine the first reader role among the one or more authorized reader roles as the target reader role. For example, assuming that the one or more authorized reader roles include an uplink auxiliary reader and a downlink auxiliary reader, and the first reader role requested by the first request message is a downlink auxiliary reader, the access network device may determine the target reader role as the downlink auxiliary reader.
[0316] In another example, when the third information is the link status between the access network device and the IoT terminal, such as the uplink packet loss rate and the downlink packet loss rate, if the uplink packet loss rate between the access network device and the IoT terminal is greater than the downlink packet loss rate, and the authorized one or more reader roles include an uplink auxiliary reader, then the target reader role is determined to be an uplink auxiliary reader. If the downlink packet loss rate between the access network device and the IoT terminal is greater than the uplink packet loss rate, and the authorized one or more reader roles include a downlink auxiliary reader, then the target reader role is determined to be a downlink auxiliary reader.
[0317] In another example, when the third information is the link status between the access network device and the IoT terminal, such as the uplink budget and downlink budget, if the uplink budget between the access network device and the IoT terminal is lower than the downlink budget, and the authorized one or more reader roles include an uplink auxiliary reader, then the target reader role is determined to be the uplink auxiliary reader. If the downlink budget between the access network device and the IoT terminal is lower than the uplink budget, and the authorized one or more reader roles include a downlink auxiliary reader, then the target reader role is determined to be the downlink auxiliary reader.
[0318] Optionally, in some feasible implementations, the access network device determining the target reader role of the terminal device can also be understood as: the access network device obtains fourth information and determines the target reader role of the terminal device based on the fourth information. In other words, the access network device can directly determine the target reader role based on the fourth information. The fourth information includes one or more of the following information: capability information of the terminal device, contract data of the terminal device, a first request message from the terminal device, the link status between the access network device and the IoT terminal device, or the wireless resource status of the access network device. For an understanding of the capability information of the terminal device, the contract data of the terminal device, the link status between the access network device and the IoT terminal device, and the wireless resource status of the access network device, please refer to the aforementioned relevant description and will not be repeated here.
[0319] S502: The access network device sends first information to the terminal device. Correspondingly, the terminal device receives the first information from the access network device.
[0320] The first information instructs the terminal device to perform the target reader role. Optionally, after receiving the first information, the terminal device may send fifth information to the access network device, where the fifth information indicates whether the terminal device accepts to perform the target reader role.
[0321] Optionally, in addition to sending the first information to the terminal device, the access network device may also send resource configuration information to the terminal device. The resource configuration information indicates / includes one or more of the following information: frequency information, frequency band information, transmit power, transmission bandwidth, transmission rate, or execution duration. The resource configuration information is used by the terminal device to perform the target reader role.
[0322] It should be understood that the first information and the resource configuration information can be carried in the same message, or the first information and the resource configuration information can be carried in different messages. Optionally, the first information can also be carried in the resource configuration information. That is, in addition to indicating / including one or more of the above-mentioned frequency information, frequency band information, transmit power, transmission bandwidth, transmission rate, or execution duration, the resource configuration information can also indicate / include the first information.
[0323] In a possible implementation, the access network device may send the first information and / or resource configuration information to the terminal device during the registration process.
[0324] As described in S501, during or after the registration process, the first core network device can send one or more authorized reader roles to the terminal device, so that the terminal device can send a first request message to the access network device based on the one or more authorized reader roles. Optionally, during or after the registration process, the first core network device can also send at least one cell identifier to the terminal device, and the cell corresponding to the at least one cell identifier is a cell that supports Internet of Things services (or a cell that supports environmental energy acquisition to enable Internet of Things services), where one cell identifier is used to identify a cell, and the cell corresponding to the at least one cell identifier includes the first cell. The at least one cell identifier is used for cell switching / reselection. The above-mentioned authorized one or more reader roles and the at least one cell identifier can be carried in the same message, such as a registration accept or a downlink NAS message. Exemplarily, the at least one cell identifier can specifically be a cell list, and the cell list includes at least one cell that supports Internet of Things services.
[0325] In this application, the Internet of Things may include an environmental energy acquisition Internet of Things, an environmental energy enabling Internet of Things, or a passive Internet of Things, etc., and is not limited here.
[0326] In this application, the Internet of Things service may include or be replaced by an environmental energy acquisition Internet of Things service, an environmental energy enabling Internet of Things service, or a passive Internet of Things service, etc., without limitation.
[0327] In this application, supporting IoT services can be understood as supporting IoT service management or supporting IoT terminal management, etc.
[0328] It is understandable that the above steps S501 and S502 can occur during the registration process or after the registration process. It should be understood that before the terminal device initiates the registration process, the terminal device usually needs to perform network selection and cell selection. Therefore, before initiating the registration process, the following step S500 may also be included:
[0329] S500: The access network device broadcasts the second indication information. Correspondingly, the terminal device receives the second indication information from the access network device. Step S500 is optional.
[0330] The second indication information indicates that the first cell supports the Internet of Things service (or indicates that the first cell supports the environmental energy acquisition Internet of Things service), or the second indication information indicates that one or more cells of the access network device support the Internet of Things service (or the environmental energy acquisition Internet of Things service), and the one or more cells include the first cell.
[0331] For example, the second indication information can be carried in a broadcast message (e.g., a system information broadcast (SIB) message). In one implementation, the terminal device can trigger / enable / activate / determine / determine to function as a reader based on a user operation on the terminal interface. Therefore, when the terminal device determines to function as a reader, the terminal device can select a cell (e.g., the first cell) that supports IoT services based on the second indication information.
[0332] Optionally, during the registration process, if the cell currently accessed by the terminal device (for example, the first cell) is a cell that supports IoT services, the access network device can select the first core network device that supports IoT service management based on the first cell accessed by the terminal device.
[0333] Optionally, during the registration process, if the cell currently accessed by the terminal device (for example, the second cell) is a cell that does not support the Internet of Things service, the access network device can select the first core network device that supports the Internet of Things service or supports the management of the Internet of Things service based on the first indication information. Here, the first indication information may be sent by the terminal device to the access network device when initiating the registration process, and the first indication information is used to indicate that the terminal device supports the Internet of Things service, supports the environmental energy acquisition Internet of Things service, and supports the reader function (or reader role). Exemplarily, supporting the Internet of Things service can be replaced by supporting the environmental energy acquisition Internet of Things service, requesting to obtain the Internet of Things service, requesting to obtain the environmental energy acquisition Internet of Things service, requesting to act as a reader, etc. Exemplarily, the first indication information may be the capability information of the terminal device. In another possible implementation method, the first indication information may be the type information of the terminal device. The type information of the terminal device may indicate that the terminal device supports the reader function.
[0334] Optionally, if the cell accessed by the terminal device is a second cell under the access network device that does not support the Internet of Things service, and there are some cells under the access network device that support the Internet of Things service, then the access network device has the ability to select the AMF that supports the Internet of Things service, process the RRC, N2 messages, resource scheduling, etc. related to the Internet of Things service, that is, the above S501 and S502 can be executed normally. After step S502, before the terminal device performs the target reader role, the terminal device can perform cell reselection or cell switching according to at least one cell identifier sent by the first core network device to access the cell that supports the Internet of Things service (for example, the first cell). That is to say, if the terminal device needs to perform the target reader role through the cell that supports the Internet of Things service, the terminal device can perform cell reselection after receiving the first information sent by the access network device to access the cell that supports the Internet of Things service to perform the target reader role.
[0335] Optionally, after step S502, before the terminal device performs the target reader role, the terminal device may perform cell reselection or cell switching according to the broadcast message (e.g., SIB) to access a cell supporting the Internet of Things service (e.g., the first cell). In other words, if the terminal device needs to perform the target reader role through a cell supporting the Internet of Things service, the terminal device may perform cell reselection after receiving the first information sent by the access network device to access a cell supporting the Internet of Things service to perform the target reader role.
[0336] Optionally, if the cell accessed by the terminal device is a second cell, and all cells under the access network device where the second cell is located do not support the Internet of Things service, then the terminal device can perform cell reselection or cell switching based on the at least one cell identifier to access a cell (such as the first cell) under another access network device that supports the Internet of Things service. After performing cell reselection, the terminal device can initiate a switching process or a registration process (such as a mobility registration update process) to the new access network device.
[0337] In the embodiment of the present application, by executing the communication method, the capability negotiation between the network and the terminal device can be completed, enabling the terminal device to perform the target reader role and complete the Internet of Things business, which is conducive to improving the reliability of communication.
[0338] The following describes the various scenarios described in Figure 5 above:
[0339] For example, please refer to Figure 6, which is another flow chart of the communication method provided in an embodiment of the present application. In Figure 6, the first core network device is an AMF and the second core network device is a UDM or UDR. As shown in Figure 6:
[0340] S600: The access network device sends a broadcast message. Correspondingly, the terminal device receives the broadcast message from the access network device.
[0341] The broadcast message (e.g., SIB) may include second indication information, where the second indication information indicates that the first cell supports the Internet of Things service, or the second indication information indicates that one or more cells of the access network device support the Internet of Things service, where the one or more cells include the first cell, so that the terminal device can access the first cell supporting the Internet of Things service according to the second indication information.
[0342] For more understanding of the second indication information, please refer to the relevant description in S500 in Figure 5, which will not be repeated here.
[0343] S601: A terminal device selects to access a first cell, which is a cell supporting Internet of Things services.
[0344] S602: The terminal device sends an AN message to the access network device. Correspondingly, the access network device receives the AN message from the terminal device.
[0345] The AN message includes first indication information, and / or information such as capability information of the terminal device. Exemplarily, the first indication information, and / or capability information of the terminal device may be specifically carried in a NAS message (e.g., a registration request) of the AN message. The first indication information indicates that the terminal device supports IoT services. The capability information of the terminal device indicates the reader roles supported by the terminal device. For example, the capability information of the terminal device may indicate one or more of the following roles: uplink auxiliary reader, downlink auxiliary reader, auxiliary reader, reader, or reader providing carrier assistance, etc.
[0346] For more information about the first indication information and the capability information of the terminal device, please refer to the relevant description in Figure 5, which will not be repeated here.
[0347] S603: The access network device performs AMF selection.
[0348] In one implementation, the access network device can select an AMF that supports the management of IoT services based on the first indication information.
[0349] In another implementation, when the first cell to which the terminal device accesses supports IoT services, the access network device may select a management AMF that supports IoT services based on the first cell.
[0350] S604: The access network device sends an N2 message to the AMF. Correspondingly, the AMF receives the N2 message from the access network device.
[0351] The N2 message includes a NAS message (eg, a registration request).
[0352] S605: The terminal device, AMF, AUSF, and UDM execute the security authentication process of the terminal device.
[0353] S606. AMF interacts with UDM / UDR to obtain the contract data of the terminal device.
[0354] Optionally, AMF can also interact with UDR through PCF to obtain the contract data of the terminal device.
[0355] The subscription data indicates the reader role that the terminal device is allowed to serve as. For example, the subscription data may indicate one or more of the following roles: uplink auxiliary reader, downlink auxiliary reader, auxiliary reader, reader, or reader providing carrier assistance, etc.
[0356] For more information about the contract data, please refer to the relevant description in Figure 5, which will not be repeated here.
[0357] S607: The AMF sends a context request to the access network device. Correspondingly, the access network device receives the context request from the AMF.
[0358] In one implementation, if the AMF determines the authorized reader role of the terminal device, the context request includes one or more authorized reader roles of the terminal device. For example, the AMF may determine the authorized reader role or roles based on the terminal device's subscription data and / or the terminal device's capability information, and send the determination to the access network device.
[0359] In another implementation, if the access network device determines the authorized reader role of the terminal device, the context request includes the terminal device's capability information and / or the terminal device's subscription data. Optionally, in this implementation, the access network device may also send the determined authorized reader role of the terminal device to the AMF. For example, the authorized reader role may be included in the context response and sent to the AMF.
[0360] Exemplarily, the context request may be a context establishment request or a context modification request, etc., which is not limited here.
[0361] For more understanding of the authorized reader role of the terminal device, please refer to the relevant description in Figure 5, which will not be repeated here.
[0362] S608: The AMF sends a NAS message to the terminal device. Correspondingly, the terminal device receives the NAS message from the AMF.
[0363] Exemplarily, the NAS message may be a registration accept message or a registration reject message. The NAS message includes one or more reader roles authorized for the terminal device and / or identification information of at least one cell supporting IoT services.
[0364] S609: The terminal device sends a first request message to the access network device. Correspondingly, the access network device receives the first request message from the terminal device.
[0365] The first request message is used to request to be the first reader role. For example, the first reader role can be determined by the terminal device according to one or more authorized reader roles of the terminal device included in the NAS message. S609 is an optional step.
[0366] For more understanding of the first request message, please refer to the relevant description in Figure 5, which will not be repeated here.
[0367] S610: The access network device determines the target reader role.
[0368] The access network device may determine the target reader role from one or more authorized reader roles based on one or more of the following information: the terminal device's capability information, the first request message, the link status between the access network device and the IoT terminal, or the access network device's wireless resource status. For details, see the relevant description of step S501 in FIG. This description is omitted here.
[0369] For more understanding of how the access network device determines the role of the target reader, please refer to the relevant description of step S501 in Figure 5, which will not be repeated here.
[0370] S611: The access network device sends first information to the terminal device. Correspondingly, the terminal device receives the first information from the access network device. The first information is used to indicate the target reader role.
[0371] Exemplarily, the first information may be carried in an AN message. Optionally, the AN message may further include resource configuration information, where the resource configuration information includes one or more of the following information: frequency information, frequency band information, transmit power, transmission bandwidth, transmission rate, or execution duration. The resource configuration information may be used to execute the target reader role. In one possible implementation, the resource configuration information indicates the resources (e.g., wireless resources) used by the terminal device when executing the target reader role.
[0372] For more understanding about the access network device sending the first information to the terminal device, please refer to the relevant description of step S502 in Figure 5, which will not be repeated here.
[0373] S612: The terminal device sends the fifth information to the access network device. Correspondingly, the access network device receives the fifth information from the terminal device.
[0374] The fifth information is used to indicate whether the terminal device accepts to perform the target reader role. For example, the fifth information can be carried in an AN message. Step S612 is an optional step.
[0375] Optionally, if the terminal device accepts execution of the target reader role, the terminal device may use the resources indicated by the resource configuration information to execute the functions of the target reader role. In one implementation, the terminal device may trigger / enable / activate the terminal device's use of resources to execute the target reader role based on user operations on the terminal interface. In another implementation, the terminal device may determine / determine execution of the reader role based on user operations on the terminal interface. After receiving the resource configuration information sent by the access network device, the terminal device may execute the target reader role based on the resource configuration information.
[0376] Optionally, please refer to Figure 7, which is another flow chart of the communication method provided by an embodiment of the present application. In Figure 7, the first core network device is AMF, and the second core network device is UDM or UDR as an example for illustration. The access network device in Figure 7 can support multiple cells, some of which support IoT services (such as the first cell) and some cells do not support IoT services (such as the second cell). Therefore, the access network device has the ability to select AMF that supports IoT services, process RRC, N2 messages, resource scheduling, etc. related to IoT services. As shown in Figure 7:
[0377] S700: The access network device sends a broadcast message. Correspondingly, the terminal device receives the broadcast message from the access network device.
[0378] The broadcast message (eg, SIB) may include second indication information, the second indication information indicating that the first cell supports the IoT service, or the second indication information indicating that one or more cells of the access network device support the IoT service, the one or more cells including the first cell. S700 is an optional step.
[0379] For more understanding of the second indication information, please refer to the relevant description in S500 in Figure 5, which will not be repeated here.
[0380] S701: A terminal device selects to access a second cell, which does not support IoT services.
[0381] S702: The terminal device sends an AN message to the access network device. Correspondingly, the access network device receives the AN message from the terminal device.
[0382] The AN message includes first indication information, and / or information such as capability information of the terminal device. Exemplarily, the first indication information, and / or capability information of the terminal device may be carried in a NAS message (e.g., a registration request) of the AN message. The first indication information indicates that the terminal device supports IoT services. The capability information of the terminal device indicates the reader roles supported by the terminal device. For example, the capability information of the terminal device may indicate one or more of the following roles: uplink auxiliary reader, downlink auxiliary reader, auxiliary reader, reader, or reader providing carrier assistance, etc.
[0383] For more information about the first indication information and the capability information of the terminal device, please refer to the relevant description in Figure 5, which will not be repeated here.
[0384] S703: The access network device selects AMF.
[0385] In one implementation, if the AN message in step S702 includes first indication information, the access network device can select an AMF that supports the management of IoT services based on the first indication information.
[0386] In another implementation, if the AN message in step S702 does not include the first indication information, the AMF selected by the access network device to access may be an AMF that does not support IoT service management.
[0387] S704: The access network device sends an N2 message to the AMF. Correspondingly, the AMF receives the N2 message from the access network device.
[0388] The N2 message includes a NAS message (eg, a registration request).
[0389] S705. AMF performs AMF reselection (AMF rellocation).
[0390] In one possible implementation, when the registration request (or NAS message) sent by the terminal device includes the first indication information and / or the capability information of the terminal device, the AMF may perform AMF reselection based on the information, wherein the reselected AMF supports IoT services or supports IoT service management. That is, if the AMF selected by the access network device in step S703 is an AMF that does not support IoT service management, then AMF reselection may be performed in step S705 to select an AMF that supports IoT services; if the AMF selected by the access network device in step S703 is an AMF that supports IoT service management, then step S705 here may not be performed.
[0391] S706. The terminal device, AMF, AUSF, and UDM execute the security authentication process of the terminal device.
[0392] S707. AMF interacts with UDM / UDR to obtain the contract data of the terminal device.
[0393] The subscription data indicates the reader role that the terminal device is allowed to serve as. For example, the subscription data may indicate one or more of the following roles: uplink auxiliary reader, downlink auxiliary reader, auxiliary reader, reader, or reader providing carrier assistance, etc.
[0394] For more information about the contract data, please refer to the relevant description in Figure 5, which will not be repeated here.
[0395] S708: The AMF sends a context request to the access network device. Correspondingly, the access network device receives the context request from the AMF.
[0396] Exemplarily, the context request may be a context establishment request or a context modification request, etc., which is not limited here.
[0397] In one implementation, if the AMF determines the authorized reader role of the terminal device, the context request includes one or more authorized reader roles of the terminal device. For example, the AMF may determine the authorized reader role or roles based on the terminal device's subscription data and / or the terminal device's capability information, and send the determination to the access network device.
[0398] In another implementation, if the access network device determines the authorized reader role of the terminal device, the context request includes the terminal device's capability information and / or the terminal device's subscription data. Optionally, in this implementation, the access network device may also send the determined authorized reader role of the terminal device to the AMF. Exemplarily, the authorized reader role may be carried in a context response (e.g., a context establishment response or a context modification response) and sent to the AMF.
[0399] For more understanding of the authorized reader role of the terminal device, please refer to the relevant description in Figure 5, which will not be repeated here.
[0400] S709: The AMF sends a NAS message to the terminal device. Correspondingly, the terminal device receives the NAS message from the AMF.
[0401] Exemplarily, the NAS message may be a registration accept message or a registration reject message. Optionally, the registration reject message is used to indicate that the terminal device needs to access a cell that supports IoT services. The NAS message may include identification information of at least one cell that supports IoT services. The at least one identification information includes identification information of the first cell.
[0402] Optionally, the NAS message may include one or more reader roles authorized for the terminal device.
[0403] S710: The terminal device sends a first request message to the access network device. Correspondingly, the access network device receives the first request message from the terminal device.
[0404] The first request message is used to request to be the first reader role. For example, the first reader role can be determined by the terminal device according to one or more authorized reader roles of the terminal device included in the NAS message. S710 is an optional step.
[0405] For more understanding of the first request message, please refer to the relevant description in Figure 5, which will not be repeated here.
[0406] S711. The access network device determines the target reader role.
[0407] The access network device may determine the target reader role from one or more authorized reader roles based on one or more of the following information: the terminal device's capability information, the first request message, the link status between the access network device and the IoT terminal, or the access network device's wireless resource status. For details, see the relevant description of step S501 in FIG. This description is omitted here.
[0408] For more understanding of how the access network device determines the role of the target reader, please refer to the relevant description of step S501 in Figure 5, which will not be repeated here.
[0409] S712: The access network device sends first information to the terminal device. Correspondingly, the terminal device receives the first information from the access network device.
[0410] In one implementation, the first information instructs the terminal device to perform the target reader role. Exemplarily, the first information may be carried in an AN message. Optionally, the AN message may also include resource configuration information, which includes one or more of the following: frequency information, frequency band information, transmit power, transmission bandwidth, transmission rate, or execution duration. This resource configuration information may be used to perform the target reader role.
[0411] For more understanding about the access network device sending the first information to the terminal device, please refer to the relevant description of step S502 in Figure 5, which will not be repeated here.
[0412] S713: The terminal device sends the fifth information to the access network device. Correspondingly, the access network device receives the fifth information from the terminal device.
[0413] The fifth information is used to indicate whether the terminal device accepts to perform the target reader role. For example, the fifth information can be carried in an AN message. Step S713 is an optional step.
[0414] For more understanding about the terminal device sending the fifth information to the access network device, please refer to the relevant description in Figure 6, which will not be repeated here.
[0415] S714. The terminal device performs cell reselection / switching to access the first cell.
[0416] The terminal device performs cell reselection based on the identification information of one or more cells in step S709 or the second indication information in the broadcast message (eg, SIB) in step S700 to access the first cell, which is a cell supporting the Internet of Things service.
[0417] In one possible implementation, after receiving the first information, the terminal device learns that it needs to select a cell that supports the Internet of Things service, and performs cell reselection or switching based on the identification information of one or more cells sent by the AMF or based on the broadcast message. Optionally, the first information may also instruct the terminal device to select a cell that supports the Internet of Things service. The terminal device can check whether the currently accessed cell supports the Internet of Things service based on the first information. If not, it performs cell reselection or switching. Exemplarily, the terminal device can specifically perform cell reselection or switching based on the identification information of one or more cells sent by the AMF, or perform cell reselection or switching based on the broadcast message to access the first cell.
[0418] It is understandable that the terminal device may execute step S714 before executing the target reader role, that is, after step S714, the terminal device may execute the target reader role. It is understandable that the terminal device may use the resources indicated by the resource configuration information to execute the function of the target reader role. In one implementation, the terminal device may trigger / enable / activate the function of the terminal device to execute the target reader role using resources based on the user's operation on the terminal interface. In another implementation, the terminal device may decide / determine to execute the reader role based on the user's operation on the terminal interface, and when the terminal device receives the resource configuration information sent by the access network device, it may execute the target reader role according to the resource configuration information.
[0419] Optionally, please refer to Figure 8, which is another flow chart of the communication method provided in an embodiment of the present application. In Figure 8, the first core network device is AMF, and the second core network device is UDM or UDR as an example for illustration. The access network device 1 in Figure 8 can support multiple cells, none of which support IoT services. The access network device 2 in Figure 8 can support multiple cells, some of which support IoT services (such as the first cell), and some cells do not support IoT services (such as the second cell), or all cells under the access network device 2 support IoT services. As shown in Figure 8:
[0420] S800: Access network device 2 sends a broadcast message. Correspondingly, the terminal device receives the broadcast message from access network device 2.
[0421] The broadcast message (e.g., SIB) may include second indication information, where the second indication information indicates that the first cell under access network device 2 supports the Internet of Things service, or the second indication information indicates one or more cells under access network device 2 that support the Internet of Things service, where the one or more cells that support the Internet of Things service include the first cell. S800 is an optional step.
[0422] For more understanding of the second indication information, please refer to the relevant description in S500 in Figure 5, which will not be repeated here.
[0423] S801: The terminal device selects to access a second cell under access network device 1. The second cell is a cell that does not support IoT services.
[0424] S802: The terminal device sends an AN message to the access network device 1. Correspondingly, the access network device 1 receives the AN message from the terminal device.
[0425] The AN message includes first indication information, and / or information such as capability information of the terminal device. Exemplarily, the first indication information, and / or capability information of the terminal device may be carried in a NAS message (e.g., a registration request) of the AN message. The first indication information indicates that the terminal device supports IoT services. The capability information of the terminal device indicates the reader roles supported by the terminal device. For example, the capability information of the terminal device may indicate one or more of the following roles: uplink auxiliary reader, downlink auxiliary reader, auxiliary reader, reader, or reader providing carrier assistance, etc.
[0426] For more information about the first indication information and the capability information of the terminal device, please refer to the relevant description in Figure 5, which will not be repeated here.
[0427] S803. Access network device 1 performs AMF selection.
[0428] It should be noted that, since the access network device 1 does not have the ability to select an AMF that supports the Internet of Things service based on the first indication information, the access network device 1 may select an AMF that supports the management of the Internet of Things service, or may select an AMF that does not support the management of the Internet of Things service. In one possible implementation, if the AMF selected by the access network device 1 does not support the Internet of Things service, an AMF that supports the Internet of Things service can be selected through AMF redirection (such as AMF relocation). For ease of understanding, the embodiment of the present application is mainly illustrated by taking the example of the access network device 1 selecting an AMF that supports the management of the Internet of Things service as an example.
[0429] S804: Access network device 1 sends an N2 message to the AMF. Accordingly, the AMF receives the N2 message from access network device 1, which includes a NAS message (e.g., a registration request).
[0430] S805. The AMF sends a NAS message to the terminal device. Correspondingly, the terminal device receives the NAS message from the AMF.
[0431] The NAS message includes identification information of at least one cell supporting IoT services. The at least one identification information includes identification information of the first cell under access network device 2. In one possible implementation, the NAS message in step S805 is a registration accept message or a registration reject message. Optionally, the registration reject message indicates that the terminal device needs to access a cell supporting IoT services.
[0432] Optionally, the NAS message may include information such as one or more reader roles authorized for the terminal device determined by the AMF.
[0433] For an understanding of the authorized reader role of the terminal device, please refer to the relevant description in FIG5 , which will not be repeated here.
[0434] S806. The terminal device performs cell reselection / switching to access the first cell under access network device 2.
[0435] In a possible implementation, the terminal device may perform cell reselection based on identification information of one or more cells in the NAS message in step S805 to access the first cell under the access network device 2.
[0436] Optionally, in another possible implementation, the terminal device may also select the first cell according to the second indication information in the broadcast message (e.g., SIB) in step S800. Exemplarily, the terminal device may perform cell reselection based on the NAS message sent by the AMF. For example, the NAS message indicates that the currently accessed cell does not support IoT services, or the NAS message indicates a cell that supports IoT services.
[0437] Among them, the above-mentioned first cell is a cell that supports Internet of Things services.
[0438] Optionally, after step S806, the terminal device may initiate a registration process or a handover process to the access network device 2, that is, execute S807 to S817 in FIG8 :
[0439] S807: The terminal device sends an AN message to the access network device 2. Correspondingly, the access network device 2 receives the AN message from the terminal device.
[0440] The AN message includes first indication information, and / or information such as capability information of the terminal device. Exemplarily, the first indication information, and / or capability information of the terminal device may be carried in a NAS message (e.g., a registration request) of the AN message. The first indication information indicates that the terminal device supports IoT services. The capability information of the terminal device indicates the reader roles supported by the terminal device. For example, the capability information of the terminal device may indicate one or more of the following roles: uplink auxiliary reader, downlink auxiliary reader, auxiliary reader, reader, or reader providing carrier assistance, etc.
[0441] S808. Access network device 2 performs AMF selection (AMF selection).
[0442] In one possible implementation, the access network device 2 performs AMF selection based on the cell supporting the Internet of Things service accessed by the terminal device, or performs AMF selection based on the first indication information sent by the terminal device. Exemplarily, the AMF is an AMF that supports the Internet of Things service.
[0443] S809: Access network device 2 sends an N2 message to the AMF. Accordingly, the AMF receives the N2 message from access network device 2.
[0444] The N2 message includes a NAS message (eg, a registration request).
[0445] S810. The terminal device, AMF, AUSF, and UDM execute the security authentication process of the terminal device.
[0446] S811, AMF interacts with UDM / UDR to obtain the contract data of the terminal device.
[0447] For an understanding of the contract data, please refer to the relevant description in Figure 5, which will not be repeated here.
[0448] S812: The AMF sends a context request to access network device 2. Accordingly, access network device 2 receives the context request from the AMF.
[0449] S813. The AMF sends a NAS message to the terminal device. Accordingly, the terminal device receives the NAS message from the AMF. Exemplarily, the NAS message is a registration accept message.
[0450] S814: The terminal device sends a first request message to the access network device 2. Correspondingly, the access network device 2 receives the first request message from the terminal device.
[0451] For more information about the first request message, please refer to the relevant description in Figure 5, which will not be repeated here. S814 is an optional step.
[0452] S815. Access network device 2 determines the target reader role.
[0453] For more understanding of how the access network device 2 determines the role of the target reader, please refer to the relevant description of step S501 in Figure 5, which will not be repeated here.
[0454] S816: Access network device 2 sends first information to the terminal device. Correspondingly, the terminal device receives the first information from access network device 2. The first information is used to indicate the target reader role.
[0455] For more understanding on the access network device 2 sending the first information to the terminal device, please refer to the relevant description of step S502 in Figure 5, which will not be repeated here.
[0456] S817: The terminal device sends the fifth information to the access network device 2. Accordingly, the access network device 2 receives the fifth information from the terminal device. This step S817 is optional.
[0457] It should be noted that, for the understanding of S807 to S817, please refer to the relevant description of S602 to S612 shown in FIG6 , which will not be repeated here.
[0458] It should be noted that in the various embodiments of the present application (such as the embodiments shown in Figures 5, 6, 7 and 8), unless otherwise specified and there is no logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other.
[0459] The communication device provided in this application will be described in detail below with reference to FIG9 and FIG10 .
[0460] It is understood that in order to implement the functions in the above embodiments, the communication device includes hardware structures and / or software modules corresponding to the execution of each function. It should be readily apparent to those skilled in the art that, in combination with the units and method steps of each example described in the embodiments disclosed in this application, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in hardware or in a manner driven by computer software depends on the specific application scenario and design constraints of the technical solution.
[0461] Figures 9 and 10 are schematic diagrams of the structures of possible communication devices provided in the embodiments of the present application. These communication devices can be used to implement the functions of the terminal device or access network device or first core network device in the above method embodiments, and thus can also achieve the beneficial effects possessed by the above method embodiments. In the embodiments of the present application, the communication device can be one of the terminal devices 120a-120j as shown in Figure 1, or it can be the access network device 110a or 110b as shown in Figure 1, or it can be a module (such as a chip) applied to the terminal device or access network device or first core network device.
[0462] As shown in Figure 9, the communication device 900 includes a processing unit 910 and a transceiver unit 920. The communication device 900 is used to implement the functions of the terminal device, access network device, or first core network device in any of the method embodiments shown in Figures 5 to 8 above.
[0463] When the communication device 900 is used to implement the functions of the terminal device in any of the method embodiments shown in FIG5 to FIG8:
[0464] The transceiver unit 920 is configured to send a first request message to the access network device, where the first request message is used to request to serve as a first reader role;
[0465] The transceiver unit 920 is configured to receive first information from an access network device, where the first information instructs the terminal device to perform a target reader role.
[0466] In a possible implementation, the transceiver unit 920 is further configured to receive one or more reader roles authorized for the terminal device from the first core network device;
[0467] The processing unit 910 is further configured to determine the first reader role according to one or more reader roles authorized for the terminal device.
[0468] In a possible implementation, the transceiver unit 920 is configured to:
[0469] The capability information of the terminal device is sent to the access network device, where the capability information of the terminal device indicates reader capabilities supported by the terminal device, and the capability information of the terminal device is used to determine the target reader role.
[0470] In a possible implementation, the transceiver unit 920 is configured to:
[0471] A first indication message is sent to the access network device, where the first indication message indicates that the terminal device supports the Internet of Things service; the first indication message is used to determine the first core network device that supports the management of the Internet of Things service.
[0472] In a possible implementation, the cell accessed by the terminal device is a second cell, and the second cell does not support the Internet of Things service;
[0473] The transceiver unit 920 is further configured to receive second indication information from the access network device, where the second indication information indicates that the first cell supports the Internet of Things service, or the second indication information indicates that one or more cells of the access network device support the Internet of Things service, where the one or more cells include the first cell;
[0474] The processing unit 910 is further configured to perform cell reselection or cell handover according to the second indication information to access the first cell.
[0475] In a possible implementation, the cell accessed by the terminal device is a second cell of the access network device, and the second cell does not support the Internet of Things service;
[0476] The transceiver unit 920 is further configured to:
[0477] Receiving at least one cell identifier from the first core network device, where the cell corresponding to the at least one cell identifier is a cell supporting the Internet of Things service under the access network device, and the cell corresponding to the at least one cell identifier includes the first cell;
[0478] Perform cell reselection or cell handover according to the at least one cell identifier to access the first cell.
[0479] In a possible implementation, the cell accessed by the terminal device is a second cell, and all cells under the access network device where the second cell is located do not support the Internet of Things service;
[0480] The processing unit 910 is further configured to receive at least one cell identifier from the first core network device, where the cell corresponding to the at least one cell identifier is a cell supporting the IoT service under the access network device, and the cell corresponding to the at least one cell identifier includes the first cell;
[0481] The processing unit 910 is further configured to perform cell reselection or cell handover according to the at least one cell identifier to access the first cell.
[0482] In a possible implementation, the transceiver unit 920 is further configured to:
[0483] Receive resource configuration information from the access network device, the resource configuration information including one or more of the following information: frequency information, frequency band information, transmission power, transmission bandwidth, transmission rate, or execution duration; the resource configuration information is used by the terminal device to execute the target reader role.
[0484] In a possible implementation, after receiving the first information from the access network device, the transceiver unit 920 is further configured to:
[0485] Sending fifth information to the access network device, where the fifth information indicates whether the terminal device accepts to execute the target reader role.
[0486] In a possible implementation, the target reader role or the one or more reader roles authorized by the terminal device include the following roles: auxiliary reader, uplink auxiliary reader, downlink auxiliary reader, reader, or reader providing carrier assistance.
[0487] In one possible implementation, the first core network device includes an access management device, a tag management device, an environmental energy acquisition Internet of Things management device, a unified data management device, a user data storage device, a network capability exposure device, a policy control device, or a session management device.
[0488] When the communication device 900 is used to implement the function of the access network device in any of the method embodiments shown in FIG5 to FIG8:
[0489] Processing unit 910, configured to determine a target reader role of the terminal device;
[0490] The transceiver unit 920 is configured to send first information to the terminal device, wherein the first information instructs the terminal device to perform the target reader role.
[0491] In a possible implementation, when determining the target reader role of the terminal device, the processing unit 910 is configured to:
[0492] Obtaining one or more reader roles authorized for the terminal device;
[0493] A target reader role of the terminal device is determined from the authorized one or more reader roles.
[0494] In a possible implementation, when obtaining one or more reader roles authorized by the terminal device, the processing unit 910:
[0495] The transceiver unit 920 receives one or more reader roles authorized for the terminal device from the first core network device.
[0496] In a possible implementation, when obtaining one or more reader roles authorized by the terminal device, the processing unit 910 is configured to:
[0497] Determining one or more reader roles authorized for the terminal device according to second information; the second information includes one or more of the following information: capability information of the terminal device and / or subscription data of the terminal device;
[0498] The capability information of the terminal device indicates the reader roles supported by the terminal device, and the contract data of the terminal device indicates the reader roles that the terminal device is allowed to serve as.
[0499] In a possible implementation, the transceiver unit 920 is configured to:
[0500] The one or more reader roles authorized for the terminal device are sent to the first core network device, so that the first core network device sends the one or more reader roles authorized for the terminal device to the terminal device.
[0501] In a possible implementation, the processing unit 910 is configured to:
[0502] Acquire third information; the third information includes one or more of the following information: capability information of the terminal device, a first request message from the terminal device, a link status between the access network device and the Internet of Things terminal, or a wireless resource status of the access network device; wherein the capability information of the terminal device indicates a reader role supported by the terminal device, and the first request message is used to request to serve as the first reader role;
[0503] The target reader role is determined from the one or more authorized reader roles according to the third information.
[0504] In a possible implementation, when determining the target reader role of the terminal device from the one or more authorized reader roles according to the third information, the processing unit 910 is configured to:
[0505] determining the reader role supported by the terminal device indicated by the capability information of the terminal device among the one or more authorized reader roles as the target reader role; or,
[0506] determining the first reader role among the one or more authorized reader roles as the target reader role; or,
[0507] When the uplink budget between the access network device and the Internet of Things terminal is lower than the downlink budget, and the authorized one or more reader roles include an uplink auxiliary reader, determining the target reader role as an uplink auxiliary reader; or,
[0508] When a downlink budget between the access network device and the Internet of Things terminal is lower than an uplink budget, and the authorized one or more reader roles include a downlink auxiliary reader, the target reader role is determined to be a downlink auxiliary reader.
[0509] In a possible implementation, when determining the target reader role of the terminal device, the processing unit 910 is configured to:
[0510] Acquire fourth information; the fourth information includes one or more of the following information: capability information of the terminal device, subscription data of the terminal device, a first request message from the terminal device, a link status between the access network device and the Internet of Things terminal, or a wireless resource status of the access network device; wherein the capability information of the terminal device indicates a reader role supported by the terminal device, and the first request message is used to request to serve as the first reader role;
[0511] The target reader role is determined according to the fourth information.
[0512] In a possible implementation, the transceiver unit 920 is configured to:
[0513] receiving capability information of the terminal device sent by a first core network device, where the first core network device supports Internet of Things service management; or
[0514] Receive capability information of the terminal device sent by the terminal device.
[0515] In a possible implementation, when receiving the capability information of the terminal device sent by the first core network device, the transceiver unit 920 is configured to:
[0516] During the registration process, a context request or a terminal device capability check request sent by the first core network device is received, where the context request or the terminal device capability check request includes capability information of the terminal device.
[0517] In a possible implementation, the transceiver unit 920 is further configured to receive first indication information from the terminal device, where the first indication information indicates that the terminal device supports an Internet of Things service;
[0518] The processing unit 910 is further configured to select a first core network device that supports management of the IoT service according to the first indication information.
[0519] In a possible implementation, the processing unit 910 is configured to:
[0520] When the first cell accessed by the terminal device supports the Internet of Things service, the first core network device is selected according to the first cell accessed by the terminal device, and the first core network device supports the management of the Internet of Things service.
[0521] In a possible implementation, the transceiver unit 920 is configured to:
[0522] Broadcast second indication information, wherein the second indication information indicates that the first cell supports the Internet of Things service, or the second indication information indicates that one or more cells of the access network device support the Internet of Things service, so that the terminal device accesses the first cell supporting the Internet of Things service according to the second indication information, and the one or more cells include the first cell.
[0523] In a possible implementation, the transceiver unit 920 is configured to:
[0524] Send resource configuration information to the terminal device, where the resource configuration information includes one or more of the following information: frequency information, frequency band information, transmission power, transmission bandwidth, transmission rate, or execution duration; the resource configuration information is used by the terminal device to perform the target reader role.
[0525] In a possible implementation, after sending the first information to the terminal device, the transceiver unit 920 is further configured to:
[0526] Fifth information is received from the terminal device, where the fifth information indicates whether the terminal device accepts to perform the target reader role.
[0527] In a possible implementation, the target reader role or the one or more reader roles authorized by the terminal device include the following roles: auxiliary reader, uplink auxiliary reader, downlink auxiliary reader, reader, or reader providing carrier assistance.
[0528] In one possible implementation, the first core network device includes an access management device, a tag management device, an environmental energy acquisition Internet of Things management device, a unified data management device, a user data storage device, a network capability exposure device, a policy control device, or a session management device.
[0529] When the communication apparatus 900 is used to implement the function of the first core network device in any of the method embodiments shown in FIG. 5 to FIG. 8 , in one implementation:
[0530] The processing unit 910 is configured to obtain one or more reader roles authorized by the terminal device;
[0531] The transceiver unit 920 is configured to send one or more reader roles authorized for the terminal device to the terminal device; the one or more authorized reader roles are used to determine a target reader role.
[0532] In a possible implementation, when obtaining the one or more reader roles authorized by the terminal device, the processing unit 910 is configured to:
[0533] Determine one or more reader roles authorized for the terminal device based on the capability information of the terminal device and / or the contract data of the terminal device, where the capability information of the terminal device indicates the reader capabilities supported by the terminal device, and the contract data of the terminal device indicates the reader roles that the terminal device is allowed to serve.
[0534] In a possible implementation, the transceiver unit 920 is configured to:
[0535] Sending one or more reader roles authorized for the terminal device to the access network device.
[0536] In a possible implementation, the acquiring of one or more reader roles authorized by the terminal device, the processing unit 910 is configured to:
[0537] The transceiver unit 920 receives one or more reader roles authorized for the terminal device from the access network device.
[0538] In a possible implementation, before receiving the one or more reader roles authorized for the terminal device from the access network device, the transceiver unit 920 is configured to:
[0539] Send the capability information of the terminal device to the access network device.
[0540] In a possible implementation, the transceiver unit 920 is configured to:
[0541] The capability information is received from the terminal device.
[0542] In a possible implementation, the transceiver unit 920 is configured to:
[0543] At least one cell identifier is sent to the terminal device, where the cell corresponding to the at least one cell identifier includes a first cell, and the cell corresponding to the at least one cell identifier is a cell that supports the Internet of Things service. The at least one cell identifier is used for cell reselection or cell switching to facilitate the terminal device to access the first cell.
[0544] In a possible implementation, the first core network device is a first core network device that supports the Internet of Things service.
[0545] In a possible implementation, the target reader role or the one or more reader roles authorized by the terminal device include the following roles: auxiliary reader, uplink auxiliary reader, downlink auxiliary reader, reader, or reader providing carrier assistance.
[0546] When the communication apparatus 900 is used to implement the function of the first core network device in any one of the method embodiments shown in FIG. 5 to FIG. 8 , in another implementation:
[0547] The processing unit 910 is configured to obtain one or more reader roles authorized by the terminal device;
[0548] The transceiver unit 920 is configured to send one or more reader roles authorized for the terminal device to the access network device; the one or more authorized reader roles are used to determine a target reader role.
[0549] In a possible implementation, when obtaining one or more reader roles authorized by the terminal device, the processing unit 910 is configured to:
[0550] Determine one or more reader roles authorized for the terminal device based on the capability information of the terminal device and / or the contract data of the terminal device, where the capability information of the terminal device indicates the reader capabilities supported by the terminal device, and the contract data of the terminal device indicates the reader roles that the terminal device is allowed to serve.
[0551] In a possible implementation, the transceiver unit 920 is further configured to:
[0552] The capability information is received from the terminal device.
[0553] In a possible implementation, the transceiver unit 920 is further configured to:
[0554] Receive the subscription data of the terminal device from the second core network device.
[0555] In a possible implementation, the transceiver unit 920 is further configured to:
[0556] One or more reader roles authorized for the terminal device are sent to the terminal device.
[0557] In a possible implementation, the transceiver unit 920 is further configured to:
[0558] At least one cell identifier is sent to the terminal device, where the cell corresponding to the at least one cell identifier includes a first cell, and the cell corresponding to the at least one cell identifier is a cell that supports the Internet of Things service. The at least one cell identifier is used for cell reselection or cell switching to facilitate the terminal device to access the first cell.
[0559] In a possible implementation, the first core network device is a first core network device that supports the Internet of Things service.
[0560] In a possible implementation, the target reader role or the one or more reader roles authorized by the terminal device include the following roles: auxiliary reader, uplink auxiliary reader, downlink auxiliary reader, reader, or reader providing carrier assistance.
[0561] In one possible implementation, the first core network device includes an access management device, a tag management device, an environmental energy acquisition Internet of Things management device, a unified data management device, a user data storage device, a network capability exposure device, a policy control device, or a session management device.
[0562] In one possible implementation, the second core network device includes a unified data management device, a user data storage device, a network capability exposure device, a policy control device, a session management device, a tag management device, an environmental energy enabling Internet of Things device, an environmental energy acquisition Internet of Things terminal management device or an authentication service device.
[0563] For a more detailed description of the processing unit 910 and the transceiver unit 920 , reference may be made to the relevant description in any of the method embodiments shown in FIG. 5 to FIG. 8 .
[0564] As shown in Figure 10, communication device 1000 includes a processor 1010 and an interface circuit 1020. Processor 1010 and interface circuit 1020 are coupled to each other. It will be appreciated that interface circuit 1020 may be a transceiver or an input / output interface. Optionally, communication device 1000 may further include a memory 1030 for storing instructions executed by processor 1010, input data required by processor 1010 to execute instructions, or data generated by processor 1010 after executing instructions.
[0565] When the communication device 1000 is used to implement any of the methods shown in FIG. 5 to FIG. 8 , the processor 1010 is used to implement the functions of the processing unit 910 , and the interface circuit 1020 is used to implement the functions of the transceiver unit 920 .
[0566] When the communication device is a chip used in a terminal device, the terminal device chip implements the functions of the terminal device in the above method embodiment. The terminal device chip receives information sent to the terminal device by the access network device through other modules in the terminal device (such as a radio frequency module or antenna); or the terminal device chip sends information to other modules in the terminal device (such as a radio frequency module or antenna), and the information is sent by the terminal device to the access network device.
[0567] When the above-mentioned communication device is a module applied to an access network device, the access network device module implements the functions of the access network device in the above-mentioned method embodiment. The access network device module receives information from other modules in the access network device (such as a radio frequency module or an antenna), and the information is sent by the terminal device to the access network device; or, the access network device module sends information to other modules in the access network device (such as a radio frequency module or an antenna), and the information is sent by the access network device to the terminal device. The access network device module here can be a baseband chip of the access network device, or it can be a CU, DU or other module, or it can be a device under the open radio access network (O-RAN) architecture, such as an open CU, open DU and other devices.
[0568] It is understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.
[0569] The method steps in the embodiments of the present application can be implemented in hardware or in software instructions that can be executed by a processor. The software instructions can be composed of corresponding software modules, and the software modules can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disk, mobile hard disk, CD-ROM or any other form of storage medium well known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. The storage medium can also be an integral part of the processor. The processor and storage medium can be located in an ASIC. In addition, the ASIC can be located in an access network device or a terminal device. The processor and storage medium can also exist in the access network device or the terminal device as discrete components.
[0570] In the above embodiments, all or part of the embodiments may be implemented using software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are performed in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device, or other programmable device. The computer program or instructions may be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions may be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; an optical medium, such as a digital video disk; or a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or nonvolatile storage medium, or may include both volatile and nonvolatile types of storage media.
[0571] In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.
[0572] It is understood that the various numbers used in the embodiments of this application are merely for ease of description and are not intended to limit the scope of the embodiments of this application. The order of the sequence numbers of the above-mentioned processes does not necessarily imply a specific order of execution; the order of execution of the processes should be determined by their functions and inherent logic.
Claims
1. A communication method, It is characterized in that include: Determine the target reader role of the terminal device; First information is sent to the terminal device, where the first information instructs the terminal device to perform the target reader role.
2. The method according to claim 1, It is characterized in that The determining of the target reader role of the terminal device includes: Obtaining one or more reader roles authorized by the terminal device; A target reader role of the terminal device is determined from the one or more authorized reader roles.
3. The method according to claim 2, It is characterized in that The obtaining of one or more reader roles authorized by the terminal device includes: One or more reader roles authorized for the terminal device are received from the first core network device.
4. The method according to claim 2, It is characterized in that The obtaining of one or more reader roles authorized by the terminal device includes: Determine one or more reader roles authorized for the terminal device according to second information; the second information includes one or more of the following information: capability information of the terminal device and / or subscription data of the terminal device; The capability information of the terminal device indicates the reader roles supported by the terminal device, and the contract data of the terminal device indicates the reader roles that the terminal device is allowed to serve.
5. The method according to claim 4, It is characterized in that The method further comprises: One or more reader roles authorized for the terminal device are sent to the first core network device, so that the first core network device sends the one or more reader roles authorized for the terminal device to the terminal device.
6. The method according to any one of claims 2 to 5, It is characterized in that The method further comprises: Acquire third information; the third information includes one or more of the following information: capability information of the terminal device, a first request message from the terminal device, a link state between the access network device and the Internet of Things terminal, or a wireless resource state of the access network device; wherein the capability information of the terminal device indicates a reader role supported by the terminal device, and the first request message is used to request to be a first reader role; The determining the target reader role of the terminal device from the one or more authorized reader roles includes: The target reader role is determined from the one or more authorized reader roles according to the third information.
7. The method according to claim 6, It is characterized in that The determining the target reader role of the terminal device from the one or more authorized reader roles according to the third information includes: determining the reader role supported by the terminal device indicated by the capability information of the terminal device among the one or more authorized reader roles as the target reader role; or, determining the first reader role among the one or more authorized reader roles as the target reader role; or, When the uplink budget between the access network device and the Internet of Things terminal is lower than the downlink budget, and the authorized one or more reader roles include an uplink auxiliary reader, determining the target reader role as an uplink auxiliary reader; or, When the downlink budget between the access network device and the Internet of Things terminal is lower than the uplink budget, and the authorized one or more reader roles include a downlink auxiliary reader, the target reader role is determined to be a downlink auxiliary reader.
8. The method according to claim 1, It is characterized in that The determining of the target reader role of the terminal device includes: Acquire fourth information; the fourth information includes one or more of the following information: capability information of the terminal device, subscription data of the terminal device, a first request message from the terminal device, a link state between the access network device and the Internet of Things terminal, or a wireless resource state of the access network device; wherein the capability information of the terminal device indicates a reader role supported by the terminal device, and the first request message is used to request to be a first reader role; The target reader role is determined according to the fourth information.
9. The method according to any one of claims 4 to 8, It is characterized in that The method further comprises: receiving capability information of the terminal device sent by a first core network device, wherein the first core network device supports Internet of Things service management; or, Receive capability information of the terminal device sent by the terminal device.
10. The method according to claim 9, It is characterized in that The receiving capability information of the terminal device sent by the first core network device includes: During the registration process, a context request or a terminal device capability check request sent by the first core network device is received, and the context request or the terminal device capability check request includes capability information of the terminal device.
11. The method according to any one of claims 1 to 10, It is characterized in that The method further comprises: Receiving first indication information from the terminal device, where the first indication information indicates that the terminal device supports an Internet of Things service; A first core network device that supports management of the Internet of Things service is selected according to the first indication information.
12. The method according to any one of claims 1 to 10, It is characterized in that The method further comprises: When the first cell accessed by the terminal device supports the Internet of Things service, the first core network device is selected according to the first cell accessed by the terminal device, and the first core network device supports the management of the Internet of Things service.
13. The method according to any one of claims 1 to 12, It is characterized in that The method further comprises: Broadcast second indication information, wherein the second indication information indicates that the first cell supports the Internet of Things service, or the second indication information indicates that one or more cells of the access network device support the Internet of Things service, so that the terminal device accesses the first cell supporting the Internet of Things service according to the second indication information, and the one or more cells include the first cell.
14. The method according to any one of claims 1 to 13, It is characterized in that The method further comprises: Resource configuration information is sent to the terminal device, where the resource configuration information is used by the terminal device to perform the target reader role.
15. The method according to claim 14, It is characterized in that The resource configuration information includes one or more of the following information: frequency point information, frequency band information, transmission power, transmission bandwidth, transmission rate, or execution duration.
16. The method according to any one of claims 1 to 15, It is characterized in that After sending the first information to the terminal device, the method further includes: Fifth information is received from the terminal device, where the fifth information indicates whether the terminal device accepts to perform the target reader role.
17. The method according to any one of claims 1 to 16, It is characterized in that The target reader role or the one or more reader roles authorized by the terminal device include the following roles: an uplink auxiliary reader, a downlink auxiliary reader, a reader, or a reader providing carrier assistance.
18. A communication method, It is characterized in that include: Sending a first request message to the access network device, where the first request message is used to request to serve as a first reader role; First information is received from an access network device, where the first information indicates that the terminal device performs a target reader role.
19. The method according to claim 18, It is characterized in that The method further comprises: Receiving one or more reader roles authorized for the terminal device from the first core network device; The first reader role is determined according to one or more reader roles authorized by the terminal device.
20. The method according to claim 18 or 19, It is characterized in that The method further comprises: The capability information of the terminal device is sent to the access network device, where the capability information of the terminal device indicates reader capabilities supported by the terminal device, and the capability information of the terminal device is used to determine the target reader role.
21. The method according to any one of claims 18 to 20, It is characterized in that The method further comprises: A first indication information is sent to the access network device, wherein the first indication information indicates that the terminal device supports the Internet of Things service; the first indication information is used to determine a first core network device that supports the management of the Internet of Things service.
22. The method according to any one of claims 18 to 21, It is characterized in that The cell accessed by the terminal device is a second cell, and the second cell does not support the Internet of Things service; The method further comprises: Receiving second indication information from the access network device, where the second indication information indicates that the first cell supports the Internet of Things service, or the second indication information indicates that one or more cells of the access network device support the Internet of Things service, where the one or more cells include the first cell; Perform cell reselection or cell switching according to the second indication information to access the first cell.
23. The method according to any one of claims 18 to 21, It is characterized in that The cell accessed by the terminal device is the second cell of the access network device, and the second cell does not support the Internet of Things service; The method further comprises: Receiving at least one cell identifier from the first core network device, where the cell corresponding to the at least one cell identifier is a cell supporting the Internet of Things service under the access network device, and the cell corresponding to the at least one cell identifier includes a first cell; Perform cell reselection or cell handover according to the at least one cell identifier to access the first cell.
24. The method according to any one of claims 18 to 21, It is characterized in that The cell accessed by the terminal device is the second cell, and all cells under the access network device where the second cell is located do not support the Internet of Things service; The method further comprises: Receiving at least one cell identifier from the first core network device, where the cell corresponding to the at least one cell identifier is a cell supporting the Internet of Things service under the access network device, and the cell corresponding to the at least one cell identifier includes a first cell; Perform cell reselection or cell handover according to the at least one cell identifier to access the first cell.
25. The method according to any one of claims 18 to 24, It is characterized in that The method further comprises: Resource configuration information is received from the access network device, where the resource configuration information is used by the terminal device to perform the target reader role.
26. The method according to claim 25, It is characterized in that The resource configuration information includes one or more of the following information: frequency point information, frequency band information, transmission power, transmission bandwidth, transmission rate, or execution duration.
27. The method according to any one of claims 18 to 26, It is characterized in that After receiving the first information from the access network device, the method further includes: Sending fifth information to the access network device, wherein the fifth information indicates whether the terminal device accepts to execute the target reader role.
28. The method according to any one of claims 18 to 27, It is characterized in that The target reader role or the one or more reader roles authorized by the terminal device include the following roles: an uplink auxiliary reader, a downlink auxiliary reader, a reader, or a reader providing carrier assistance.
29. A communication method, It is characterized in that include: Obtain one or more reader roles authorized by the terminal device; One or more reader roles authorized for the terminal device are sent to the terminal device; the one or more authorized reader roles are used to determine a target reader role.
30. The method according to claim 29, It is characterized in that The step of obtaining one or more reader roles authorized by the terminal device includes: Determine one or more reader roles authorized for the terminal device based on the capability information of the terminal device and / or the contract data of the terminal device, wherein the capability information of the terminal device indicates the reader capabilities supported by the terminal device, and the contract data of the terminal device indicates the reader roles that the terminal device is allowed to serve.
31. The method according to claim 30, It is characterized in that The method further comprises: Sending one or more reader roles authorized for the terminal device to the access network device.
32. The method according to claim 29, It is characterized in that The step of obtaining one or more reader roles authorized by the terminal device includes: Receive one or more reader roles authorized for the terminal device from the access network device.
33. The method according to claim 32, It is characterized in that Before receiving the one or more reader roles authorized for the terminal device from the access network device, the method further includes: Send capability information of the terminal device to the access network device.
34. The method according to claim 30, 31 or 33, It is characterized in that The method further comprises: The capability information is received from the terminal device.
35. The method according to any one of claims 29 to 34, It is characterized in that The method further comprises: At least one cell identifier is sent to the terminal device, the cell corresponding to the at least one cell identifier includes a first cell, the cell corresponding to the at least one cell identifier is a cell supporting the Internet of Things service, and the at least one cell identifier is used for cell reselection or cell switching to facilitate the terminal device to access the first cell.
36. The method according to any one of claims 29 to 35, It is characterized in that The first core network device is a first core network device that supports the Internet of Things service.
37. The method according to any one of claims 29 to 36, It is characterized in that The target reader role or the one or more reader roles authorized by the terminal device include the following roles: an uplink auxiliary reader, a downlink auxiliary reader, a reader, or a reader providing carrier assistance.
38. A communication device, comprising a unit or module for executing the method as described in any one of claims 1-17, or, comprising a unit or module for executing the method as described in any one of claims 18-28, or, comprising a unit or module for executing the method as described in any one of claims 29-37.
39. A communication device, It is characterized in that It includes a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor or send signals from the processor to other communication devices outside the communication device, and the processor is used to implement the method as described in any one of claims 1 to 17 through a logic circuit or execute code instructions, or to implement the method as described in any one of claims 18 to 28, or to implement the method as described in any one of claims 29 to 37.
40. A computer readable storage medium, It is characterized in that The storage medium stores a computer program or instruction. When the computer program or instruction is executed by the communication device, it implements the method as described in any one of claims 1 to 17, or implements the method as described in any one of claims 18 to 28, or implements the method as described in any one of claims 29 to 37.
41. A computer program product, It is characterized in that The method comprises a computer program code, which, when executed on a computer, implements the method according to any one of claims 1 to 17, or implements the method according to any one of claims 18 to 28, or implements the method according to any one of claims 29 to 37.
Citation Information
Patent Citations
Communication method and related device
CN119052835A
Data exchange method based on radio frequency recognition technology
CN101197684A
Thing internet system for electrical operation routine inspection
CN102594923A
Communication method and device
CN116056028A
Method and system for shifting a communication session
US20180338008A1
Cited By
Methods and apparatus for communication in internet of things network
WO2026118189A1
