CN117280725A

CN117280725A - Access control method and terminal

Info

Publication number: CN117280725A
Application number: CN202080101809.7A
Authority: CN
Inventors: 杨皓睿
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2020-07-28
Filing date: 2020-07-28
Publication date: 2023-12-22
Also published as: WO2022021067A1

Abstract

The application relates to an access control method and a terminal. The access control method comprises the following steps: the relay terminal acquires an access type AC corresponding to a service for relaying for the remote terminal; the relay terminal performs access control checking according to the AC and the unified access control UAC parameters. The embodiment of the application can perform unified access control on the service which needs to be relayed by the remote terminal through the relay terminal.

Description

Access control method and terminal

Technical Field

The present application relates to the field of communications, and more particularly, to an access control method and a terminal.

Background

With the development of fifth Generation communication (5 th-Generation, 5G) applications, network control interaction service (Network Controlled Interactive Services, NCIS) services are introduced into standards as a new service form for related standardized services.

The NCIS service is mainly aimed at applications such as augmented Reality (Augmented Reality, AR), virtual Reality (VR), games, etc., and has high requirements on service quality such as rate, time delay, packet loss rate, high-speed codec, etc. For example: for VR games, it is desirable to achieve a 10Gbps rate, with no more than 10E-4 (10 to the power of-4) packet loss. The session established for the NCIS service is an NCIS session, and User Equipments (UEs) in the same NCIS session may be considered to form an NCIS group, for example: team formation in game.

Communication of a remote (remote) UE is served through a terminal-to-network relay (UE-to-network relay) to provide a more high-speed, reliable, etc. service, and coverage can be further expanded. For example: remote UEs that are not in coverage may be served by relay (relay) UEs. How to perform unified access control on a service that needs to be relayed by a remote UE through a relay UE is needed to be solved.

Disclosure of Invention

The embodiment of the application provides an access control method and a terminal, which can uniformly access control a service which needs to be relayed by a remote terminal through a relay terminal.

The embodiment of the application provides an access control method, which comprises the following steps:

the relay terminal acquires an access type AC corresponding to a service for relaying for the remote terminal;

the relay terminal performs access control checking according to the AC and the unified access control UAC parameters.

and the remote terminal sends an access type AC corresponding to the service for relaying the remote terminal to the relay terminal so as to perform access control check at the relay terminal according to the AC and the unified access control UAC parameter.

The embodiment of the application provides a terminal, which comprises:

the acquisition module is used for acquiring an access type AC corresponding to the service relayed by the remote terminal;

And the checking module is used for performing access control checking according to the AC and the unified access control UAC parameters.

The embodiment of the application provides a terminal, which comprises:

and the sending module is used for sending an access type AC corresponding to the service for relaying the remote terminal to the relay terminal so as to perform access control check on the relay terminal according to the AC and the unified access control UAC parameter.

The embodiment of the application provides a terminal, which comprises a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory so as to enable the terminal to execute an access control method executed by the relay terminal.

The embodiment of the application provides a terminal, which comprises a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory so that the terminal executes an access control method executed by the remote terminal.

The embodiment of the application provides a chip for realizing the access control method.

Specifically, the chip includes: and a processor for calling and running the computer program from the memory, so that the device installed with the chip executes the access control method executed by the relay terminal.

Specifically, the chip includes: and a processor for calling and running the computer program from the memory, so that the device mounted with the chip executes the access control method executed by the remote terminal.

The embodiment of the application provides a computer readable storage medium for storing a computer program which, when executed by a device, causes the device to execute an access control method executed by a relay terminal.

The embodiments of the present application provide a computer-readable storage medium storing a computer program that, when executed by a device, causes the device to perform an access control method performed by a remote terminal.

Embodiments of the present application provide a computer program product including computer program instructions that cause a computer to perform an access control method performed by a relay terminal.

Embodiments of the present application provide a computer program product comprising computer program instructions for causing a computer to perform an access control method performed by a remote terminal.

The embodiments of the present application provide a computer program that, when run on a computer, causes the computer to execute an access control method executed by a relay terminal.

The embodiments of the present application provide a computer program which, when run on a computer, causes the computer to perform an access control method performed by a remote terminal.

According to the embodiment of the application, the access type corresponding to the service for relaying the remote terminal and the unified access control parameter are acquired through the relay terminal, access control checking is carried out, and unified access control can be carried out on the service which needs to be relayed by the remote terminal through the relay terminal.

Drawings

Fig. 1 is a schematic diagram of an application scenario according to an embodiment of the present application.

Fig. 2 is a schematic diagram of a system architecture of ProSe UE-to-Network Relay.

Fig. 3 is a schematic flow chart of an access control method according to an embodiment of the present application.

Fig. 4 is a schematic flow chart of an access control method according to another embodiment of the present application.

Fig. 5 is a flow chart of one example of an access control method according to another embodiment of the present application.

Fig. 6 is a flow chart of another example of an access control method according to another embodiment of the present application.

Fig. 7 is a schematic block diagram of a terminal according to an embodiment of the present application.

Fig. 8 is a schematic block diagram of a terminal according to another embodiment of the present application.

Fig. 9 is a schematic block diagram of a terminal according to another embodiment of the present application.

Fig. 10 is a schematic block diagram of a communication device according to an embodiment of the present application.

Fig. 11 is a schematic block diagram of a chip according to an embodiment of the present application.

Fig. 12 is a schematic block diagram of a communication system according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.

The technical solution of the embodiment of the application can be applied to various communication systems, for example: global system for mobile communications (Global System of Mobile communication, GSM), code division multiple access (Code Division Multiple Access, CDMA) system, wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) system, general packet Radio service (General Packet Radio Service, GPRS), long term evolution (Long Term Evolution, LTE) system, advanced long term evolution (Advanced long term evolution, LTE-a) system, new Radio (NR) system, evolved system of NR system, LTE-based access to unlicensed spectrum, LTE-U) system on unlicensed spectrum, NR (NR-based access to unlicensed spectrum, NR-U) system on unlicensed spectrum, non-terrestrial communication network (Non-Terrestrial Networks, NTN) system, universal mobile communication system (Universal Mobile Telecommunication System, UMTS), wireless local area network (Wireless Local Area Networks, WLAN), wireless fidelity (Wireless Fidelity, wiFi), fifth Generation communication (5 th-Generation, 5G) system, or other communication system, etc.

Generally, the number of connections supported by the conventional communication system is limited and easy to implement, however, with the development of communication technology, the mobile communication system will support not only conventional communication but also, for example, device-to-Device (D2D) communication, machine-to-machine (Machine to Machine, M2M) communication, machine type communication (Machine Type Communication, MTC), inter-vehicle (Vehicle to Vehicle, V2V) communication, or internet of vehicles (Vehicle to everything, V2X) communication, etc., and the embodiments of the present application may also be applied to these communication systems.

Optionally, the communication system in the embodiment of the present application may be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, a dual connectivity (Dual Connectivity, DC) scenario, and a Stand Alone (SA) fabric scenario.

Optionally, the communication system in the embodiments of the present application may be applied to unlicensed spectrum, where unlicensed spectrum may also be considered as shared spectrum; alternatively, the communication system in the embodiments of the present application may also be applied to licensed spectrum, where licensed spectrum may also be considered as non-shared spectrum.

Embodiments of the present application describe various embodiments in connection with network devices and terminal devices, where a terminal device may also be referred to as a User Equipment (UE), access terminal, subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, user Equipment, or the like.

The terminal device may be a Station (ST) in a WLAN, may be a cellular telephone, a cordless telephone, a session initiation protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital assistant (Personal Digital Assistant, PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle device, a wearable device, a terminal device in a next generation communication system such as an NR network, or a terminal device in a future evolved public land mobile network (Public Land Mobile Network, PLMN) network, etc.

In embodiments of the present application, the terminal device may be deployed on land, including indoor or outdoor, hand-held, wearable or vehicle-mounted; can also be deployed on the water surface (such as ships, etc.); but may also be deployed in the air (e.g., on aircraft, balloon, satellite, etc.).

In the embodiment of the present application, the terminal device may be a Mobile Phone (Mobile Phone), a tablet computer (Pad), a computer with a wireless transceiving function, a Virtual Reality (VR) terminal device, an augmented Reality (Augmented Reality, AR) terminal device, a wireless terminal device in industrial control (industrial control), a wireless terminal device in unmanned driving (self driving), a wireless terminal device in remote medical (remote medical), a wireless terminal device in smart grid (smart grid), a wireless terminal device in transportation security (transportation safety), a wireless terminal device in smart city (smart city), or a wireless terminal device in smart home (smart home), and the like.

By way of example, and not limitation, in embodiments of the present application, the terminal device may also be a wearable device. The wearable device can also be called as a wearable intelligent device, and is a generic name for intelligently designing daily wear by applying wearable technology and developing wearable devices, such as glasses, gloves, watches, clothes, shoes and the like. The wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also can realize a powerful function through software support, data interaction and cloud interaction. The generalized wearable intelligent device includes full functionality, large size, and may not rely on the smart phone to implement complete or partial functionality, such as: smart watches or smart glasses, etc., and focus on only certain types of application functions, and need to be used in combination with other devices, such as smart phones, for example, various smart bracelets, smart jewelry, etc. for physical sign monitoring.

In this embodiment of the present application, the network device may be a device for communicating with a mobile device, where the network device may be an Access Point (AP) in WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, a relay station or an Access Point, a vehicle device, a wearable device, and a network device (gNB) in an NR network, or a network device in a PLMN network for future evolution, or a network device in an NTN network, etc.

By way of example and not limitation, in embodiments of the present application, a network device may have a mobile nature, e.g., the network device may be a mobile device. Alternatively, the network device may be a satellite, a balloon station. For example, the satellite may be a Low Earth Orbit (LEO) satellite, a medium earth orbit (medium earth orbit, MEO) satellite, a geosynchronous orbit (geostationary earth orbit, GEO) satellite, a high elliptical orbit (High Elliptical Orbit, HEO) satellite, or the like. Alternatively, the network device may be a base station disposed on land, in a water area, or the like.

In this embodiment of the present application, a network device may provide a service for a cell, where a terminal device communicates with the network device through a transmission resource (e.g., a frequency domain resource, or a spectrum resource) used by the cell, where the cell may be a cell corresponding to a network device (e.g., a base station), and the cell may belong to a macro base station, or may belong to a base station corresponding to a Small cell (Small cell), where the Small cell may include: urban cells (Metro cells), micro cells (Micro cells), pico cells (Pico cells), femto cells (Femto cells) and the like, and the small cells have the characteristics of small coverage area and low transmitting power and are suitable for providing high-rate data transmission services.

Fig. 1 schematically illustrates a communication system 100. The communication system comprises one network device 110 and two terminal devices 120. Alternatively, the communication system 100 may include a plurality of network devices 110, and the coverage area of each network device 110 may include other numbers of terminal devices 120, which are not limited in this embodiment of the present application.

Optionally, the communication system 100 may further include other network entities such as a mobility management entity (Mobility Management Entity, MME), an access and mobility management function (Access and Mobility Management Function, AMF), and the embodiment of the present application is not limited thereto.

The network device may further include an access network device and a core network device. I.e. the wireless communication system further comprises a plurality of core networks for communicating with the access network devices. The access network device may be a long-term evolution (LTE) system, a next-generation (NR) system, or an evolved base station (evolutional node B, abbreviated as eNB or e-NodeB) macro base station, a micro base station (also called "small base station"), a pico base station, an Access Point (AP), a transmission point (transmission point, TP), a new generation base station (new generation Node B, gNodeB), or the like in an licensed assisted access long-term evolution (LAA-LTE) system.

It should be understood that a device having a communication function in a network/system in an embodiment of the present application may be referred to as a communication device. Taking the communication system shown in fig. 1 as an example, the communication device may include a network device and a terminal device with a communication function, where the network device and the terminal device may be specific devices described in the embodiments of the present invention, and are not described herein again; the communication device may also include other devices in the communication system, such as a network controller, a mobility management entity, and other network entities, which are not limited in this embodiment of the present application.

It should be understood that the terms "system" and "network" are used interchangeably herein. The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.

It should be understood that, in the embodiments of the present application, the "indication" may be a direct indication, an indirect indication, or an indication having an association relationship. For example, a indicates B, which may mean that a indicates B directly, e.g., B may be obtained by a; it may also indicate that a indicates B indirectly, e.g. a indicates C, B may be obtained by C; it may also be indicated that there is an association between a and B.

In the description of the embodiments of the present application, the term "corresponding" may indicate that there is a direct correspondence or an indirect correspondence between the two, or may indicate that there is an association between the two, or may indicate a relationship between the two and the indicated, configured, or the like.

In order to facilitate understanding of the technical solutions of the embodiments of the present application, the following description is given of related technologies of the embodiments of the present application, and the following related technologies may be optionally combined with the technical solutions of the embodiments of the present application as an alternative, which all belong to the protection scope of the embodiments of the present application.

As shown in fig. 2, a system architecture for a (ProSe-Services, proSe) UE-to-network relay (ProSe UE-to-network relay) in a 4G network is provided. A Remote terminal (Remote UE) is connected to a ProSe UE-to-Network Relay (ProSe UE-to-Network Relay) through a PC5 interface, and the Relay terminal is connected to a RAN (e.g., E-UTRA, NR base station, etc.) through a Uu interface. The Non-Access Stratum (NAS) accesses EPC (Evolved Packet Core )/5 GC (5G core) through SGi interface.

For the 5G terminal-to-network relay (UE-to-network relay) architecture, there are two possible architectural approaches, either the L3 (Layer-3, layer three) architecture or the L2 (Layer-2, layer two) architecture.

The main differences between the L3 architecture and the L2 architecture are as follows:

under the L3 architecture, a Remote (Remote) UE does not need to register in the network, and may transmit data only through a Relay (Relay UE), such as ProSe terminal-to-network Relay (ProSe UE-to-network Relay), similar to the architecture under the 4G network.

Under the L2 architecture, the remote UE and the ordinary UE are similar, and the required procedures (such as registration and session establishment) are performed. However, data and signaling under the L2 architecture is transmitted to a base station, such as an eNB, through a relay UE.

In the procedure of ProSe UE-to-network relay in EPS (Evolved Packet System ), the relay UE can establish a new PDN connection for relay. The relay UE needs to use a suitable public data network (Public Data Network, PDN) connection (connection) in order for the relay UE to transmit relay data for the remote UE. Which PDN connection is used to transmit relay data is determined by the relay UE. For example, the relay UE may transmit all relay data using one dedicated PDN connection.

In the L3 architecture under the 5G network, the remote UE may also establish an appropriate PDU session (session) for transmitting the data of the remote UE in a similar manner. Illustratively, the upstream data flow may include: remote UE- > relay UE- > RAN- >5GC- > DNN- > application server (Application server). The downlink is reversed.

In the related protocol, when the UE needs to access to the network, unified access control (Unified Access Control, UAC) is required. The NAS layer of the UE may determine an Access type (AC) according to a service triggering the Access network, and a relationship between the service and the AC may be stored as a correspondence table. The correspondence table may include rules (Rule), type of Access attempt (Type of Access attempt), requirements to be satisfied (Requirements to be met), access type (Access Category), and the like. For example, the type of access attempt corresponds to Emergency service (Emergency), ac=2. As another example, the type of access attempt applies to an access attempt (Access attempt for delay tolerant service) for delay tolerant services, ac=1. The type of access attempt corresponds to MO IMS registration related signaling (MO IMS registration related signalling), ac=9. As another example, the type of access attempt corresponds to MO MMTel voice call (MO MMTel voice call), ac=4. As another example, the type of access attempt corresponds to MO MMTel voice call (MO MMTel video call), ac=5. And if the type of access attempt corresponds to NAS short message or IP short message (MO SMS over NAS or MO SMSoIP), ac=6. The specific AC is merely an example, and the correspondence table may be specifically set according to the requirements of the actual application scenario. Further, the correspondence table may be stored in the relay terminal and the remote terminal.

After the NAS layer determines the AC, it determines the RRC establishment cause based on the AC (establishment cause), and sends the AC and the RRC establishment cause to the RRC layer. The AC and RRC establishment cause may be sent to the RRC layer together or separately. The RRC layer judges whether the access is possible or not according to the parameters corresponding to the AC broadcasted in the system information. Each AC corresponds to a threshold and the RRC layer can determine a random number between 0 and 1. If the random number is less than the critical value, indicating that the access is available; if it is greater than the threshold, it indicates that access is denied and a timer, such as T390, is calculated. The timer binds to the AC and the AC's access control fails or is disabled before expiration. After the RRC layer judges, the NAS layer is informed of the result.

The occasions when the UE needs to make a UAC may include a variety of, for example: the UE enters a connection state from an Idle state; or UAC is carried out for specific services in a connection state, and corresponding ACs are needed to be found for all services in an idle state. For example, the UAC need only be performed for the following traffic in the connected state:

-IMS related services (related services);

SMS (SMS over NAS) on NAS;

-PDU session establishment (session establishment);

-PDU session modification (session modification);

-Re-activating or restoring user plane resources (Re-activate or resume user plane resources of PDU session) of the PDU session.

In the 4G network, only the L3 architecture is provided, and the remote UE does not need to perform access control because it does not need to directly access the network. Because the data of the remote UE is relayed by the relay UE, the relay UE uses MO (Mobile Originated ) data (mo_data) for all traffic of the remote UE.

Since the relay UE may trigger access control by the relay requirement of the remote UE, the embodiments of the present application may provide a specific access control method to perform UAC for the service of the remote UE.

Fig. 3 is a schematic flow chart diagram of an access control method 200 according to an embodiment of the present application. The method may alternatively be applied to the system shown in fig. 1, but is not limited thereto. The method includes at least some of the following.

S210, the relay terminal acquires an Access Category (AC) corresponding to a service for relaying for the remote terminal;

s220, the relay terminal performs Access control checking according to the AC and Unified Access control (control UAC) parameters.

In the embodiment of the present application, the correspondence between various services and access types may be preset. If the relay terminal receives the service of the remote terminal, which needs to be relayed, the access type corresponding to the service can be determined according to the corresponding relation. For example: the AC of the emergency service is 2, the AC of the voice call service is 4, the AC of the video call service is 5, etc.

Optionally, in an embodiment of the present application, the relay terminal receives a system message, where the system message includes the UAC parameter. Specifically, the relay terminal receives a system message including UAC parameters from the network.

Optionally, in the embodiment of the present application, the relay terminal performs access control checking according to the AC and the unified access control UAC parameter, including: the relay terminal obtains UAC parameters corresponding to the AC, and performs access control check according to the UAC parameters corresponding to the AC.

Specifically, after the relay terminal acquires the AC, the UAC parameter corresponding to the AC may be found in a system message from the network. The UAC parameters may include a critical value corresponding to AC (called UAC-BarringFactor in the standard) and UAC-BarringTime corresponding to AC. Then, access control checks are made using the AC and UAC parameters. For example: the UE determines a random number between 0 and 1, and considers access to be allowed if the random number is smaller than the corresponding uac-barrenfactor of the AC, otherwise considers access to be forbidden. If access is disabled, a random number between 0 and 1 is determined, for example, the T390 value is calculated according to the following disclosure:

T390＝(0.7+0.6×rand)×uac-BarringTime

optionally, in an embodiment of the present application, the relay terminal receives the data packet from the remote terminal.

Optionally, in the embodiment of the present application, the obtaining, by the relay terminal, an AC corresponding to a service for relaying for the remote terminal includes: the relay terminal analyzes the packet header of the data packet to obtain the AC.

In one example, if the remote terminal has an AC added to the header of the data packet. After the relay terminal receives the data packet from the remote terminal, the packet header can be parsed to obtain the AC.

Optionally, in an embodiment of the present application, the acquiring, by the relay terminal, the AC of the remote terminal includes: the relay terminal matches the data packet by using a data descriptor in a user equipment routing policy (User Equipment Routing Selection Policy, URSP) of the relay terminal to obtain the characteristic of a packet data unit PDU session (session) of the data packet; the relay terminal determines the AC according to characteristics of the PDU session.

In one example, if the relay terminal parses the header of a data packet from the remote terminal, and cannot acquire an AC, the data packet may be matched to obtain the PDU session characteristics of the data packet using a data descriptor in the urs or local configuration (local configuration). The AC is then determined based on the characteristics of the PDU session.

Optionally, in an embodiment of the present application, the relay terminal determines the AC according to characteristics of the PDU session, including at least one of the following manners:

Mode 1: in case the characteristics of the PDU session correspond to emergency services, the AC is a first identification for identifying the emergency services. For example, the characteristics of the PDU session correspond to emergency traffic, ac=2.

Mode 2: in case the characteristics of the PDU session correspond to a generic PDU session, the AC is a second identification for identifying the generic session. For example, the characteristics of a PDU session correspond to a normal PDU session, such as a session for transmitting internet data, ac=7.

Mode 3: in case the characteristics of the PDU session correspond to internet protocol (Internet Protocol, IP) multimedia subsystem (IP Multimedia Subsystem, IMS) signaling and/or data, the AC is determined according to parameters of a quality of service (QoS) flow of the transmitted data.

Mode 4: in case the PDU session is used for transmitting IMS signaling and/or data, the AC is determined from the service coding of the QoS flow of the transmitted data.

Optionally, in the embodiment of the present application, in mode 3, the determining the AC according to the parameters of the QoS flow of the transmitted data includes at least one of:

determining that the AC is a third identifier for identifying IMS signaling under the condition that the QoS flow is used for transmitting the IMS signaling according to the parameters of the QoS flow of the transmitted data;

According to the parameters of the QoS flow of the transmitted data, determining that the AC is a fourth identifier for identifying the voice call under the condition that the QoS flow is used for transmitting the IMS voice call;

according to the parameters of the QoS flow of the transmitted data, determining that the AC is a fifth identifier for identifying the video call under the condition that the QoS flow is used for transmitting the IMS video call;

and determining that the AC is a sixth identifier for identifying the IP short message in the case that the QoS flow is used for transmitting the IP short message according to the parameters of the QoS flow of the transmitted data.

For example, after receiving the data packet, the relay terminal may match a packet filter (packet filter) of the QoS flow to determine a certain QoS flow. The QoS flow is determined for transmitting signaling or data type based on parameters of the QoS flow such as 5QI (5G QoS Indicator,5G quality of service indication), rate, bit error rate, delay, etc., and thus AC is determined. For example, qoS flows are used to transport IMS signaling, e.g. 5 qi=8, ac=9. For another example, qoS flows are used to transmit voice calls, e.g., 5qi=1, then ac=4. For another example, qoS flows are used to transmit video calls, e.g., 5qi=5, then ac=5. For another example, if the QoS flow is used to transmit an IP short message, ac=6.

Optionally, in an embodiment of the present application, the method further includes: the relay terminal receives signaling from the remote terminal.

Optionally, in the embodiment of the present application, the obtaining, by the relay terminal, an AC corresponding to a service for relaying for the remote terminal includes: the relay terminal acquires the AC from the signaling.

Optionally, in the embodiment of the present application, the obtaining, by the relay terminal, an AC corresponding to a service for relaying for the remote terminal further includes: in case the AC is not included in the signaling, a specific AC is acquired.

For example, the relay terminal may receive signaling from the remote terminal over a PC5 signaling radio bearer (signalling radio bearers, SRB). For example, the remote terminal transmits signaling to the relay terminal at the time of service generation. The signaling may include therein a corresponding AC for relaying traffic for the remote terminal. If the AC is not included in the signaling, a particular AC may be employed for subsequent access control checks. The specific AC may be a default value set at the relay terminal, which is used in case that the AC cannot be acquired from the remote terminal.

Optionally, in the embodiment of the present application, the relay terminal performs access control checking according to the AC and the unified access control UAC parameter, including: a Proximity-Services (ProSe) layer or a Non-Access Stratum (NAS) layer of the relay terminal determines a radio resource control (Radio Resource Control, RRC) establishment cause value according to the AC, and then sends the AC and the cause value to the RRC layer of the relay terminal together or respectively, or the RRC layer obtains the AC to determine an RRC establishment cause value; the RRC layer judges whether the remote terminal can access the network or not through UAC parameters corresponding to the AC in the system information.

For example, in the relay terminal, after the NAS layer determines the AC, the RRC establishment cause (establishment cause) may be determined according to the AC, and the AC and the cause (cause) may be issued to the RRC layer. The RRC layer judges whether the network can be accessed or not according to UAC parameters corresponding to the AC broadcasted in the system information. Each AC corresponds to a threshold and the RRC layer can determine a random number between 0 and 1. If the random number is smaller than the critical value, the network can be accessed; if the random number is greater than the threshold, access is denied.

Optionally, in an embodiment of the present application, the method further includes: in case of failure of the UAC, the relay terminal sends a failure notification to the remote terminal, the failure notification including a cause of the failure of the UAC and/or a timer for causing the remote terminal not to transmit the data to the relay terminal until the timer expires.

For example, if the relay terminal determines the AC using a data packet from the remote terminal, the failure notification may be sent with part or all of the content of the data packet. Of course, the failure notification may not include part or all of the content of the packet, but may include only the cause and/or timer of the UAC failure. For another example, if the relay terminal determines the AC using signaling from the remote terminal, a cause of the UAC failure and/or a timer may also be included in the failure notification when the failure notification is sent. The remote terminal may begin counting after receiving the cause and the timer, and the remote terminal may not transmit data to the relay terminal until the timer expires. The remote terminal may select other relay terminals or select direct network devices such as base stations for service.

Fig. 4 is a schematic flow chart diagram of an access control method 300 according to an embodiment of the present application. The method may alternatively be applied to the system shown in fig. 1, but is not limited thereto. The method includes at least some of the following.

And S310, the remote terminal sends an access type AC corresponding to the service for relaying the remote terminal to the relay terminal so as to perform access control check at the relay terminal according to the AC and the unified access control UAC parameter.

Optionally, in the embodiment of the present application, the remote terminal sends, to the relay terminal, an access type AC corresponding to a service for relaying for the remote terminal, including: the remote terminal transmits a data packet to the relay terminal, the header of the data packet including the AC.

Optionally, in an embodiment of the present application, the remote terminal sends an access type AC of the remote terminal to the relay terminal, including: the remote terminal sends signaling to the relay terminal, the signaling including the AC.

Specific examples of the method 300 for executing the remote terminal in this embodiment may be referred to the related descriptions of the remote terminal in the method 200, and are not repeated herein for brevity.

The access control method of the present application is described below by way of specific examples.

Example 1: an access control method under a layer three (L3 relay) architecture is shown in fig. 5.

S11, the Relay (Relay) UE receives system information broadcast by a base station (RAN) and reads UAC parameters in the system information. The UAC parameters include an AC adjustment factor (factor).

S12, the relay UE receives a data packet of a Remote (Remote) UE, such as a PC5 data packet, and the Remote UE can determine the AC by itself and then adds the AC to the data packet header, and the format is exemplified as follows:

AC	packet (data Packet)

S13, if an AC is added in the packet header, the relay UE uses the AC and determines an RRC establishment cause (establishment cause) value according to the AC.

If the AC is not in the header, the relay UE matches the received data packet with its own URSP or data descriptor (traffic descriptor) in the local configuration to determine the characteristics of the PDU session (session) to which the data should correspond. Characteristics of a PDU session may include, for example: data network names (Data Network Name, DNN), single network slice selection assistance information (Single-Network Slice Selection Assistance Information, S-NSSAI), and the like. And then determining the corresponding AC according to the characteristics of the PDU session, wherein the determination mode is exemplified as follows:

mode 1: if the PDU session is used to transmit emergency traffic, ac=2 is used.

Mode 1: ac=7 is used if it is a normal PDU session, and UAC is skipped if the relay UE is in a connected state.

Mode 3: if the PDU session is to transport IMS signaling and data, since there are 4 IMS related ACs, it is necessary to determine the different ACs by finer granularity parameters. Examples are as follows:

(1) AC, IMS signaling (ac=9), IMS voice call (ac=4), IMS video call (ac=5), IP short message (SMSoverIP) (ac=6) are determined by parameters of QoS flow of transmission data.

(2) Each AC corresponds to a service code (service code) associated with the QoS flow from which the AC is derived. The correspondence of service codes and QoS flows may be determined by a remote UE, a relay UE, or a network. The correspondence may be stored in the relay UE.

The action of this step S13 may be completed in a proximity service layer (ProSe layer) or NAS layer of the relay UE.

S14, the relay UE transmits a PC5 data packet (data) to the remote UE, wherein the PC5 data packet carries UAC failure reasons and a timer. If the UAC fails, the relay UE may notify the remote UE of the data transmission failure and notify the reason. In addition, the relay UE may also send a Timer (Timer) to the remote UE, and the remote UE may not transmit the corresponding data until the Timer expires. In this case, the remote UE may select other relay UEs or select a direct base station for service.

In this example, the relay UE may perform UAC for traffic of a different remote UE.

Example 2: an access control method under a layer two (L2 relay) architecture is shown in fig. 6.

S21, the relay UE receives system information broadcast by the base station and reads UAC parameters in the system information.

S22, the RRC information of the remote UE can be transmitted to the relay UE by using the PC5 SRB, and the relay UE is transmitted to the RAN. The PC5 SRB may include an AC and RRC message, and may further include an RRC establishment cause value. Therefore, regardless of whether the remote UE enters the connected state in the connected state or the idle state, UAC is performed according to the relevant protocol and the RRC establishment cause value is determined. The remote UE sends the determined AC (optional) and RRC establishment cause values to the relay UE.

S23, if the relay UE receives the AC, UAC can be carried out according to the AC, and the RRC establishment cause value of the relay UE can be determined. For example, using the AC of the remote UE to determine the AC and RRC establishment cause; or directly takes the RRC establishment cause of the remote UE as the self.

If the Relay UE does not receive AC, specific AC and specific RRC establishment cause values for Relay traffic are used, or MO signaling (mo_signaling), MO data (mo_data) (determined by receiving packets from PC5 SRB or PC5 DRB) are used.

The action of S23 may not be perceived by the NAS layer of the relay UE. For example: the AC and/or RRC establishment cause of the remote terminal is sent to the PDCP (Packet Data Convergence Protocol) layer or the adaptation layer of the relay UE through the PC5 SRB and then directly transferred to the RRC layer of the relay UE without passing through the NAS layer of the relay UE.

And S24, the relay UE transmits PC5 signaling (signaling) to the remote UE, wherein the signaling carries UAC failure reasons and a timer. If UAC fails, the relay UE informs the remote UE of the data transmission failure and informs the reason, and meanwhile, a timer can be sent to the remote UE, and the remote UE does not transmit corresponding data before the timer expires. At this time, the remote UE may select other relay UEs or select a direct-connected base station for service.

The access control method of the embodiment of the application can be applied to all relay services using the PC5 (in Device-to-Device (D2D) communication) to transmit data.

Fig. 7 is a schematic block diagram of a terminal 400 according to an embodiment of the present application. The terminal 400 may include:

an obtaining module 410, configured to obtain an access type AC corresponding to a service relayed for a remote terminal;

And a checking module 420, configured to perform access control checking according to the AC and the unified access control UAC parameter.

Optionally, in an embodiment of the present application, as shown in fig. 8, the terminal further includes:

the first receiving module 430 is configured to receive a system message, where the system message includes the UAC parameter.

Optionally, in the embodiment of the present application, the checking module is further configured to obtain a UAC parameter corresponding to the AC, and perform access control checking according to the UAC parameter corresponding to the AC.

Optionally, in an embodiment of the present application, the terminal further includes:

a second receiving module 440 for receiving data packets from the remote terminal.

Optionally, in an embodiment of the present application, the obtaining module 410 includes:

the parsing sub-module 411 is configured to parse the header of the data packet to obtain the AC.

Optionally, in an embodiment of the present application, the obtaining module includes:

a matching sub-module 412, configured to match the data packet by using a data descriptor in the self user equipment routing policy urs to obtain a characteristic of a packet data unit PDU session of the data packet;

a determining submodule 413 for determining the AC according to the characteristics of the PDU session.

Optionally, in an embodiment of the present application, the determining submodule is configured to determine the AC according to a characteristic of the PDU session, including at least one of:

In case the characteristics of the PDU session correspond to an emergency service, the AC is a first identification for identifying the emergency service;

in the case that the characteristic of the PDU session corresponds to a normal PDU session, the AC is a second identifier for identifying the normal session;

in case the characteristics of the PDU session correspond to internet protocol, IP, multimedia subsystem, IMS, signalling and/or data, determining the AC according to parameters of a quality of service, qoS, flow of the transmitted data;

in case the PDU session is used for transmitting IMS signaling and/or data, the AC is determined from the service coding of the QoS flow of the transmitted data.

Optionally, in an embodiment of the present application, the determining submodule is configured to determine the AC according to parameters of a QoS flow of the transmitted data, including at least one of:

a third receiving module 450 for receiving signaling from the remote terminal.

Optionally, in an embodiment of the present application, the obtaining module 410 further includes:

a first acquisition sub-module 414 for acquiring the AC from the signaling.

Optionally, in an embodiment of the present application, the obtaining module further includes:

a second acquisition sub-module 415 is configured to acquire a specific AC if the AC is not included in the signaling.

Optionally, in the embodiment of the present application, the checking module is further configured to send the AC and the cause value to the RRC layer together or separately after the proximity service ProSe layer or the NAS layer determines the cause value for radio resource control RRC establishment according to the AC; and judging whether the remote terminal can access the network or not by the UAC parameters corresponding to the AC in the system information in the RRC layer.

a notification module 460, configured to send a failure notification to the remote terminal in case the UAC fails, where the failure notification includes a cause of the UAC failure and/or a timer, where the timer is configured to make the remote terminal not transmit the data to the relay terminal until the timer expires.

The terminal 400 of the embodiment of the present application can implement the corresponding function of the relay terminal in the foregoing method embodiment. The flow, function, implementation and beneficial effects corresponding to each module (sub-module, unit or assembly, etc.) in the terminal 400 can be referred to the corresponding description in the above method embodiments, and will not be repeated here.

It should be noted that, the functions described in the respective modules (sub-modules, units, or components, etc.) in the terminal 400 of the application embodiment may be implemented by different modules (sub-modules, units, or components, etc.), or may be implemented by the same module (sub-module, unit, component, etc.).

Fig. 9 is a schematic block diagram of a terminal 500 according to another embodiment of the present application. The terminal 500 may include:

and the sending module 510 is configured to send, to the relay terminal, an access type AC corresponding to a service for relaying for the remote terminal, so as to perform access control check at the relay terminal according to the AC and the unified access control UAC parameter.

Optionally, in an embodiment of the present application, the sending module is further configured to send a data packet to the relay terminal, where a header of the data packet includes the AC.

Optionally, in an embodiment of the present application, the sending module is further configured to send signaling to the relay terminal, where the signaling includes the AC.

The terminal 500 of the embodiment of the present application can implement the corresponding function of the remote terminal in the foregoing method embodiment. The flow, function, implementation and beneficial effects corresponding to each module (sub-module, unit or assembly, etc.) in the terminal 500 can be referred to the corresponding description in the above method embodiments, and will not be repeated here.

It should be noted that, the functions described in the respective modules (sub-modules, units, or components, etc.) in the terminal 500 of the application embodiment may be implemented by different modules (sub-modules, units, or components, etc.), or may be implemented by the same module (sub-module, unit, component, etc.).

Fig. 10 is a schematic structural diagram of a communication device 600 according to an embodiment of the present application. The communication device 600 comprises a processor 610, which processor 610 may call and run a computer program from a memory to cause the communication device 600 to implement the methods in embodiments of the present application.

Optionally, as shown in fig. 10, the communication device 600 may further comprise a memory 620. Wherein the processor 610 may invoke and run a computer program from the memory 620 to cause the communication device 600 to implement the method in the embodiments of the present application.

The memory 620 may be a separate device from the processor 610 or may be integrated into the processor 610.

Optionally, as shown in fig. 10, the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, and in particular, may send information or data to other devices, or receive information or data sent by other devices.

The transceiver 630 may include a transmitter and a receiver, among others. Transceiver 630 may further include antennas, the number of which may be one or more.

Alternatively, the communication device 600 may be a relay terminal or a remote terminal in the embodiments of the present application, and the communication device 600 may implement corresponding processes implemented by the relay terminal or the remote terminal in the methods in the embodiments of the present application, which are not described herein for brevity.

Fig. 11 is a schematic structural diagram of a chip 700 according to an embodiment of the present application. The chip 700 includes a processor 710, and the processor 710 may call and run a computer program from a memory to implement the methods of the embodiments of the present application.

Optionally, as shown in fig. 11, chip 700 may also include memory 720. The processor 710 may invoke and run a computer program from the memory 720 to implement the method performed by the relay terminal or the remote terminal in the embodiments of the present application.

Wherein the memory 720 may be a separate device from the processor 710 or may be integrated into the processor 710.

Optionally, the chip 700 may also include an input interface 730. The processor 710 may control the input interface 730 to communicate with other devices or chips, and in particular, may obtain information or data sent by other devices or chips.

Optionally, the chip 700 may further include an output interface 740. The processor 710 may control the output interface 740 to communicate with other devices or chips, and in particular, may output information or data to other devices or chips.

Optionally, the chip may be applied to a relay terminal or a remote terminal in the embodiments of the present application, and the chip may implement a corresponding flow implemented by the relay terminal or the remote terminal in each method in the embodiments of the present application, which is not described herein for brevity.

The chips applied to the relay terminal or the remote terminal may be the same chip or different chips.

It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, or the like.

The processors mentioned above may be general purpose processors, digital signal processors (digital signal processor, DSP), off-the-shelf programmable gate arrays (field programmable gate array, FPGA), application specific integrated circuits (application specific integrated circuit, ASIC) or other programmable logic devices, transistor logic devices, discrete hardware components, etc. The general-purpose processor mentioned above may be a microprocessor or any conventional processor.

The memory mentioned above may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. The volatile memory may be random access memory (random access memory, RAM).

It should be understood that the above memory is exemplary but not limiting, and for example, the memory in the embodiments of the present application may be Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), direct RAM (DR RAM), and the like. That is, the memory in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

Fig. 12 is a schematic block diagram of a communication system 800 according to an embodiment of the present application. The communication system 800 includes a relay terminal 810 or a remote terminal 820.

A relay terminal 810 for acquiring an AC corresponding to a service for relaying to the remote terminal 820; and performing access control checking according to the AC and UAC parameters.

A remote terminal 820 for transmitting an AC corresponding to a service for relaying the remote terminal to the relay terminal 810.

Wherein the relay terminal 810 may be used to implement the corresponding functions implemented by the relay terminal in the above-described method, and the remote terminal 820 may be used to implement the corresponding functions implemented by the remote terminal in the above-described method. For brevity, the description is omitted here.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present application, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line (Digital Subscriber Line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). 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, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., a floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid State Disk (SSD)), or the like.

It should be understood that, in various embodiments of the present application, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic thereof, and should not constitute any limitation on the implementation process of the embodiments of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

The foregoing is merely a specific embodiment of the present application, but the protection scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions should be covered in the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

An access control method, comprising:

the relay terminal acquires an access type AC corresponding to a service for relaying for the remote terminal;

and the relay terminal performs access control checking according to the AC and the unified access control UAC parameters.
The method of claim 1, wherein the method further comprises:

And the relay terminal receives a system message, wherein the system message comprises the UAC parameter.
The method according to claim 1 or 2, wherein the relay terminal performs an access control check according to the AC and unified access control UAC parameters, comprising:

and the relay terminal acquires the UAC parameters corresponding to the AC and performs access control check according to the UAC parameters corresponding to the AC.
A method according to any one of claims 1 to 3, wherein the method further comprises:

the relay terminal receives a data packet from the remote terminal.
The method of claim 4, wherein the relay terminal acquiring the AC corresponding to the service for relaying to the remote terminal comprises:

and the relay terminal analyzes the packet header of the data packet to obtain the AC.
The method of claim 4, wherein the relay terminal acquiring the AC corresponding to the service for relaying to the remote terminal comprises:

the relay terminal matches the data packet by utilizing a data descriptor in a user equipment routing strategy URSP of the relay terminal to obtain the characteristic of a packet data unit PDU session of the data packet;

and the relay terminal determines the AC according to the characteristics of the PDU session.
The method of claim 6, wherein the relay terminal determining the AC according to characteristics of the PDU session comprises at least one of:

in the case that the characteristics of the PDU session correspond to an emergency service, the AC is a first identifier for identifying the emergency service;

in the case that the characteristic of the PDU session corresponds to a common PDU session, the AC is a second identifier for identifying the common session;

determining the AC according to parameters of a quality of service QoS flow of the transmitted data under the condition that the characteristics of the PDU session correspond to the IMS signaling and/or the data of the IP multimedia subsystem;

in case the PDU session is used for transmitting IMS signaling and/or data, the AC is determined from the service coding of the QoS flow of the transmitted data.
The method of claim 7, wherein determining the AC according to parameters of QoS flows of the transmitted data comprises at least one of:

according to the parameters of the QoS flow of the transmitted data, determining that the AC is a third identifier for identifying IMS signaling when the QoS flow is used for transmitting IMS signaling;

according to the parameters of the QoS flow of the transmitted data, determining that the AC is a fourth identifier for identifying the voice call under the condition that the QoS flow is used for transmitting the IMS voice call;

According to the parameters of the QoS flow of the transmitted data, determining that the AC is a fifth identifier for identifying the video call under the condition that the QoS flow is used for transmitting the IMS video call;

and determining that the AC is a sixth identifier for identifying the IP short message under the condition that the QoS flow is used for transmitting the IP short message according to the parameters of the QoS flow of the transmitted data.
A method according to any one of claims 1 to 3, wherein the method further comprises:

the relay terminal receives signaling from a remote terminal.
The method of claim 9, wherein the relay terminal obtaining the AC corresponding to the service for relaying to the remote terminal comprises:

the relay terminal acquires the AC from the signaling.
The method of claim 9, wherein the relay terminal acquiring the AC for relaying traffic for the remote terminal further comprises:

and acquiring a specific AC in the case that the AC is not included in the signaling.
The method according to any one of claims 1 to 11, wherein the relay terminal performs an access control check according to the AC and unified access control, UAC, parameters, comprising:

the adjacent service ProSe layer or non-access stratum NAS layer of the relay terminal determines a Radio Resource Control (RRC) establishment cause value according to the AC, and then sends the AC and the cause value to the RRC layer of the relay terminal together or respectively;

And the RRC layer judges whether the remote terminal can access the network or not through UAC parameters corresponding to the AC in the system information.
The method of any one of claims 1 to 12, wherein the method further comprises:

and in case of the UAC failure, the relay terminal sends a failure notification to the remote terminal, wherein the failure notification comprises a reason and/or a timer of the UAC failure, and the timer is used for enabling the remote terminal not to transmit the data to the relay terminal until the timer is finished.
An access control method, comprising:

and the remote terminal sends an access type AC corresponding to the service for relaying the remote terminal to the relay terminal so as to perform access control check at the relay terminal according to the AC and the unified access control UAC parameter.
The method of claim 14, wherein the remote terminal transmitting to the relay terminal an access type AC corresponding to the traffic for relaying the remote terminal, comprises:

and the remote terminal sends a data packet to the relay terminal, and the packet head of the data packet comprises the AC.
The method of claim 14, wherein the remote terminal transmitting the access type AC of the remote terminal to a relay terminal comprises:

The remote terminal sends signaling to the relay terminal, the signaling including the AC.
A terminal, comprising:

the acquisition module is used for acquiring an access type AC corresponding to the service relayed by the remote terminal;

and the checking module is used for performing access control checking according to the AC and the unified access control UAC parameters.
The terminal of claim 17, wherein the terminal further comprises:

and the first receiving module is used for receiving a system message, and the system message comprises the UAC parameters.
The terminal according to claim 17 or 18, wherein the checking module is further configured to obtain a UAC parameter corresponding to the AC, and perform an access control check according to the UAC parameter corresponding to the AC.
The terminal according to any of claims 17 to 19, wherein the terminal further comprises:

and the second receiving module is used for receiving the data packet from the remote terminal.
The terminal of claim 20, wherein the acquisition module comprises:

and the analysis submodule is used for analyzing the packet head of the data packet and acquiring the AC.
The terminal of claim 20, wherein the acquisition module comprises:

a matching sub-module, configured to match the data packet by using a data descriptor in a self user equipment routing policy urs, so as to obtain a characteristic of a packet data unit PDU session of the data packet;

A determining submodule, configured to determine the AC according to a characteristic of the PDU session.
The terminal of claim 22, wherein the determining submodule is configured to determine the AC based on characteristics of the PDU session, including at least one of:

in the case that the characteristics of the PDU session correspond to an emergency service, the AC is a first identifier for identifying the emergency service;

in the case that the characteristic of the PDU session corresponds to a common PDU session, the AC is a second identifier for identifying the common session;

determining the AC according to parameters of a quality of service QoS flow of the transmitted data under the condition that the characteristics of the PDU session correspond to the IMS signaling and/or the data of the IP multimedia subsystem;

in case the PDU session is used for transmitting IMS signaling and/or data, the AC is determined from the service coding of the QoS flow of the transmitted data.
The terminal of claim 23, wherein the determining submodule is configured to determine the AC according to parameters of QoS flows of the transmitted data, including at least one of:

according to the parameters of the QoS flow of the transmitted data, determining that the AC is a third identifier for identifying IMS signaling when the QoS flow is used for transmitting IMS signaling;

According to the parameters of the QoS flow of the transmitted data, determining that the AC is a fourth identifier for identifying the voice call under the condition that the QoS flow is used for transmitting the IMS voice call;

according to the parameters of the QoS flow of the transmitted data, determining that the AC is a fifth identifier for identifying the video call under the condition that the QoS flow is used for transmitting the IMS video call;

and determining that the AC is a sixth identifier for identifying the IP short message under the condition that the QoS flow is used for transmitting the IP short message according to the parameters of the QoS flow of the transmitted data.
The terminal according to any of claims 17 to 19, wherein the terminal further comprises:

and the third receiving module is used for receiving the signaling from the remote terminal.
The terminal of claim 25, wherein the acquisition module further comprises:

and the first acquisition submodule is used for acquiring the AC from the signaling.
The terminal of claim 25, wherein the acquisition module further comprises:

and the second acquisition sub-module is used for acquiring the specific AC under the condition that the AC is not included in the signaling.
The terminal of any of claims 17 to 27, wherein the checking module is further configured to send the AC and the cause value together or separately to an RRC layer after determining a radio resource control, RRC, establishment cause value from the AC by a serving ProSe layer or a NAS layer; and judging whether the remote terminal can access the network or not through the UAC parameters corresponding to the AC in the system information in the RRC layer.
The terminal according to any of claims 17 to 28, wherein the terminal further comprises:

and the notification module is used for sending a failure notification to the remote terminal under the condition that the UAC fails, wherein the failure notification comprises a reason and/or a timer of the UAC failure, and the timer is used for enabling the remote terminal not to transmit the data to the relay terminal until the timer is ended.
A terminal, comprising:

and the sending module is used for sending an access type AC corresponding to the service for relaying the remote terminal to the relay terminal so as to perform access control check on the relay terminal according to the AC and the unified access control UAC parameter.
The terminal of claim 30, wherein the transmitting module is further configured to transmit a data packet to the relay terminal, and a header of the data packet includes the AC.
The terminal of claim 30, wherein the transmitting module is further configured to transmit signaling to the relay terminal, the signaling including the AC.
A terminal, comprising: a processor and a memory for storing a computer program, the processor being adapted to invoke and run the computer program stored in the memory to cause the terminal to perform the method according to any of claims 1 to 13.
A terminal, comprising: a processor and a memory for storing a computer program, the processor being adapted to invoke and run the computer program stored in the memory to cause the terminal to perform the method of any of claims 14 to 16.
A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any one of claims 1 to 13.
A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any of claims 14 to 16.
A computer readable storage medium storing a computer program which, when executed by a device, causes the device to perform the method of any one of claims 14 to 16.
A computer readable storage medium storing a computer program which, when executed by a device, causes the device to perform the method of any one of claims 14 to 16.
A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 13.
A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 14 to 16.
A computer program which causes a computer to perform the method of any one of claims 1 to 13.
A computer program which causes a computer to perform the method of any of claims 14 to 16.